CP30/G30/MC31 Firmware Service Update Version 2993 (19 Aug 2013) Release Notes

Transcription

1 CP30/G30/MC31 Firmware Service Update Version 2993 (19 Aug 2013) Release Notes Summary This package contains updated firmware for the Kingfisher CP30/G30/MC31 modules. Note: This firmware should be used with Toolbox PLUS+ Version or later. Upgrade Procedure First, upgrade Toolbox PLUS+ to the latest version ( or later). Then run Toolbox PLUS+, connect to the target module, and select Download > Firmware. It is recommended that all CP30 and MC31 modules in an RTU should be upgraded to the same firmware version. The standard upgrade package firmware2993.tgz contains updated firmware, Linux kernel and bootloader. The latter two components will be automatically upgraded if required. For G30, use firmware2993_g30.tgz. A firmware upgrade will delete all files from the RTU, including any user logic and logged events. The currently loaded configuration and RTU settings (e.g. IP address) will be preserved. Change Descriptions The following sections summarise the changes made in each production release and service update since production release Version 2597 (5-May -2011). describes new functions or capabilities that have been added to the firmware. These will normally have no effect on existing functionality, unless specifically noted. refer to changes that have been made to existing functionality. Any potential incompatibilities (for example, changes that may be required to project files) will be highlighted in the individual entries. are corrections or improvements that have been made because the previous behaviour of the firmware was incorrect or sub-optimal. Any potential incompatibilities resulting from these fixes will be highlighted in the individual entries. Note: This release has undergone functional and regression testing using our standard test environments. However, every RTU application is different. We recommend that any new firmware version be tested with your application before deployment. CP30/G30/MC31 Firmware 2993 Release Notes 1

