deviceWISE M2M 15.1 Release Notes

What's new in the deviceWISE 15.1 release

The latest released build is 15.1-031.  

Supported platforms

deviceWISE M2M Enterprise Gateway products

• Software Products
  • AIX (Version 6.1 and Version 7.1)
  • Linux (CentOS5 and CentOS6)
  • Windows (Windows XP SP3, Windows 7, and Windows Server 2008 R2)
• Embedded Products
  • Mitsubishi MESInterface IT
  • Mitsubishi WinCPU
  • Siemens ERPC

deviceWISE M2M Asset Gateway products

• Software Products
  • Linux (CentOS5 and CentOS6)
  • Windows (Windows XP SP3 and Windows 7)
• Embedded Products
  • Advantech Uno*
  • B&B Electronics Spectre V3
  • CalAmp LMU-5000 (Rev C and Rev G)
  • GateTel EZMoto V2
  • Mitsubishi CCPU12*
  • Multitech OCG-D (Models H4, H5, and EV2)
  • NetComm Wireless Routers (NTC-6200, NTC-40, NTC-30WV, NWL-12, NWL-11)
  • Option CloudGate (Models CG0192 and CG0112)
  • Siemens (MicroBox, NanoBox)*
  • Siemens ERPC*
  • Systech SysLINK SL-500

New features

• New Actions and Events

  • TR50 MQTT Publish Action 

  • TR50 MQTT Publish Receive Event

  • TR50 Command Aggregator
  • TR50 Actions for Attributes and Tags
• Transaction Server updates

  • 3rd Party Library Updates

• TR-50 Package

  • C API updates

  • Java API updates
• New Asset Gateway:
  • B&B Electronics Spectre V3
• Workbench 
  • Add search capability within the trigger editor
  • 3rd Party Library Updates

Enhancements to existing features

• Add ability to generate a report for a sub-trigger
• Add caller information(file and line) to log when malloc fails

• Tunnel Manager picker needs to allow cut/paste of IP:PORT

• Diagnostics files will include the *.properties files

Driver updates

Refer to the Management Portal -> Developer page -> Resources item to identify the drivers and driver versions supported on a specific platform with this release. Both new installations and updates should include the drivers for this release.  The following drivers updates are included with this release.

• Add connectivity to Mitsubishi iQ-R 

• The Rockwell driver now supports reading and writing an entire Rockwell UDT tag in a single trigger action

• Implement asynchronous model for Rockwell SLC 500 and the MicroLogix PLCs to improve performance

• Improve diagnostic capabilities for the Omron CIP Listener, the Siemens Listener, the Mitsubishi Listener, and the Rockwell CIP and PLC/SLC 500 Listener by expanding the number of connection and message variables.

New Prototype Proxy Drivers

• DanLaw - for telematics
• Semtech LoRa - for long range wireless communications

Third Party Library Updates

Core 

    The following libraries have been updated to current levels.

•    Libraries for XML processing and internal configuration storage 
•    OpenSSL is now at 1.01.m

Transaction Server  

      The following libraries have been updated to current levels

•       Libraries for XML and SOAP processing.
•       JDBC Libraries for SQLServer, Oracle and DB2 database access. ( Note that the MESInterface-IT and Siemens ERPC database access libraries have not been updated. ).
•       Internal logging and configuration storage libraries.
•       The embedded JRE for Windows( including WinCPU) and Linux based products is now at JRE 1.8u25. ( Note that the MESInterface-IT, Siemens ERPC, and AIX JRE levels have not been updated. ).

Workbench 

    The following libraries have been updated to current levels

•      Internal logging and persistence libraries
•      XML, WSDL, and JSON processing 
•      HTTP, ActiveMQ, and MQTT support libraries 
•      The embedded JRE is now at 1.8u25.

Limited Release** features

Notes:
* - Denotes a supported gateway that was not specifically tested for this release. Of the Asset Gateways listed, most use a standard Linux or Windows load or they are very similar to a tested Enterprise Gateway.
** - Limited Release features meet customer specific features and configurations. These features may not be available in all hardware and operating system configurations.

Supported Driver Versions

More information about drivers can be found on the Device driver list.

The following drivers are fully supported with this release.

