question

Clair A avatar image
0 Likes"
Clair A asked Clair A commented

Why does OnAGVAllocationFailed alter a model ?

Reset and run the attached model, it's working fine.

Now try the following steps:

  1. Attach TaskExecuter2 to the TaskExecuter Process Flow
  2. Reset
  3. Remove TaskExecuter2 from the TaskExecuter Process Flow
  4. Reset
  5. At this step the model is supposed to be in the same state as before step 1. However run the model and at time = 34.19 it throws an exception.

It looks like having a source activity triggered by OnAGVAllocationFailed messed up "something somewhere" on reset.

Any clue from the developers ? @anthony.johnson

FlexSim 17.0.0
agv allocation
2017-01-03-onagvallocationfailed-1700.fsm (107.8 KiB)
· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Clair A avatar image Clair A commented ·

The 2 AGVs are already attached to the AGV Process Flow and already connected to the network. The error occurs when you attach the TaskExecuter2 to the TaskExecuter Process Flow as I described above.

I attached the model in this state and here is the exception:

time: 34.195049 exception: Exception Caught in TaskExecuter::beginTask(treenode task) object: /TaskExecuter2
time: 34.195049 exception: Exception Caught in TaskExecuter::receiveTaskSequence(treenode newts) object: /TaskExecuter2
time: 34.195049 exception: Exception Caught in dispatchtasksequence(treenode tasksequence, treenode dispatcher DEFAULTNULL)
time: 34.195049 exception: Exception caught in start() of activity "Travel to Next Look For Work" in "AGV". Continuing throw...
time: 34.195049 exception: Exception caught in TreeNode::callMemberFunction() c++/dll execution. Throwing... MAIN:/project/exec/usercommandlist/Process Flow/releasetoken/node c: MAIN:/project/exec/usercommandlist/Process Flow/releasetoken/node i: MAIN:/project/exec/usercommandlist/Process Flow/releasetoken/node thisClass: MAIN:/project/exec/usercommandlist/Process Flow/releasetoken/node
time: 34.195049 exception: Exception caught in evaluation of MAIN:/project/exec/usercommandlist/Process Flow/releasetoken/node
0 Likes 0 ·
2017-01-03-onagvallocationfailed-1700.fsm (108.5 KiB)

1 Answer

Sam Stubbs avatar image
0 Likes"
Sam Stubbs answered Clair A commented

Sorry I misunderstood your question earlier. I've had one of the developers look at it, and it seems like this is a bug. We've reported this, and sent it to the developers. Sorry about the inconvenience.

· 6
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Clair A avatar image Clair A commented ·

@Sam Stubbs Do you know if the developers have a quick workaround for this ?

The model I had attached is just a sample model to help you find the bug but the request came from one of our licensed users. This issue broke his model and we don't know how to repair it.

0 Likes 0 ·
Sam Stubbs avatar image Sam Stubbs ♦ Clair A commented ·

I just recreated your model in 16.2 and it also threw the exception... Could you clarify what you mean and what happened when the user's model broke. Because if this has never worked, then changing it shouldn't have broken the model.

0 Likes 0 ·
Clair A avatar image Clair A Sam Stubbs ♦ commented ·

Yes, I had also tested it in 16.2 and the issue was the same.

What I mean could be simplified as follows:

  • the model was working fine
  • we added a Process Flow with a source activity triggered by OnAGVAllocationFailed
  • we noticed the exception quoted above
  • so we go back by deleting the Process Flow which has a source activity triggered by OnAGVAllocationFailed
  • however as shown in the example above once you remove the "sick part", the model stays sick and it still throws the exception. So the only solution for the user is to go back to a previous backup of his model and loose some other work he has done between the 2 backups.
0 Likes 0 ·
Show more comments