140NOE77101 Firmware Executive Release Notes (V5.4-V6.7)

Click Now to Visit our 140NOE77101 Product Page.

 

V6.7

2/24/2016

Problem fixed / Enhancement

Details

• Improves Global Data and IO Scanner performance after a swap over in a Hot Standby System

• Removed a Remote Code Execution vulnerability in the websSecurityHandler (Advisory ICSA-15-351-01)

V6.6

10/19/2015

Problem fixed / Enhancement

Details

• Removed a web server vulnerability to a remote file inclusion attack. (ICS-ALERT-15-224-02)

• When using I/O Scanner control bits to turn On/Off I/O Scanner entries, it can intermittently cause the NOE to reboot causing a 20 second outage of Ethernet communications. Corrected the control bit disable feature from forcing the I/O Scanner state machine to finish.

V6.5

8/15/2015

Problem fixed / Enhancement

Details

• In a Hot Standby system, Global Data services may stop after a switchover of the PLC.
• Issue has been managed with updated code. Refer to the Global Data Addendum for further details.

Enhancement

• Resolves Java 1.8 issues.

V6.4

12/12/2014

Problem fixed / Enhancement

Details

• After an application download via Concept,the NOE77101 IO Scanner communications does not restart. In Unity PLC the NOE will ARP for DUP IP after every Application down load. In Concept the NOE will only ARP if the IP parameters have changed when Concept logs out. The Health Timeout timer is stopped on a Link Down,so the Health bits are not updated in the CPU. Now the IO Scanner Health Bits will go unhealthly on link down and not glitch on Link Up.

V6.3

9/5/2014

Problem fixed / Enhancement

Details

• MBP_MSTR block reports an error 1001 after an application download. During an application download, the IP component was temporarily applying the broadcast IP which disrupted the MSTR block. Code modifications were made and the MSTR block works as expected.

V6.2

6/30/2014

Problem fixed / Enhancement

Details

• In HTTP using directory traversals an attacker can bypass the basic authentication mechanism. (Advisory ICSA-14-273-01) Checks have been put in so that this is no longer possible.

• Web page issue with Java Version 1.7. Files did not have security signature. The Java dialog box provides a warning indicating that this is a unsigned application. The files all have been properly signed.

• On Hot Standby switchover, under extremely high traffic loads, there was a possibility that the NOE would not come online. Situation was corrected and the NOE comes online regardless of the traffic.

• With a Concept Hot Standby application, under unusual test conditions, there is a chance an NOE could lose its IP address. The NOE module will configure its IP address under those conditions.

• Quantum CPU may crash with error EC0E after completing a download of an application. Fixes a potential CPU EC0E crash issue where configuration data was not cleared when a smaller program was downloaded over a larger one that was previously installed. I/O Scanner configuration data is now cleared before the new data is downloaded and reconfigured.

V6.1

11/11/2013

Problem fixed / Enhancement

Details

• SNMP webFailedAttempts (1.3.6.1.4.1.3833.1.5.4) and webSuccessfulAccess (1.3.6.1.4.1.3833.1.5.4) do not The MIB structure and MIB Agent have been corrected. webSuccessfulAccess (1.3.6.1.4.1.3833.1.5.4) do not increment

• Client communications do not start on swap over in HSBY system On swap over, the communications now start as soon as possible after the switchover

• When Using code 15 in a MBP_MSTR function block the first Fixed the first request fault condition.

• When the IO Scanner breaks out FC23 to FC16 and FC3, any change to the data being written in FC16 will toggle between the old and new data for a number of scans. The function sends the correct data in all messages

• I/O scanner using a Radio Modem cannot establish contact. The timeout algorithm was adjusted to accomadate low communication data rates.

• Client communications do not start on swap over in HSBY system On swap over, the communications now start as soon as possible after the switchover

• After a cable pull, communications does not re-establish with certain Moxa or Sixnet switches Communications now resumes when the cable is reinserted.

V6.0

3/30/2013

Problem fixed / Enhancement

Details

• This is a special security release. The Unity configuration features listed require Unity hotfix V7.0_HF20050608

Enhancement

• The default behavior of enabled FTP/TFTP and HTTP Service at module boot up has changed On power up the NOE module will have the FTP/TFTP servers and HTTP service enabled when in non-configured mode, or when configured by an older version of Unity Pro/DTM that does not have FTP/HTTP Cyber Security control.
• Concept will not have any changes to enable/disable FTP/TFTP or HTTP in the configuration. When using Concept, both FTP/TFTP and HTTP will be enabled in the configuration at all times allowing MSTR to control the enable/disable of the services.

• The MSTR block now supports the OpCode 0xFFF0 to be used by the user to enable and disable FTP/TFTP and HTTP services in the module on-the-fly, when Unity has enabled the service.
• Once the enabled state of the services are changed by a MSTR they remain unchanged until the next MSTR block call with OpCode 0xFFF0, or the load of a new application, or the module is reset/power cycled . This OpCode works on Concept and Unity controller installations. In Concept the Web server/pages must be updated by the user to be able to control HTTP state of enable/disable, using the file NOE77101_WEB.zip. Bring the Web version up to V5.00 or above.

• New Log Out Web Page Users click on Diagnostics and go to Controller Status in the side menu. Below the applet is the logout button.

• Web Restrictions: When the FTP is disabled and HTTP is enabled there will be some Web restrictions as they require a FTP access.

• Data Editor/Viewer is not fully functional: the user does not have the ability to save or retrieve tables, or get variables from the namespace.

• When FTP/TFTP is disabled the corresponding ports 21(FTP), and 69(TFTP) are be closed . If the ports have an open connection when the MSTR is executed to disable FTP, the connection is be closed.

V5.4

12/20/2012

Problem fixed / Enhancement

Details

• NOE77101 connection closure mechanism can cause error 6003 in M1E MSTR function block. A special socket option was added to all Modbus server connections called “No Linger” to facilitate HSBY switchovers. However that state was inadvertently added to two paths which caused the problem seen

• Communications gradually degrades then stop after running for about 16 months. Due to mishandling of a 32 bit timer overflow in the stack as the timer approached the overflow point the performance of the NOE would degrade and at the point of overflow it would stop. It would recover on its own.

• In Quantum Ethernet modules I/O Scanning causes excessive ARP traffic when using a gateway. Each line of an I/O scanner issues its own ARP prior to establishing a connection. This can cause excessive traffic for a router or gateway. The I/O scanner will now issue an ARP for each IP address rather than for each line of the scanner. This will eliminate multiple ARPS to the same device.

• If the cable is pulled from the Ethernet port and notreconnected for approximately 70 hours or longer, the connection is not re-established. A slow memory leak, caused by the web server polling the port resulting in a lack of resources, was corrected.

Enhancement

• OpCode 16 to close connections available for Concept. Request for functionality similar to Unity where OpCode 16 in the MBP_MSTR block aborts the Ethernet connections.

Thank you for reading our post on the 140NOE77101 Firmware Executive Release Notes.

You can call 1-800-691-8511 or email sales@mrostock.com to request a 140NOE7701 price quote.