The following drivers have a "Limited Availability" status.

Known issues for the deviceWISE 15.1 release

Actions and Events

MAP-7595:  Error message returned on Success path of trigger action

Description:  When printing out a log message connected to the success path of a trigger action the trigger action's 'Error message' output variable contains text describing an error.  Local DB Import has an output variable called 'ErrorMessage'. Printing out the contents of this variable shows text, "UNIQUE constraint failed: RobotDeviceDefinitions.DeviceName", which is not expected on a successful path.

MAP-7658:  Two consecutive gateway trigger Log Message actions are written to Exception Log out of sequence

Description:  In rare events, two consecutive gateway trigger Log Message actions can occur within the same milisecond.  Both actions will have the same timestamp and there is a chance that they will not appear in the expected order.

MAP-7740:  Log Message action not logging the $ char in a log message

Description:  The Log Message action does not write the $ char in an exception log message.  This can be bypassed by using 2 $ chars back to back.

Asset Gateway for CalAmp

MAP-5369: OS Shutdown action does not work on a CalAmp RevC or RevG

Description: The OS Shutdown action does nothing when executed on a CalAmp RevC/ or RevG. This feature has not been implemented in the Asset Gateway for CalAmp.

Asset Gateway for Multitech

MAP-4860: Local time zone for Brussels is 2-hours off

Description: Setting the local time for Brussels, Belgium is two hours off in the Asset Gateway for Multitech.

Workaround: Select the local time option for Paris, France in the Asset Gateway for Multitech.

Enterprise Gateway for Windows

MAP-3455: The Enterprise Gateway for Windows Restart feature from the Node Administration tab does not work as designed

Description: The Restart feature available from Workbench -> Administration -> Node Administration tab may not cleanly stop and then restart the runtime. When there are many active transports and listeners, the Transaction Server does not restart properly.

Workaround: Follow the instructions in the section "Manually restarting a node" on Enabling MySQL support.

Enterprise Gateway for Linux

MAP-7266:  Subtrigger call on enterprise node fails stating that it is not started even though it has started

Description:  For the 15.1 release, an update was included so that deviceWISE would remove the existing event immediately before creating the new one.

Enterprise Gateway for ERPC

MAP-1933: On a Enterprise Gateway for Siemens ERPC, a controlled Listener fails to connect to queue manager on first attempt

Description: When accessing a WebSphere MQ server via a transport or a listener, the very first connect request after boot fails due to a limitation in the firmware. Subsequent connect requests work correctly.

Workaround: Repeat the connect request.

MAP-3634: FTP action with Transfer Mode set to Active fails on Enterprise Gateway for Siemens ERPC

Description: When using a trigger FTP action, the Put and Get operations do not work when Transfer Mode set to Active on ERPC.

Workaround: Set the Transfer Mode parameter to Passive instead of Active until the problem is fixed in a future release.

MAP-5707: FTP client does not connect to server in passive mode on ERPC

Description: The deviceWISE FTP Server in the Enterprise Gateway for Siemens ERPC cannot support a FTP client in passive mode.

Workaround: Use the FTP active mode instead.

MAP-6793:  A TR50 connection with SSL will fail on ERPC

Description:  TR-50 is not supported on the ERPC platform.

MAP-7758:  ERPC: FTP Server gets into a bad state after a file transfer put

Description:  15.1-build 26 has a problem when running the FTP action's Put operation.  The file transfer completes successfully, (Passive mode) but the FTP server is in a bad state. An attempt to stop the FTP Server results in the ftp server hanging and eventually crashing the core.

Firmware Update

MAP-7083:  Firmware update of a Entperise Gateway environment from 13.2.0 to 14.2.0-018 fails

Description:  A minimum level of 13.3.0  is required for a firmware update to 14.2.0 to be successful on the Enterprise Gateway product.  If you are at 13.2, a full install of the 14.2 Enterprise Gateway product is required.  Asset Gateway products are not affected.  Note that an update to Enterprise Gateway 15.1 from 14.2  is not supported. A full install is required.

HTTP Server

MAP-5090: The HTTP Server has problems with Network Intrusion monitoring tools

Description: Certain network intrusion tools can cause the deviceWISE HTTP server to crash.

