Question:
An older SCADAPack controller (not an x70 controller) is out in the field and has been running for years. The original programmer is long gone and we are not sure if we have a backup of the project or if the backup we have is the most recent?
Answer:
Older SCADAPacks (like the SP32, SP334, SP357, SP LP etc..) have two main programming tools, depending on what type of firmware is installed on the device, TelePACE firmware or IsaGRAF firmware.
TelePACE Studio is strictly a ladder-based programming tool and works with TelePACE firmware in the SCADAPack. SCADAPack Workbench follows an IEEE programming standard that allows for the mix and match of different programming languages like function block diagram, ladder, structured text, etc.
If you do have a backup of the project for this device, then a project for TelePACE firmware would have a .LAD or .TPJ file extension. If needed, you can download TelePACE Studio here.
A project for ISaGRAF firmware could either be a large folder or .PIA or .ISASLN file. If needed, you can download SCADAPack Workbench and Utilities here.
With either software, you may need to Unblock it before you unzip it and install it.
If you do not have a backup configuration
If you do NOT have a backup configuration, you will need to confirm what type of firmware is installed on the controller. For this, you will need to use the embedded Firmware Loader utility that is a part of either programming environment. Firmware Loader can be found in TelePACE Studio or in another software package called SCADAPack Configurator (this is one of the Utilities with the SCADAPack Workbench download.)
The following instructions will use screen captures for TelePACE Studio but SCADAPack Configurator screenshots will be very similar.
Once you have a new project started, please verify you are configured to talk to the correct type of controller, then adjust the protocol, depending on how you are trying to connect to the device.
- If your particular SCADAPack has a USB connection, this will be the most straightforward link and set the protocol to Modbus/USB.
- If the SCADAPack has an ethernet port and it is in use, you can use the port if you know the configured IP address. Set the protocol to Modbus/TCP then go to Configure Settings to enter the correct parameters.
- If the SCADAPack does not have an ethernet port or you do not know the configured IP address, then you will need to set the protocol to Modbus RTU and try to connect serially. By default, serial ports are set for Modbus RTU, Station address 1, 9600 baud, 8 data bits, no parity, one stop bit. If the serial ports have been changed from default, trial and error may be necessary. The serial ports should also have Tx and Rx LED. If the cabling is correct, you should see Rx LED activity, even if you have an incorrect parameter.
Once you have cabling and communication parameters set up, please go to the tree structure on the left hand side and select Firmware Loader.
If the firmware type is IsaGRAF, your options will be limited. Please contact Technical Support for further assistance.
If the firmware type is TelePACE, then you should be able to Read the project with TelePACE Studio. Unfortunately, SCADAPack controllers running a TelePACE program do not have register tags, network titles and comments stored on them. you will still have a working version of the logic but it could be more challenging to understand the logic.
For customers new to TelePACE Studio, a copy of the training manual has now been made available at:
Released for:Schneider Electric India

