Udc3000 Manual

[Ilona Brownson]

Themix of Honeywell products and their protocols makes me think that someone might have attempted and then abandoned the project, given the mix of protocols. The absence of the program in the Basic module might disclose how the project actually got before being abandoned.

1. Pairing - High Limits

I suspect that one of the UDC's for each pair of controllers is a high limit controller for a temperature control loop. The fact that the comm cable only runs to the first controller in the pair confirms that.

a. UDC 500

The UDC 500 is way past its expected life span. It was obsolete when I started selling Honeywell in 1988. I only one I ever saw was one that was replaced in about 2004. If it still trips as a high limit, why not use it until it dies, but it could be lights out any day.

a. UDC 2300B

DC230H is a high limit version. DC230x-xx-1x had an "RS-485 ASCII/Modbus option". The ASCII is a proprietary ASCII protocol, not Modbus ASCII (106 page manual). The Modbus option was Modbus RTU. Very few sold with the comm option, even fewer implemented. No one ever implemented the ASCII version to my knowledge.

I know that a UDC 2500 UL-approved High Limit controller (Modbus slave) will not accept a Modbus "write" Function Code (FC 06) for the operating setpoint variable. One of the main operational uses in heat treat is to use a setpoint appropriate for the load for the high limit controller, but UL does not allow remote (comm) change of the operating setpoint. I never tested to see whether a reset function (to reset the latched output) could be implemented via Modbus (I see that there's an output override value at (4)0035 that might reset the output)

b. UDC 3000

The UDC3000 VersaPro (first generation) had one of two comm options, a proprietary DMCS protocol or communications RS-422/485, for another proprietary protocol with a 135 page manual. As a Honeywell distributor we were aware of a couple OEMs who used DCMS; but I never encountered anyone who actually implemented the none-DCMS proprietary protocol. That early, first generation model did NOT run the Modbus protocol.

c. CSP mode

For Modbus comm, the UDC used a "CSP" mode to accept remote setpoint writes to the UDC to save the EEPROM. The CSP mode held the remotely written setpoints in RAM and those updated setpoints were not written to EEPROM, because the EEPROM has a life-time limitation of the number of writes it could accept before bits failed. Anyone communicating setpoint ramp values should have used the CSP mode because the constantly changing setpoints could crash the EEPROM (which is the units firmware) in a matter of weeks.

3. DCP setpoint programmers

The DCP102 is either a Yamatake "setpoint programmer" (runs 1 of x internal preconfigured ramp/soak setpoint profiles and can run the associated PID control) sold by Honeywell as a private label or a Honeywell France import. I can't remember, but I suspect the latter because the configuration uses letters and truncated words, as opposed to Yamatake's love of numerical codes ("function 17" instead of "Inp 1 Type")

A DCP 100 spec sheet dated 1996 says, "RS485 ASCII serial communications", (which is table 4, code #1 in the model number). It is not likely to be Modbus ASCII. The user manual does not cover communications and I never had manual for the ASCII communications. A numeral 1 in the model number says that these DCP102 had the 485 ASCII comm card.

@DanW You were right on the money with everything basically. The project got delayed for several months and I've spent the 5 days worth of my time trying to get this system working with the ASCII format.

3a8082e126