CP-11-T3 Version 1.45e (released 19 April 2013)
Summary
This package contains updated firmware for the Kingfisher CP-11 processor modules.
Highlights of this release include:

T3 performance improvements.
Note : Firmware version 1.45e is functionally the same as Beta Version 0.46d (4-Feb-2013). The only
change made to the firmware was the version number to indicate that this version is now an official
release.
IMPORTANT: This firmware does not support older T Ethernet option board and also does not
support CP-10.
-
Version 1.45a is the last firmware version that supports the CP-11 with T Ethernet option
board.
Version 1.44f is the last firmware version that supports CP-10. CP-10 does not support T3
Ethernet option board.
These older firmware versions are available from downloads section of the CSE Semaphore
web site.
Upgrade Procedure
Run Toolbox32, connect to the target module, and select Utilities > Advanced > Download CPU
Firmware.
Select the firmware file V145e.h32 to continue with the firmware download.
A firmware upgrade will delete any user logic, logged events and user configuration. Only the
configuration of the first 4 ports will be retained, to enable communication to be established with
the target after firmware download.
Change Description
The following is a summary of the changes made since version 1.45d (26-Jun-2012).
New functionality

None.
Changes

T3 performance improvements.
Fixes

Correction to T3 operation when ports 2 & 3 are both using T3 option cards and communicating
simultaneously. (#446)
Page 1 of 18
Version 1.45d, released 26/6/2012

Corrections to prevent event log corruption/loss when using T3 option card to retrieve logs.

Corrected Kingfisher protocol transfer over T3 using the via field.
Version 1.45c, released 27/3/2012

Minimum PostTx Timeout for socket closure on T3 port changed from 10 to 1 sec.

Added re-intialisation of sockets on postTx timeout. They were being closed on timeout, but not
made available for subsequent communication.

Added support for #YPINACT on T3 ports.
Version 1.45b, released 27/3/2012

Added T3 Support; no longer supports T.

CP-10 no longer supported.
Version 1.45a, released 1/12/2011

Last version that supports Option-T Ethernet in CP-11.

CP11 ethernet ports can now be reset on port 2 and 3 by setting bit 7 and 8 in the mode register
respectively.

Blockreq task now resets the EXECUTE flag so the task will be re-triggered at a later stage. This
prevents for example DNP3 tasks to be left unprocessed.

The message protocol analyser tried to decode messages as Modbus protocol when the port
protocol was set to DNP3 and the Modbus driver was loaded. Valid Kingfisher and DNP3
message which were preceded by one noise character were likely to incorrectly be decoded.
Noise characters are most likely to happen on radio and leased line links.

Made ethernet MAC addresses unique for redundant processors for CP10/11 and CP21.

Added mode bit (=12) that controls if Kingfisher messages should be relayed out of the same
port (when set no relay).

Added Support for IO-5 module and AO-3 module

If socket is Force Closed, then re-initialise socket to prevent FIN-ANK Flooding

Increased TCP timeout to 1000ms and only 2 retries to handle 3G modems
Version 1.44f, released 6/12/2009

Last version that supports CP-10 hardware.

When more than 4 sockets are in use, force close (Fin-Ack), the oldest active socket prior to reuse for RTU originated new socket connections.
Page 2 of 18
Version 1.44e, released 23/10/2009

Turn Off Loopback Mode always to enable RS485 to work in 4 wire mode. (does not require GND
connection)

If an MC-11 has a Line-2 option card, then CP-11 would not send a Carrier Tone via the Line-2
option card. Is now added in.
Version 1.44d, released 06/10/2008

Implemented fix for FIN-ACK flooding when using Ethernet option-T cards.
Version 1.44c, released 24/07/2008

Fixed Mbus init&resp,S2 over Ethernet when used as responding device.

Fixed Mbus slave protocols over Ethernet, broken as result of 1.44b changes.
Version 1.44b, released 20/06/2008

Modified the Rx Ethernet to discard packets that contain more than 1 valid kingfisher message.
Version 1.44a, released 02/05/2008

Increased timeout for SS_RADIO ports to allow for large packets to be received

The Status Flag of RX_UPDATE single was not always being set when the message failed. Now
fixed.

Increased the limit of messages to a RTU at a time from 2 to 4. This is to allow for the handling of
multiple messages using DNP3 protocol.

Block Message pending bits (port and link) were not cleared properly after a block message was
withdrawn. This is now fixed.
Version 1.43f, released 16/10/2007

Removed Anti-Reset Windup features from the existing PID function block that were added
previously

Created a new function block PID_ADV to support the Anti-Reset Windup features.

Added support for the Genisys Master protocol driver. Must be used with Toolbox V1.46a.

Added support for the Genisys Slave protocol driver via MC-11.

Added #YPSTrr.12 to control UDP destination port.
#YPSTrr.12 = 1 auto assigned destination port.
#YPSTrr.12 = 0 destination port fixed according to port protocol.
Version 1.43e, released 20/06/2007

Added support for the Conitel slave protocol driver. Must be used with Toolbox V1.45f.
Page 3 of 18
Version 1.43d, released 12/06/2007

Paging: Changed handling of pager messages to prevent transmit message buffer overflow from
occurring.

Ethernet: The Post TX parameter under Module Port Configuration can be used to adjust the
socket timeout to a user-defined value of between 1 and 600 seconds.
Version 1.43c, released 09/05/2007

RxUpdate: Changed handling of dial retries and message fail, so that an RxUpdate message is
failed when all PSTN dial retries have failed on the first message in the RxUpdate sequence.
Previously dial retries would be repeated for each message in the RxUpdate sequence.

Added support for Anti-Reset Windup features in the standard PID function block.

Added support for new GPRS2 driver and port. GPRS2 is required for Wavecom GPRS modems
with latest firmware.
Version 1.43b, released 25/01/2007

Added support for new Tandberg TT4030 protocol driver.

Corrected the initialisation of the RS485 port. Previously it would not receive until it had
transmitted.

Ethernet: Added flag to check for port enabled status before re-initialising the port after a
physical disconnect/reconnect.
Version 1.43a, released 21/12/2006

Changed UDP to always send/receive using port 473. To allow for more flexible ethernet
operation with routers and redundant links.

Bug fix: modified watchdog code to prevent warm starts when loading ladder files greater than
400kB.
Version 1.42f, released 22/08/2006

An RTU will only use the "Reply" socket IP address/port numbers, to communicate with another
RTU, whilst the valid attempts is less than 3. When 2 attempts to send a message fail, then the
"Reply" socket information will be made invalid for future use.
Version 1.42e, released 17/07/2006

Added Monitoring of LINK Status from Option T Ethernet board.

The RTU port register Link status (#YPSTnn.07) was changed to match the Ethernet physical LINK
status.

When RTS is on, then enable loopback mode (DTR on). When RTS is off, then disable loopback
mode (DTR off).
Page 4 of 18

When the initialise bit is set for an RTU in the network list (#YLSTxxx.11), it indicates that the
existing socket needs to be closed and a new socket must be initialised. This feature allows a
user to force the RTU to use an alternative socket (redundant path).

The RTU will send any reply messages to RTUx on the socket that last received a message.
Version 1.42d, released 09/02/2006

Added support for the new GPS_NMEA protocol.
Version 1.42c, released 06/12/2005

Added extra delay before daughterboard detection to allow boards with processors enough time
to startup after CP is powered up mainly Bitbus boards.
Version 1.42b, released 01/09/2005

If the reply message returned to an RX-UPDATE (or similar type block) message, was a "NO
ACCESS" message, the reply was accepted but no further data was processed and the
RX_UPDATE sequence froze. Now a "NO ACCESS" message is flagged like a failure.

Added error messages when data structure sizes (port list, network list, etc) are incorrect.

Improved analyser code so that characters that do not belong to any protocol message
(according to RTU) are sent in separate message to Toolbox as the characters which are part of a
protocol message. Each protocol message is sent to the Toolbox in separate message. This helps
the Toolbox to display the received data in the same way as the RTU is interpreting it.

Created support for SS_RADIO on MCx port and updated the SS_RADIO code.

RS485: Improved accuracy of post-tx for RS485 ports. Accuracy is now 1 millisecond.

RS485: Fix for receiving the last character sent back:
After last TX interrupt the RX-interrupt is not directly enabled. It is now re-enable when
transmitter is switched off (after post-tx). Receive buffer is cleared than first to remove any
characters we have received back.

Added functionality to allow resetting of CPU serial port.

Increased startup delay before detecting option board.

Improved timing of analysing received character strings and of comms analyser messages.

The function to convert a floating point variable to a long (or integer) value in the ladder logic is
fixed

Implemented system register RTUTYPE for PC-1, CP-1, SBX, CP10 and CP21. This field worked
only for LP1 and was otherwise left 0.

Ensured the working of the AGA8 detailed calculation

Checked that the new image capture card worked OK.
Page 5 of 18
Version 1.42a, released 05/04/2005

Ladder logic would not run and MCx modules would not work in previous version when
processor was in even slot.
Version 1.41f, released 31/03/2005

Added support for Spread Spectrum radio option board.

CP10 ethernet. Polling with DNP3 address 0 was no longer working (broken since V1.41d).

CP10 UDP ethernet: RTU would not respond correctly when IP address or IP port of remote
device was changed on the fly (for example if STANDBY SCADA would take over). RTU now
handles randomly changing IP addresses.

Created millisecond field for ladder processing (#YMSEC). Derived from hundredths field to keep
it in sync with other clock registers. Resolution is therefore 10msec.

Relaying RTUs would change the KF2 clock synchronisation messages. This could result in clock
sync failure or larger clock synchronisation inaccuracies

RTU could flag IOBUS failure inappropriately.
Version 1.41e, released 13/01/2005

CP10 ethernet: fixed problem with OPENMODBUS. Citect would generate error and loose
communication after some time period.
Version 1.41d, released 17/12/2004

GPRS: Fixed problem where certain messages were not sent correctly across GPRS link.

PSTN: RTU would not dial if 2nd character in string was bigger than 250. (only potential problem
if protocol is not Kingfisher Series II, Modbus or DNP3).

Fixed some minor redundancy issues:
-
When CPU restarts into master mode it clears the message buffer.
-
When standby processor looses contact with duty processor, it takes over but it now
assumes there is no standby processor anymore. It used to assume that the previous duty
would have become the duty.
-
Fixed problem where CPU would remove itself from backplane.

CP10 ethernet: added support for OPENMODBUS. Initiating and responding.

T-option (CP10): fixed problem where it was not possible to establish an ethernet connection on
some networks (for timing reasons?). This problem was introduced in V1.41c.

T-option (CP10): fixed problem where randomly a lot of ethernet messages were sent.
Version 1.41c, released 29/09/2004

Implemented userdefined protocol as driver. TX-USER will now also work when the port protocol
is not set to USER_DEFINED. In that case all characters received while message in pending are
processed by the user defined protocol driver.
Page 6 of 18

Ability to have than one DNP3 session running on a CP10 ethernet port.

Improved prioritised scanning of I/O modules. If only one medium priority module was available,
the scanning process would stall and the module would not be scanned.

T-option: Keeps processing other ports when trying to establish or close an ethernet connection.

T-option. Finding new socket is performed from last to first so first socket stays reserved for
example Series II protocol when using DNP3.

T-option. If ethernet link is instigated, source port address is set to a number between 2000 and
2100.

T-option. If port pre-tx is set to 1,2 or 3, this is the number of sockets is reserved for incoming
socket connections (listen mode). The remaining sockets can be used for outgoing connections.

T-option: ethernet chip sometimes reports incorrect receive pointers. This could lead to port
lock up.

GPRS: Fixed sending messages bigger than 300 bytes (DNP3 frames with extra insert characters).


Version 1.41b, released 23/08/2004


Redundancy:
-
Made backplane polling more robust.
-
Improved checking for other duty at startup.
-
Added continuous checking if there is more than one redundant duty active.
NOTE: Redundacy not recommended with CP10 processors. CP11 processors are more robust.
Version 1.41a, released 17/08/2004

CP10 ethernet redundancy. Ethernet port on redundant processor will shut down (be disabled)
when configured to.

AI-10 is reconfigured when 2 comms failures occur in a row (power reset and old AI-10 firmware)
or when the AI-10 has its re-initialise bit set (AI-10 version 3 and later). This is done to prevent
the situation where the AI-10 looses its configuration (power down) but this is not noticed by
the RTU.

When entering the monitor mode, the RS485 transmitters on backplane buses are stopped.

Fixed download firmware across network link. Worked last in version V1.40a.

When new driver was downloaded, memory behind driver in flash memory(= other driver) was
corrupted if distance from end of driver till end of sector was bigger than 64K.

Never send an RTU restart message out of an ethernet port.

Redundancy driver is now merged into firmware. So firmware can be remotely downloaded
when RTU has redundancy.
Page 7 of 18

The redundant processor swaps when its logic is invalid instead of disabled. This change
prevents the processor from swapping when new logic is being downloaded or no logic has yet
been downloaded.

Enable Logic will return negative acknowledge received when no ladder present.

LED C will toggle when module is in redundant standby (slave) mode.

When a 1 is written to system register red_startup, the module will startup in redundant mode,
for the 1st startup.

Redundancy: Increased standby (slave) update rate.

Fixed problem with preserving IP address when downloading new firmware across network link.
IP address was lost\corrupted if address of IP address info was changed between new and old
firmware.

clock sync: made new S2 clock sync function backwards compatible with old MCx firmware.
Meaning: If MCx firmware 1.41 or older is loaded in an MCx module through which a clocksync is
performed, this new firmware will still perform a fairly accurate clock sync.
Version 1.40f, released 29/07/2004

Put extra delay in before daughterboard detection so modules with processors have enough
time to boot when CP module powers up.

Added support for TRIO E-series radio driver
Version 1.40e, released 12/07/2004

Improved GPRS interface.
-
Defined new port status bit INITIALISE (#YPSTpp.11). When set the GPRS modem will be reinitialised.
-
Time to perform redial if previous dial fails is now randomised. This should prevent situation
where RTUs are dialling each other at the same times and therefore failing (GPRS and PSTN).
first re-dial between 15 and 75 seconds after last attempts.
2nd re-dial between 15 and 75 seconds + 1 minute after last attempt.
3rd re-dial between 15 and 75 seconds + 2 minutes after last attempt.
etc.

Improved clock sync accuracy for series2 and DNP3 protocol on serial ports.

Fixed parity error detection on port 1 of CP10 processor.

Improved closing of sockets on T-option board.

The master processor will swap to redundant mode when its logic is disabled. A processor will
not enter redundant mode till it has been in control for at least a minute. This is done to prevent
the quick swapping of processors.
Version 1.40d, released 11/06/2004

Ethernet T-option board driver improvements.
Page 8 of 18

-
Under certain circumstances RTU could restart and corrupt its memory when connecting and
disconnecting to an ethernet network.
-
Fixed working of ethernet option board in PORT 3 of processor. Bug introduced in version
v1.40c.
-
Improved some time out values for ethernet option board.
-
Improved handling of very long ethernet messages.
-
Improved relaying kingfisher protocol messages through ethernet option board.
Running comms analyser on a remote RTU port where the report port is the same as the
analyser port is no longer allowed. Allowing this causes an avalanche of messages which cause
havoc of radio networks.
Version 1.40c, released 27/05/2004

Added support for Allen Bradley ethernet protocol (CSP). Port number is 2222.

Improvements to ethernet driver

Added GPRS support.

Fixed #YTICK.SEC and other timer ticks. They do not work properly when there is a I/O SCAN
INTERVAL configured. Introduced in version V1.40b.
Version 1.40b, released 20/02/2004

do not generate event logs from DI-10 events when no memory is configured for event logs.

Improvements to ethernet driver:
-
Improved general reliability.
-
Improved socket handling.
-
RTU now sends ARP message with MAC address at warm start.
-
Multiple messages can be simultaneously sent on ethernet port.
-
if UDP, the last socket now listens by default at port 473. This done so there is a kingfisher
UDP port available when port is configured with DNP3 protocol.

KF2 protocol support over CMDA. Must allow long inter-character delay on PSTN ports. Post-tx
delay is used as maximum inter-character delay (default 350msec).

RTU will wait 3 seconds (instead of 1.5) after initialisation command is sent to modem (CDMA).

When RTU is in secondary listen mode it should not process clocksync or master pager
messages.

When RTU is in primary standby mode, it will still accept reply messages from outstations. This
allows to still poll outstations.

Improved clock synchronisation accuracy using KF2 and DNP3 protocols especially across
ethernet link.

Redundancy:
Page 9 of 18
-
If bit 5 of the mode register is set, port 2 of the redundant processor is disabled.
-
If bit 6 of the mode register is set, port 3 of the redundant processor is disabled.

success counter no longer incremented when new network data block has been received. The
success counter was used to indicate to the SCADA system that new data for an RTU had been
received. #YLUPDrrr has taken over this function.

Message buffer full is set if message buffer is almost full. This flag is now set regardless what
type of messages are placed in message buffer.
Version 1.40a, released 01/12/2003

DNP3 is available on T Option.

T Option supports UDP and TCP/IP

If event logging on the DI-10 is enabled, event logs can be ignored by setting the matching
channel bit in AOxx.16 of the DI10 module.

Added support for LINE-2 HOT link port option (no Rx-LED support yet).
Version 1.39e, released 28/07/2003

Ethernet T-option functionality fixed in CP11.

If firmware is downloaded through network and RTU has reprogrammed itself, the RTU cold
starts directly because it cannot return to the (new) firmware.

Added support for different character formats for USER DEFINED protocol.
7/8 bits; no/even/odd parity; 1/2 stopbits.

If communication link was RADIO or Private Line, messages are delayed when Carrier Detect is
active. When reply message came in late and retry was about to be sent, a problem could occur
whereby the message was not deleted from the message buffer. This could lead to the
MSG_BUFFER_FULL flag to be set.
Version 1.39d, released 15/07/2003

Ethernet T-option board now supports client and server modes. Allowed for downloading
firmware through T-option. T-option currently supported on port 2.

Made some more improvements to the comms analyser.

Port protocol Modem Switch Unit on processor port is made useful for fast terminal interface
traffic.

fixed bug that could freeze processing of block message. #Ypstxx.9 could stay active.

fixed start-up problems of version V1.39c
Version 1.39c, released 17/06/2003

added support for DATRAN slave driver.

made improvements to analyser mode messages.

added support for PET and GSM paging on the MCx module.
Page 10 of 18
Version 1.39b, released 09/05/2003

RTS would sometimes stay on if posttx is 5msec or less.

increased delay after PSTN modem comes online after dialing from 1 to 3 seconds.

If processor is in redundant mode it will not send any carrier test commands to MCx modules.

fixed CP10 redundancy (redundant processor could corrupt itself).

#YLSTxx.2 (pending) could have been incorrectly set if RTU was routed through MCx port.

Improved internal handling of communication messages.
Version 1.39a, released 05/03/2003

Toolbox appends spaces behind phone numbers. Fixed code to cope with "NODIAL" phone
string.

Stricter handling of Series II protocol messages:
-
RTU will not relay messages via RTU 0 and will not relay messages on same port when via
RTU is 0.
-
removed code from Series II protocol for old Toolbox which swapped target and via RTU
message fields.
-
do not respond to messages from RTU 0.

configuration of I/O modules only happened after warm start. It did not occur when I/O module
appeared on backplane after initial start up scan.

implementation of Ethernet Option board for CP10
Supports : 10MB ethernet full duplex
Server mode only available in this release.
Exception reporting not supported, Poll only
Version 1.38c, released 13/01/2003

Implemented redundancy for CP11 module.

If primary phone number = "NODIAL", we will not hang up but maintain the existing connection.

Added optimised network register access by addding new selectable mode to allocate 16kB lookup buffer for network registers blocks.

Activate DTR by default on RS232 port.

Fixed initialisation of PS11 module.
Version 1.38b, released 20/11/2002

Implemented pager number (RIC codes) as strings. The pager number length configured
determines the number of characters send to the paging service. The maximum length is 14
characters.

Bug fix, caused CP10 processor board to occasionally reset multiple times before starting up
correctly. Bug introduced in V1.38a.
Page 11 of 18
Version 1.38a, released 29/7/2002

Support for new CP11 board (same PCB as CP21, with dual UART for backplane)

Fixup for UserDefined protocol functions:
if Rx message timed out, pending bit was never cleared.
NOTE: this firmware works for old CP10 boards and new CP11 boards, code dynamically detects
CP10/CP11 board, sets UART addresses accordingly
Version 1.37f, released 13/6/2002

Support for PS-11: send config data, and accept arbitrary size response to 'Get Analogs'
command

Better error checking on reply to SOE requests, we occasionally got spurious SOE logs when
switching off DI10 module

Define diagnostic word 2 in system registers

Define 'Enable Logic' bit first scan after logic enabled (by S2 msg)
Version 1.37e, released 23/5/2002

Allow for AI-10 configuration parameters
Version 1.37d, released 23/4/2002

Fixup for PowerDown mode: didn’t work for Port 2/3 CTS wakeup also, don’t assert RTS for ports
not selected for CTS wakeup

Fixup for analyser of DNP3 messages via MC ports, fixed Rx messages previously but not Tx
messages

Added I/O module configuration for failsafe for all Digital Output modules
(DO-2/5, IO-1, IO-2, IO-3)

Fixup for TxUser function: network regs, odd txcount, last char was missed

Rx/TxUser: allow indirect station address in local regs
Version 1.37c, released 6/3/2002

Implemented User-defined Comms Protocol (TxUser and RxUser ladder functions)

Fixup for framing of Rx DNP3 messages (caused problems on LOB2 boards, because they receive
noise chars when idle)

Reject noise chars from LOB2 boards discard if CD is not on

Faster scanning of DI-10 sequence-of-events: now happens every 500 mS

Fixup for analyser of DNP3 messages via MC ports

Fixup string to get into monitor mode => 'KF2MONITOR'
Page 12 of 18
Version 1.37b, released 28/11/2001

Added support for new Inline protocol.

Added support for new PS-10 module (v3) with battery charge control

Included Rx/Tx Single EventLogs, and EventLog statistics functions
Version 1.37a, released 19/7/2001

Added support for AI-10 module

Allow microtran protocol on CP10 port3

Made DI-10 counter registers writable from logic

New DI-10 SOE address mapping modes (allows event logs to be mapped to local registers)

Added DI-10 On/Off Status registers (these record changes-of-state on inputs, based on SOE
records)

Added support for prioritized scanning of I/O modules

Added collision avoidance for new Line Option Board (LOB-2) (wait for CD to drop before Tx)

Fixup for RS422 operation on ports 2/3 inhibits Rx while Tx active
Version 1.36f, released 06/04/2001

Fix up warm start resetting of dial-up option board (if &D2 configured)

Added code to handle configurable parameters for AI-4 module

Support for new Private Line / Radio Option Board (LOB-2)

Change to backplane comms structure for DNP3 messages
NOTE: DNP3 comms now requires MC1/MC10 firmware 128 or later
Version 1.36e, released 12/12/2000

Recompiled code with updated library files (affects dnp3 only).
Version 1.36d, released 15/11/2000

new GE-FANUC PLC SNP-X Driver

Fixup in Kingfisher FC48 for upload of PSTN list

new system log types : Battery Low/OK (for LP-1), Port Security Access
Version 1.36c, released 5/7/2000

redundancy does not work in version V136b. Fixed in this version.

fixup in start-up code, which could have caused firmware corruption after downloading
firmware

fixup timeouts on CM-bus for long DNP-3 messages

new AGA8_Detail driver
Page 13 of 18
v136b, released 9/5/2000

added support for DNP3 protocol.

Modbus implemented as driver and merged with INITIATING MODBUS driver.
Note: Modbus driver is now also required for responding to Modbus messages.

New: COMMS ANALYSER function (see Toolbox comms analyser/comms terminal).

Drivers can now also be downloaded in RAM. Driver must be downloaded after downloading
memory configuration with space for driver.

Improved clock sync function especially in relation to DNP3 clock synchronisation.

updated MC10 initialisation routine so module initilises PLINE attenuation factor after power up.
Originally a warm start command was needed to activate programmed attenuation factor
(especially on port 3).

RxUpdate function now supports 2048 local registers.
NOTE:
System register (register_blocks) must be set to ALL (ffff) in Toolbox. Then all 2048 local regs will
be updated, but hardware regs will NOT be updated in this case(there is a 32 block update limit
for every RTU).

All 2048 local registers are now updated in redundant processor (instead of only first 1024).

added extra software control of Line Option Board to prevent hardware lockup.

Minitran and Microtran protocol can now work with KF2 on the same port.
v136a, released 1/2/2000

added event log wrap-around counter to detect if event log buffer has been wrapped around.

added FRAME message. When sending a message in multiple frames, the retries are handled by
the BLOCKMSG sending the complete message. The RTU will send the first frame by setting up
the connection. Consecutive frames are sent direct without dialling. The last frame will be sent
and will wait for a reply. After each frame is sent, the BLOCKMSG is informed.

Timer register 63 was corrupted when one of the MC-1 ports was not configured in port list.

RTU did not learn with which RTU it is online with on port 3 of the CPU (PSTN).

KF2 protocol command Program Flash Ram can now be used for downloading firmware (across
network).

When an acknowledged is received from a Set Output Bit message to an outstation, the network
registers are updated. The update counter however was not. Update on Citect screen was
therefore very slow.

eliminated most communication error on CMBUS when using redundant processors. Receive
routine started waiting for command, even before command was sent and therefore sometimes
timed out.

Upgrades to Video Capture functions:
Page 14 of 18
-
added protection to check if RTU is really talking to a video board.
-
default picture quality is now set to 80 instead of 25.
-
added support for video module to work on MC-10 module.
v135f, released 20/12/99

Attenuation for Line Option Board now also works on MC10.

CP10 protected against downloading Firmware Module on incorrect address.

improved software interface to Line Option Board to prevent possible lock-up problems.

improved matching of received Kingfisher Series II reply messages with a message waiting for a
reply. The test is expanded with testing if the reply came in at the same port as it was sent out
of. This is done because a message can be send out on different ports to the same RTU
simultaneously (e.g. for communication path testing). By doing so the RTU sometimes
mismatched a reply with the wrong message causing a communication path to be flagged good
while it actually failed and vice versa.

prevented RTU from receiving back its own messages on a RS485 port.

Monitor Weather station protocol did not work on CP10 module. A Toolbox version of V1.35a or
later is required.

receiving messages on a processor port can be disabled by setting the initiating protocol to 100.
v135e, released 22/11/99

increased processing speed.

if a port higher than port 6 was used for Kingfisher Series II protocol, internal memory variables
could have been overwritten with various mysterious results. For example it could effect the I/O
scan rate, the ladder logic #YTICK pulses and CPU redundancy.

redundancy: improvements to updating event logs to redundant processor.
v135d, released 18/11/99

By default a Modbus Master RTU will reply with data for any RTU. A new option has been added
that when an RTU is configured with a system ID of 0 (in the network list) the Modbus Master
RTU will not respond for this RTU.

redundancy: first release for CP10 module. Implementation is fully compatible with CP1
redundancy except the port inactivity monitors are removed.

Failures on CMBUS were counted in system register which contains the IOBUS fail count.

Serial ports now work without errors at 57600 and 115200 baud.
v135c, released 11/11/99

improved speed reading/writing to network registers.

general improvements to initialisation of Line Option Board.
Page 15 of 18
v135b, released 29/10/99

Added functionality for DI-10 Module, Sequence-of-Events processing and Configurable IO
Modules.

Reduced maximum number of PIDs in ladder logic to 16.

added code to prevent RTU to respond to modbus messages when RTU is in Modbus initiating
mode only.

added initialisation functions to allow for different data formats (parity, number of data bits,
etc.) on the serial ports for the different protocols.

Fixed PSTN with external modem on serial board (problem created in V135a).
v135a, released 3/8/99

improved detection between serial and dial(pstn) board. Incorrect detection caused incorrect
working of CD-LED.

Line Option Board: When RTU was warm started while option board was transmitting port
would lock up.

Fixed problem that ladder logic or event logs could get corrupted.
v134f, released 28/6/99

Long messages on Port 1 could fail when data was received with inter-character delays.

If ladder was bigger than 32K and smaller than 64K the ladder size was calculated incorrectly and
RTU could lock up.
v134e, released 3/6/99

new protocol MODBUS ASCII initiating.

Communication functions as RX-UPDATE and TX-UPDATE that will generate multiple messages to
be sent will activate a bit BLOCK_PENDING (bit 9) in the port and network link status registers
(#YPSTpp.9 and #YLSTrr.9) to indicate they are active. RXUPDATE driver version 3 required to
work correctly.

2 new system registers added containing fail counters for IO and CM backplane buses.

allowed logic to be bigger than 64K.

DI-5 module count was reset after RTU came back from power down mode. Therefore the pulses
recorded in power down state were discarded. This problem occurred from firmware V132a.

outputs not sent to modules before ladder has been run, to prevent glitches on outputs on startup.

ladder functions: Tx Event logs, Rx Event Logs, Get Event Log Count and Set Event Log Pointer
are not by default included anymore from this firmware version onward. Firmware with the
above functions can be generated on special request.

fixed bug in TXIMAGES function.
Page 16 of 18

CP-10 Carrier detect for radio communication was inverted. No messages were sent out because
of this.

CP-10 Added code for RADIO_HOT option.

Power down mode is terminated after RTU has been powered down.

improved detection between serial and dial(pstn) board. Problems caused by incorrect detection
were CD LED did not work properly and port could lock up when characters received during start
up.

Fixed problem that Tx/Rx LEDs would stay on (Line option board).

slot address is updated regularly.

checked and enabled CP-10 drivers: INLINE, PAGING and SERIES1.

fixed code to send radio pager messages on MC-1 port.
V134d, reserved
v134c, released 5/3/99

fixed problem that certain modules did not startup properly and watchdog was triggered
continuously.

Implemented RS422 communications.

Implemented JZA protocol driver.

If no valid 12V or 24V is present the module will watchdog to prevent ram corruption.

Pre-tx on a PSTN port is now used as a delay before sending the first message after coming
online.

Block msg pending counter is reset on a warmstart (#YLSTrr.9 works properly).

Reply message is always placed in communication buffer. Even if there are already a lot of
messages pending to the target RTU.

Increased maximum nuber of messages pending to one RTU from 6 to 10.

Added safeguard to prevent communication buffer to be completely filled up by block messages
(they won't then be able to generate child messages and therefore lock up the communication).

Increased timeout to wait for message from MC-1. Prevents occasional communication failures.

Primary/secondary: Secondary master will relay messages to the primary when it is in listen
mode. When it is in control mode it will update its own data values.
v134b, released 28/1/99

updates for Video Daughterboard

the RTS is now dropped for 2 seconds if a PSTN modem does not disconnect after a ATH0
command. Guard time before "+++" expanded from 1 to 2 seconds.
Page 17 of 18

added extra code to improve handling of PSTN comms on MC-1 module.

disabled counting dial fails as message attempts fail.
v134a, released 18/1/99

First release for CP-10 module
Page 18 of 18