This is an ACOPOStrak demo project template developed by B&R Spain. The aim of this project is to reduce the time that is needed to develop a first project viability study.
The project contains some tasks that can be easily adapted to fit almost any initial setup. Based on our previous experience developing customized demo simulations, we classified the tasks in 2 different groups.
- Single shuttle operations: The shuttles will be operated individually (one product each shuttle). There are 3 available tasks depending on how many shuttles should be processed simultaneously.
Of course, the different type of tasks could be combined such as:
- Paired shuttle operations: The shuttles will be operated in pairs (one product carried between two shuttles).
Before any process can take place, the synch between two shuttles (ProcSync) must take place. After that, depending on how many products should be processed at the same time, the different tasks can be combined accordingly.
A possible layout configuration could be arranged such as:
IMPORTANT! In order to use this template, the user should be familiar with the ACOPOStrak configuration and programming.
The project has been tested with the following versions:
- Automation Studio 4.12
- Scene Viewer 4.3
- mappView / mappMotion / mappControl (version 5.24)
- AR G4.90
From the Physical View, change the layout adding or deleting as many ACOPOStrak segments as needed. The Global.var file should also be modified accordingly.
After the layout has been defined, the .assembly, .sector and .processpointlist files should be adapted as well.
Depending on how your product will be carried (between one or two shuttles), use the tasks inside the "SingleSh" or "PairedSh" folders. Notice that in the task header it is indicated if the task should be always included (mandatory) in your simulation or not.
Each task has its own configuration parameters in the _INIT subroutine.
They will need to be changed or adapted according for each task.
- PPAdr: Process point of the actual station.
- SecAdr: Sector of the actual station.
- PPDest: Process point of the next station.
- SecDest: Sector of the next station.
- Speed_IN: Entry station speed. (Should be the same as the output station speed from the previous station).
- Acc_IN: Entry station acceleration. (Should be the same as the output station acceleration from the previous station).
- Speed_OUT: Output station speed.
- Acc_OUT: Output station acceleration.
- WaitTime: Station waitting time in ms.
- DistTravelled/1/2: Stopping distance (from the processpoint) for each shuttle.
- ReleaseSts: Defines if the station is a "release station". If it is, the global output production (in ppm) will be increased by this station.
- Red,Green,Blue: RBG shuttle color configuration (from 0 to 1) after the process is completed.
Example:
After all the tasks are correctly configured and added to the software configuration, the project can be transfered to ArSim using an offline installation.
After the file is opened, establish communication via OPC UA.
Access the HMI via http://127.0.0.1:81/index.html?visuId=Visu. Through the user interface, you will be able define several parameters from the simulation.
This task generates one string that can be used alongside with the paper widget allowing us to easily identify when there is an active issue with some segment.
All the segment names must start with the same prefix. For example, if the segments are called "Seg_A_1, Seg_A_2, Seg_A_3...", the following task code line must be adapted accordingly.
The paper widget from the HMI is intended to be used with the .svg file that is automatically generated by the AS project. To make it easier to visualize, it is recommended to delete the elements "segtable", "sectortable" and "trptable" from the svg file.
After these modifications, in order to show the image centered, the viewBx parameters can be modified. The easiest way to do it, is to reuse the values given by the viewBox settings from the .wsp file.