The goal is to clone the settings of a working PU410 board to a brand new same one, in order to be able to use it in case of failure of the working one.
The setup is an MP200 controller connected to an PU410 board which in turn is connected to an 800xA HMI station with CBA and Plant explorer workplace installed. In the Plant explorer workplace, the rta board is defined as network 11 node 2. With the working board connected to the HMI through PC slot 1, backing up and storing of the three .CD files is done successfully via "RTA Board Control/RTA Board Configuration aspect - RTA Board BACKUP button". However, pressing the RTA Board Config button in the same aspect (in order to DUDBS), ONB launches but fails with message:
Issuing manually SLTARG 11,2 also returns the same result (ILLEGAL COMMAND). In the CBA project, only the MP200 controller is defined. There is no RTA node there.
Question No.1: Apart from the above mentioned RTA Board BACKUP button, is it also necessary to connect online to the working PU410 and do a database backup in order to get a full backup of it? If yes, how can this be achieved in our case?
Now, when the new PU410 board is connected to the HMI through PC1 with the correct network settings according to manual, PC1 slot pings successfully but the status of the Communication Aspect in control structure switches between yellow and red. Any effort to start the new board via "RTA Board Control/RTA Board Control aspect - Start Button" fails. The status of the RTA board indicates dead.
Question No.2: How can communication with the new board be established? As previously mentioned, the board is already defined in the Plant Explorer Workplace with network settings 11,2. Furthermore, after the communication is established, is the Start Button the way to upload the three backup files? Lastly, is TRDBS RTA via onb also necessary?
AFAIK, apart from IP address, there is no configuration stored in a PU410.
If both PU410 have identical IP-configuration, it should be possible to replace one with the other - no other settings required.
The RNRP Monitor will tell if it see PU410, it should. Setting a non 172.16.x.y/22 address will prevent RNRP to start, this is not fatal but will prevent redundant Ethernet connection between host computer and PU410. It is recommended to keep the default address of 172.16.168.50 since it allow RNRP to operate.
Not even PU410 firmware version matters, only the very first version 1.0-0 should be avoided since it would restart every 47 day or so due to a 32-bit counter wrap. This was corrected in 1.0-1. The more recent versions have improved firmware for System Hardening, etc. but nothing in the older versions prevents a proper boot and access to MB300.
Try using the PU410Maintenance tool (same tool is used to upgrade firmware) to check if PU410 respond or not.
If you can't get it to work, ask regional ABB support to assist you will fault tracing or even replacing a faulty unit.
If "SLTARG 0,0" gives "ILLEGAL COMMAND" the board has not been booted correctly, or some custom or expert command processor lacking SLTARG has been loaded after boot. Reboot the PU410 to restore the correct command processor.
Normally, "SLTARG x,y" would give illegal command only if CBA version of ONB is missing.
The ONB version of Advant Master connect only permit "SLTARG 0,0" for RTA Board Maintenance purposes. To connect to a controller, install the CBA version of ONB, but remember to select "PU410 *shared* with AC 400 Connect" when asked during installation.