gibt es eine Möglichkeit die Anwenderdaten eines Shuttles “remanent” zu speichern und diese nach einem Neustart ( ACOPOStrak Versorgungsspannung komplett AUS/ EIN) wieder dem richtigen Shuttle zuzuordnen. Eine RFID Lösung sollte es nicht unbedingt sein.
Is there a way to save the user data of a shuttle “remanently” and assign it to the correct shuttle again after a restart (ACOPOStrak supply voltage completely OFF/ON)? It should not necessarily be an RFID solution.
if ACOPOStrak is switched off, all shuttle data is also lost.
When switching on, the shuttles are searched for and the system assigns a unique ID. The Trak does not know which individual shuttle is it e.g. does not recognize the serial code.
This requires either an RFID or a barcode reader in the application. The printed serial numbers are then shown in the barcode.
When a shuttle passes the RFID reader or barcode reader, the application can then assign the individual ID.
(If you can ensure that the shuttles have not moved during the power-off, then the old user data could of course be reassigned.)
theoretically I could make sure that the shuttles are not moved. Is there a ready-made solution from B&R to reassign the user data in this case? Do you have a solution for me for the implementation? It concerns three systems with a total of approx. 300 shuttles in the system. Of course, I also have the problem with the lost user data after every software update. Currently, all systems always have to be emptied beforehand, which is not so nice.
unfortunately I’ve no example. It is more an idea for a very specific idea.
1.) you have to ensure the shuttles don’t move during power-off
2.) Get all shuttles’ positions and user data with MC_BR_AsmCopyShuttleData_AcpTrak
3.) Save this array to a data object or a file
4.) after power-on you have to compare the current shuttle positions by considering a tolerance.
Hello Christoph,
I have already integrated the MC_BR_AsmCopyShuttleData_AcpTrak into the project, but I use it for other things. It could have been that there is already something official from B&R. I’ll think of a way to implement it.
Hello Aldo,
unfortunately only one instance of MC_BR_AsmCopyShuttleData_AcpTrak is allowed, so either you reuse its results or you move the ‘hard’ way (MC_BR_AsmGetShuttle_AcpTrak, MC_BR_ShReadInfo_AcpTrak
MC_BR_ShCopyUserData_AcpTrak )
You’re welcome.