While you have to register to be able to leave a message on this board, you can always contact Eaton directly with your technical questions.

Technical Resource Center
The Technical Resource Center provides product selection, application and general technical support for Eaton electrical products:

To reach an EatonCare representative, please call: (877) ETN CARE or (877) 386-2273.

Crisis Response
7x24 emergency support: Web Site for more information.
North America: 1-800-498-2678

Power Quality (UPS, Air Flow Management, Rack Power Distribution)
Tech Support: Web Site for more information.

The typical method of programming the GPC was to use the software provided by Encorp.  This software connected to the GPC using the Lonworks LonTalk protocol.  Since LonTalk required an external converter (usually RS-232 to LonTalk twisted pair), some users requested an alternate method of changing setpoints that did not require the LonTalk gateway.

Since the GPC also included a Modbus RS-485 port and since many of the setpoints within the GPC were memory mapped within the Modbus register map, changing setpoints via Modbus is possible.

A simple program loader that used the Modbus protocol was developed that can be downloaded from http://www.pps2.com/communications/DGMonitor.htm. 

A user manual explaining how to use this software can be reviewed http://www.pps2.com/communications/files/DGHelp.doc.

The source code for the VB 6.0 application can be downloaded here:
http://www.pps2.com/communications/files/DGMonitorSourceCode.zip

Complete Cross Reference of LonWorks SNVTs to Modbus Registers used in GPC:
http://pps2.com/communications/files/GPC/rev2-0%20control%20variables.xls

(Limited) Cross Reference of SNVT to Modbus Register used in this VB Program:
http://pps2.com/communications/files/GPC/Tagname%20Cross-Ref.xls

As those who worked with with the HPPC 1500 or 1700 systems recall, the programming software and programming methodology are different for the HPPC compared with the PC700, 900, 1100 and 1200 processors.

Refer to http://www.pps2.com/communications/799.php and download the HPPC programming (APL or Advanced Program Loader) manual as well as the HPPC Systems Manual and the HPPC Systems Manual supplement for more information on those differences.

This forum provides technical information on connectivity, communications, software and systems integration regarding both current and legacy Eaton and Westinghouse communicating products.  It also includes general technical documentation about topics that I've encountered over my career.

After I retired from Eaton I took over the maintenance of this site.

You are encouraged to click around the board.  Use the search function to look up a topic. 

The button for search is at the top of each page.

We have switched off the acceptance of new member registration due to spam problems.  Sorry about that. 

If you have any questions, just message me via email or LinkedIn.

Dave Loucks
dgl@lec.engineer
https://lec.engineer
https://www.linkedin.com/in/dgloucks/

If you wanted to dig deep into the INCOM protocol, here are the detailed documents from the Eaton web site:

• IL 17384  Part A IMPACC Communications Standard
  http://www.eaton.com/ecm/groups/public/@pub/@electrical/documents/content/1030709222496.pdf
  (Note: 2011 Version of this document is available here.)
  
• IL 17384  Part B Metering Products
  http://www.eaton.com/ecm/groups/public/@pub/@electrical/documents/content/il17384b.pdf
• IL 17384  Part C Protective Relays and Trip Units
  http://www.eaton.com/ecm/groups/public/@pub/@electrical/documents/content/il17384c.pdf
  (Note: a more up-to-date version of the protocol document for the Digitrip 520MC and the Digitrip 1150 is attached below)
• IL 17384  Part D Motor Protection and Control
  http://www.eaton.com/ecm/groups/public/@pub/@electrical/documents/content/il17384d.pdf
• IL 17384  Part E Panel-Mounted Operator Interfaces http://www.eaton.com/ecm/groups/public/@pub/@electrical/documents/content/il17384e.pdf
• IL 17384  Part F Transfer Switches and I/O Devices http://www.eaton.com/ecm/groups/public/@pub/@electrical/documents/content/il17384f.pdf

Here's some more information on other INCOM networking devices:

• Modbus MINT Instruction Leaflet
  http://www.eaton.com/Electrical/USA/ProductsandServices/PowerQualityandMonitoring/NetworkingHardware/mMINT/index.htm
