Cancel
Showing results for 
Search instead for 
Did you mean: 

Broker to Coordinate Tool Changes After X Parts Made?

Pioneer
Pioneer

Hi all,

 

In a previous thread I was looking to manage non-overlapping tool changes between five mould presses using an always active (infinitely looping) method. Attached below is a simpler example model with three common presses and tool changes being handled in this way.

 

This strategy however was pointed out for being complicated. The tool change method is even more complicated in my main model as the fifth press is unique from the other presses and can only handle a few specific tools. With how I currently have things set up, press five will cause the other four presses to hang when it completes running its queued tools for the day (handled in a seperate queue from the one that the other four presses reference)

 

Can a broker be used to coordinate tool changes between presses? Tool changes are required when the number of shots run through a tool meet the set requirement for that tool. When this is true (and there is no ongoing tool change), a queue list is referenced for the next tool to be run in the press making the request. Each of the tools have different shot requirements. I've reviewed the example models related to brokers and exporters but I'm still not sure how to configure these objects to work in this manner (when ShotsCount = ShotReq, tell the broker to coordinate a tool change).

 

How can I set this up with my example model?

1 REPLY

Re: Broker to Coordinate Tool Changes After X Parts Made?

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

the broker mediates exporter to importer of services; so you need all three elements

There should be a threat in this forum to simulate unique tools using exporters, but I dont find it.

 

First it is possible.

You need several steps:

- trigger a "real" setup process of the presses, the easiest way is to change the name of the MU in the entrance control before actions (e.g. add a following number to the MU name, for the runtime of one tool keep it, than change the name--> this will trigger the setup process).

Activate the importer and define a service for the setup process. If you have only one exporter (Worker) who is offering this service, only one setup process can be done on the same time.

 

Create for each tool one exporter (define for each different tool a special service).

If you trigger the setup --> change the service for processing (tool) and setup (tool+worker) of the importer; the broker will mediate the right tool (if it is available).

 

This you can also do with the worker (just change the icon for the tool and the icon for the "workplace" for the tool) to have a better visual control.

 

 

Steffen Bangsow
freelance simulation specialist  
web: www.bangsow.eu
mail: steffen@bangsow.net