We are moving! We are currently migrating our community to the new Bosch Connected Industry Online Portal. The community will be available latest in the new year again, until then it will be in read-only mode. Click here for more information.
09-12-2022 02:57 PM
Good evening,
I don't understand very well the difference between variuos WpcSeparationMode.
First of all, I don't know the difference between STOPPER and SEPARATOR. Then I'm able to fully understand the documentation (WpcSeparationMode ENUM).
The documentation speaks about "queries" of the sensors, but I don't really understand how the query the sensors.
This is a stupid question, so forgive me for that, but I'd like to ask it: Is there a way to let the separator work automatically, without having to implement a CommandHandler to issue the SEPARATE Command?
Solved! Go to Solution.
09-13-2022 02:00 PM
Hallo,
this is not a stupid question. We also had the same problem with the WpcSeparation. And had a workshop together with the BCI. The BCI is working on that topic. Hopfully they will release the new version, soon. At that the WpcSeparationMode will be not available, because the function was not clear.
09-13-2022 02:09 PM
thank you for the feedback.
I hope to have news soon!
10-19-2022 10:43 AM
First of all sorry for the late reply!
About the difference between stopper and separator: There is a mechanical difference between the two. A separator consists of two pins working together like a rocker. That way the timing is less relevant and it is always guaranteed exactly one carrier passes the separator when moving it back and forth once. A stopper is just one pin that allows any number of carriers to pass through while it is open.
About the documentation: Thanks for the hint. We will fix this translation error in a future version. "Query" should just be carrier detection (by the SAt/SOn sensor).
There is no way to let this object automatically handle the separation without starting any command. But there is an alternative approach: The objects belonging to the transfer system (i.e. the NexeedTrs... objects) are designed for automatic wpc handling based on standardized transfer node types.
Now about PKlein's answer: I am sorry I have to disappoint you, but there are no activities going on concerning this object. A colleague does remember there were some discussions about the object, but there has never been a commitment to start any development. This must be a misunderstanding. If you have any specific requirements, please contact the helpdesk.
10-19-2022 12:03 PM
Thank you for your answer.
I have understood that I have to actively issue a SEPARATE command.
For that reason I have implemented the station in this way: I used a SpecialTransferNode as a command handler (SepHandler4 in the picture below) under the TransferGroupMaster and I put the Separaters under it.
Then, I used the SqC_Run chain of the special node to implement the code for the separators.