• Modbus MINT Application Note
  http://pps2.com/communications/files/INCOM/mMINT%20App%20Note%20R04.pdf
• Profibus MINT
  http://www.eaton.com/Electrical/USA/ProductsandServices/PowerQualityandMonitoring/NetworkingHardware/PMINT/index.htm
• DeviceNet PONI
  http://www.eaton.com/Electrical/USA/ProductsandServices/PowerQualityandMonitoring/NetworkingHardware/DPONI/index.htm
• Modbus PONI
  http://www.eaton.com/Electrical/USA/ProductsandServices/PowerQualityandMonitoring/NetworkingHardware/ModbusPONI/index.htm
• MINT (Modular INCOM Network Translator)
  http://www.eaton.com/Electrical/USA/ProductsandServices/PowerQualityandMonitoring/NetworkingHardware/MINTII/index.htm
• IPONI (INCOM Product Operated Network Interface)
  http://www.eaton.com/Electrical/USA/ProductsandServices/PowerQualityandMonitoring/NetworkingHardware/IPONI/index.htm

Changing Setpoints using INCOM Pass-Through on Modbus MINT
http://pps2.com/communications/files/INCOM/Modbus_INCOM_pass-through_V4.pdf

I've attached a link to a document that explains how to send INCOM commands through a Modbus MINT using something called INCOM pass-through.  The attached document includes example code written in VB2010, but the methodology would work for any programming language.  If you want a copy of the source code or the published (install files), you can download both from: http://pps2.com/files/mb/index1.php

The example I show is how to change a setpoint inside an automatic transfer switch controller (ATC-600 or ATC-800), but the method of writing an embedded INCOM message within the Modbus payload is the same.  Also, the method for changing setpoints within a device works with any INCOM device with a write-able setpoint buffer (e.g. OPTIM circuit breaker trip units, IQ/DT/MP/FP series protective relays, etc.)

In case anyone needed an overview of some of the common communications formats that Eaton uses, I've attached a PDF of a PowerPoint.

Click here to watch a get-started demo on how to use the NLSW-784 software: http://pps2.com/v/1/nlsw784_intro.php
(I hadn't used it in over 25 years so was a little rusty... as you'll see in my demo! )

In case anyone was trying to troubleshoot a ladder diagram from one of these processors and you were looking for information on what the special functions (TS, UC, LC, etc.) on the printout meant, you can download a copy of the 1200/1250 manual from http://www.pps2.com/communications/PC1200.php.

The PC700, 900, 1100, 1200 and 1250 shared the same programming language.  In fact, programs were portable to the extent that they could be downloaded from one and uploaded to another, just so long as the functions and/or I/O count you chose didn't exceed the limitations of a particular model of processor.  If you need a 700/900 Hardware / Systems Manual, you can download that at the end of this article.

Programming Software
You can also download a copy of the Numa-Logic programming software from https://app.box.com/s/9k64uda58uybr45xhjnh7xwj6uvzl58h.  Note that 783, 783U and 784 software were simply different combinations of options.  All versions performed ladder programming (both on and offline) within the PLC.  The ability to document those ladder diagrams with custom text was an optional feature of some.  See table below:

Westinghouse Catalog #	Programming	Document Ladder	Offline Utilities
NLSW-783	Yes	No	No
NLSW-783U	Yes	No	Yes
NLSW-784	Yes	Yes	No
NLSW-786	Yes	Yes	Yes

In addition to the "offline" utilities, Westinghouse offered an add-on program called WHO (Westinghouse Help Outline) that provided online utilities.  These included:

• Ability to remotely start and stop the PLC over the network
• Advanced programming, tuning and visualization for the PID function in the PLCs
• Search for used coil references
• Search for used special and literal functions
• Connect to a remote PLC via dial-up modem
• Connect to a remote PLC via the PC1100/1200 LAN

... and many more.

