It was quite a tricky process as we had over 20 systems each with a 16x16DM frame and AV3 and 6 or 7 DM transmitter inputs in each frame. ?
We used an RMC3 to handle all the mac address programming.
Basically, when a transmitter got plugged in to a system, the Ethernet Offline Manager for that particular port would trigger a bit of code and send?"rcon slot x.1 est\r". ?From there it was just a case of parsing out the mac address. ?This mac address was then passed through to the RMC3 processor running our mac address lookup code which would compare that mac to all the ones it had on file and if a match was found, it would return the name that had been previously assigned to it and return that information to the appropriate system. (EIC)?
If it didnt find a match, it would prompt the user to enter a name for the device which was then saved to the mac address list text file stored on the RMC3 processor. ??
Depending on the complexity of the system you are programming, you may not even need to read and write from a file. ?We had to as we were trying to manage over 100 TX units with the client wanting the abillity to add more as required. ?If you have a pre-determined quantity of TX units, no reason you couldnt hardcode the mac addresses in a simpl+ module and simply perform a lookup/comparison everytime a device comes online.
?
