Changing resource count does not copy all settings from the resource

Question

question

Patrick Zweekhorst asked Jun 25, '20 Matt Long answered Jul 10, '20

Changing resource count does not copy all settings from the resource

Hi,

When you have an AGV as resource in your processFlow the offset travel setting is not copied to the created objects if the count of the resource is changed. You can see this by creating an resource of an AGV taskExecuter. Set the offset travel to: "Do not travel offsets for load/unload tasks". Change the count of the resource to 2. The new AGV has its offset travel set to "Use navigator for offset travel". It would be nice if this setting was also copied when changing the resource count.

If something is not clear please let me know.

Software Version:

FlexSim 20.1.3

agv flexsim 20.1.3 resource offset travel resource count

· 2

Jeff Nordgren commented · Jun 26, 2020 at 01:42 PM

@Patrick Zweekhorst,

Can you send a sample model of the problem to help us replicate it. Using a resource in PF uses objects that already exist, it doesn't create them. So I'm not sure exactly what the problem you are having is. A sample would be helpful.

Thanks.

0 ·

Patrick Zweekhorst commented · Jun 26, 2020 at 01:54 PM

@Jeff Nordgren,

Attached is an example model that shows the problem. When you change the count of the resource and press reset extra objects are created if the count is more than what you had. That makes a copy of TaskExecuter1. As you can see in the picture the offset settings are not copied when the second task executer is created:

ExampleResouceAgv.fsm

I hope the problem is clear now, if not please let me know

Picture.png

0 ·

1593179647466.png (83.5 KiB)

exampleresouceagv.fsm (330.1 KiB)

picture.png (64.8 KiB)

Answer 1 · 2020-07-10T14:01:11Z

Matt Long answered Jul 10, '20

Looks like when the Resource copies the object, it has to attach the AGV back to the AGVNetwork navigator. The process of doing this resets the offset travel parameter. If you open TaskExecuter1's properties and remove the Navigator then hit apply, then add the navigator back to AGVNetwork and hit OK, then when you reopen its properties the offset travel has changed.

We'll add this to the dev list.

question