WHO was a TSR (terminate and stay resident) program that was loaded under DOS before starting the NLSW ladder programming programs.  When resident, WHO would monitor certain keys (see help files at http://pps2.com/files/nl/) and "pop up" when those keys were triggered.

To use this software you needed a computer that could run (or emulate) an IBM PC running MS-DOS.  Because NLSW was written in 8088 assembly language, it wrote directly to hardware ports on the computer to control video, keyboard and serial port.  Regarding serial ports, your computer running the NLSW software needs an EIA-232 port (either actual or emulated via USB or Ethernet terminal server) to connect to the Numa-Logic PlCs.  Many companies sell USB to EIA-232 converters for computers, so you many need to purchase one if your computer does not include a 232 port built in.  Another option for obtaining a 232 serial port is to connect a terminal server to the PLC and then connect the PLC to Ethernet.

Note that the 232 port pin-outs vary by device.  On the Numa-Logic PLCs, 25-pin ports were used on the CPUs and they were wired as DTE (Data Terminal Equipment, meaning data output on TxD pin 2, data input on RxD pin 3, etc.)  Your computer (or 232 adapter) will almost certainly have a 9-pin port, and it too will be wired as DTE, although the pin numbers for a 9-pin 232 port are different than a 25-pin 232 port.  The table below gives the pin names and numbers for both 9 and 25-pin ports.

You will need a 9-to-25 pin "cross-over" or "null-modem" cable to connect between your computer and the PLC.  Refer to Section 4 and Appendix E of http://www.pps2.com/communications/files/NumaLogicCommOverview.pdf for more details on the EIA-232 pinout for these PLCs.  Pay particular attention to the fact that the PLC 232 port pins 5 (Clear to Send) and 6 (Data Set Ready) must be high for the PLC to respond to any message.  These "modem control signals" are used to buffer traffic over ports that may become congested and the receiving device (a modem, usually) needs to tell the data terminal to stop sending data.  For a direct connection to a PC this is not a problem.

The simplest method of insuring pins 5 and 6 are high is to jumper pin 4 (Request to Send) to pin 5 (Clear to Send) and separately jumper pin 6 (Data Set Ready) to pin 20 (Data Terminal Ready) on the PLC.  Likewise, the NLSW-784 software honors those signals on the 9-pin side too.  Some software packages (but not NLSW784) required that the computer's Data Carrier Detect (DCD, pin 8 on a 25-pin port or pin 1 on a 9-pin port).  An example of such a cable appears here:

For the Numa-Logic to PC connection, the PLC 25-pin side of the cable needs to be a female connector.  The PC 9-pin side of the cable also needs to be a female connector.

---

9-pin EIA-232 Port (configured as DTE and usually male connectors on device requiring female cable connector)



   
   
   
   
   
   
   
   
   
   

Pin No.	Name	Dir	Notes/Description
1	DCD	IN	Data Carrier Detect. Raised by DCE when modem synchronized.
2	RD	IN	Receive Data (a.k.a RxD, Rx). Arriving data from DCE.
3	TD	OUT	Transmit Data (a.k.a TxD, Tx). Sending data from DTE.
4	DTR	OUT	Data Terminal Ready. Raised by DTE when powered on. In auto-answer mode raised only when RI arrives from DCE.
5	SGND	-	Ground
6	DSR	IN	Data Set Ready. Raised by DCE to indicate ready.
7	RTS	OUT	Request To Send. Raised by DTE when it wishes to send. Expects CTS from DCE.
8	CTS	IN	Clear To Send. Raised by DCE in response to RTS from DTE.
9	RI	IN	Ring Indicator. Set when incoming ring detected - used for auto-answer application. DTE raised DTR to answer.

25-pin EIA-232 Port (configured as DTE and usually male connectors on device requiring female cable connector)



   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   

Pin No.	Name	Dir	Notes/Description
1	PGND	IN	Protective ground.  Cable shield connected here.
2	TD	OUT	Transmit Data (a.k.a TxD, Tx). Sending data to DCE from DTE.
3	RD	IN	Receive Data (a.k.a RxD, Rx). Arriving data from DCE.
4	RTS	OUT	Request to Send.  Raised by DTE when it wishes to send.  Expects CTS from DCE.
5	CTS	IN	Clear to Send. Raised by DCE in response to RTS from DTE
6	DSR	IN	Data Set Ready. Raised by DCE to indicate ready.
7	SGND	-	Signal ground / common for all other signals.
8	DCD	IN	Data Carrier Detect. Raised by DCE when modem synchronized.
9	+	OUT	+VOLTAGE.  Defined but typically not implemented.
10	-	OUT	-VOLTAGE.  Defined but typically not implemented.
11	-	-	Unassigned pin.  No connection.
12	sDCD	IN	Secondary Data Carrier Detect (or Received Line Signal Detector)
13	sCTS	IN	Secondary Clear To Send.
14	sTD	OUT	Secondary Transmit Data (sTxD).
15	TSET	IN	Transmitter Signal Element Timing.
16	sRD	IN	Secondary Received Data (sRxD).
17	RSET	IN	Receiver Signal Element Timing.
18	LL	OUT	Local Loopback.
19	sRTS	OUT	Secondary Request To Send.
20	DTR	OUT	Data Terminal Ready.  Typically raised when the data terminal (PC or PLC) is powered and ready.
21	RL	OUT	Remote Loopback.
22	RI	IN	Ring Indicate.  Raised by DCE and sent to DTE to tell DTE to get ready... a call is coming.
23	sCTS	-	Data Signal Rate Selector. Can sent by either DCE or DTE.
24	ETSET	OUT	External Transmit Signal Element Timing.
25	TM	IN	Test Mode.

Modems
If connecting a program loader through a modem, that modem will almost always have its 232 port wired as DCE (Data Communiations Equipment).  When the original 232 standard was written, 232 was envisioned as a short distance (50 feet max.) cable that would connect DTE (computers, printers, etc.) to DCE (modems).  The plan was to use a straight-through 25-pin to 25-pin cable to connect DTE and DCE devices together.

9-pin EIA-232 Port (configured as DCE and usually female connectors on device requiring male cable connector)



   
   
   
   
   
   
   
   
   
   

Pin No.	Name	Dir	Notes/Description
1	DCD	OUT	Data Carrier Detect. Raised by DCE when modem synchronized.
2	RD	OUT	Receive Data (a.k.a RxD, Rx). Transmitted data from DCE.
3	TD	IN	Transmit Data (a.k.a TxD, Tx). Data input from DTE.
4	DTR	IN	Data Terminal Ready. Raised by DTE when powered on and monitored by DCE.
5	SGND	-	Ground
6	DSR	OUT	Data Set Ready. Raised by DCE to indicate ready.
7	RTS	IN	Request To Send. Raised by DTE when it wishes to send. Monitored by DCE.
8	CTS	OUT	Clear To Send. Raised by DCE in response to RTS from DTE.
9	RI	OUT	Ring Indicator. Raised by DCE when incoming ring detected - used for auto-answer application. DTE raises DTR to answer.

25-pin EIA-232 Port (configured as DCE and usually female connectors on device requiring male cable connector)



   
   
   
   
   
   
   
   
   
   
   

Pin No.	Name	Dir	Notes/Description
1	PGND	IN	Protective ground.  Cable shield connected here.
2	TD	IN	Transmit Data (a.k.a TxD, Tx). Sending data to DCE from DTE.
3	RD	OUT	Receive Data (a.k.a RxD, Rx). Data sent from DCE.
4	RTS	IN	Request to Send.  Raised by DTE when it wishes to send and monitored by DCE.  DCE sends CTS in response.
5	CTS	OUT	Clear to Send. Raised by DCE in response to RTS from DTE
6	DSR	OUT	Data Set Ready. Raised by DCE to indicate ready.
7	SGND	-	Signal ground / common for all other signals.
8	DCD	OUT	Data Carrier Detect. Raised by DCE when modem synchronized (carrier detected).
20	DTR	IN	Data Terminal Ready.  Typically monitored by DCE to answer phone when raised by DTE.
22	RI	IN	Ring Indicate.  Raised by DCE and sent to DTE to tell DTE to get ready... a call is coming.