![gx works 2 local bit status gx works 2 local bit status](https://i.ytimg.com/vi/ITI8z2VoU4g/maxresdefault.jpg)
Quote : So I'm using the Mitsubishi Q series, with gx works 2 and ladder logic. The Arduino PID is a valve positioner, which minimizes the error between the measured motor (valve) position feedback (PV) and the motor (valve) position setpoint, by changing its CV that is sent to the motor/servo/motor-positioning-system. minimizes the difference (error), between the measured flow feedback and the flow setpoint, by sending a motor (valve) position setpoint to the Arduino, and Which element compares the motor (valve) position feedback to the motor (valve) position setpoint?Īll of those assumptions are to suggest that Which element compares the flow feedback to the flow setpoint? I would assume it is the desired motor (valve) position. What is the nature of the setpoint value provided to the Arduino by the PLC? I would assume it is the desired flow rate.
![gx works 2 local bit status gx works 2 local bit status](https://s.yimg.com/uu/api/res/1.2/8UHxC4nR.tlMs4JsAeigHw--~B/aD05Njc7dz0xNzE4O2FwcGlkPXl0YWNoeW9u/https://www.blogcdn.com/slideshows/images/slides/381/828/2/S3818282/slug/l/embargoed-until-march-2-meta-virtual-workspace-1-car-design-1.jpg)
What is the nature of the setpoint value provided to the PLC by the HMI? 0% is valve closed, 100% is valve fully opened). I would assume it is somehow controlling the motor position and/or valve position (e.g. What does the CV output of the Arduino's PID control? drbitboy, DMD (added that signature for )) If all or most of those assumptions are correct, and my simulation/PLC/Arduino/PID confusion can be resolved, then the PLC is acting as a kind of deadband front-end to the PID. If the converted feedback value is not within 5% of the HMI-provided setpoint value, send the HMI-provided setpoint value to the Arduino I assume that was a typo and the 5% is tolerance, but please correct that assumption if needed perhaps you "within 5% of range of the setpoint" i.e. You actually wrote "within 5% of the setpoint tolerance" If the converted feedback value is within 5% of the HMI-provided setpoint value, do nothing The PLC compares the converted feedback value to the HMI-provided setpoint value I suppose there could also be other processing e.g. I assume to the same offset and units as the HMI-provided setpoint value. Which begs the question, how does the PV get to the PID on the Arduino? So perhaps the "feedback" value is actually the PID's CV, i.e. The Arduino implements a PID, and where the process is I am not sureĪlthough it sounds like something is being simulated on the PLC I assume the Arduino calculates the value based on the most recent setpoint previously sent to the Arduino I assume the value is read from the Arduino The HMI provides a setpoint value, between 0 and 144, to the PLC from HMI Please allow me to restate that back to you, slightly re-ordered, how I hear it: I am open to suggestions for additional features to make the process more robust, such as the use of a light beacon. If the feedback is within +/-5 percent of the setpoint tolerance, the motor remains in the same position otherwise, the PLC resends the setpoint to the Arduino to adjust the motor as needed.
![gx works 2 local bit status gx works 2 local bit status](https://m.media-amazon.com/images/I/61FDlIwLLpL._AC_US800_.jpg)
The set point will be provided by the HMI between 0 and 144, and the PLC will convert the feedback and compare it to the setpoint. For the HMI interface, the project will be simulated on the PLC using GT designer. I'm using Arduino to gain hands-on experience with how the PLC interacts with the Arduino. So I'm using the Mitsubishi Q series, with gx works 2 and ladder logic.