Applies To:
  • CitectSCADA 5.x
Summary:
I need to talk serially to an AB Powermonitor 3000 but can not get communications to work. What could be wrong? 

Solution:
The AB Powermonitor 3000 requires CRC error checking when talking to it. Citect's KE drivers use BCC error checking by default but a newer driver has been developed to support CRC error checking. The driver version is 2.01.00.000 A2 or higher which is available from Citect Support.

Below are configuration details for the Powermonitor.

IOServer Configuration:

IOServer Name: IOServer

Board Configuration:

IOServer Name: IOServer
Board Name: Board1
Board Type: COMX
Address: 0

 Port Configuration:

IOServer Name: IOServer
Port Name: Port_1
Number: 1 (This is the COM port number)
Board Name: Board1
Baud Rate: 9600
Data Bits: 8
Stop Bits: 1
 Parity: NONE

IODevice Configuration:

IOServer Name: IOServer
Name: Powermonitor_3000
Number: 1
Address: 117 -CRC
Protocol: KE500
Port Name: Port_1

The address of the I/O Device is where you tell Citect to use CRC error checking by specifying the option -CRC. The address of the device is the unit ID number on the side of the Powermonitor. Note this ID number is decimal and must be converted to octal for the Citect configuration so in my case the unit ID number was 79 (or octal 117).

An alternate option is to use the ABRSLinx driver but that requires the user to purchase RSLinx OEM version software.

 
Keywords:
 

Attachments