Node PID enable/disable not working

[Frank2]

Hi,

I am not getting the PID in disable mode. Am I doing something wrong?

[{"id":"6deef0a.ca0fa1","type":"function","z":"d71f1b7b.004ad8","name":"","func":"msg = {payload:1}\nmsg.enable = 1;\nmsg.topic = \"enable\"\n\nreturn msg;","outputs":1,"noerr":0,"x":314,"y":182,"wires":[["37d2fe8f.ccfba2"]]}]

Frank

[Colin]

Which pid node are you using? node-red-xxxxx-xxxxx

[Frank2]

Hi Colin,

I am using this one:

node-red-contrib-pid

node-red-contrib-pid

Frank

[Colin]

@Frank2

node-red-contrib-pid

That function node should work, and does work for me. I notice though that the status display does not change until the next time it receives a process sample, so if you are not also sending it data then you won't know that it has worked. Feed an inject node direct into the pid node to give it something to do and your function node should work. If not then post a mini-flow with injects and the function and pid node exhibiting the problem.

[Frank2]

Ah Colin,

You are right again. Disable is displayed when other feed is going in.

Thanks.
Frank

[Frank2]

My reflow oven stayed on this afternoon burning my PCB so thought the PID was the issue. I didn't set all variables to default when off. Grrr. But the graph looks great now.

[Colin]

I have submitted an issue against the node, next time I am doing anything to it I will sort it. https://github.com/colinl/node-red-contrib-pid/issues/8

[Frank2]

Thanks highly appreciated. It helps hobby programmers like me to visualize their mistakes. I can see nothing is turning on my oven because some nodes putting out data after presumed stopped. Buffering or temp updates messing with my output