THOMSON REMOTE COMMUNICATION - V3.0, CIM 3.0 User Manual

Download

REMOTE

COMMUNICATION

SYSTEM

VERSION 3.0

USER MANUAL

9087A – 198th Street, Langley, BC Canada V1M 3B1  Telephone (604) 888-0110

Telefax (604) 888-3381  E-Mail: info@thomsontechnology.com  www.thomsontechnology.com

PM055 REV 2 00/08/31

REMOTE COMMUNICATION SOFTWARE INDEX

SECTION 1 COMMUNICATION INTERFACE MODULE (CIM)

VERSION 3.0

.............................................................................................................. 1

1. INTRODUCTION ....................................................................................................... 1

2. GENERAL DESCRIPTION........................................................................................2

3. HARDWARE INTERFACE ........................................................................................ 3

4. TELEPHONE PORT 1 ............................................................................................... 6

5. PORT 2A/B................................................................................................................6

6. PORT 3A/B................................................................................................................7

7. CIM OPERATION FUNCTIONS ................................................................................ 7

8. CIM BLOCK DIAGRAM ............................................................................................8

9. CIM SPECIFICATIONS .............................................................................................8

10. CIM INSTALLATION ............................................................................................. 9

10.1. B

10.2. R

10.3. D

10.4. M

10.5. M

ATTERY SUPPLY INPUT

EMOTE COMMUNICATION WIRING

IELECTRIC TESTING

OUNTING LOCATION/INSTALLATION

OUNTING DIMENSIONS

10.6. RS-232

AND

RS-485422 W

....................................................................................... 9

..................................................................... 10

.......................................................................................... 10

.................................................................. 10

..................................................................................... 10

IRING

....................................................................... 11

11. TROUBLESHOOTING.........................................................................................13

11.1. D

ATABASE RE-INITIALIZATION

............................................................................ 15

SECTION 2 THS 2000 SOFTWARE PROGRAM

.............................

1. INTRODUCTION ..................................................................................................... 16

1.1. D

EFINITIONS

....................................................................................................... 16

PM055 Rev 2 00/08/31 Thomson Technology

REMOTE COMMUNICATION SOFTWARE INDEX

1.2. I

1.3. C

1.4. I

MPROVEMENTS

OMPUTER SYSTEM REQUIREMENTS

NSTALLATION

.................................................................................................. 17

.................................................................................................... 18

.................................................................. 17

2. QUICK START ........................................................................................................18

2.1. S

2.2. S

2.3. S

2.4. S

2.5. S

2.6. S

2.7. S

2.8. S

2.9. S

TEP

TART

1 S

2: L

3: S

4: E

5: C

6: I

7: V

8: I

9: S

THS 2000................................................................................... 18

OGON

DENTIFY CONTROLLERS

SSUE CONTROLLER COMMANDS

................................................................................................. 18

ET HOST CONNECTION METHOD

NTER SITE PROPERTIES

ONNECT TO SITE

................................................................................ 20

...................................................................... 20

....................................................................... 21

IEW CONTROLLER DATA

AVE/RESTORE SITE-LIST INFORMATION

..................................................................... 21

.......................................................... 19

........................................................... 21

............................................... 22

3. CONFIGURATION................................................................................................... 22

3.1. P

ASSWORDS

...................................................................................................... 22

3.2. S

3.3. S

3.4. C

3.5. C

3.6. A

ITE-LIST MANAGEMENT

ITE CONFIGURATION

OMMUNICATIONS INTERFACE MODULE SETTINGS

ONTROLLER CONFIGURATION

UTO-ANSWER CONFIGURATION

.................................................................................... 23

......................................................................................... 24

.............................................. 27

........................................................................... 35

......................................................................... 38

4. OPERATION............................................................................................................ 38

4.1. B

4.2. C

4.3. V

4.4. P

4.5. A

ASICS

.............................................................................................................. 38

ONNECTING SITES

IEWING AND COMMANDING CONTROLLERS

RINTING

UTO-ANSWER OPERATION

........................................................................................................... 44

............................................................................................ 41

................................................................................ 44

....................................................... 42

5. CIM BYPASS WIRING ............................................................................................45

6. TROUBLESHOOTING ............................................................................................ 47

PM055 Rev 2 00/08/31 Thomson Technology

REMOTE COMMUNICATION SOFTWARE INDEX

SECTION 3 CIM PROTOCOL

.......................................................... 48

1. INTRODUCTION ..................................................................................................... 48

2. PHYSICAL LAYER.................................................................................................. 48

3. DATALINK LAYER ................................................................................................. 49

4. PRESET MULTIPLE REGISTERS (TYPE 16) ........................................................ 50

4.1. P

4.2. E

RESET MULTIPLE REGISTERS RESPONSE

XAMPLE

EMOTE KEY PRESS OPERATION

: R

.......................................................... 51

...................................................... 51

5. READ HOLDING REGISTERS (TYPE 3)................................................................ 52

5.1. R

5.2. R

5.3. E

EAD HOLDING REGISTERS REQUEST

EAD HOLDING REGISTERS RESPONSE

XAMPLE

EAD REGISTERS

: R

200 TO 201........................................................... 52

................................................................ 52

.............................................................. 52

6. APPLICATION LAYER ........................................................................................... 53

7. DATA TYPES AND FORMATS............................................................................... 54

8. CIM PORT CONFIGURATION ................................................................................ 54

9. CIM GENERAL CONFIGURATION ........................................................................ 55

10. CIM PASSWORDS ..............................................................................................56

11. CIM LOGIN .......................................................................................................... 56

12. CIM ABOUT ......................................................................................................... 56

13. CIM RTU LIST...................................................................................................... 57

14. CIM CALLOUT..................................................................................................... 58

15. MEC 20 REGISTER TABLES.............................................................................. 59

16. MEC 20 MESSAGES (VERSION 1.0) .................................................................61

PM055 Rev 2 00/08/31 Thomson Technology

iii

REMOTE COMMUNICATION SOFTWARE INDEX

16.1. MEC 20 P

16.2. MEC 20 V

16.3. MEC 20 G

16.4. MEC 20 G

16.5. MEC 20 A

16.6. MEC 20 D

16.7. MEC 20 F

RESS KEY

ALID DATA/DISPLAY

ET VERSION

ET SUMMARY

NALOG VALUES

ISPLAY DETAILS

AULT DETAILS

.......................................................................................... 61

....................................................................................... 62

..................................................................................... 63

................................................................................. 64

................................................................................. 66

.................................................................................... 66

........................................................................... 62

17. TSC 800 REGISTER TABLES ............................................................................67

18. TSC 800 MESSAGES (VERSION 1.0) ................................................................67

18.1. TSC 800 P

18.2. TSC 800 V

18.3. TSC 800 G

18.4. TSC 800 G

18.5. TSC 800 G

18.6. TSC 800 D

RESS KEY

ALID DATA/DISPLAY

ET VERSION

ET SUMMARY

ET ANALOG VALUES

ISPLAY DETAILS

......................................................................................... 68

.......................................................................... 68

..................................................................................... 68

.................................................................................... 69

......................................................................... 72

............................................................................... 73

19. CRC CALCULATION........................................................................................... 74

20. NOTES:................................................................................................................75

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

SECTION 1

COMMUNICATION INTERFACE MODULE (CIM)

VERSION 3.0

1. Introduction

This section is intended version 3.0 of the Communication Interface Module (CIM). For

other product versions, contact Thomson Technology, Inc. to obtain applicable

instruction manuals.

The Thomson Technology (TTI) remote communication system with the CIM 3.0 and

Modbus™ protocol provides remote monitoring and control of TTI microprocessor-based

controllers as used in the power generation industry. The system consists of 2 main

components as follows:

• Communication Interface Module (CIM): The CIM provides the hardware and

software interface between a Modbus compliant device (customer supplied) and the

specific microprocessor-based controllers as used at a generator site.

• Remote Terminal Unit (RTU): An RTU is a device that directly operates the

equipment at a generator site. These devices are the actual microprocessor-based

controllers as developed by Thomson Technology, Inc. (e.g. MEC 20 engine

controller or TSC 800 transfer switch controller.

The following diagram depicts a typical remote communication system.

MICROPROCESSOR ENGINE CONTROLLER

CIM

TO MODBUS COMPLIANT

DEVICE OR RS 485 NETWORK

ENGINE

GEN

MEC 20

SILENCE RESET

DECREMENT INCREMENT NEXT

LAMP TEST

OFF AUTO

READY

SPEED SIGNAL

LOAD

EMERGENCY

TEST

STOP

ALARM

SHUTDOWN

EXIT ENTER

RUN

PM055 Rev 2 00/08/31 Thomson Technology

RTU Site

G:\ENGINEER\PRODUCTS\ICS\HOST.VSD

SECTION 1 COMMUNICATION INTERFACE MODULE

Some advanced features of the remote communication system with the CIM 3.0 module

and Modbus™ protocol are as follows:

• One CIM module can control and monitor up to 10 RTUs at a generator site using a

single direct serial/phone link.

• Configuration of all communication system setpoints is done using software.

• CIM Port #2 can be configured for RS-232, RS-422 or RS-485 serial communication

types. RS-485 communication allows multiple CIM's to be interconnected to any

Modbus™ RS-485 network. RS-485 is recommended for the best distance and noise

immunity. Port #2 has a hardware protocol auto-detection option that removes the

confusion of determining whether the port is in RS-232 or RS-485 mode. Just plug in

and communicate (assuming the baud rate etc. is set correctly).

• Security features have been implemented to allow password protection. However

these features along with auto-detection and modem functionality can be bypassed

with a "fixed Modbus" option that is intended for direct PLC function where remote

access is not necessary.

• With onboard modem support, CIM 3.0 offers remote telephone connectivity with

auto callout and pager support with up to 32 characters. Up to 3 phone numbers can

be programmed into the CIM for remote THS connection or pager notification. In the

case of a failed connection, retries can be specified.

Further information on the Modbus™ protocol support on the CIM can be found in

SECTION 3 and at the Modicon website (www.modicon.com

NOTE: Throughout this document, CIM's, MEC 20's and TSC 800's are generically

referred to as remotes.

2. General Description

The Communication Interface Module (CIM) is an advanced communication interface

device for remote communication to Thomson Technology's latest generation of

Microprocessor-based engine generator and transfer switch control products. One CIM

module can communicate with networked MEC 20 engine generator controllers or TSC

800 transfer controllers. The serial communication ports can be used for direct

connection to a personal computer (port #2) or to other remote connected devices (port

#3). An internal modem is available with the CIM, which provides direct connection to a

telephone system.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

The CIM provides the following advanced features:

• Dedicated Microprocessor-based design provides fast operation without restricting

RTU operation.

• One CIM module can provide interface to a complete networked RTU system. This

leads to a single telephone line connection per site rather than typical multiple line

solutions.

• Internal 14.4 kbaud modem available for direct connection to telephone system.

• Flexible design provides two fully configurable serial ports.

• Standard plug-in telephone RJ45/RJ11 type jacks and DB9 computer ports provide

simple interconnection to system.

• The ability to callout to a THS host station or pager when an RTU fault occurs frees

the user from continual monitoring. It also allows for immediate remote response to

problems.

3. Hardware Interface

The main features of the CIM are described as follows with reference to the following

figure.

CIM

Port Specifications

Port 1: Telephone line connection to internal modem Port 2: RS232 DTE, RS422 or RS485 Serial port or ext. modem Port 3: RS232 DCE, RS422 or RS485 Serial port

Notes:

1) See user manual for available Port 2 & 3 protocols.

2) The internal modem is disabled when a local Port 2 connection is made.

3) Port 3B is MEC 20 and TSC 800 pin compatible.

4) Refer to instruction manual for alternate port connections.

Port 1

Remote Terminal Unit

INTERFACE MODULE

To Telephone Line

14.4kb Internal Modem

Power

Service

DC Fault

Power

8-35Vdc

+/- -/+ G

Port 2

Port 3

COMMUNICATION

MADE IN CANADA

PM055 Rev 2 00/08/31 Thomson Technology

G:/ENGINEERING/PRODUCTS/ICS/1029009.VSD Rev. 2 98/12/04

SECTION 1 COMMUNICATION INTERFACE MODULE

3.1. DC Power Input: Terminals are provided for DC power input to the CIM

module. Power input is non-polarity sensitive and can range from 8-