Workaround: Disable the deviceWISE HTTP Server if it is not required. Do not run network intrusion tools when the deviceWISE HTTP Server is enabled.

Local Database (Local DB) 

MAP-4732: The Local DB Import action with the "First Row is Header" parameter set to true fails.

Description: Importing a csv file with a header row into a Local DB table will cause a failure.

Workaround: Set the "First Row is Header" parameter to false, import it, and then remove the first row.

MAP-5404: Problem reading database entries when a comma/line-feed combination is the last item in a list of database entries

Description: If a comma/line-feed combination is the last item in a list of database entries, then a problem occurs

Workaround: Add a dummy column in the database to represent the blank after the comma. For example, if you have 15 data entries and the last entry has a comma, then add a 16th column to your database.

Transaction Server

MAP-685: Transports do not recover properly from Store and Forward

Description: When using the WMQ transport and the transport reports the error MQJMS007, it might cause the transport to switch in and out of Store and Forward, even though the transactions are successfully delivered to the WMQ queue.

Workaround: Check the WMQ queue manager. If the listener shows the state other than Started, then it is likely that you have encountered this issue. Set the listener to Started to restore proper functionality.

MAP-2972: Enterprise Gateway for Siemens ERPC faults with Transaction Server not being able to connect after a package remove

Description: After an Add or Remove of a package, such as a device driver, the node might have a fault where the Transaction Server cannot connect.

Workaround: You will need to restart deviceWISE. Follow the instructions for Manually restarting a deviceWISE node on Packages.

MAP-3930: IFS: sometimes the Transaction Server fails to start

Description: When setting transports, especially an iTAC transport, with "Load transport at initialization" parameter checked, and using a memory optimized Transaction Server that is not a match for the transports with "Load transport at initialization", it is possible that the Transaction Server will fail to start on Mitsubishi MESInterface IT nodes.
Rebooting the module with the "Standard" Enterprise Access option will allow the Transaction Server to come up successfully, the transports can then be modified to remove the "Load transport at initialization" parameter. The memory optimized Transaction Server can then be re-set to the desired one.

MAP-4002: Updating logical variables in a transport map and not editing the corresponding trigger can lead to undesirable consequences.

Description: In this scenario the trigger will be disabled when it fires, and the action will return an error code of -6409 (invalid variable type) in the Exceptions log. Because the trigger will not be recovered on it's own, the user will have to edit and re-save the trigger manually.

MAP-4796: NVARCHAR Support Limitation

Description: The NVARCHAR and NCHAR datatypes for Oracle are not supported on the following platforms:

• Mitsubishi MESInterface-IT
• deviceWISE Enterprise Gateway for Siemens ERPC

MAP-5170: JSON payload transport maps for the HTTP transport are not supported on all platforms

Description: This feature is not supported on the following platforms:

• Mitsubishi MESInterface-IT
• deviceWISE Enterprise Gateway for Siemens ERPC

MAP-5684: JMS Netweaver Transport/Listener on an Enterprise Gateway for Siemens ERPC cannot initialize connection with the JMS Netweaver server

Description: This feature is not supported on the following platforms:

• Mitsubishi MESInterface-IT
• deviceWISE Enterprise Gateway for Siemens ERPC

MAP-5685: JMS Netweaver support jars are not packaged with the ERPC or MESInterface IT product install files

Description: This feature is not supported on the following platforms:

• Mitsubishi MESInterface-IT
• deviceWISE Enterprise Gateway for Siemens ERPC

MAP-6604:  HANA database insert fails ERPC

Description:  The NVARCHAR and NCHAR datatypes are not supported on the deviceWISE Enterprise Gateway for Siemens ERPC product.

MAP-7388:  New Oracle JDBC driver transport maps cannot enumerate schemas/table definitions on an Oracle 9 server

Description:   Beginning with the deviceWISE 15.1 release, the deviceWISE Enterprise Gateway products for Linux, Windows and AIX use a later version of the Oracle JDBC driver that only supports Oracle 12.1, 11.2, 11.1.

 Oracle 9.2 was end-of-lifed in July 2010.

• The FAQ link is here: http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-faq-090281.html#01_02
• The end-of-life information for Oracle database server products is here:  http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf

