3/30/2016 9:06 AM | |
Joined: 10/7/2005 Last visit: 4/26/2024 Posts: 3004 Rating: (1046)
|
Hello Jengeese I fear your problem lies in the fact that N and M will always be on once a Setpoint (SP) change took place. Example:
I fear your current logic work more on luck than anything else and with the "decoupling" help of the 150ms GET communication cycles (and should possibly play up both ways every so often). Suggest you'll implement a handshaking mechanism to make it more robust. |
Cheers |
|
3/30/2016 4:01 PM | |
Posts: 84 Rating: (0) |
Dear Fritz, Thanks for the suggestion. But, can you please help me a bit more with a similar logic or anything else? |
3/31/2016 1:37 AM | |
Joined: 10/7/2005 Last visit: 4/26/2024 Posts: 3004 Rating: (1046)
|
Ok, let's try a rather simple solution first as per attached that won't even require additional handshaking mechanism. It's a quick and dirty idea and not tested, so please give it a run and let us know the outcome. |
Cheers |
|
This contribution was helpful to1 thankful Users |
Follow us on