Jump to content

Recommended Posts

Posted

Got issues with a combiner. i have a server that processes the member parts but has a 0.1 probability of going to scrap, this means the batch size has changed.

the parent part has a integer state that gets updated when this happens but doesn't update the combiner batch quantity property.

I have attached an image showing this issue. you can see the pallet number displayed which is the way i match the parts with the correct pallet. the pallet(parent) also displays the batch size using the same integer state which i use in the combiner logic. Theres a pallet with 4 items on it and it shows the batch is 4 so why wont that process it?

Also attached the whole model so you can look at it all

 

simio.png

Batch and Scrap.spfx

Posted

I used to have a similar problem. My advice, avoid the pallet entering the combiner untill you have defined de @new@ batch size, elseway the batchsize wont be updated.

In my case I put a scan step in a prevoious node, retaining the pallet ouside the combiner until I've re-defined the batchsize.

Let me know if that works

Rds

 

  • 2 weeks later...
Posted
On 12/24/2022 at 9:06 PM, ShawnNevers said:

You could also use the Release Batch Early Triggers to recheck the condition after an event.

 

image.thumb.png.91c624d0429d0a60f49301bbda658290.png

Hi there, tried this as well. i get this error: image.png.f8ee5dcd122295cd7ad7a4ceb6a912f6.png

please advise.

×
×
  • Create New...