The MESInterface-IT and deviceWISE Enterprise Gateway for Siemens ERPC products are able to enumerate schemas from Oracle 9.2 because the JDBC driver has not been updated.

Transaction server XSD support

MAP-3141: XSD: Xpath expression should not be saved in the XML if Specify Map and Sequence Keys in header check box is selected

Description: This issue only affects JMS listeners with the XSD payload. When there is both an XPath expression and a JMS header property specified on the JMS listener XSD Payload panel, and the header property is missing from the incoming JMS message, the XPath expression is used to determine the listener map id, instead of the default listener map id.

MAP-3695: XSD: Default or fixed value provided in the XSD will be erroneously used

Description: If the XSD used to create a listener map contains a required attribute with a default or fixed value, it is considered valid. At runtime, instead of the XML being rejected as invalid, the default or fixed value provided in the XSD will be erroneously used.

MAP-4665: XSD: Imported transport map and listener map definitions from an older runtime into a newer runtime are not namespace aware unless XSD is requeried

Description: If you are importing a transport map or listener map that was defined with XSDs and was created in a 12.4 or prior release, then the map needs to queried again and saved in order for 'nil' element processing to be handled correctly.

MAP-4666: Listener doesn't support XSDs with namespaces

Description: A Listener configured to process XSD based payloads will not be able to successfully handle an XML with namespace qualified elements.

Workaround: The workaround is to provide an XML request without namespaces.

Transaction Server Web Services SOAP

MAP-5181: SOAP Header Parameter limited support

Description: SOAP Header Parameter support is not available on the Enterprise Gateway for Siemens ERPC and Mitsubishi MESInterface-IT products.

TR-50

MAP-7007:  TR50: Deadlock 

Description:  Gateway may experience a rarely occurring deadlock condition after several days or weeks of operation.  If this occurs, a watchdog will expire and reset the gateway to resume operations.

MAP-7739:  TR50 not honoring default settings on the TR50 Advanced Connection Management panel

Description:  When the TR50 Advanced Connection Management setting was set to Enabled, the GPS values were never being published. To work around this problem, set the Report Location to Management Portal setting to Disable and click the Save button.  Set the Report Location to Management Portal setting to Enabled, and click the Save button again. The GPS coordinates began publishing to the cloud.  

MAP-7743:  TR50 Control Connection Action not persisting the state after restarting the gateway.

Description:  If TR50 state is changed (from Started to Stopped or Stopped to Started) using the TR50 Control connection action, then the state will be changed.  However after restarting the gateway, then the TR50 will maintain the original TR50 state after a restart.  If the Workbench is used to change the TR50 state, then the state will be persisted.

Workbench

MAP-7653:  In in transport map a logical variable is renamed, it disappears from the bottom

Description:  If you rename a logical variable in a transport map, then it is removed from the bottom half.   If there are many rows, then you will not see the field go blank.  If renamed, then it should auto-populate in the bottom half.

Drivers

MAP-3140: Siemens S7 listener gets stuck in stopping state on Enterprise Gateway for Siemens ERPC

Description: After the Siemens S7 listener device receives data and a corresponding trigger is executed, stopping the Siemens S7 listener device results in the listener becoming stuck in the Stopping state. This happens during operations when the Siemens S7 listener device is using the normal TCP mode (not ISO-n-TCP). After a trigger executes the receipt of an unsolicited message, the S7 listener device cannot be stopped.

A firmware upgrade from Siemens is anticipated in order to resolve this behavior.

MAP-5066: CloudLINK package remove isn't removing the feature  and  MAP-5158Package remove failed - OS error

Description: On some platforms with limited operating system resources for memory or disk (persistence storage), there may be failure when attempting to add or remove packages. These failures are the result of the limited system resources and possible runtime behavior such as memory fragmentation. When these failures occur, restarting the node at the operating system level (power off then power on) may then allow the package add or remove to succeed. In other scenarios, you may have reached a platform limit based on the application definitions, the number and size of packages added and other dynamic runtime requirements.

MAP-6082:  Writing an empty string for Siemens STRINGs of length 207 or more does not clear bytes as expected

