Hello, my question is about WpcSeparation object, how to use it and understand it properly with different use cases. With a simple stopper usage it is clear if all of the timing, positioning and so on fits perfectly, but If I have some issues I have always problems to understand what is the purpose of some parameters and how is the behaviour under it. I have tried to simulate different behaviours with digital machine aswell with some trials but result is not so clear for me. 1) Assuming we have a simple stopper and just one sAt input to check wpc with a light sensor, which takes time have the falling edge of the sAt input. In this case we get an error that the input should be false after separation. Is there a way to provide a functionality that it waits some amount of time ( user defined ) before closing the seperator again and give an error? I thought OpenOnSAt parameter is being used for such purpose, but for me it only changed to behaviour to no error, but in this case seperator just closes immidiately which causes the wpc to jump before it leaves the mechanics. 2) In this case, there is a second question, what does OpenOnSAt parameter exactly ? 3) Is there an example use case of UserDataAt,UserDataOn, NextUserData, or are they just some additional data working exactly like WpcDataAt and reason to have it to just separate standard WPCData definition with some required data additionaly ? 4) Is there a difference between using the object with WPC_SEPARATION_MODE and WPC_STOPPER_MODEwith sOn activated ? Because what I can notice is only with WPC_SEPARATION_MODE forces me to use SOn and if I activate sOn for WPC_STOPPER_MODE it does the same job. 5) Inside the documentation for WPC_STOPPER_MODE it says that the object works with negative signal from PSAt, does it mean falling edge of the pSAt ? If it is for me it looks like object doesnt care about the falling edge of the pSAt, it just closes after some time even the pSAt is still there. Thank you in advance for the support
... View more
