(2)| 3/2/2022 8:50 AM | |
|
Joined: 8/1/2019 Last visit: 12/8/2025 Posts: 304 Rating:
|
thanks, but it doesnt solve the example problem that i mentioned in the question |
| 3/3/2022 12:04 AM | |
|
Joined: 3/14/2008 Last visit: 1/15/2026 Posts: 2233 Rating:
|
Hi, Indeed, the procedure described is just a validity check for the recipe, which is also executed when you want to release the recipe for production. It checks the setpoint limits, which are hardcoded in the SFC, it does not say anything about the actual quantity to be dosed in the tank. In my opinion, the amount to be transferred is a business rule which must be taken into account before the batch is started. Some years ago there was a software addon called APF which let's you create business rules and validation of transfer volumes to and from tanks using special blocks. If done correctly a job could be created which could create a batch in batchCC automatically. This was very neat, but APF is not getting updated anymore and had some flaws as well (was only valid for small PCS7 projects) What we do now is using the new IL block called BatchIf (Industry Library V9.0 SP1). It allows you to create, release and start a batch with predefined recipe name, version, material quantity's, material names and parameters that can be configured in the CFC. If all data is filled in, you create a trigger and the BatchIf will create the batch (if all parameters are valid ofcourse). You can use CFC to check the desired quantity if it fits, if so, you trigger the BatchIf to create a batch in batchCC. Very neat. Another way is to do a setpoint check in a batch transition using a tagcollect block to send actual and desired quantity to batch where you can use it inside the control recipe. However, the batch is then already started and you need to abort it or something if the quantity does not fit. So better is to do this before the batch is started. |
|
If I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to
|
|
Follow us on