Using both GIS and AGV navigator for the same taskexecuter

Question

question

Julio R asked Nov 7, '22 Julio R commented Nov 10, '22

Using both GIS and AGV navigator for the same taskexecuter

I am trying to do a train model where I use the new AGV navigator features designed for trains for the movements in the terminals but then use the GIS navigator for the long travel between terminals.

I think this is not the best approach, but I was trying different things and I tried to connect the AGV to a AGV Control Point and to a GIS point so then I could try to dinamically change set the navigator through code.

Not only this did not work, but when I connected the AGV to the AGV network after connecting it to the GIS network, I got a error message that then I got every time I clicked on the AGV after the first time, and would only go away if I delete the AGV and create a new one.

Other than using different taskExecuters for representing GIS traveling and the operations in the terminal, is there other approach that will allow me to do this?

Software Version:

FlexSim 22.2.2

gis agv train navigator

1667841749899.png (12.9 KiB)

· 2

Joerg Vogel commented · Nov 10, 2022 at 04:59 AM

It sounds to me you do an experiment about everything. Macro and micro world with one tool. I would split both worlds. Build a subset for GIS and set a train to be inactive whenever he is entering a station to do travel task at this station. This travel task are done in a different subset by a different train. If this configuration is complete, you deactivate this local train and switch state on the GIS train again.

0 ·

Julio R Joerg Vogel commented · Nov 10, 2022 at 06:57 PM

This was actually the approach I took. Here is the proof of concept I did:

GIS Trenes Prueba de concepto.fsm

0 ·

gis-trenes-prueba-de-concepto.fsm (1.8 MiB)

Answer 1 · 2022-11-09T19:27:18Z

Jordan Johnson answered Nov 9, '22

My guess is that attempting to connect a TE to two navigators isn't supported. So yes, you got an exception, but I don't know that it's really a bug, since it's not a valid operation.

Programmatically changing TEs is not something we officially support or test or worry about..

All that said, it might be possible. Here's a demo model. The important parts are as follows:

Be sure that the TE has no active task sequences
Use contextdragconnection() to disconnect from one navigator before connecting to another.
Use contextdragconnection() from the GIS Point to the TE to connect to the GIS navigator
Use function_s(agvNetwork, "addMember", te, startPoint) to connect to the AGV navigator.

Do lots of experiments with this approach before using it in a project. For example, I don't know how the new AGV will interact with existing AGVs when the AGV suddenly teleports like that. If you start getting weird behavior or exceptions, then you may have to avoid this approach. Consider expanding this demo model to include more of the situations and logic you would encounter in your project, so you don't get too far down the road and discover an unresolvable issue.

GISAGVDemo.fsm

gisagvdemo.fsm (105.5 KiB)

question