How to understand WpcSeparation object and its parameters properly?

[boezcan]

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

[SteffenR-]

You will get an answer next week from our application team.

Meanwhile of course everybody else can share his/her experience 😀

[SebBeetz]

Hello and sorry for my late response! 😔

...somehow the entry disappeared from my personal schedule 2 weeks ago so once more I apologize for any inconvenience!

Before I answer your questions please note that we are currently evaluating the latest version V1.2.18 and working on a revised new version V2.0, which we plan to release by the end of the year. So if you or anyone else from the forum has any hints for us to make NexeedWpcSeperation V2.0 better, or would like to share bad experiences with the current object versions, we'd love for you to post it here in the forum!

So now to your questions:

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.

To get your desired behaviour you need to increase the CloseDelay in the common parameters. The description of this parameter in ControlPlusStudio =>"Closing delay in LEADFRAME_MODE" is misleading here because this delay is used seperation mode regardless. The stopper cylinder will be closed
after the time in CloseDelay so you can "play" with that time until the workpiece carrier runs throw smoothly without "jumps".

2) In this case, there is a second question, what does OpenOnSAt parameter exactly?

Unfortunately this parameter is useless in object versions <=V1.2.x and will be eliminated in V2.0.

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?

Yes, you're right! The only reason is to separate WpcData from other application specific data. We are currently thinking about kicking out UserData in V2.0 and provide only one parameter for any data to switch during seperation.

4) Is there a difference between using the object with WPC_SEPARATION_MODE and WPC_STOPPER_MODE with 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.

Yes, that's also right! WPC_STOPPER_MODE with connected SOn parameter behaves the same way like WPC_SEPARATION_MODE.
Therefore, there will be no parameter "SeperationMode" in future versions because we think it is more misleading for application engineers than helpful!

5) Inside the documentation for WPC_STOPPER_MODE it says that the object works with negative signal from SAt, does it mean falling edge of the SAt ? If it is for me it looks like object doesnt care about the falling edge of the SAt, it just closes after some time even the SAt is still there.

Yes if SOn is not connected the object "is working with the negative signal of SAt", means the stopper will close at falling edge of SAt
EXCEPT the time in CloseDelay is running up earlier. Otherwise the behaviour your question 1 was aiming for (stopper should close although SAt is still =TRUE) will not work.

Please check your time configured in CloseDelay and select a time that is longer than the workpiece carrier needs to leave the stopper, means the time from "open the stopper" to "SAt=FALSE". Maybe the documentation is not yet detailed enough at this point.

Best regards,
Sebastian