amr system quetion

[a4225283]

I want to combine some logic from A* with AGV path. It's a very simple example, but I need to use A* to help me calculate distances. So how can I use PowerFlow to implement this functionality? (For example, using a task list and customizing the pickup and drop-off locations.) Without relying on A* connections.

What I want to do is simple: after the machine finishes processing, it's sent to the PORT (Q), and then the downstream machine's PORT is retrieved using a task list to complete the assignment and transport. However, I'm a bit unsure how to integrate these two modeling methods.

What I want to do is simple: after the machine finishes processing, it's sent to the PORT (Q), and then the downstream machine's PORT is retrieved using a task list to complete the assignment and transport. However, I'm a bit unsure how to integrate these two modeling methods.

[FelixMoehlmann]

The items need to actually be send somewhere for the Use Transport field to get executed and push the item to the work list. Either through port connections or by pushing them to a (separate) list and having the other queues pull them.

Ultimately it doesn't matter how the items end up on the work list, just that they have a destination label set when that happens. So the push could also be done in object triggers or Process Flow.

Rather than using an extra object to denote the load/unload location of an object I would write coordinates to a label on the object and use those.

[a4225283]

I know this approach can be used, but I need to handle some more complex production line logic, so I prefer to use a list approach. Also, since there might be multiple destination options, I'd like to use a list approach for that as well.

[FelixMoehlmann]

Like I said, you can of course first push the item to another list and have it be pulled by the receiving objects. Or an Event-Triggered Source in a Process Flow creates a token for each item when it becomes available and the token then runs through a decision logic that determines where it should be send.

There are many options to model this and which one is 'best' will depend on the requirements and personal preference. Having objects pull from a list is probably the simplest. But dynamic priorities would be better handled by a centralized logic that first looks at the state/content/forecast of all involved objects before making a decision.

[a4225283]

I'd like to ask how the destination labels are designed, and also, how do I execute the "assign label" task to complete the progress checklist?

[a4225283]

I want to write the model in a similar way, but it seems that many tags and other features cannot be satisfied...

[FelixMoehlmann]

When the item is pushed to the list in the "Use Transport" field the destination label is written to it (as well as "preempt" and "priority", but those are not strictly necessary). If you don't use that option, you need to add the "destination" label somewhere else. In the example this could be done at the same time as the "Type" label is set. How/where this is done in the final model will depend on what decision logic needs to be applied.

Pushing the items to the "SendList" first and having the other queues pull them, add the label and then put them on the WorkList would be one possible approach.