Description: If an empty string is written to a Siemens PLC, all the bytes of the string are set to 0x00 and the actual length byte is set to 0. This behavior changes when the maximum length of the string is 207 to 254 bytes. In this case the actual string length byte is set to 0, but the string bytes are not cleared. Not clearing the bytes is done to reduce the network traffic between the driver and the PLCs. Strings that are greater than 206 bytes requires the driver to send multiple messages to the server. The key to writing an empty string is setting the actual length byte to 0, so the string will have a NULL value.

MAP-6811:  Siemens LOGO PLC device disables periodically and MAP-6911:  Siemens LOGO PLC device gets stuck in Stopping state

Description: Lab tests have demonstrated that the Siemens LOGO PLC will not maintain simultaneous socket connections from multiple nodes. The LOGO PLC will terminate connections, which results in the associated device becoming disabled. The disabled device will re-establish a socket connection to the LOGO, only to have that connection eventually reset by the LOGO. It is recommended that connections to the LOGO PLC be limited to one node at a time. 

MAP-6931:  A deviceWISE update doesn't update the sqlite shared library 

Description:  Customers upgrading from pre-14.2 versions to version 14.2 or higher must first do a firmware update to the 14.2 level.

MAP-6938:  Rockwell CIP Event will not work when Size of One Element is set to 0 and STRINGs have more than 444 characters

Description:  The Rockwell CIP Event allows the Size of One Element field to be set to 0 and any messages using STRINGs of 444 characters or less to be received. However, any STRING with greater than 444 characters will result in an error. The workaround is to make sure you indicate the size of the String being read in the Size of One Element field.

MAP-9291:  Atlas trigger stops working

Description:  A few problems were found when a device goes disabled.  This is a known issue with versions 1.3.6 through 1.4.1 of the Atlas Copco driver.  A fix was provided in version 1.4.2 of the Atlas Copco driver in the 16.1.9 release.  

Modem

MAP-3167: Simultaneous Cellular connect/disconnect and Modem power on/off can cause reboot of Asset Gateway

Description: We found a scenario where the Asset Gateway will reboot when simultaneous control actions are executed. When the Set Modem Power Level action and the Control Cellular Connection action (or Workbench operation) is executed repeatedly and simultaneously, a crash can occur resulting in a reboot.

We have not seen this problem during normal operation where the use of the Set Modem Power Level action cycling of power between "Online" and "Low Power" rarely occurs.

Fixed defects in deviceWISE 15.1 release

The following defects were highlighted as known issues in previous releases, and were fixed in this release.

Asset Gateways

MAP-7058:  System alert for a disabled device does not get cleared even after the device has been deleted

Description:  System alerts for disabled devices are cleared when using 14.2-build 19 and later releases.

MAP-7090:  RSSI warning poor signal strength at -55db

Description:  Gateway returns the correct signal strength warning messages using 14.2-build 19 and in 15.1.

MAP-7099:  Channel Post Crash

Description:  Fixed in 14.2-build 19 and in 15.1.

MAP-7132: Core returning different type name/number pairs for different commands

Description:  Fixed in 14.2-build 19 and in 15.1.

MAP-7270:  Trigger with Variable Group not firing (fixed in 14.2-build 19)

Description:  Trigger with Variable Group fires correctly when using 14.2-build 19 and in 15.1.

MAP-7282:  Read File action not reading a file with a single line without CRLF

Description:  Action now works correctly with and without a CRLF when using 14.2-build 19 and in 15.1.

MAP-8033:  SET action -- integer to string not cleaning up buffer 

Description:  Fixed in 15.1-build 31.

Drivers

MAP-6709:  OPC-DA Client crashes during device validation

Description: The driver was attempting to release resources that were not allocated when an OPC-DA Client was validated. This was leading to a crash. This problem has been corrected.

MAP-6729:  OPC-DA Server doesn't shut down correctly on node restart

Description: The OPC-DA Server was not receiving a stop message prior to a node restart. This was causing problems with certain OPC-DA Clients. Code was added so that the OPC-DA Server is notified upon a node restart so that it can formally close and notify any connected clients that it is stopping.  

MAP-6843:  OPC-DA Server should start after the device starter is finished working, not when loading -- there is time window where devices are just loading and no variables exists --- leads to failures during startup

