Hi Kevingalvez12, Our team made a documentation of PI control simulation using Autotune function block. Unfortunately, it's not in English. From there, we've also successfully applied autotuning of PI control a few times in projects. However, we don't have comparison with other brand PLC, so I can't tell how great it is, but I can say it's useful. Let me share some key Autotuning parts of the simulation. Below is how the FBD looks like: The key here are the PARA input in both AUTOTUNE and PI_B blocks. In Autotune PARA, there are 3 variables: step_ampl, tmax, and perf. For step_ampl and tmax values in actual application, you can refer to below table (also can be found in the Help): In order to set this values, you will need to create a DDT variable with Type: Para_AUTOTUNE. In this example, the variable name is "para_autotune" Autotune PARA_C output is linked to PI_B PARA input. The variable is also a DDT: Para_PI_B. Or if you're using PIDFF block, the type is Para_PIDFF. The variable name in this example is "temp_parameters". Except Kp, Ti, (Td and Kd), other parameters must be manually set. Leave it blank for Kp, Ti, (Td and Kd). And here is the simulation result: note: Autotune was started few seconds after setpoint was set. Hope this helps. Cheers, Pradipta
... View more
Some modbus devices use 1-based addressing, others use 0-based addressing. When master and slave have different address base, the "shift" occurs. The fastest way to identify this issue is indeed by trial and error, since not all manufacturer state this in the modbus device manual.
... View more