35Vdc.

3.2. Telephone Port: The telephone port is used to interconnect to a telephone

system. This port is internally connected to a 14.4 Kbaud modem. This

port uses a 6 pin RJ11 plug-in jack connection.

3.3. Diagnostic LEDs: The CIM module provides four diagnostics LED lights

are described as follows:

• Power: This LED is illuminated whenever the CIM has correct DC

supply voltage applied.

• Service: This LED illuminates when the CIM has an internal fault in

which the unit must require service.

• DC Fault: This LED is illuminated whenever the CIM's internal power

supply has shutdown do an internal fault or an external overvoltage

condition from the DC supply input. To reset a DC fault, the DC supply

voltage must be removed for 30 seconds, then re-applied.

3.4. Internal Modem: The CIM is provided with an internal 14.4 Kbaud

modem. The modem is internally connected between the telephone port

and port 2A/B.

3.5. Port 2B: Port 2B may be interconnected to a remote terminal unit (RTU)

or Personal computer (PC). Port 2B can be configured to RS-232 or RS-

485/-422 type transmission signal. When a personal computer is

connected to Port 2B, a null modem cable or connector must be used.

When the CIM modules' internal modem is used, port 2B is disabled. This

port uses an 8 pin RJ45 plug-in connector. An LED indicator is provided

to signal when the port is communicating. Port 2B is internally wired in

parallel with Port 2A.

3.6. Port 2A: Port 2A may be interconnected to a remote terminal unit (RTU)

or PC. Port 2A can be configured to RS-232 or RS-485/-422 type

transmission signal. When a personal computer is connected to Port 2A,

a null modem cable or connector must be used in series with the PC

cable. When the CIM modules' internal modem is used, port 2A is

disabled. This port uses a 9 pin standard DB9 female plug-in connector.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

An LED indicator is provided to signal when the port is Transmitting. Port

2A is internally wired in parallel with Port 2B.

3.7. Port 3B: This port may be interconnected to a remote terminal unit (RTU).

Port 3B utilizes a RS-422 type transmission signal that is compatible with

MEC 20 or TSC 800 controllers. The standard connection for a MEC 20

or TSC 800 controller (RTU) application is for port 3B to be connected to

the RTU. This port uses an 8 pin RJ45 plug-in connector and allows for a

direct connection to TTI MEC 20 and/or TSC 800 controllers. Port 3B is

internally wired in parallel with Port 3A.

3.8. Port 3A. This port may be interconnected to a remote terminal unit (RTU)

or directly to a PC. Port 3A utilizes a RS-422 type transmission signal that

is compatible with MEC 20 or TSC 800 controllers. The standard

connection for a MEC 20 or TSC 800 controller (RTU) application is for

port 3A to be connected to the RTU. This port uses a 9 pin DB9 female

connector. Port 3A is internally wired in parallel with Port 3B.

NOTE: CIM Port 2 cannot be used concurrently with the modem (CIM Port 1). An RS-

232 or RS-422 cable can be connected to the CIM, but cannot be active if the modem is

to be used. An RS-485 connection will effectively disable the modem whether it is active

or inactive.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

4. Telephone Port 1

Detail pin numbers and usage designations for the telephone port are as follows:

Signal Type - Telephone Direction Port 1A RJ11 #

No Connection No Connection 1

No Connection No Connection 2

TIP Input/output 3

Ring Input/output 4

No Connection No Connection 5

No Connection No Connection 6

5. Port 2A/B

Detail pin numbers and usage designations for Port number 2A/B are as follows:

RS-485 half-duplex

(Pending)

RS-422 full-duplex

(Pending)

RS-232

(DTE)

Direction RJ45 # DB9 #

Sa' Rxa CD Input 1 1

Sb' Rxb Rx Input 2 2

Sb Txb Tx Output 3 3

Sa Txa DTR Output 4 4

Ground Ground GND Passive 5 5

NC NC DSR Input 6 6

NC NC RTS Output 7 7

NC NC CTS Input 8 8

RI n/c n/a 9

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

6. Port 3A/B

Detail pin numbers and usage designations for Port number 3A/B are as follows:

RS-485 half-duplex

(Pending)

RS-422 full-duplex

(Pending)

RS-232

(DCE)

Direction RJ45 # DB9 #

Sa Txa CD Output 1 1

Sb Txb Tx Output 2 2

Sb' Rxb Rx Input 3 3

Sa' Rxa DSR Input 4 4

Ground Ground GND Passive 5 5

NC NC DTR Output 6 6

NC NC CTS Input 7 7

NC NC RTS Output 8 8

RI n/c n/a 9

7. CIM Operation Functions

The CIM module provides the following main functions when used in a communication

system:

RTU & Modbus™ Device Interface: The CIM is the main communication interface

component between a Modbus™ compliant device and the remote terminal units. The

CIM provides the necessary hardware interface (i.e. COM Ports) as well as the

Modbus™ software protocol interface.

Protocol Data Processing: The CIM receives incoming communication signals from

various types of RTUs and processes the data into the specific Modbus™ language as

required for the application. The processed data then gets transferred to the applicable

port and transmitted to a remote Modbus™ compliant device.

CIM Configuration: The CIM stores vital information in non-volatile FLASH memory

pertaining to a specific RTU site as defined by the user. Stored information includes, site

name, site passwords, and auto callout phone numbers (3).

RTU Polling: The CIM module will automatically poll connected RTUs to determine their

operating status and to signal an auto callout (callout is only operational when the

modem feature is operational) to the remote Modbus™ compliant device to alert a user

of an abnormal condition.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

8. CIM Block Diagram

+–

8-35Vdc

Battery

Voltage

EMI/RFI FILTER

LED's

DIAGNOSTIC

POWER SUPPLY

(CORE)

MICROPROCESSOR

DUART

9. CIM Specifications

DC Power to all IC's

Channel

Select Logic Port 2

or Modem

14.4kb Internal Modem

PORT 2 DRIVER

RS232/485

NOTE: The Modem is disabled when an activre Port 2 connection is made.

PORT 3 DRIVER

RS232/485

Telephone

Port 1

RJ11

DB9

RJ45

DB9

RJ45

G:/R&D/PRODUCTS/ICS/DESIGN/CIM/1029012.VSD Rev. 0 99-08-26

Telephone Line

Modbus (TM)

Compliant

Device

Alternate Port Connections

MEC 20/ TSC 800

• Power supply: 8 to 35Vdc, negative ground

• Power consumption: 5 watts (max.)

• Operating temperature: -15(C to +50(C

• Storage temperature: -40(C to +85(C

• Environmental: NEMA 1

• Vibration: 1g, 5-250Hz

• Humidity: 5 to 95% non-condensing

• Dimensions: 150mm W x 180mm H x 50mm D

• Internal Modem 14.4 kbaud, Hayes™ AT set compatible

• Communication Ports Hardware Port 1 Telephone T/R Port 2 RS-232/-422/-

485 asynch., 1200-19200 baud Port 3 RS-422, asynchronous 4800 baud

• Communication Ports Software Protocol Port 1 Telephone Port 2 Modbus™

Protocol Port 3 TTI T-Net Protocol

Specifications subject to change without notice.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

10. CIM Installation

NOTE: Installations should be done according to all applicable electrical regulation

codes as required.

The following installation guidelines are provided for general information only pertaining

to typical site installations. For specific site installation information, consult Thomson

Technology as required.

CAUTION!!! Qualified personnel must do all installation and/or service work

performed only. Failure to do so may cause personal injury or death.

10.1. Battery Supply Input

The CIM can operate on any battery supply from 8 to 35 volts DC nominal

Wiring from the system battery to the CIM should conform to the following

guidelines to avoid possible communication module malfunction and/or

damage.

Avoid wiring from the engine starter terminals - wiring should go directly

from the battery terminals to the control panel where the CIM module is

located (to avoid voltage drop in the starter cables and starter motor

commutation noise).

CAUTION!!! The battery charger must be turned off before battery cables

are removed from the battery (i.e. for servicing). Failure to do so may

subject the control panel to an overvoltage condition in which damage

may result.

Under noisy environments (i.e. gas engines with high voltage ignitions,

etc.), wiring from battery should be a twisted pair of #14 AWG (2.5mm2)

wires.

The use of AC or DC operated solenoids or relays in control systems can

sometimes cause high voltage spikes on the DC power supply, which

may cause electronic devices to fail. Transient suppression devices are

recommended for all inductive devices sharing wiring or if physically

located near the CIM module. For DC operated relays or solenoids, use a

suitably rated counter EMF Diode (or commonly known as "freewheeling"

diode). For AC operated relays or solenoids, use a suitably rated metal

oxide varistor (MOV) or capacitor/resistor suppressor.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

10.2. Remote Communication Wiring

All communication interconnecting wiring to/from the CIM Module shall

utilize #22 AWG-8 wire, twisted, shielded cable with RJ45 connectors.

All remote communication wiring outside the control panel must be run in

separate conduit and shall not be located near AC power cables to

prevent pick-up of induced voltages.

10.3. Dielectric Testing

Do not perform any high voltage dielectric testing on the CIM connected

in the circuit as serious damage will occur to the module.

10.4. Mounting Location/Installation

The CIM Module is designed for mounting directly onto a control panel

inner sub-panel. Considerations should be given for the following:

The controller should be installed in a dirt free, dry location away from

extreme heat sources. Adequate space should be provided around the

CIM module for control wiring.

10.5. Mounting Dimensions

The CIM mounting dimensions are shown in the following diagram:

150 mm

95mm95 mm

190 mm

54.5mm 54.5mm

109mm

ENCLOSURE DEPTH: 50mm

G:/R&D/PRODUCTS/ICS/DESIGN/CIM/102910.VSD Rev. 1 98-12-04

200mm

4 HOLES Ø 4.77mm. (.188 in.)

DRAWING SCALE: .6:1

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

10.6. RS-232 and RS-485422 Wiring

This section describes the cabling necessary to connect a host PC to a

CIM using RS-232 and to connect to an RS-485 or RS-422 network

10.6.1. Host PC Connection

The host PC connection to the CIM requires a null-modem adapter, as

both devices believe they are DTE.

10.6.1.1. Host PC DB-25 To CIM DB-9

DTE DB-25 DB-9 CIM

GND 1 n/c GND

TXD 2 2 RXD

RXD 3 3 TXD

RTS 4 8 CTS

CTS 5 7 RTS

DSR, DCD 6,8 4 DTR

SG 7 5 SG

DTR 20 6,1 DSR,DCD

10.6.1.2. Host PC DB-9 To CIM DB-9

DTE DB-9 DB-9 CIM

TXD 3 2 RXD

RXD 2 3 TXD

RTS 47 8 CTS

CTS 8 7 RTS

DSR, DCD 1,6 4 DTR

SG 5 5 SG

DTR 4 6,1 DSR,DCD

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

10.6.2. RS-485/-422 Connection

The following hardware configuration is required for 4 wire RS-

485/-422 from the port 2 on the CIM to an RS-232 port on a

computer:

The following parts are connected in order from the RS-232 side

(computer) to the RS-485/-422 side (the CIM).

RS-232 to RS-485 or RS-422 adapter (set to DCE)

DB-25 to RJ45 adapter (or custom cable) for RS-422/-485 on the

CIM port 2(see below wiring).

Insure that the correct handshaking signals are connected on the

RS-232 side of the RS-485/-422 converter. Many RS-485

converters use the RTS line to control the transmitter (which must

be tri-stated during receive mode). It is important to insure that the

converter is configured correctly and the correct handshaking lines

are wiring appropriately. If the handshaking lines (RTS) are not

wired correctly the connection may appear to work but damage

may occur and communications may be unreliable over time.

DB-25 from RS-422 converter CIM Port 2

Signal Pin Pin Signal

TXB+ 14 1 RXB+

TXA- 2 2 RXA-

RXA- 5 3 TXA-

RXB+ 17 4 TXB+

GND (optional) 7 5 GND

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

DB-25 from RS-485 converter CIM Port 2

Signal Pin Pin Signal

TXB+, RXB+ (jumpered) 14,17 1,4

TXA-, RXA- (jumpered) 2,5 2,3

RXB+,TXB+ (jumpered)

RXA-, TXA(jumpered)

GND (optional) 7 5 GND

• Note that the RS-232 side of the RS-485 converter will most

likely require the RTS line be connected along with TX, RX

and GND.

11. Troubleshooting

Refer to the following list of typical problems. Consult the factory for any detailed

information or for any problems not listed.

CAUTION!!! Before opening the enclosure to perform any service task, it is

imperative to isolate the control system from any possible source of power.

Failure to do so may result in serious personal injury or death due to electrical

shock.

Service procedures must be undertaken by qualified personnel only!

SYMPTOM CORRECTIVE ACTION

CIM does not power up even with correct DC power applied

Check that there are no wiring errors/short circuits connected to the CIM. Note: The CIM Module contains an electronic fuse that triggers upon an overload or overvoltage condition and does not reset until the supply voltage is removed.

Verify all communication cables are connected to the correct ports.

Failure to communicate with PC (direct

Ensure that the RTU's (TSC 800 and MEC 20) are connected to Port 3 on the CIM.

connected).

Ensure the correct MEC 20 communication port (J7) is utilized. P

rt J7 is white in color. The black RJ45 connector on the MEC

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 1 COMMUNICATION INTERFACE MODULE

20 is for the expansion port, damage may occur to the CIM if this port is connected! When direct connection is used from port 2A to a PC, ensure a null modem cable or connector is used. (see

Host PC Connection

Verify all settings in the THS 2000 program are correct. Critical settings are as follows:

Port 3 baud rate--4800

Controller address--THS setting and controller setting must match

Site Name--THS setting and CIM setting must match. Note: factory default setting in CIM is "site"

Site Password--THS setting and CIM setting must match. Note: factory defeat setting in CIM is "user".

If multiple MEC 20 controllers are connected to a single system, verify all controller node addresses are different.

Failure to communicate with PC (Modem connected).

Failure to communicate with PC.

RTU site may be busy calling out if an alarm condition is present on the controller. Reset all fault conditions at the controller and set for automatic mode to cancel the auto call out condition.

Verify PC modem operates correctly (test independently with another software system).

Verify PC modem is set for 9600 baud operation.

Ensure phone numbers programmed for both PC site location and RTU equipment location are correct.

If you encounter difficulty connecting to a CIM with the Host software make sure the CIM is not trying to call-out. When the CIM is trying to call-out to the Host sites it will not respond to outside requests for connection. In this situation the user can be patient and make repeated attempts at connection until the CIM has exhausted its phone numbers and retries (can be over 12 mins in some cases with 3 numbers and 3 retries). Or the user can let the host successfully call-out to the Host software. After the phone numbers are successfully attempted or retries are exhausted the CIM will go back into a log-in ready state. If time is important, the CIM may be power cycled, for a brief time after the CIM power is restored (after the 2 quick blinks on the Port 2 LED) the CIM will be log-in ready. However the CIM will eventually go into a call-out state to report the site alarm situation.

PM055 Rev 2 00/08/31 Thomson Technology

The above situation is the most common cause for not bein

SECTION 1 COMMUNICATION INTERFACE MODULE

able to establish a connection to the CIM. For testing and configuration it is recommended that the call-out function be disabled until it is required, this will eliminate the frustration described above.

Verify the connected controller is programmed for the specific

Site RTU fails to auto callout to PC.

auto callout function (i.e. common alarm, common shutdown or common fail)

Verify the Host software is in auto-answer mode, see THS2000 User Manual, Auto-answer Configuration

The CIM port configuration changes will not go into effect until

the CIM has been power cycled. Port configuration changes do not work.

For Modbus communications ensure that the CIM is being

addressed with the correct node address. The factory default

CIM node address is '1', this should not be confused with the

RTU node addresses connected to Port 3 of the CIM.

11.1. Database Re-initialization

If state of the internal database is unknown a reset to factory default

conditions can be done by the following procedure:

a) Remove power from the CIM.

b) Remove the CIM back cover.

c) Connect a wire from the CIM ground terminal located next to the power

connections.

d) Connect the other end of the ground wire to the testpoint located on

the bottom of the daughter board (the daughter board is plugged into the

bottom of the CIM motherboard) located on the bottom of the CIM that

should be visible with the bottom cover removed.

e) With the bottom testpoint grounded carefully apply power to the CIM