Description: The OPC-DA Server has been modified to start after all devices. This will ensure that if a device being serviced by the OPC-DA Server starts when the node is started, it will be in a started state prior to the OPC-DA Server starting. This ensures that the tags defined on that device can be serviced by the OPC-DA Server. 

MAP-6777:  OMRON NJ has memory leak in the CIPUCMMWrite

Description:  When the PLC sends a CIPUCMMWrite to the Omron CIP Listener, a small amount of memory was being lost during the message processing. Depending upon the number of messages sent by an Omron NJ PLC, this would eventually lead to an out of memory error on the node. This has been corrected.

MAP-6796:  OPC Server attempts to get the modifications that were made to the Global Variables device and then the server will crash

Description:  Stopping and restarting the OPC DA Server would at times result in a crash. Under certain conditions, the Internal memory used by the OPC DA Server was being released by multiple processes, which resulted in the processes crashing. The release of these resources is now being coordinated by a single process which has solved this problem.

MAP-6858:  Melco Driver on WinCPU should be built with the latest version of the EZSocket Library

Description:  The Mitsubishi driver was updated to compile with version 11.49 of the EasySocket library.

MAP-6977: Listeners not starting up automatically after boot 

Description:  This issue was a regression introduced by changes made for MAP-6225 in 13.3 and 14.1.  MAP-6225 introduced a change to verify that the runtime supports the listener when the listener is started.  The sequencing of listener starts at node start-up now has to wait on the task that completes listener feature initialization.

MAP-6979:  Reading 3-element STRING220 array on Siemens S7-400 device crashes node

Description:  Attempts to read arrays of large strings (> 218 bytes) on an S7-400 could result in system crashes. This would happen on the S7-400 because of its ability to handle larger communication payloads. The driver’s algorithm to determine where to write the data returned from the S7-400 wasn’t taking into account the larger payloads. This lead to a condition where the driver was overwrite memory. This has been corrected.

MAP-6984 OPC DA Client crashes if XML descriptor file is deleted

Description: An XML descriptor file is created when the deviceWISE OPC DA Client driver enumerates the tags defined on an OPC DA Server. A system crash was encountered if this file was subsequently deleted from the system and the OPC DA Client device that utilized the file was restarted. The driver was modified to detect the presence of this file when an OPC DA Client device is started. Enumeration will be from the server if the file is not found otherwise enumeration will occur using the tags defined in the XML descriptor file.

MAP-7076:  RTI Modbus XML descriptions not enumerating (fixed in 14.2-build 19)

Description:  This fixes a regression that was introduced in build 14.1.  Also fixed in 15.1

MAP-7131:  Rockwell (CIP) event, Set Single Attribute, isn't honoring the string size of the tag. (fixed in 14.2-build 19)

Description:  When the data in a Set Single Attribute message, sent from a Rockwell PLC is received by deviceWISE, deviceWISE will determine the size of the string using the LEN field of the String. This field indicates the true length of the String. Previously the driver was using the value supplied by the user in the Input Length field on the Trigger definition panel.  Also fixed in 15.1

MAP-7133:  Rockwell CIP trigger event is missing INT8 and UINT8 data types for Data Table Write command (fixed in 14.2-build 19)

Description:  INT8 and UINT8 data types were added to all of the Rockwell unsolicited messages.  Also fixed in 15.1.

MAP-7228:  Reads and Writes to Omron CJ, CV, and CS devices aren't byte swapped (fixed in 14.2-build 19)

Description:  A fix was made to the byte swapping logic to ensure that values written to the Omron device are correct regardless of the origination of the write.  Also fixed in 15.1

MAP-7255:  Siemens Heartbeat message causes Siemens TIA Portal software to go offline (fixed in 14.2-build 19)

Description:  Previously on some S7 systems, the response to the heartbeat message required two transmission frames. The message has been modified resulting in a much smaller response transmission. Heartbeat functionality can now be turned off by setting the Keep Alive value to 0 when defining an S7 device type.  Also fixed in 15.1

MAP-7280:  OMRON CS1 crashes when it is stopped (fixed in 14.2-build 19)

Description:  The communication between processes used in the Omron driver, during the stopping of an Omron CS1 device, would at times lead to a system crash.  Also fixed in 15.1

