How to replace a serial meter with an Ethernet meter in Power SCADA Operation (PSO) 9.0.

Issue

A serial meter on an daisy chain was replaced with a new Ethernet meter. The Power SCADA Operation project must be updated so the new device communicates.

Product Line

Power SCADA Operations 8.2

Power Operation 2020 and 9.0

Power Operation 2021

Power Operation 2022

Power Operation 2023

Power Operation 2024

Environment

Device Manager

Device replacement

Resolution

1. Open Power SCADA Studio.
2. Go to Topology → I/O Devices and locate the row for the replaced device. Capture its parameters (I/O Server, Name, Protocol/Driver, etc.).
3. Open I/O Device Manager (right‑side panel).
4. In I/O Device Manager, select the active project → Manage a Single Device… → Remove one I/O device.
   • Complete the removal wizard and, when prompted, select Add / remove / update more equipment to continue.
5. Choose Create one I/O device and select the correct device profile for the new Ethernet meter.

   • If the profile isn’t available, add it via Device Profile Editor, then export it to the project and return to I/O Device Manager. See FA404306 for instructions on how to add a device profile to a project.
   Reuse the exact same Equipment Name and I/O Device Name as the removed device to preserve existing tag/graphics bindings.
6. • If the name differs (even syntax), a new tag set will be created and any graphics referencing the old tags would have to be edited.
7. Select the same Primary Server (and Standby Server, if applicable) as the old device.
8. Configure Modbus TCP communications (using the project’s Modbus driver—commonly PwrModbus when added via I/O Device Manager).
   • Enter the IP address of the meter and the Unit ID / Device Address required by the device:
     • Many TCP devices ignore Unit ID or expect 1.
     • 255 appears in some guides but is not universal.
     • For TCP→serial gateways, set the serial slave ID behind the gateway. Always follow the meter/gateway manual.
9. Confirm the wizard’s Port Name; keep the new, unique name—do not reuse the old port name.
10. Finish the I/O Device Manager workflow. Compile the project and restart the applicable I/O Server in Runtime so the device begins communicating.

Note: If the selected device profile adds driver parameters (timeouts, word‑order, etc.), review any driver/INI parameters in Setup Editor / citect.ini per the driver’s reference.