for at least 2 seconds. You may now remove power and reassemble the

CIM. The CIM has defaulted back to factory settings.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

SECTION 2

THS 2000 SOFTWARE PROGRAM

1. Introduction

The THS 2000 software program remotely controls and monitors a Thomson Technology

(www.

program operates on an IBM-compatible Personal Computer with Microsoft Windows 95™,

Microsoft Windows 98™, Microsoft Windows NT™ 4.0 or Microsoft Windows 2000 operating

systems (www.microsoft.com

communicate to TTI generator control system site. A site consists of a single Communication

Interface Module (CIM) and one or more associated Remote Terminal Unit (RTU) controllers.

The THS 2000 software is designed to allow a direct connection (via RS-232, RS-422 or RS-

485) to Port 2 of the CIM or a remote connection (via a host PC modem) with the internal

modem of the CIM on Port 1. The host PC modem must already be configured before

attempting a remote connection. See the operating-system help for installing and configuring

modems.

Version 3.1 of the THS2000 is intended for operation with version 3.0 of the CIM, but also

provides support for previous versions of the CIM.

Throughout this document, text that looks like this for filenames and other computer-type

text; text that appears in menus, dialog boxes and buttons looks like this windows-type text.

thomsontechnology.com) generator/transfer-switch control system. The THS 2000

). The THS 2000 program uses a TTI designed protocol to

1.1. Definitions

CIM Communications Interface Module; the communications hub for a site

Dialog box interactive window allowing the user to view or change settings

MEC 20 Microprocessor Engine Controller

Modbus industry-standard serial automation protocol defined by Modicon

(www.modicon.com

RTU Remote Terminal Unit; in this context, a MEC 20 or a TSC 800

TSC 800 Transfer Switch Controller

Site a CIM and one or more connected RTUs

Site-list the site-list is the list of remote sites, primarily used for auto-answer and

multiple CIM sites

PM055 Rev 2 00/08/31 Thomson Technology

), part of Schneider Automation, Inc.

SECTION 2 THS 2000 SOFTWARE PROGRAM

1.2. Improvements

A number of improvements have been made to this version of the THS 2000 software.

Most of the improvements correspond to added features of CIM version 3.0, but some of

the changes are applicable to the previous version of the CIM. See See Section 1

more information on device-specific features and Section 3

for the Modbus protocol.

for

The most notable improvement is the use of the Modbus protocol for communications to

the CIM.

The new features in THS 2000 are:

• Support for new CIM 3.0 Modbus protocol as well as previous CIM protocol versions.

• Automatic RTU (MEC 20 and TSC 800) discovery on login. This will eliminate the

need for the user to program the individual node address and controller type for each

site (CIM). See Controller Discovery

• Support for these additional CIM 3.0 features:

 32 character telephone numbers for callout, see Auto-answer Configuration

 call all numbers option for CIM callout, see Auto-answer Configuration

 CIM Port 2 auto-detect feature for the hardware protocol, see CIM Port 2

 bounded controller addresses for faster detection, see CIM Advanced

;

• CIM Port 2 can now be configured for speeds from 1200bps up to 19.2kbps, instead

of being fixed at 9600bps. This works for old CIM versions as well.

• Support for multiple remote callout sites. THS version 1.0 and 1.1 only support auto-

answer for a single site. A system with two CIM sites that can callout, would not work

correctly. This has been fixed by adding multiple sites to a single THS 2000 file. The

calling-in CIM is then identified from the loaded set of sites. See Site-list

Management.

• The MEC 20 digital fault labels that are disabled are blanked out in THS 2000. This

feature requires the latest version of the MEC 20.

• Improved communications reliability over noisy communication lines.

THS2000 version 3.1 adds the ability to connect directly to an RTU, bypassing the

CIM. A maximum of one RTU, MEC20 or TSC800, is allowed. The auto-answer

feature of THS2000 is not supported in this mode, as it is a function of the CIM. The

auto-discovery of controllers is likewise not available. See CIM Bypass Wiring

for a

wiring description.

1.3. Computer System Requirements

The supported operating-systems are:

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

• Microsoft Windows 95™, Service Release 2 or later;

• Microsoft Windows 98™;

• Microsoft Windows NT™ 4.0 Workstation or Server, Service Pack 3 or later;

• Microsoft Windows 2000.

A minimum of 2 MBytes of hard drive space on the chosen installation drive is necessary

for proper operation.

A modem that is fully supported by the operating-system is required for remote

operation. It is important that the correct modem driver software is installed correctly.

A FIFO-enabled serial-port is required for direct connections.

Microsoft Internet Explorer™ 4.01 or later is recommended for use with the on-line help.

However, Microsoft Internet Explorer 3.02 is sufficient if the hhupd.exe file, included with

the THS 2000 distribution, is run first; this executable is provided by Microsoft for

updating help file support.

1.4. Installation

The THS 2000 software consists of two files, the THS3v0.EXE file and the

THS3v0.CHM file. Both files should be copied to a directory on your hard drive, such

as C:\THS. The first file, THS3v0.EXE is the THS 2000 executable. You can make a

link to this file on your desktop by dragging and dropping the THS3v0.EXE from the

explorer to the desktop. The second file, THS3v0.CHM, is the on-line help file.

If you are using Microsoft Internet Explorer 3.02, the file hhupd.exe will be required to

execute and update a system file for HTML Help support. That file is not required if

Microsoft Internet Explorer 4.01 or later is installed.

2. Quick Start

This section will get you up and running the THS 2000 quickly and easily. This chapter covers

the simple tasks that are necessary to communicate with a site. More advanced topics will be

covered in a later section.

2.1. Step 1 Start THS 2000

Double-click on the THS 2000 icon

See Installation

(THS3v0.EXE) to start the program.

2.2. Step 2: Logon

The Password dialog box will appear as shown below. Type in your password and click

the OK button or just click the OK button if you have not programmed any passwords

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

yet. There are no passwords configured initially, so click on OK to continue if you are

running for the first time.

See Passwords

and Starting And Logging On.

2.3. Step 3: Set Host Connection Method

Select the Connect command from the Site menu (or toolbar button or press F9 ). This

command will normally bring up a list of accessible sites, however, if no sites are

defined, you will be required to choose a host connection method. This dialog box is

shown below.

Select your connection method, either a specific modem (e.g. Hayes Accura 288 V.34 +

FAX) or a serial port (e.g. Direct using COM1). If you select a direct communications

port, you are also able to modify the port settings. The default settings are likely

sufficient for now, so click the OK button.

See Host Connection

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

2.4. Step 4: Enter Site Properties

Once the connection method is established, you will be prompted for the site properties,

such as site name, as shown below. This allows you to enter the first site in the site-list.

The name and password fields correspond to the name and password already

programmed into the CIM that is managing the remote site. The description field is

optional and can be used to describe the site. The phone number is entered for a remote

site.

The name and password parameters must match the CIM on the intended site. The

default name is "site" and the default password is "user." These parameters are case

insensitive.

See Site Properties

2.5. Step 5: Connect To Site

The next dialog box displays the list of sites, as shown below. At this point, there is only

one site and it’s already selected. From this dialog you can add, remove and modify site

properties; modify the connection method; and connect to the selected site.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

Clicking on the Connect button will begin the connection process. If you experience

problems connecting to the remote site, please refer to the troubleshooting section of

this manual.

See Connecting A Site

2.6. Step 6: Identify Controllers

Once you are connected to the remote site, you need to identify the controllers on the

site. If you are running CIM 3.0 or higher, the THS 2000 software will offer the controllers

that have already been discovered, as shown below. You merely need to accept the

controller list to have them added to the site. If you are running an older CIM, you must

identify and add the controllers manually; see the Adding A Controller

section later in this

manual.

At this point, you are connected and communicating with the CIM and its controllers. The

status bar at the bottom of the window will flicker and display a message similar to

"Connected to EastWing."

2.7. Step 7: View Controller Data

A set of buttons at the top of the window will contain the word List and the number of

each controller. This is the Controller Bar. Clicking a button on the Controller Bar selects

the current view in the main part of the window. The list-view is a list of all the controllers

and the controller views are representations of an individual controller.

When the selected site is connected, the dot in the middle of the controller bar button will

indicate the status of the controller (green, yellow, red or black).

See Controller Views

2.8. Step 8: Issue Controller Commands