MAP-7291:  Org sees periodic connection loss with various nodes in different physical locations (fixed in 14.2-build 19)

Description:   Fixed in 14.2-build 19 and in the 15.1 release.

MAP-7298:  Siemens LOGO driver reads and writes past its maximum indexes (fixed in 14.2-build 19)

Description:  The I, M, and Q registers have been removed from the Siemens LOGO device. The user will no longer be able to access these data regions.  Also fixed in 15.1

MAP-7976 - OPC Client and OPC Servers were updated to use the new 'C' Libraries

Description:  15.1-build 31 and following releases will have this update.

MAP-7978:  Memory leak when doing a backup

Description:  Fixed in 15.1-build 31.

Enterprise Gateways

MAP-6745:  FTP Server not maintaining Started state across node start

Description:  Versions 13.x and 14.1 did not maintain the FTP Server started state across a node start.  This function was restored in the 14.2 release.

MAP-7013:  AIX Node Crash with HTTP Listeners

Description:  Increased async worker's stack size with the 14.2 release.

Firmware Update

MAP-8004:  Firmware update minimum version updated.

Description:  15.1-build 27 is the minimum version required to do a firmware update to 15.2.

Node Export

MAP-5814:  Improve Backup Memory Utilization Need to be able to export larger projects

Description:  Instead of creating one large XML file and then sending the large file to the Workbench, the runtime code will send a series of items to the Workbench.  

Note:  The Workbench will support the previous method and the current method of exporting projects.

Transaction Server

MAP-7011:  The MESInterface-IT and Enterprise Gateway for Siemens ERPC product  MySQL transport cannot execute a SELECT transaction with mySQL 5.5 or 5.6 server ( fixed in 14.2-build 20 and in the 15.1 release ) 

Description:  Accessing MySQL Database Server 5.5 or later is not supported from the following Enterprise Gateway products 

• Mitsubishi MESInterface-IT

(Note: Other Enterprise Gateway products do not have this limitation)

A SELECT Transport map executed against a mySQL 5.5 or later server will fail with the following exception message logged. 
"Error:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near "OPTION SQL_SELECT_LIMIT=DEFAULT" at line 1"

The workaround is to use a MySQL Server version 5.1 or earlier.

MAP-7077:  Defining a new WS_SOAP transport fails with a popup indicating that pool size is required (fixed in 14.2-build 19)

Description:  Fixed in 14.2-build 19 and in the 15.1 release.

MAP-7086:  An XML parsing error message displayed by the GETLISTENERINFO(4302) command contains unescaped XML special characters (fixed in 14.2-build 19)

Description:  The Workbench doesn’t render the Listener panel correctly if there are un-escaped XML special characters embedded. 

MAP-7087:  Attribute value that is mapped to an input variable is not emitted in the SOAP request if the associated element input variable is not specified (fixed in 14.2-build 19)

Description:  Fixed in 14.2-build 19 and in the 15.1 release.

MAP-7272:  DB Transport with nonFIFO enabled hangs indefinitely (fixed in 14.2-build 19)

Description:  A fix was made to the DB Transport with nonFIFO enabled that prevents it from hanging indefinitely when transitioning out of Store and Forward.  Also fixed in 15.1

MAP-7306:  POSTGRES SELECT transport map with a defined Where clause causes TS to catch a NullPointerException 

Description:  For the 15.1 release, a POSTGRES Select transport map defined using a where clause would fail with a severe error. 

MAP-7362:  dwcore process crashes when processing a notification update

Description:  For the 15.1 release, we corrected an error that overran the memory buffer.

MAP-7381:  Transaction server does not enumerate the list of schemas from SQL Server

Description:  For versions before 15.1, the 1.2 version of the SQLServer JDBC driver was querying schema information from the database incorrectly.   In deviceWISE version 15.1 and later the JDBC driver was updated to version 4.0 and this corrected the issue.

MAP-7569:  Transport maps defined from a WSDL file with elements contaiing embedded periods are not handled correctly

Description:  For the 15.1 release, the workbench will replace periods in the automapped names to underscore prior to populating the input and output panels.  The Transaction Server will scan the array input/output count variables for embedded periods and replace them with the underscore character.