2 Version 2993 Service Update (19 Aug 2013) Incorrect DNP3 time setting procedure was used when a slave serial DNP3 device responded with a NEED_TIME indication to a poll from the RTU. (#899) Incorrect MC31 firmware version shown in system logs (#734) Possible lockup when setting real time clock. (#408) Possible lockup in bootloader immediately after reboot (F1 LED on). (#212) Incorrect port number was sometimes used when using DNP3 over UDP (port 1024 rather than 20000), particularly when a shared IP address was configured. (#657) Possible CP30 restart when a number of comms messages are received in rapid succession (#975, bug introduced in version 2933). Possible CP30 restart when a number of comms messages are received in rapid succession on a serial port (#977). Improved performance of serial port when receiving large messages. Version 2981 Production Release (9 Jul 2013) It is no longer necessary to adjust the trigger execution timeout setting in redundant CP30 systems; if set, these settings will be ignored. On startup, the execution timeout is now set to fixed values of 500ms/10000ms for the primary/secondary CP30. Once the system is operational, the secondary CP30 timeout reverts to 500ms the same as the primary. Previously, the CP30 would fail to start if downloaded logic contained new function blocks that were not implemented by the firmware. The firmware will now ignore these function blocks. A warning message will be written to the system log. Improved service report format (diag.sh). Note that Toolbox PLUS+ Version includes a function to retrieve this report. When a DNP3 poll sent by the RTU was not answered, the next poll occurred after 10 seconds, even if the route timeout setting was set to a lower value. (#804) Potential issue with saving of diagnostic information on reboot. (#783) In redundant systems with long or variable cycle times, standby CP30 could sometimes incorrectly detect failure of the active CP30, resulting in both becoming active at the same time. (#117) CP30/G30/MC31 Firmware 2993 Release Notes 2

3 When powering up an RTU with redundant CP30s, in some cases the secondary CP30 (odd slot number) would become the initially active processor, rather than the primary. (#228, #809) The USER_RX function block did not properly clear the received data buffer. (#703) Possible lockup in bootloader immediately after reboot (F1 LED on) partial fix. (#212) DNP3 master no longer sends repeated disable unsolicited messages in the absence of an acknowledging slave device. (#722) KF_GET_COMM_STATS and KF_GET_PORT_STATS function blocks were not properly reporting errors. (#420, #121, #163) MC31 module disappeared from active CP30 s module list when configuration containing an MC31 serial port was loaded. (#696) Standby CP30 module could sometimes disappear from active CP30 s module list, resulting in the standby CP30 no longer being synchronised with the active. (#419) Version 2933 Service Update (29 Apr 2013) DNP3 event poll with qualifier 07 requesting a limited number of event Logs did not return requested events logs for each class. (#185) DNP3 master communications were using TCP when route was configured for UDP. (#654, bug introduced in version 2897) KF_RESET_MODULE function block did not work for MC31 module. (#652, bug introduced in version 2902) Possible DNP3 communications loss between master RTU and slave RTU following slave restart partial fix. (#657) Version 2927 Service Update (10 Apr 2013) The default setting for the syscontact SNMP variable is now RTU Administrator (#520). KF_MODULE_OK function block always returned FALSE for MC31 (#608, bug introduced in version 2902). No response was sent for SNMP requests containing multiple object identifiers (#599). CP30/G30/MC31 Firmware 2993 Release Notes 3

4 Possible CP30 restart when a large configuration loaded (#615, bug introduced in version 2918). The syscontact variable was not able to be set via SNMP (#520). After writing to unmapped floating point DNP3 analog output points, their flag field was being cleared (#627). Possible CP30 restart if message received for an unconfigured protocol, or in certain other error conditions (#624, bug introduced in version 2918) Version 2918 Service Update (21 Mar 2013) Added diagnostic logging for events such as port/protocol startup and termination, reboots, and resetting to the default configuration. Added a script (diag.sh) for collecting diagnostic RTU and system information, for use by the support team. If a port or protocol handler terminates abnormally, the system will no longer attempt to restart it. Instead, the RTU will be rebooted. (#528) Possible protocol handler crash on startup, especially if several protocols are enabled (#93) Incorrect handling of DNP link layer NACK received after sending a link reset request (#544) DNP3 slave can stop responding under heavy polling (#433) Possible Ethernet port handler crash if connection is closed during data transfer (#413) Port/protocol handlers were not always shut down correctly. (#496) Version 2902 Service Update (21 Feb 2013) Serial data format can now be configured for MC31 ports (requires Toolbox PLUS ) (#231) MC31 modules are now reported to Toolbox+ as "MC31" rather than "MC30/31" CP30/G30/MC31 Firmware 2993 Release Notes 4

5 Version 2897 Service Update (05 Feb 2013) Enabled Linux "date" command - can be used to read current date/time. Setting the time is not supported. Added script (format.sh) and utilities to allow a corrupted /usr partition to be reinitialised (#214). Improved synchronisation between firmware and Toolbox PLUS+ during firmware and configuration updates. RTU will now respond to requests from DNP3 master address 0 (#318) Possible lockup when setting real time clock partial fix. (#408) Incoming DNP3 polls were failing when RTU was configured to return unsolicited data (#99) Fixed polling of concurrent Modbus slaves where lower 8 bits of address are the same. (#427) Incorrect gratuitous ARP requests sent on startup, resulting in them being ignored. Reconnection following reboot may now be slightly faster. (#395) In firmware upgrade preinstall script, "serial" process is no longer killed, as its parent (kingfisher) will try to restart it. Removed routine debug port output for DNP3 and KF protocols (#230) Removed some spurious redirections of ssh/isagraf packets Incorrect error message in firmware updater Version 2879 Service Update (15 Nov 2012) IIN register for DNP3 now indicates the actual number of events yet to be sent to the master. Events in the current message are now counted as sent. (#311) Unsolicited DNP3 messages over UDP were always being sent to port They are now directed to the port from which the last poll was received. (#229) Added workaround for occasional failures seen when using T3 cards on MC31. (#134) MC31 sometimes incorrectly interpreted backplane messages from the CP30. This could cause the MC31 to be marked as absent, which in turn resulted in loss of communications on the MC31 ports. (#295) CP30/G30/MC31 Firmware 2993 Release Notes 5

6 Version 2874 Production Release (25 Oct 2012) Redboot and Linux flash partitions can now be updated during firmware upgrade. Feedback is now provided to Toolbox+ during firmware upgrade and configuration load. Added support for T3/A3 Ethernet option card. Added Chinese gas standard function blocks (GB/T and GB/T21446) MC-31: Multiple protocols are now supported on port 1. MC-31: Added support for Modbus ASCII. MC-31: Added support for KF_MODULE_RESET function block. Clock synchronisation: KF_RX_UPDATE_SINGLE will sync the clock on remote RTU if control bit 3 is set. The CP30 will also respond to a KF2 protocol time sync message. Allow configuration of MC-30 with external modem. Added support for multiple object identifiers in SNMP GET-REQUESTs RTU configuration (but not logic) is now maintained following firmware upgrade. (#223) Adjusted PLL settings (in Redboot and firmware) to improve reliability at low temperatures. Added support for hardware changes: new G30 OLED screen (flip display horizontally) and recent versions of Ramtron chip. Allow Modbus addresses to be 16-bit (although only lower 8 bits are used in protocol addresses) Allow zero length community name in SNMP SEND TRAP function block Any part of CP30 file system can be read via Kingfisher protocol. Writes are still restricted to /usr/kingfisher/var. Enabled DNP3 Secure Authentication aggressive mode Enabled keep-alive on slave Ethernet sockets, so that inactive clients are detected. (#120) Kingfisher protocol responds to standard system ID (0xAE) as well as configured system ID Modbus master requests can be sent to multiple slaves in the same logic cycle File system errors could cause CP30 to fail to restart (F1+F2 LEDs on). (#355) Incorrect number of events was returned for DNP3 class 1,2,3 poll with qualifier 07. (#185) Kingfisher protocol messages where the Destination and Via fields do not match the RTU address are now ignored. (#207) RS422 configuration information was not being correctly passed to the MC31. (#251) CP30/G30/MC31 Firmware 2993 Release Notes 6

7 DNP3 responses over UDP were being sent to incorrect port number. (#229) Crash when more than 30 changed Modbus registers are read from the RTU (#173,#194) During firmware upgrade, ensure that monitor process is stopped prior to stopping kingfisher process. One additional event was sent when fixed number of events requested from Toolbox+ (#60) AGA8 continued to return error values after error condition removed. (#91) Avoid queuing partial message when serial transmit buffer almost full Corrected DI-10 event retrieval to ensure the correct application of time stamps relative to last clock synchronisation Corrected UDP transport configuration for DNP3 (including for unsolicited messages) Corrections to the selection and re-use of DNP slave sessions when forwarding messages through an RTU, in particular routing between Ethernet and serial ports on the MTU. Ethernet DNP3 messages are now forwarded using the protocol type (UDP/TCP) configured in the route entry, rather than always defaulting to TCP. Fixed issue with DNP3 unsolicited reporting Some DNP3 tx messages were being incorrectly marked as "pending" (requiring timeout/retry) Delays could occur on Status dialog if no patches present on CP30. (#69) Discovery feature in Toolbox+ now works correctly. (#17, #177) Isagraf virtual machine could sometimes fail to start up properly when project is very large. For redundant CP30s, specified processor timeout now always overrides that calculated from configured cycle trigger time. G30 did not start up with firmware version 2676-OS6. (#65) Improved operation of file transfers using Kingfisher protocol. In KF_RX_DATA function block, a value of 0 was not updated on master RTU Incorrect status field in KF_GET_MODULE_OK for slots where no module is present Initialisation string was not set correctly for radio option cards KF_RX_UPDATE_SINGLE issues: incorrect status value, and CRC check error that was causing data block to be resent Possible MC-31 Ethernet port lockup when connection removed for > 2 minutes Modbus multiple write failure when values to be written are the same as current values. Possible Ethernet driver crash due to incorrect timer cleanup. Possible incorrect MC-30 operation when CP30 is configured as slave and master Possible crash if invalid address set in KF_SET_ROUTE function block. CP30/G30/MC31 Firmware 2993 Release Notes 7

8 SNMP writes to CP30 would sometimes fail. (#127) Some timeout calculations were incorrect, particularly for small timeout values. (#124) Subnet mask was not configured correctly on MC31. (#100) Class 1 trip/close DNP3 points were not generating event logs. (#165) Following changeover to standby CP30, MC31 was buffering messages received before being detected and reconfigured by CP30, which could lead to protocol errors. (#286) Protocol responses could be sent to incorrect port number following MC31 cable disconnect and reconnect, causing extended comms outage (#296) Version 2676 Production Release (7 Oct 2011) Addition of direct hardware support for DNP3 trip/close binary output model; Addition of support for DNP3 over UDP protocol; Addition of support for suppression of DNP3 message forwarding; Addition of support for limiting of DNP3 event queuing; Addition of support for Get Bulk requests by SNMP daemon protocol; Addition of support for clearing event logs on passive CP30 processor; Addition of support for selected block updates for Kingfisher RX Update operations; Addition of support for ISaGRAF Workbench on-line changes and debug operations through secondary Ethernet port; Update to IEC and IEC to permit multiple-master operations; Update to DNP3 support for Warm Restart and Cold Restart functions; Update to DNP3 point restart status bit assertion; Update to DNP3 message pending operations; Update to DNP3 point update process for master operations; Update to Modbus register update process for master operations; Update to serial modem handler for improved carrier detection; Update to Network Time Protocol (NTP) operations to additionally set hardware real-time clock; Update to synchronisation messages between redundant CP30 processors; Update to shared IP address functionality between redundant CP30 processors; CP30/G30/MC31 Firmware 2993 Release Notes 8

9 Correction to DNP3 binary input and binary output status reporting; Correction to DNP3 broadcast message functionality; Correction to DNP3 message parsing and session creation; Correction to Kingfisher RX Update memory block calculations; Correction to Kingfisher protocol system identifier matching; Correction to G30 power supply card checksum calculation; Correction to G30 analog output channel assertion on MX-3 I/O card; Correction to serial modem transmission inactivity and hang-up timers; Correction to serial loopback operations for RS-422/RS-485 operations; Correction to Option T2 Ethernet communication option board handler operations; CP30/G30/MC31 Firmware 2993 Release Notes 9