Once connected to a site, commands can be issued to controllers through the Mec20

Command or Tsc800 Command menu items under the Controller menu.

See Controller Commands

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

2.9. Step 9: Save/Restore Site-list Information

The current site-list can be saved by using the Save or Save As commands under the

File menu or the toolbar button.

A previously saved site-list file can be retrieved using the Open command from the File

menu or the numbered recent file list under the File menu or the toolbar button.

See Saving A Site-list

and Opening An Existing Site-list.

3. Configuration

The THS 2000 software allows the configuration of passwords, lists of sites, the

Communications Interface Module (CIM) and the auto-answer feature. Configuration of THS

2000 site-lists and other parameters is generally done once and then used many times in an

operational capacity.

3.1. Passwords

The THS 2000 program can be secured with the use of passwords. The password levels

are:

3.1.1. READ-ONLY

The read-only user can only monitor an RTU site and may not change any

settings or modes of operation.

3.1.2. READ/WRITE

The read/write user can monitor an RTU site and may change any settings or

modes of operation as desired.

3.1.3. MASTER

The master read/write user can monitor an RTU site and may change any

settings or modes of operation as desired. The master read/write user can also

view or modify the lower-level security passwords.

The Options item under the Tools menu will present the user with master security

level with a choice that allows the passwords to be modified, as shown below.

For a user with less than the master security level, that menu item is grayed-out.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

The site passwords are normally shown as a series of asterisks (*), but can be shown in

actual letters by enabling the show-site-password check box.

3.2. Site-list Management

THS 2000 allows you to create, save and reopen site-lists. A site-list is a

collection of one or more sites that are all accessed through the same host

modem. A site-list can also be configured for auto-answer, allowing any of the

listed remote sites to call THS 2000 in case of an alarm condition.

The list of sites, the site properties, the connection method and the auto-answer

settings are all stored in the .THS file. This file can be created, opened and

saved from THS 2000.

3.2.1. Creating A New Site-list

A new site-list can be created using the New command from the File menu (or

toolbar button). This command will bring up the Site Properties dialog, as shown,

for the first site in the site-list.

The name and password fields correspond to the name and password already

programmed into the CIM that is managing the remote site. All of the site names

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

within a site-list must be unique. The description field is optional. The phone

number is entered for a remote site.

3.2.2. Opening An Existing Site-list

An existing site-list can be opened using the Open command from the File menu

(or the toolbar button). This command will bring up the conventional Windows

dialog allowing you to select a file to open.

The File menu also stores the most recently used four site-list files. These can be

opened directly by selecting the file name from the File menu or using the

shortcut key sequence ALT-F followed by the number (1-4) of the desired file.

Note: files created by previous versions of THS 2000 can be opened, but they

will only contain a single site in the site-list. If this file is modified and saved, you

will no longer be able to open it from previous versions of THS 2000.

3.2.3. Saving A Site-list

A site-list can be saved to disk by using the Save or Save As commands from the

File menu (or the toolbar button). These commands will invoke the standard

Windows dialog for saving a file.

Note: files saved by this version of software will not be readable by previous

versions of THS 2000.

3.3. Site Configuration

Viewing and modifying the site configuration begins with the Connect item under

the Site menu. This action will produce the list of sites (see Site-list

Management), as exemplified in the following diagram. From this dialog box, new

sites can be added to the site-list

site's properties viewed or modified

viewed or modified.

, sites can be removed from the site-list or a

. The host connection method can also be

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

In addition, the site be connected (see Connecting A Site

) from this dialog.

3.3.1. Adding A Site

Electing to add a site by clicking the Add button of the Connect To dialog

box will present you with the Site Properties dialog box depicted in the

following figure. This allows you to enter the name and password of the

new site, which is the name and password of the CIM on that site. The

description can be any descriptive text. The phone-number can only be