MAP-8036:  Allow "service name" to be specified in the connection

Description:  In 15.1-build 31 and following, Oracle can be configured for either "connect with services" or "connect with SID".

MAP-8048:  WSDL files that reference XSDs from the original server are not processed correctly by the WSDL parsing utilities

Description:  Fixed in 15.1-build 31.

MAP-8049:  WSDL files cannot be queried from a server that requires basic authentication

Description:  Fixed in 15.1-build 31.

TR-50 Package

MAP-7070:  TR50 not working with Proxy   

Description:  TR50 works with HTTP Proxy when using 14.2-build 19 and also in the 15.1 release.

MAP-7139:  TR50: When saved tr50 hardware-id is not present on the gateway, tr50 will try to connect with uninitialized thingKey

Description:  If the saved hardware-id is not found in the system, then the first hardware-id in the list will be selected and used. A log entry will be made to the exception log when this occurs.

MAP-7311:  deviceWISE Gateway Core - Receiving TR-50 Requests before trigger engine is running on startup

Description:  For the 15.1 release, we added functions to suspend the retrieval of the mails, so it would suspend the mail on startup, and then resume the retrieval after all triggers are loaded.

MAP-7467:  TR50 Connection State Change trigger event not firing on connection loss

Description:  For the 15.1 release, we updated the logic for a connection loss and also added a "Status" event variable to represent the current TR50 Status, which could be "Connected", "Broken" or "Stopping". The state is now always equal to the TR50 State in the TR50 admin panel.

MAP-7722:  TR50: Execute Method fails when the method has no completion variable

Description:  For the 15.1 release, the parameter check for the completion variable was removed.

Workbench

MAP-7043:  Variable watch window does not support the same named device/variable from different nodes  

Description:  Fixed in 14.2-build 19 and in the 15.1 release.

MAP-7085 - Transport Map for Aggregate function doesn't use the row count variable value when auto-generating variables using the 'Map Variables' button 

Description:  Fixed in 14.2-build 19 and in the 15.1 release.

MAP-7088:  Workbench doesn't allow selection of Integers that expose their bits in the Variable Group panel  

Description: Fixed in 14.2-build 19 and in the 15.1 release.  

MAP-7170:  Variable Watch window corrupts when values updated quickly and the window's columns are sorted  

Description:  Fixed in 14.2-build 19 and in the 15.1 release.

MAP-7310:  Workbench -- generating automap incorrectly from stored procedures  

Description:  Fixed in 14.2-build 19 and in the 15.1 release.  The auto-map no longer is adding a sequence number to each. 

MAP-7338:  Workbench cacheing device/license information

Description:  For the 15.1 release, the Workbench will now listen to LICENSE channel and update the licenses when a message is received there. 

MAP-7893:  Export of Report in XML is not correct

Description:  15.1-build 31 changed reports to use CDATA formatting of B64 data for XML exports.

MAP-7971:  Chunked Export ignoring encryptExports flag

Description:  Fixed in 15.1-build 31

Technology Preview Extension (also known as Sandbox)

MAP-7599:  JSON Decode trigger action is leaking memory (Sandbox Feature)

Description:  In versions before 15.1, the use of the JSON Decode trigger action would result in the loss of system memory. The amount of memory lost depended on the size of the JSON string being decoded and the frequency in which the trigger action is executed.  This was fixed in 15.1.

Upgrading from previous versions

Backup before upgrading! 
You should backup your configuration from the Workbench prior to upgrading to a new version of deviceWISE.

Updating from an older release level of an Enterprise Gateway

If you are updating an Enterprise Gateway to 15.1.0, you must do a complete product installation. A firmware update from an older release, such as 13.3.0, 14.1.0 or 14.2.0, is not supported.
This is required to install the supporting libraries and 3rd party support files. These supporting files are not included in a firmware update for an Enterprise Gateway, but are included in a complete install.
After the complete product installation, you will need to add all device drivers and extensions from the new 15.1.0 release level.

Updating from an older release of an Asset Gateway

If you are updating an Asset Gateway to 15.1.0, you can use the firmware update option to update from an older release.
After the firmware update completes, you will need to add all device drivers and extensions from the new 15.1.0 release level.

For more information about upgrading your software, see Updating products.