Wrong Sequence trig behaviour


Still working on my project , I solve some of the issue but still some sequence trig not expected. Even on the boot trig I find some of the last patch to been trig true.
I have corrected the case where there was input without data to transfer in “if-else” node, or in “any” node type.
I have also added a defer node between boot and "first “any” node.



Does someone have any idea why some patch from my systeme trig prematurely on boot??

All patches will trigger during initialization. Most should return without doing anything if nothing needs done, but if a node executes code without first checking for changes of input values, that will execute on boot.

So any idea on how i can avoid these trig, i have tried adding defer node and it does not seem to work.
It is not acceptable that some pump start randomly.

They won’t start “randomly”…only when relay is turned on. If you are talking about SV4_KB, it is always turned on, but you don’t always allow state to change, so it will never turn off. You probably want the input tied to ON rather than ACT. If there is a particular relay node that always initializes to wrong value at boot, then stabilizes after initialization, you could disable it by adding a delay node with delay-ACT tied to a ‘not’ node, then to relay-ACT so that the relay will not update until delay timer has expired.

There are a lot of places where you add if-else nodes that just return true/false or 1/0. There is no reason to do this since input fed to if-else-COND is already true/false, which is interpreted as 1/0 for numeric inputs. If you want to reverse the value (if-else-T = False), then use ‘not’ node rather than an if-else node. This will be more efficient and make your code easier to read.

You don’t provide all your code, so it is difficult to determine what else might be wrong since we can’t determine what all the inputs to each patch will be during initialization. This is complex enough, it would be better to attach a xodball of your project rather than images of each patch. It would also make it easier to debug if we knew exactly which parts are not doing what you expect; what do you expect & what is it doing?

Thank you for yopur comments. I would like to provide to you the code but i don’t know how to proceed.
Sorry but I don’t understand what you mean by " attach a xodball".


There are two formats for saving your projects. The default is a .xodball file that is stored in your workspace. You can find your workspace by going into XOD and selecting File > Switch Workspace. Attach your project file to your post to share it here.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.