@Sam Stubbs @Matthew Gillespie @Logan Gold
So here is what is going on:
I have a main source feeding a main line and then several processors triggering an inside line once an object passes through it that will eventually combine at the three combiners... This a very reduced sample model that if I can get it to work here I should be able to put my model together. I want to put this together in model:jbexamplemodel
The problems that I am having:
Problem 1: My source 1,2,3 are triggering every time an object comes through, (as it should if there weren't rejects involved), but with rejects my sub lines are overproducing. ( I am looking for the processor to know if it needs to trigger sources 1,2,3 based on which reject queue it came from in model: jbexamplemodel)
Problem 2: When an object from the main line gets sent to the reject, its match will assume the combiner and wait there until its match comes down the main line.( Model: rejectreturn will show this, and what I am looking for as far as having something go to rejects then get recreated from the source)
So here is what I am looking for:
Once something enters the rejectqueue1 want it to inform mainsource to create the same item that was rejected. (Similar to: rejectreturn.fsm ).... Then I want it to pass through the processors and only trigger the sources that it needs objects to be created at:
For Example: (Model: jbexamplemodel)
Say, an object is created at mainsource, travels out of processor1a, triggers source1 and then after processor1b is sent to rejectqueue1.
I want rejectqueue1 to send it to the sink when it has mainsource create the same object. Then I want it to pass processor1a without triggering source1 because it already triggered source1 but didnt make it to combiner1 so it should know it doesnt need to trigger source1 but does need to trigger source 2&3...
This would then carry on... if it was sent to rejectqueue2 then it would be recreated at main source it would know it would need to trigger source , but not source2 because it was already triggered and didnt make it to combiner 2, then trigger source 3... and so on...
Probelm 2: Next... If you run model: rejectreturn you will see that after an object is sent to rejects, its already triggered match will assume the position at the combiner and wait for its object to return down the main line. Is there a way to sort through mainqueue1 and secondqueue1 and only allow objects to enter if there is one in each spot so it doesnt get blocked like in model: rejectreturn?
----------------------------------
I know that was a lot but I wanted to be as clear as possible.
I want to thank you for any and all support.
I would not be reaching out if i wasn't already on an extreme time crunch! All support is greatly appreciated.