entered for a host connection that is a modem (see Host Connection

The password field is normally shown as all asterisks (*), but can be

made to display the actual letters (see Passwords

3.3.2. Removing A Site

Clicking the Remove button of the Connect To dialog box will cause THS

2000 to ask you if you really want to remove the selected site. Choosing

the affirmative option will delete the selected site from the site-list.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

3.3.3. Site Properties

Selecting the Properties button of the Connect To dialog box will bring up

the Site Properties dialog box, as in section Adding A Site

details of the selected site, as shown here.

This dialog box can also be displayed by right-clicking on the name of the

site in the site-list dialog.

3.3.4. Host Connection

The host connection method can be changed from the Connect Using

command of the Site menu or the Connect Using button of the Connect

, but with the

To dialog box (see Connecting A Site

). This command will bring up the

Host PC Connection dialog box, as shown here.

In the list-box, you can select any modems or communication ports that

are recognized by the operating system. Modems can be added and

configured in the Modem entry in the Windows Control Panel (see the

operating system documentation).

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

In THS2000 version 3.1, an additional option allows THS2000 to bypass

the CIM and connect to a single controller, MEC20 or TSC800. For a

direct connection using one of the serial ports, the baudrate is

automatically set to 4800 to match a direct controller connection. The CIM

bypass mode does not allow THS2000 to receive alarm callouts from the

site.

If a direct communication port is selected, the Port Settings button will

click-able. Selecting the Port Settings button will bring up the Port

Settings dialog box, as shown below, where advanced communications

parameters can be viewed and modified.

Supported baudrates are 1200, 2400, 4800, 9600, 14400 and 19200. The

Restore Defaults button set the parameters to RS-232 signal type, no

parity, 8 data bits, 1 stop bit and 9600 baud.

The RTS activation is only applicable under RS-485. This defines the

level of the RTS line that is used by RS-232 to RS-485 converters to

signal a transmission. Unless otherwise specified, this should be active

high for most converters.

These parameters must be matched to the Port 2 configuration of the CIM

on the site (see CIM Port 2

Changes to the port settings do not take effect until the site is

reconnected.

3.4. Communications Interface Module Settings

The heart of communications to a remote site is the Communications Interface

Module (CIM). All the remote controllers, TSC 800s and MEC 20s, are attached

to this device. Normally, the CIM is not connected to the host computer. The

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

normal operation for the CIM is to poll the status of each controller and attempt to

discover new controllers. When the status of a controller indicates an alarm

condition, the CIM can be programmed to call the host and report that an alarm

condition exists.

When connected to a host computer running THS 2000, the CIM discontinues its

polling and allows the THS 2000 software to interrogate the controllers.

The CIM can be configured by selected the CIM Properties item in the Site menu.

This will bring up the Current Site Properties dialog box. This window is a tabbed

collection of dialogs that query and display different parameters from the CIM,

including the site information, version, port configuration and callout phone-

numbers.

When a value is modified, the Apply button will become click-able. Clicking the

Apply button will send the changes to the CIM; also, clicking the OK button will

send the changes to the CIM if you answer yes to the "save changes" question.

Hitting the Cancel button will abort any changes that have not yet been written.

After the new values are written to the CIM, they are read from the CIM and

displayed.

Some of the CIM's properties screens contain a Refresh button that will simply

re-read the data from the CIM.

For more information on the CIM, see Section 1

3.4.1. CIM Site

Selecting the CIM Site tab in the Current Site Properties dialog box will produce a

display similar to that shown in next figure. The F2 key (or the toolbar button) can

also be used to select the Current Site Properties dialog box. From here, you can

enter the site name and site password that will be used by the site connection

described in section Connecting A Site

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

The name and password fields have a maximum length of 16 characters and

case does not matter. CIM versions prior to CIM3.0 are limited to 12 characters

for the site name and 8 characters for the password.

Note: all CIMs that are intended for callout operation to the same site-list must

have unique site names.

3.4.2. CIM Version

The CIM Version tab simply reads and displays the version information, including

the serial number, from the CIM, as shown below. This may be useful for future

compatibility issues and service.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

Note: CIM version prior to version 3.0 did not have a serial-number or Modbus

support; these fields appears as N/A when communicating with one of these

older devices.

3.4.3. CIM Callout

The CIM Callout tab configured the callout feature, which allows the CIM to call

the host in case of an alarm condition. The dialog box is depicted in the next

figure. Refer to section Auto-answer Operation

for more information on CIM

callout and THS 2000 auto-answer features.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

Note: CIM versions prior to version 3.0 did not support the call-all-numbers

feature; this option is grayed-out for those devices. Also, in older CIM versions,

all the phone numbers shared the same number of attempts; this is reflected in

this dialog box by tying all there attempts choices together, so if one is changed

they are all changed.

3.4.4. CIM Database

All the properties of the CIM described in this chapter are stored in an internal

database. This database, and thus the CIM properties, can be reset to factory

default values by initializing the database. The command to initialize the

database can be found in the CIM Database tab of the Current Site Properties

dialog box, as shown here.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

This feature is provided as a last resort. It should not be invoked unless you

know what you are doing or you are under the guidance of a qualified service

person.

3.4.5. CIM Port 2

A CIM connected directly to a PC host or a Programmable Logic Controller (PLC)

is connected serially to Port 2. The serial connection parameters are under the

CIM Port 2 tab of the Current Site Properties dialog box, as shown here.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

The signal-type indicates the type of physical connection between the host and

CIM. The RS-232/Modem option indicates that a connection is via a standard

RS-232 cable or the internal modem (CIM Port 1). The RS-422 and RS-485

options are for multi-drop networks. The auto-detect option will allow the CIM to

attempt to decide for itself which physical connection is in use. The default

signal-type is auto-detect.

The other parameters are standard serial type parameters, including parity, data

bit size, stop bits and baudrate. The baudrate values can be 1200, 2400, 4800,

9600, 14400 and 19200. The receive-timeout parameter describes the amount of

time after receiving the last byte of the packet until the packet is processed

internally.

The Restore Defaults button will restore all parameters to their initial values,

which are no parity, 8 data bits, 1 stop bit, 9600 baud and 20 millisecond receive-

timeout.

The Fixed Modbus Mode option is for enabling the fixed Modbus mode for

operation with a Programmable Logic Controller (PLC). Once in fixed Modbus

mode, the CIM no longer requires a password to login, it is essentially always

logged-in to save the PLC from having to do so. All modem functions are

disabled when in fixed Modbus mode as well, to prevent unauthorized remote

access. The only way to disable fixed Modbus mode is to connect directly (via

RS-232 or RS-485) with THS 2000, which will disable fixed Modbus mode when

attempting to log in to the CIM.

Note: the receive-timeout and auto-detect signal-type features were not

supported in previous versions of the CIM and therefore their values appears

grayed-out and read-only when examined by THS 2000.

The protocol used on Port 2 is Modbus, as described in Section 3

3.4.6. CIM Port 3

The Port 3 of the CIM is used to communicate with the controllers on the site.

The parameters for this port can be found under the CIM Port 3 tab in the Current

Site Properties dialog box, as shown here.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

These values are all currently read-only; you may not change any of these

values, they are fixed.

3.4.7. CIM Advanced

The CIM Advanced tab of the Current Site Properties dialog box allows you to

change some of the more advanced features of the CIM, such as Modbus

characteristics and controller polling. The dialog box is shown in the next figure.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

The top box contains properties unique to the Modbus operation of the CIM (see

Section 3.

). The Slave ID is the ID used by the PLC to reference the CIM; the

valid range for a Modbus slave device is 1-247.

The Poll Bounds parameters are for changing the behavior of the controller

discovery polling. Controllers have an address range of 1 to 255, but there is a

limit of 10 controllers per site. The Poll Bounds parameters reduce the range of

addresses that the CIM must poll in order to discover new devices. Reducing this

range to the expected values of the controllers, such as 1 to 10, speeds up

response time.

The Response Delay parameter dictates the amount of time, in milliseconds, to

wait before sending a response.

Note: the advanced features described here are only supported in CIM version

3.0. When THS 2000 is communicating with an older CIM, the CIM Advanced

dialog box is not available.

3.5. Controller Configuration

This section deals with the adding and removing of controllers. The controllers

currently supported by THS 2000 and the CIM are the MEC 20 Microprocessor

Engine Controller and the TSC 800 Transfer Switch Controller.

3.5.1. Controller Discovery

The THS 2000 version 3.0 in conjunction with the CIM version 3.0 supports

automatic controller discovery. When THS 2000 establishes a connection to a

remote CIM, it interrogates the CIM for the list of controllers present on this site.

The user is then prompted to accept this list of controllers or continue with the

controllers already loaded.

Version of the CIM prior to version 3.0 do not support the controller discovery

and controllers must be added manually as explained in the next section (Adding

A Controller).

3.5.2. Adding A Controller

Selecting the Add option from the Controller menu allows you to add a MEC 20

or TSC 800 controller to the site from the Add Controller dialog box, as shown

below.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

The controller address can be between 1 and 255, with no duplicates allowed.

The controller type can be a MEC 20 or a TSC 800. The description can be any

descriptive text you wish.

3.5.3. Removing A Controller

Removing a controller is accomplished by selecting the Remove item from the

Controller menu which brings up the Remove Controller dialog box, as shown

below.

The controller to be deleted is selected from the list presented.

3.5.4. Controller Properties

A controller’s properties can be examined by selected the Properties item of the

Controller menu. This brings up a menu from which you can choose the

controller to be examined, as shown below.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

After the desired controller is selected and the OK button clicked one of two

dialog boxes is presented: one for the MEC 20 and one for the TSC 800. The

MEC 20 properties dialog box is shown in the following figure. From this window,

the description can be modified and other properties, such as the controller

address and the fault-labels, can be viewed.

The TSC 800 properties dialog box is shown in the next diagram. From here, the

controller description can be modified. Additional properties, such as the

controller address, can be viewed.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

3.6. Auto-answer Configuration

An important feature of remote modem sites is the ability to dial the host and

report an alarm condition. The host side can be configured from the Auto-answer

Settings command of the Site menu, as shown below.

When the auto-answer feature is enabled, the THS 2000 software will accept

calls from any site in the currently loaded site-list.

4. Operation

4.1. Basics

This section describes the basic functionality of the THS 2000 software, from

logging-on to user interface to accessing the online help. See the Quick Start

section for a fast get-up-and-running breakdown.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

4.1.1. Starting And Logging On

Double-clicking the THS 2000 icon

starts the THS 2000 software. A splash

screen indicating the version and related information is displayed for a short

period. You will then be prompted to enter a password, as below.

The THS 2000 log on process allows for three different levels of security,

depending on the password you entered. The levels are read-only, read/write

and master (see Passwords

for more information).

You also have the option of selecting "Demo mode," which allows you to create

some simulated controllers and otherwise operates as if you had "read-only"

security privileges.

4.1.2. The Interface

The main THS 2000 interface is shown in the next diagram. It is a relatively

standard Windows-based application with a title bar, main menu, toolbar and

status bar, as well as a controller bar and a special viewing area.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

4.1.3. Title Bar

The title bar displays the currently loaded site-list file. The site-list file is a

collection of one or more generation sites that has been configured and saved

previously. The site-list file can be opened, saved and printed from the main

menu or toolbar. The THS 2000 site-list files have the file extension .THS.

4.1.4. Main Menu

The main menu provides the access to the THS 2000 commands. Some

commands are available only under certain circumstances; when the command

is not available, it is grayed-out. For example, you will not be able to add a

controller (Add from the Controller menu) until you have created an initial site

(Connect from the Site menu or New from the File menu).

The main menu commands are also available using ALT-key combinations; the

underlined character indicates the key to press in combination with the ALT key.

Many of the important commands are available using function keys; these are

indicated in the pull-down menus.

4.1.5. Toolbar

The toolbar provides instant access to many important menu commands. When

the mouse pointer is floated over the tool item, a tool tip is displayed in the status

line portion of the status bar.

4.1.6. Controller Bar

The controller bar contains a button called List and a button for each controller on

the site. The controller buttons are labeled using the controller’s identification

number (id). Pressing a button on the controller bar will change the view to

display the selected controller or the controller-list view.

When the selected site is connected, the dot in the middle of the controller bar

button will indicate the status of the controller (green, yellow, red or black).

4.1.7. Status Bar

The status bar displays status messages and indicates connection status and

security status. The status line displays tool tips and various status messages.

The connection status indicates the state of the current connection, such as

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

"Idle" or "Connected to EastWing." The security status indicates with which

security level you have logged on.

4.1.8. View

The view area displays one of two different views. The list-view shows a tabular

list of the controllers on the selected site. The controller-view displays data from

either a MEC 20 or a TSC 800.

4.1.9. Accessing Help

The command Contents from the Help menu, the toolbar button or the F1 key will

bring up an online reference.

4.1.10. Exiting

The Exit command from the File menu will exit THS 2000, disconnecting any

outstanding connections.

4.2. Connecting Sites

A site is made up of a single CIM connected to one or more controllers. Connecting to a

site is the same as connecting to a CIM. From the user’s point of view, the CIM is the

site. This section describes how sites are connected and disconnected as well as

various properties of the CIM and the host connection.

Only a single site from the site-list can be connected at a time.

4.2.1. Connecting A Site

A site can be connected using the Connect command from the Site menu, the

toolbar button or the F9 key. This will bring up the Connect To dialog depicted in

the next figure.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

This dialog lists each site contained in the currently loaded site-list and allows

you to select the site to which a connection is desired. Clicking the Connect

button will initiate a connection attempt. In addition, double-clicking on the site

name will initiate a connection attempt.

In addition, sites can be added to or removed from the site-list or simply have

their properties modified. A button labeled Connect Using is provided to jump to

the host connection settings (see Host Connection

4.2.2. Disconnecting A Site

Selecting the Disconnect command from the Site menu, the toolbar button or the

F10 key will disconnect the currently connected site. This includes hanging up

the phone line for a modem connection.

4.3. Viewing And Commanding Controllers

The main function of the Communication Interface Module (CIM) is to facilitate

communication to the controllers present on the site. The controllers currently

supported by the CIM are the MEC 20 Microprocessor Engine Controller and the

TSC 800 Transfer Switch Controller. The main view of the THS 2000 provides a

simulated front-panel of a single controller.

Controllers can be added, removed and examined from menu commands.

4.3.1. Controller Views

The bulk of the THS 2000 window is the view area. This area can be a simple list

of the controllers or a more detailed representation of a single controller. The

controller bar buttons are used to select the desired controller or the controller-list

(see also The Interface

The controller bar contains a button called List and a button for each controller on

the site. The controller buttons are labeled using the controller’s identification

number (id). Pressing a button on the controller bar will change the view to

display the selected controller or the controller-list view.

When the selected site is connected, the dot in the middle of the controller bar

button will indicate the status of the controller (green, yellow, red or black).

The next figure shows the view of a MEC 20 connected to a remote CIM. The

MEC 20 indicates that it is currently in shutdown mode. The black part of the

view is generally the same as the front panel of the actual MEC 20 device. The

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

display and buttons work as it were the actual device. Additional information

includes the digital fault status and labels, analog fault status and present

measured values.

The figure below shows the view of a TSC 800 connected to a remote CIM. Just

as the MEC 20, the black part of the view is a direct emulation of the TSC 800

front panel. The faults and values are displayed and updated frequently.

4.3.2. Controller Commands

The controllers can also be commanded to perform control functions remotely.

The control functions can be found under the MEC 20 Command or TSC 800

Command items of the Controller menu. The controller in the current view is the

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

controller being commanded. The control functions available vary by type of

controller.

The commands available for the MEC 20 are shown in next figure.

The commands for the TSC 800 are shown in the next figure.

4.4. Printing

Using the print command (the Print item from the File menu or the toolbar button) while

viewing a controller will print the currently displayed values in a simple text format. The

print command will print the list of controllers when invoked while viewing the controller

list.

4.5. Auto-answer Operation

When a remote CIM senses that a controller desires a Callout, it will start the calling out

sequence. The CIM will dial its stored phone numbers some amount of times until it

makes a connection (see CIM Callout

exist in the site-list of the THS 2000 program.

PM055 Rev 2 00/08/31 Thomson Technology

). The site in which the CIM belongs must currently

SECTION 2 THS 2000 SOFTWARE PROGRAM

When an auto-answer connection is established, an event is registered in the Auto

Answer dialog box, as shown below, and logged in the auto-answer log file (see Auto-

answer Configuration).

When a site has connected, it will remain connected for two minutes just as if connected

by the operator. During this time, the operator can view the controllers and determine the

cause of the alarm. The status bar will also display a countdown of the remaining

connection time in seconds.

5. CIM Bypass Wiring

The CIM bypass connection mode of operation has a different wiring scheme than a standard

CIM connection. The two possible methods of connection are: direct--from computer to

controller and modem--from computer to local modem to remote modem to controller. The direct

connection bypass mode is shown below:

RS-232 RS-422

IBM Compatible

The modem connection bypass mode is shown below:

RS-232

NULL

Computer

Modem Modem

RS-232

RS-422

RS-232

RS-422

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 2 THS 2000 SOFTWARE PROGRAM

An RS-232 to RS-422 converter is required to convert the signal from the computer or modem.

The required wiring from the RS-422 side of the convert to the RJ-45 connection on the

controller is as shown:

RJ-45

To Controller

To modem or

computer

RS-232

RS-422

TDB(+)

TDA(-)

RDA(-)

RDB(+)

GND

Converter

unused

The RS-232 NULL connection between the modem and the converter must pass all handshake

signals, as shown in the following diagram:

Signal/Pin Pin/Signal

DB-9

RTS

Signal/Pin Pin/Signal

DB-25

RTS

CTS

DSR

DTR

GND

The modem must store configuration in a non-volatile storage medium (such as FLASH). The

modem must be configured for the following features:

PM055 Rev 2 00/08/31 Thomson Technology

• auto-answer,

• connect at 4800 bps only (no fallback),

• echo disabled,

• no error correction,

• no compression.

CTS

DSR

DTR

GND

CTS

DSR

DTR

GND

CTS

DSR

DTR

GND

SECTION 2 THS 2000 SOFTWARE PROGRAM

All RS-232 to RS-422 converters and modems are not created equal. Thomson Technology has

tested many converter and modem combinations and the recommended parts are: 3Com

USRobotics V.90 56K Faxmodem and B&B Electronics RS-232/RS-485 Converter Model

485PTBR (also an RS-422 converter). The modem must be configured prior to operation with

the DIP switches set to (DOWN is ON):

Switch

1 2 3 4 5 6 7 8

Position: DOWN UP DOWN DOWN UP UP UP DOWN

and the following initialization strings:

AT Q0 E0 V1 X4 &K0 &D0 &M0 &B0 &H0 &R1 &N4

AT S0=1

AT &W0

6. Troubleshooting

SYMPTOM CORRECTIVE ACTION

Cannot communicate with the site.

THS 2000 software locks up.

Unable to view on-line help: "The THS 2000 help file (THS3v0.chm) could not be located."

See the CIM User Manual Troubleshooting for possible solutions.

The Host software may lock-up if auto-answer mode is on when running in direct mode, the Host software is trying to write to a modem when it may not be present. The solution is to disable auto-answer (see Auto-answer Configuration

Check that Microsoft Internet Explorer 4.01 or later is installed.

Ensure that the THS3v0.CHM file is located in the same directory as the THS3v0.EXE file.

Unable to view on-line help: unable to load a file called hhctrl.ocx.

PM055 Rev 2 00/08/31 Thomson Technology

You need to run the hhupd.exe file included with the THS 2000 distribution diskettes.

SECTION 3 CIM PROTOCOL

SECTION 3

CIM PROTOCOL

1. Introduction

This protocol document is applicable to version 3.0 of the Communication Interface

Module (TTI).

The Communication Interface Module (CIM) provides the hardware and software

interface between a Modbus™ compliant master device (customer supplied) and the

specific Remote Terminal Units (RTUs) as used at a generator site.

The Remote Terminal Unit (RTU) in this context is a device which directly operates the

equipment at a generator site. These devices are the actual microprocessor-based

controllers as developed by Thomson Technology, Inc. and include the MEC 20 Engine

Controller and the TSC 800 Transfer Switch Controller.

NOTE: This instruction manual provides detailed information on the CIM 3.0 Modbus™

protocol. For detailed information on a the CIM 3.0 hardware and installation, see the

Section 1

program, see the Section 2

associated instruction manuals.

For more information on the Modbus™ protocol, visit the Modicon web site at

www.modicon.com

datalink layer and the application layer.

. For information on operation CIM 3.0 using the THS2000 3.0 software

. For more information on specific RTU devices, refer to their

. The communications protocol is split in to the physical layer, the

2. Physical Layer

At the Physical Layer, the CIM device is connected to a Modbus Master through CIM

Port 2 (DB-9 or RJ-45) which is configurable to RS-232/-485/-422 and up to 19200 baud.

The MEC 20s or TSC 800s connect to the CIM (Host) through an RS-422 interface via

an RJ-45 connector to CIM port 3b. Up to 10 remotes can be connected to a single CIM

(Host), as shown below:

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

The remote's receive lines are always enabled. The remote's transmit lines are only

enabled while transmitting.

There is no hardware flow control.

3. Datalink Layer

NOTE: Unless noted otherwise, all fields described in this document contain unsigned

binary data stored in big-endian (most significant byte first) format. Any unused fields

contain zeroes. When describing the fields, FALSE equals zero, and TRUE equals non-

zero.

At the Datalink Layer, the host (master) is responsible for polling the CIM's. The host

sends request packets to the remotes, and the remotes respond with response packets.

The CIM acts like a local host (master) to the MEC 20's connected. The CIM takes care

of gathering data from the individual MEC 20's and storing it in a local database. The

communication format describes an interface with the CIM database.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

Unfortunately due to processing limitations response packets from the CIM to the host

can have up to 25ms gaps in the data. The CIM response data is shifted out in 16

character increments, in some cases it can take up to 25 ms to shift out the next 16

character buffer.

The host pre-transmit delay is the minimum time required between the reception of the

last byte of a frame (response) and the transmission of the first byte of a new frame

(request). The following values show the necessary pre-transmit delays to insure reliable

transmission of data to the CIM.

baudrate delay(ms)

1200 130

2400 80

4800 40

9600 30

14400 30

19200 30

The typical CIM, MEC 20 and TSC 800 data is accessible through direct register read

and writes. Programming the CIM is done using the same protocol with the CIM ID

instead of the MEC ID.

4. Preset Multiple Registers (Type 16)

The preset multiple registers packet is used to write specific values to the controllers.

Numeric values are shown in hexidecimal.

Preset Multiple Registers Request

The packet format for this request is shown below.

ss 10 aaaa pppp bb rrrr . . . . rrrr cccc

MEC 20 ID (00 to FF)

aaaa

Starting register (4aaaa)

pppp

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

Number of bytes (register count x 2)

rrrr

cccc

CRC-16 (see CRC Calculation

)

4.1. Preset Multiple Registers Response

The response to this packet is shown below.

ss 10 aaaa pppp cccc

MEC 20 ID (00 to FF)

aaaa

Starting register (4aaaa, same number as the write packet)

pppp

cccc

CRC-16 (see CRC Calculation

)

4.2. Example: Remote Key Press Operation

SEND:

ss 10 0200 0001 02 kknn cccc

MEC 20 ID (00 to FF)

keystroke number

number of times to repeat keystroke

cccc

CRC-16

RECEIVE:

ss 10 0200 0001 cccc

MEC 20 ID (00 to FF)

cccc

CRC-16

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

It is also recommended to follow up with a Display Valid Flag read to

insure the operation was successful before proceeding. The CIM does

attempt multiple operations in the case of a bad packet. However, if the

Display Valid Flag is not valid after 900ms a retry should be performed.

5. Read Holding Registers (Type 3)

The read holding register request is used for read data from the controller.

Numeric values are shown in hexidecimal.

5.1. Read Holding Registers Request

Field addressing is done with the following format:

ss 03 aaaa pppp cccc

MEC 20 ID (00 to FF)

aaaa

Starting register (4aaaa)

pppp

cccc

CRC-16 (see CRC Calculation

5.2. Read Holding Registers Response

ss 03 bb rrrr . . . . rrrr cccc

MEC 20 ID (00 to FF)

Response Byte count (Register count x 2)

rrrr

cccc

CRC-16 (see CRC Calculation

5.3. Example: Read Registers 200 To 201

SEND:

)

ss 03 0200 0002 cccc

MEC ID (00 to FF)

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

cccc

CRC-16

RECEIVE:

ss 03 04 aaaa bbbb cccc

MEC ID (00 to FF)

aaaa

bbbb

cccc

CRC-16

6. Application Layer

At the Application Layer, the Master Controller sends request messages to the CIM's,

and the CIM's respond with response messages. Communication with the MEC 20's is

done using the MEC 20 ID and a typical Modbus packet, the CIM is transparent to the

protocol. The only time the user needs to be concerned with the CIM is when CIM

configuration parameters need to be modified. CIM communication is done with the

same Modbus packet using the CIM ID instead of the MEC 20 ID. In the case of the

same ID the CIM is smart enough to look at the registers requested to figure out whether

it is meant for a CIM or MEC 20.

The data block protocol from the MEC 20 will be described in the next section.

The CIM port configuration table is used to change the port type (RS-232/-485/-422) and

data protocol options such as baudrate, start bits, stop bits, and parity. The CIM port

configuration table consists of 2 records that define CIM port 2 and port 3 options.

All register values are in hexidecimal notation, with certain Modbus interfaces you may

be required to use a decimal value. In Modbus terminology a zero does not exist in the

decimal register list therefore many PLC/software interfaces may require you to convert

the Hex to decimal and then add one. (example 100Hex -> 257 not 256). The actual

packet will include the below listed value with the '4' chopped off. The 4xxxx is another

Modbus terminology that is not used in the actual protocol, only the lower 4 digits are

converted and used in the packet description.

Values in embolded typeface are the default values for their respective fields.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

7. Data Types And Formats

The following table describes the possible return data types and formats for Modbus

registers defined in the CIM.

A register data value consists of two bytes: the most significant (MSB) and the least

significant (LSB). Data values are arranged with the MSB first (called big-endian).

Data

Type

boolean 1

enum 1

uint8 1 0-255

uint16 1 0-65535

string n special

Count

Maximum

Range

0 or nonzero

0 to maxrange

boolean value: 0=false, non-zero=true

enumeration: range from 0 to some maximum

unsigned 8-bit integer (allowable values can be further limited)

unsigned 16-bit integer (allowable values can be further limited)

character (0-255) string, ordered: MSB1, LSB1, MSB2, LSB2, ...

structure; definition depends on register range;

struct n special

ordered: MSB1=byte0, LSB1=byte1, MSB2=byte2, LSB2=byte3, ...

8. CIM Port Configuration

Description

Field

Port#2 Bitrate

Port#2 Bits/char

Port#2 Stopbits

Port#2 Parity

Port#2 Rx Timeout

Port#2 Line Protocol

PM055 Rev 2 00/08/31 Thomson Technology

(decimal)

40257 100 1 enum

40258 101 1 uint8 7 to 8 (8)

40259 102 1 uint8 1 to 2 (1)

40260 103 1 enum

40261 104 1 uint16 0 to 65535 (20)

40262 105 1 enum

Address

(hex)

Count

Data

Format

Value

0=57600, 1=38400, 2=19200, 3=14400, 4=9600, 5=4800, 6=2400, 7=1200

0=Odd, 1=Even, 2=None, 3=Mark, 4=Space

0=RS-232, 1=RS-422, 2=RS-485, 3=auto-detect

SECTION 3 CIM PROTOCOL

Port#3 Bitrate

Port#3 Bits/char

Port#3 Stopbits

Port#3 Parity

Port#3 Rx Timeout

Port#3 Line Protocol

40289 120 1 enum

40290 121 1 uint8 7 to 8 (8)

40291 122 1 uint8 1 to 2 (1)

40292 123 1 enum

40293 124 1 uint16 0 to 65535 (40)

40294 125 1 enum

0=57600, 1=38400, 2=19200, 3=14400, 4=9600, 5=4800, 6=2400, 7=1200

0=Odd, 1=Even, 2=None, 3=Mark, 4=Space

0=RS-232, 1=RS-422, 2=RS-485

The Modbus Configuration table is used specifically to assign a node address (CIM ID)

to the individual CIM unit. This is used in multiple CIM configurations. The CIM's are

slaves to any device connected to Port 2. However the CIM acts like a Master to

anything connected to Port 3. Communication to the individual MEC 20's will be done by

communicating to the CIM.

9. CIM General Configuration

Field

CIM ID 40321 140 1 uint8 0 to 255 (1)

CIM response delay (ms)

40322 141 1 uint16 0 to 5000 (30)

Poll bounds 40323 142 1 struct see below

Call out enable 40324 143 1 boolean

Call out mode 40325 144 1 enum

The CIM ID is only used for programming CIM features, it is transparent when

Address (hex)

Data Format

Value

0=disabled, 1=enabled

0=connect once, 1=connect to all

communicating with MEC 20's or TSC 800's.

The Poll Bounds structure has the following format:

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

byte0 = upper bound; default 255

byte1 = lower bound; default 0.

10. CIM Passwords

Field

Site Name

THS mode password

Modbus mode password

4033740345

4034640354

4035540363

11. CIM Login

Field

Requested Link protocol

Requested Line protocol

40385 180 1 enum

40386 181 1 enum

Address (hex)

150-158 9 string

159-161 9 string

16216A

Address (hex)

9 string

Data Format

Value

max-length =18 bytes

Value

0=THS, 1=Modbus, 2=Fixed-Modbus

0=logoff, 1=RS-232, 2=RS-422, 3=RS485, 4=Modem

4038740395

18218A

9 string

max-length =18 bytes

12. CIM About

Field

TTI Device Type identifier

TTI 4 character device name

Call out requested 40420 1A3 1

Serial Number (64bit binary)

PM055 Rev 2 00/08/31 Thomson Technology

40417 1A0 1 enum TTI=0xC53A

4041840419

4042140424

Address (hex)

1A1-1A2 2 string

1A4-1A7 4 struct

Registe r Count

Data Format

boolea n

Value

max-length = 4 bytes; "CIM3"

1=call out requested

structure-length is 8 bytes; value is factory

SECTION 3 CIM PROTOCOL

set

THS software version (upper)

THS software version (lower)

THS protocol version (upper)

THS protocol version (lower)

Modbus software version (upper)

Modbus software version (lower)

Modbus protocol version (upper)

Modbus protocol version (lower)

40425 1A8 1 uint16 0 to 65535

40426 1A9 1 uint16 0 to 65535

40427 1AA 1 uint16 0 to 65535

40428 1AB 1 uint16 0 to 65535

40429 1AC 1 uint16 0 to 65535

40430 1AD 1 uint16 0 to 65535

40431 1AE 1 uint16 0 to 65535

40432 1AF 1 uint16 0 to 65535

13. CIM RTU List

Field

Reason for last callout

Slave 1 address and type

Slave 2 address and type

Slave 3 address and type

Slave 4 address and type

41281 500 1 enum

41282 501 1 struct see below

41283 502 1 struct see below

41284 503 1 struct see below

41285 504 1 struct see below

Address (hex)

Data Format

Value

0=RTU requested callout, 1=RTU removed, 2=RTU added, 3=bad slave response

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

Slave 5 address and type

Slave 6 address and type

Slave 7 address and type

Slave 8 address and type

Slave 9 address and type

Slave 10 address and type

41286 505 1 struct see below

41287 506 1 struct see below

41288 507 1 struct see below

41289 508 1 struct see below

41290 509 1 struct see below

41291 50A 1 struct see below

The slave address and type are encoded in the following 2-byte structure:

byte0 = slave type (0=none, 1=MEC 20, 2=TSC 800),

byte1 = slave address (0 to 255).

14. CIM Callout

Field

Phone Number 1

Callout attempts count 1

Phone Number 2

Callout attempts count 2

Phone Number 3

Callout attempts count 3

4153741553

41554 611 1 uint8 0 to 9 (3)

4155541571

41572 623 1 uint8 0 to 9 (3)

4157341589

41590 635 1 uint8 0 to 9 (3)

Address (hex)

Data Format

Value

600-610 17 string max-length = 34 bytes

612-622 17 string max-length = 34 bytes

623-634 17 string max-length = 34 bytes

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

15. MEC 20 Register Tables

Specific MEC 20 data is received by addressing the MEC 20 and accessing the

appropriate registers listed below. Using a MEC 20 address of "0" will cause all MEC

20's to respond to the request. This is usually reserved for communication with a single

MEC 20 with an unknown address. Otherwise MEC 20 addresses range from 1 - 255

however only 10 RTU's (MEC 20 or TSC 800) can be connected to an individual CIM.

Field

MEC 20 Key Press (write only reg)

MEC 20 Valid Data/Display

MEC 20 Version

MEC 20 Summary

MEC 20 Analog Group 0

MEC 20 Analog Group 1

MEC 20 Display Group 0

40513 200 1 struct

40514 201 1 struct

4051540527

4051840523

4052440530

4053140539

4054040547

Address (hex)

Data Format

202-204 3 struct

20520A

20B211

21221A

21B222

6 struct

7 struct

9 struct

8 string

Value

see MEC 20 Press

Key

see MEC 20 Valid

Data/Display

see MEC 20 Get

Version

see MEC 20 Get

Summary

see MEC 20 Analog

Values

see MEC 20 Analog

Values

length = 16 bytes; see

MEC 20 Display Details

MEC 20 Display Group 1

MEC 20 Fault Details

MEC 20 Digital Fault 1 Message

MEC 20 Digital Fault 2 Message

PM055 Rev 2 00/08/31 Thomson Technology

4054840555

4055640557

4055840565

4056640573

223-22A 8 string

22B-22C 2 struct

22D-234 8 string

235-23C 8 string

length = 16 bytes; see

MEC 20 Display Details

length = 4 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

SECTION 3 CIM PROTOCOL

MEC 20 Digital Fault 3 Message

MEC 20 Digital Fault 4 Message

MEC 20 Digital Fault 5 Message

MEC 20 Digital Fault 6 Message

MEC 20 Digital Fault 7 Message

MEC 20 Digital Fault 8 Message

MEC 20 Digital Fault 9 Message

MEC 20 Digital Fault 10 Message

4057440581

4058240589

4059040597

4059840605

4060640613

4061440621

4062240629

4063040637

23D-244 8 string

245-24C 8 string

24D-254 8 string

255-25C 8 string

25D-264 8 string

265-27C 8 string

26D-274 8 string

275-27C 8 string

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

MEC 20 Digital Fault 11 Message

MEC 20 Digital Fault 12 Message

MEC 20 Estop message

MEC 20 OverCrank message

MEC 20 OverSpeed message

MEC 20 LostSpeedSignal message

MEC 20 Under Volt message

4063840645

4064640653

4076940776

4077740784

4078540792

4079340800

4080140808

27D-284 8 string

285-28C 8 string

300-307 8 string

308-30F 8 string

310-317 8 string

318-31F 8 string

320-327 8 string

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

MEC 20 Over Volt message

MEC 20 Under Freq message

MEC 20 Over Freq message

MEC 20 Over Current message

MEC 20 Weak Batt message

MEC 20 Low Batt message

MEC 20 Hi Batt message

MEC 20 Low Temp

4080940816

4081740824

4082540832

4083340840

4084140848

4084940856

4085740864

4086540872

328-32F 8 string

330-337 8 string

338-33F 8 string

340-347 8 string

348-34F 8 string

350-357 8 string

358-35F 8 string

360-367 8 string

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

MEC 20 Hi Temp1 message

MEC 20 Hi Temp2 message

MEC 20 Low Oil1 message

MEC 20 Low Oil2 message

4087340880

4088140888

4088940896

4089740904

368-36F 8 string

370-377 8 string

378-37F 8 string

380-387 8 string

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

length = 16 bytes; see

MEC 20 Fault Details

16. MEC 20 Messages (Version 1.0)

The following sections describe in detail the data registers mentioned in the above

tables, for single byte data the actual byte location in the registers is included in the

above mentioned tables.

16.1. MEC 20 Press Key

This message is used to remotely press a key on a MEC 20's front panel.

Key press actions can be used to duplicate any local action on the MEC

20 device remotely. The key press sequences can be involved therefore it

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

is recommended to program the MEC 20's locally using the actual key

pad and display. The key press write message is described below:

Field Description

This field contains the key, as follows: 0 = Null (This value is used to get the characters displayed on the LCD without pressing any of the keys) 1 = Lamp test 2 = Silence horn 3 = Reset controller 4 = Escape 5 = Decrement

byte

6 = Increment

7 = Enter 8 = Manual 9 = Off 10 = Auto 11 = Test 12 = Emergency stop 13 = Escape from program menu 14-255 = Undefined

byte

This field contains the number of times the key is to be pressed.

The response message contains the current display contents.

16.2. MEC 20 Valid Data/Display

The Data/Display Valid byte is used to determine the following. If bit 0 is

set (1) then the Current Data in the registers is valid. If bit 1 is set (1) then

the Display Data is valid (i.e. the last Keypress command has executed

successfully).

16.3. MEC 20 Get Version

This message is used to get the version information from a MEC 20. The

request message does not have any data bytes. The response message

has the following data bytes:

Field Description

byte0 ***PAD***

This field contains the remote type, as follows:

byte1

0 = MEC 20 1 = TSC 800 2-255 = Undefined

byte2 This field contains the major MEC 20 message format version

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

number.

byte3

This field contains the minor MEC 20 message format version

number. byte4 This field contains the major software version number. byte5 This field contains the minor software version number.

16.4. MEC 20 Get Summary

This message is used to get the summary information from a MEC 20. The request

message does not have any data bytes. The response message has the following data

bytes:

Field Description

This field contains the summary bitmap, as follows: Bit 15 contains TRUE if a callout is required. Bit 14 contains TRUE if a shutdown is active. This bit is the equivalent of the Shutdown LED. Bit 13 contains TRUE if an alarm is active. This bit is the equivalent of the Alarm LED. Bit 12 contains TRUE if the speed signal is present. This bit is the equivalent of the Speed Signal Present

byte0, byte1

LED. Bit 11 contains TRUE if the engine controller is ready. This bit is the equivalent of the Ready LED. Bit 10 contains TRUE if the emergency stop is active. This bit is the equivalent of the Emergency Stop LED. Bit 9 contains TRUE if the horn output is enabled. Bit 8 contains TRUE if the remote start input is enabled. Bits 7-0 are unused.

This field contains the start mode, as follows: 0 = Manual

byte2

1 = Off 2 = Auto 3 = Load test 4-255 = Unused

This field contains the system status, as follows: 0 = Switch in off 1 = Switch not in auto 2 = Unit ready 3 = Start delay 4 = Crank period

byte3

5 = Rest period 6 = Bypass delay 7 = Unit running 8 = Cooldown

9 = Unit shutdown

PM055 Rev 2 00/08/31 Thomson Technology

10-255 = Unused

SECTION 3 CIM PROTOCOL

degrees Celsius, and

byte4, byte5

This field contains the system status timer value (in seconds).

This field contains the fault state bitmap. Each bit contains TRUE if the associated fault is active. The bits are defined as follows: Bits 31-29 are unused. Bit 28 is digital fault 12 (Fault name is programmable). Bit 27 is digital fault 11 (Fault name is programmable). Bit 26 is digital fault 10 (Fault name is programmable). Bit 25 is digital fault 9 (Fault name is programmable). Bit 24 is digital fault 8 (Fault name is programmable). Bit 23 is digital fault 7 (Fault name is programmable). Bit 22 is digital fault 6 (Fault name is programmable). Bit 21 is digital fault 5 (Fault name is programmable). Bit 20 is digital fault 4 (Fault name is programmable). Bit 19 is digital fault 3 (Fault name is programmable).

byte6 (MSB),

Bit 18 is digital fault 2 (Fault name is programmable). Bit 17 is digital fault 1 (Fault name is programmable).

byte7, byte8,

byte9(LSB)

Bit 16 is low oil pressure 2. Bit 15 is low oil pressure 1. Bit 14 is high engine temperature 2. Bit 13 is high engine temperature 1. Bit 12 is low engine temperature. Bit 11 is high battery. Bit 10 is low battery. Bit 9 is weak battery. Bit 8 is over current. Bit 7 is over frequency. Bit 6 is under frequency. Bit 5 is over voltage. Bit 4 is under voltage. Bit 3 is loss of speed signal. Bit 2 is over speed. Bit 1 is over crank. Bit 0 is emergency stop.

byte10 ***PAD***

byte11

16.5. MEC 20 Analog Values

Analog Group 0 Registers are described in more detail below:

Analog Group 0 Data

byte0, byte1

PM055 Rev 2 00/08/31 Thomson Technology

This field contains the EEPROM write count. This value is incremented each time the configuration information in the EEPROM is changed. The host uses this value to determine when the fault details may have changed.

Description

This field contains the analog values bitmap, as follows: Bit 15 contains TRUE if the engine temperature is in

FALSE if the engine temperature

SECTION 3 CIM PROTOCOL

is in degrees Fahrenheit. Bit 14 contains TRUE if the oil pressure is in KPA, and FALSE if the oil pressure is in PSI. Bit 13 contains TRUE if 3 phase mode, and FALSE if 1 phase mode. Bits 12-0 are unused.

byte2, byte3 This field contains the battery voltage (in tenths of volts).

byte4, byte5

byte6, byte7, byte8, byte9

byte10, byte11

This field contains the engine RPM (in revolutions per minute).

This field contains the run hours (in hours).

This field contains the engine temperature (in degrees Celsius or degrees Fahrenheit).

byte12, byte13 This field contains the oil pressure (in KPA or PSI).

Analog Group 1 Registers are described in more detail below:

Analog Group 1 Data

byte0, byte1

byte2, byte3

byte4, byte5

byte6, byte7

byte8, byte9

byte10, byte11

byte12, byte13

byte14, byte15

Description

3 phase mode: This field contains the phase AB voltage (in volts). 1 Phase mode: This field contains the phase AB voltage (in volts).

3 phase mode: This field contains the phase BC voltage (in volts). 1 Phase mode: This field contains the phase AN voltage (in volts).

3 phase mode: This field contains the phase CA voltage (in volts). 1 Phase mode: This field contains the phase BN voltage (in volts).

3 phase mode: This field contains the average of the phase AB, BC, and CA voltages (in volts). 1 Phase mode: This field contains the phase AB voltage (in volts).

3 phase mode: This field contains the phase A current (in amps). 1 Phase mode: This field is unused.

3 phase mode: This field contains the phase B current (in amps). 1 Phase mode: This field contains the phase A current (in amps).

3 phase mode: This field contains the phase C current (in amps). 1 Phase mode: This field contains the phase B current (in amps).

3 phase mode: This field contains the average of the

hase A, B, and C currents (in amps).

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

1 Phase mode: This field contains the average of the phase A and B currents (in amps).

byte16, byte17 This field contains the AC frequency (in tenths of hertz).

16.6. MEC 20 Display Details

The Display details are broken into 2 groups. Group 0 contains the 16 ASCII characters

from the top line of the MEC 20 display. Group 1 contains the 16 ASCII characters from

the bottom line of the display. There are to many individual display messages to list all of

them here, however some basic messages should be described. The 2 most useful

messages are "non-valid" and "valid". This is mainly used for confirmation that a

keystroke has been sent and received by the MEC 20 correctly.

Group 0

Field Description

byte0 to byte15

This field contains the ASCII characters from the LCD top line.

Group 1

Field Description

byte0 to byte15

This field contains the ASCII characters from the LCD bottom line.

16.7. MEC 20 Fault Details

DigFault 1 - 12 are user programmable (see the table MEC 20 Get Summary

, bytes 6 to

9 for fault descriptions), the fault name register can be read or written to any value up to

16 characters long. This must be done locally on the MEC 20's.

Fault Detail Registers are described in more detail below:

Fault Status Shutdown/Alarm

Description

This field contains the fault details bitmap, as follows: The bits contain TRUE if the fault is programmed as a shutdown, and FALSE if the fault is programmed as

byte0, byte1

an alarm. Byte 0 contains information for digital Faults 0 - 15 (Bit15 =#15, Bit0 = #0) Byte 1 contains information for digital Faults 16 - 28 (Bit12 =#28, Bit0 =#16)

The message format for all faults is shown below:

Fault Message Description

PM055 Rev 2 00/08/31 Thomson Technology

Description

SECTION 3 CIM PROTOCOL

byte0 to byte15

characters at the end of this field are padded with spaces.

17. TSC 800 Register Tables

Specific TSC 800 data is received by addressing the TSC 800 and accessing the

appropriate registers listed below. Using a TSC 800 address of "0" will cause all TSC

800's to respond to the request. This is usually reserved for communication with a single

TSC 800 with an unknown address. Otherwise TSC 800 addresses range from 1 - 255

however only 10 RTU's (TSC 800 or MEC 20) can be connected to an individual CIM.

[table 41025 to 41065]

This field contains the ASCII fault name. Unused

Field

TSC 800 Key Press (write only reg)

TSC 800 Valid Data/Display

41025 400 1 uint16

41026 401 1 uint8

Address (hex)

Data Format

Value

see TSC 800 Press

Key

see TSC 800 Valid

Data/Display

TSC 800 Version 41027-41029 402-404 3 struct

TSC 800 Summary 41030-41036 405-40B 6 struct

TSC 800 Analog Group 41037-41049 40C-418 13 struct

TSC 800 Display Group 0 41050-41057 419-420 8 string

TSC 800 Display Group 1 41058-41065 421-428 8 string

see TSC 800 Get

Version

see TSC 800 Get

Summary

see TSC 800 Get

Analog Values

see TSC 800 Display

Details

see TSC 800 Display

Details

18. TSC 800 Messages (Version 1.0)

The following sections describe in detail the data registers mentioned in the above

tables, for single byte data the actual byte location in the registers is included in the

above mentioned tables.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

18.1. TSC 800 Press Key

This message is used to remotely press a key on a TSC 800's front panel.

It is also used to get the characters displayed on a TSC 800's LCD. The

request message has the following data bytes:

Field Description

This field contains the key, as follows: 0 = Null (This value is used to get the characters displayed on the LCD without pressing any of the keys). 1 = Lamp test 2 = Previous 3 = Decrement

byte0

4 = Increment 5 = Next 6 = No manual test 7 = Manual offload test 8 = Manual onload test 9 = Escape from program menu 10-255 = Unused

byte1

This field contains the number of times the key is to be pressed.

The response message contains the current display contents.

18.2. TSC 800 Valid Data/Display

The Data/Display Valid byte (byte1, LSB) is used to determine the

following.

If bit 0 is set (1) then the Current Data in the registers is valid.

If bit 1 is set (1) then the Display Data is valid (i.e. the last Keypress

command has executed successfully).

18.3. TSC 800 Get Version

This message is used to get the version information from a TSC 800. The

request message does not have any data bytes. The response message has the

following data bytes:

Field Description

byte0 *** PAD ***

This field contains the remote type, as follows:

byte1

0 = MEC 20 1 = TSC 800 2-255 = Undefined

byte2

This field contains the major TSC 800 message format version number.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

byte3

This field contains the minor TSC 800 message format version number.

byte4

byte5

This field contains the major software version number.

This field contains the minor software version number.

18.4. TSC 800 Get Summary

This message is used to get the summary information from a TSC 800.

The request message does not have any data bytes. The response

message has the following data bytes:

Field Description

This field contains the summary bitmap, as follows: Bit 15 contains TRUE if a callout is required. Bit 14 contains TRUE if dual prime mode, and FALSE if standard mode. Bit 13 contains TRUE if Src2 prime, and FALSE if Src1 prime. Bit 12 contains TRUE if a transfer switch failure has occurred.

byte0,

byte1

Bit 11 is unused in standard mode. This bit contains TRUE if the Src1 Start output is enabled in dual prime mode. Bit 10 contains TRUE if the Src2 Start output is enabled. Bit 9 contains TRUE if the Src1 Pretransfer output is enabled. Bit 8 contains TRUE if the Src2 Pretransfer output is enabled. Bit 7 contains TRUE if the Src1 Transfer output is enabled. Bit 6 contains TRUE if the Src2 Transfer output is enabled. Bit 5 contains TRUE if the Load On Src1 input is enabled. Bit 4 contains TRUE if the Load On Src2 input is enabled. Bits 3-0 are unused.

This field contains the test mode, as follows: 0 = None 1 = Switch offload test 2 = Switch onload test

byte2

3 = Switch off 4 = Manual offload test 5 = Manual onload test 6 = Auto offload test 7 = Auto onload test 8-255 = Unused

This field contains the system status, as follows: 0 = Src1 start delay 1 = Src2 start delay 2 = Src1 warmup delay

byte3

3 = Src2 warmup delay 4 = Pretransfer delay 5 = Finding neutral 6 = Neutral delay 7 = Transferring 8 = Transfer failed, press lamptest

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

9 = Posttransfer delay 10 = Src1 return delay 11 = Src2 return delay 12 = Src1 cooling 13 = Src2 cooling 14 = Src1 auto, Src2 auto 15 = Src1 auto, Src2 failed 16 = Src1 auto, Src2 normal 17 = Src1 auto, Src2 offload test 18 = Src1 auto, Src2 onload test 19 = Src1 auto, Src2 ready 20 = Src1 auto, Src2 running 21 = Src1 auto, Src2 starting 22 = Src1 auto, Src2 switch off 23 = Src1 failed, Src2 auto 24 = Src1 failed, Src2 failed 25 = Src1 failed, Src2 normal 26 = Src1 failed, Src2 offload test 27 = Src1 failed, Src2 onload test 28 = Src1 failed, Src2 ready 29 = Src1 failed, Src2 running 30 = Src1 failed, Src2 starting 31 = Src1 failed, Src2 switch off 32 = Src1 normal, Src2 auto 33 = Src1 normal, Src2 failed 34 = Src1 normal, Src2 normal 35 = Src1 normal, Src2 offload test 36 = Src1 normal, Src2 onload test 37 = Src1 normal, Src2 ready 38 = Src1 normal, Src2 running 39 = Src1 normal, Src2 starting 40 = Src1 normal, Src2 switch off 41 = Src1 offload test, Src2 auto 42 = Src1 offload test, Src2 failed 43 = Src1 offload test, Src2 normal 44 = Src1 offload test, Src2 offload test 45 = Src1 offload test, Src2 onload test 46 = Src1 offload test, Src2 ready 47 = Src1 offload test, Src2 running 48 = Src1 offload test, Src2 starting 49 = Src1 offload test, Src2 switch off 50 = Src1 onload test, Src2 auto 51 = Src1 onload test, Src2 failed 52 = Src1 onload test, Src2 normal 53 = Src1 onload test, Src2 offload test 54 = Src1 onload test, Src2 onload test 55 = Src1 onload test, Src2 ready 56 = Src1 onload test, Src2 running 57 = Src1 onload test, Src2 starting 58 = Src1 onload test, Src2 switch off

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

59 = Src1 ready, Src2 auto 60 = Src1 ready, Src2 failed 61 = Src1 ready, Src2 normal 62 = Src1 ready, Src2 offload test 63 = Src1 ready, Src2 onload test 64 = Src1 ready, Src2 ready 65 = Src1 ready, Src2 running 66 = Src1 ready, Src2 starting 67 = Src1 ready, Src2 switch off 68 = Src1 running, Src2 auto 69 = Src1 running, Src2 failed 70 = Src1 running, Src2 normal 71 = Src1 running, Src2 offload test 72 = Src1 running, Src2 onload test 73 = Src1 running, Src2 ready 74 = Src1 running, Src2 running 75 = Src1 running, Src2 starting 76 = Src1 running, Src2 switch off 77 = Src1 starting, Src2 auto 78 = Src1 starting, Src2 failed 79 = Src1 starting, Src2 normal 80 = Src1 starting, Src2 offload test 81 = Src1 starting, Src2 onload test 82 = Src1 starting, Src2 ready 83 = Src1 starting, Src2 running 84 = Src1 starting, Src2 starting 85 = Src1 starting, Src2 switch off 86 = Src1 switch off, Src2 auto 87 = Src1 switch off, Src2 failed 88 = Src1 switch off, Src2 normal 89 = Src1 switch off, Src2 offload test 90 = Src1 switch off, Src2 onload test 91 = Src1 switch off, Src2 ready 92 = Src1 switch off, Src2 running 93 = Src1 switch off, Src2 starting 94 = Src1 switch off, Src2 switch off 95-255 = Unused

byte4,

byte5

This field contains the system status timer value (in seconds).

This field contains the fault state bitmap. Each bit contains TRUE if the associated fault is active. The bits are defined as follows: Bits 15-8 are unused.

byte6,

byte7

Bit 7 is Src2 over frequency. Bit 6 is Src2 under frequency. Bit 5 is Src2 over voltage. Bit 4 is Src2 under voltage. Bit 3 is Src1 over frequency. Bit 2 is Src1 under frequency. Bit 1 is Src1 over voltage.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

ge (

Bit 0 is Src1 under voltage. This field contains the fault visible bitmap. Each bit contains

TRUE if the associated fault is visible. The bits are defined as follows: Bits 15-8 are unused.

byte8,

byte9

This field contains the day of the week of the system time, as follows: 0 = Sunday 1 = Monday

byte10

2 = Tuesday 3 = Wednesday 4 = Thursday 5 = Friday 6 = Saturday 7-255 = Unused

byte11

This field contains the hour of the system time. Valid values are 0-59.

byte12

This field contains the minute of the system time. Valid values are 0-59.

byte13

This field contains the second of the system time. Valid values are 0-59.

18.5. TSC 800 Get Analog Values

This message is used to get the analog values from a TSC 800. The

request message does not have any data bytes. The response message

has the following data bytes:

Field Description

This field contains the analog values bitmap, as follows:

byte0, byte1

Bit 15 contains TRUE if 3 phase mode, and FALSE if 1 phase mode. Bits 14-0 are unused.

byte2, byte3

This field contains the Src1 phase AB voltage (in volts).

3 phase mode: This field contains the Src1 phase BC

byte4, byte5

voltage (in volts). 1 Phase mode: This field contains the Src1 phase AN voltage (in volts).

byte6, byte7

PM055 Rev 2 00/08/31 Thomson Technology

3 phase mode: This field contains the Src1 phase CA volta

in volts).

SECTION 3 CIM PROTOCOL

1 Phase mode: This field contains the Src1 phase BN voltage (in volts).

byte8, byte9

This field contains the Src1 frequency (in tenths of hertz).

byte10, byte11

This field contains the Src2 phase AB voltage (in volts).

3 phase mode: This field contains the Src2 phase BC

byte12, byte13

voltage (in volts). 1 Phase mode: This field contains the Src2 phase AN voltage (in volts).

3 phase mode: This field contains the Src2 phase CA

byte14, byte15

voltage (in volts). 1 Phase mode: This field contains the Src2 phase BN voltage (in volts).

byte16, byte17

byte18, byte19

byte20, byte21

byte22, byte23

byte24, byte25

This field contains the Src2 frequency (in tenths of hertz).

This field contains the load phase AB voltage (in volts).

This field is unused.

This field contains the load frequency (in tenths of hertz).

18.6. TSC 800 Display Details

The Display details are broken into 2 groups. Group 0 contains the 16 ASCII

characters from the top line of the TSC 800 display. Group 1 contains the 16

ASCII characters from the bottom line of the display. There are to many

individual display messages to list all of them here, however some basic

messages should be described. The 2 most useful messages are "non-valid" and

"valid". This is mainly used for confirmation that a keystroke has been sent and

received by the TSC 800 correctly.

Group 0

Field Description

byte0 to byte15

This field contains the ASCII characters from the LCD top line.

Group 1

Field Description

byte0 to byte15

This field contains the ASCII characters from the LCD bottom line.

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

19. CRC Calculation

The Cyclical Redundancy Check (CRC) calculation used by Modbus is commonly called

the CRC-16 algorithm. Refer to A Painless Guide To CRC Error Detection Algorithms

Ross N. Williams for more detailed information; using the terminology of that paper, the

CRC algorithm used by the CIM is:

Name : "CRC-16"

Width : 16

Poly : 8005

Init : FFFF

RefIn : True

RefOut : True

XorOut : 0000

Check : BB3D

The following is a C code implementation of the CRC-16 method:

unsigned short CalculateCrc(unsigned char *pAddress, int nByteCount)

{ unsigned short wCrcValue = 0xffff;

while (nByteCount--) { wCrcValue ^= *pAddress; for (int i = 0; i < 8; i++) { if (wCrcValue & 1) { wCrcValue >>= 1; wCrcValue ^= 0xa001; } else { wCrcValue >>= 1; } } pAddress++; } return wCrcValue; }

PM055 Rev 2 00/08/31 Thomson Technology

SECTION 3 CIM PROTOCOL

20. NOTES:

PM055 Rev 2 00/08/31 Thomson Technology

THOMSON REMOTE COMMUNICATION - V3.0, CIM 3.0 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual