deviceWISE 16.1.3 Release Notes

What's new in the deviceWISE 16.1.3 release

The latest released build is 16.1.3-02.  This release is recommended for existing deviceWISE users who will install this version over a previous version of deviceWISE.  If you are installing for the first time, then install with deviceWISE version 16.1.2 and next do a firmware update to version 16.1.3.

Supported platforms

deviceWISE 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 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 Conduit (with Serial and GPIO and cellular modules)**
  • 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 with v1.x or v2.x firmware)
  • RedLion (Pilot Ready)
  • Siemens (MicroBox, NanoBox)*
  • Siemens ERPC*
  • Systech SysLINK SL-500 
  • USRobotics 3510 
  • Xmodus XM1710E (Pilot Ready)

New features and Enhancements to existing features

• Gateway

  • TR50: Store and Forward (Beta)
    

• Workbench

  • Added Populate Array feature in Trigger Actions

  • Usability improvements

    • Workbench can configure Tunnel Proxy settings
    • Add a column with execution time on Reports List pane
    • Allow Local db tables to be altered (add a column)
    • Context menus in the Canvas editor
      

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.

BACNet driver now allows user to specify a port

Modbus Client driver updated to support strings (Read-As)

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 16.1.3 release

Actions and Events

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.

MAP-8438:  MultiTech Conduit reboots at random when running smoke (tr50 connection related tests)

Description:  A firmware update from MultiTech is required to resolve this issue on the Conduit Gateway.

Asset Gateway for Option Cloudgate

MAP-8230:  Option V2 CDMA: Message corruption on Send SMS

Description:  For Option Cloudgate CDMA-equipped models, cellular Actions and Events related to SMS send and receive are not supported.

MAP-8231:  Option V2 CDMA: Sending a large SMS message fails on with internal cloudgate api error

Description:  For CloudGate Option CDMA-equipped models, cellular Actions and Events related to SMS send and receive are not supported.  Sending a large SMS > 160 characters fails with a cloudgate api error on an option V2 CDMA node.

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

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.

HTTP Server

MAP-4630/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.

Reports

MAP-8928:  Reports DB is not created correctly for new column for a new install of deviceWISE

Description:  For new installations of deviceWISE version 16.1.3, the Reports database is not created correctly.  The work around for new installations is to install 16.1.2 first and then do a firmware upgrade to 16.1.3.  Customers installing 16.1.3 on top of a previously installed version are not affected if they do not remove the DWLOG.DB files before installing 16.1.3.

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-8236  Wait action is not being rescheduled after a time_sync. 

Description:  There is known issue relating to WAIT action completing immediately when the timesync is enabled on a TR50 connection that has a drift of 2 seconds or greater. This implied that the trigger's sequence of events that are time sensitive may execute quicker than expected when the OS system time is adjusted to sync with the M2M Service platforms' time. 

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-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-7694:  Subscription on device that becomes stopped generates read errors

Description:  When subscribing to a started device that is later stopped, the subscription still attempts to read from that device and generates errors.

Workaround: Workbench can workaround this by stopping subs on stopped devices and restarting again on start, but keeping the subs live when the device is stopped results in fewer commands being sent.

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.

Issues fixed in the deviceWISE 16.1.3 release

The following defects were fixed in this release.

Asset Gateways

MAP-8788:  Serial port enumerator can't deal with more than 64 serial ports or 3 digit COM ports on windows.

Description:  Fixed in 16.1.3

Workbench

MAP-8881:   Trigger editor can get stuck on variable retrieval

Description:  Fixed in 16.1.3

MAP-8812:   Property file in wrong sub-folder in jar for branded workbenches

Description:  Fix for customer branded Workbenches included in 16.1.3.

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 earlier release level of an Enterprise Gateway to 16.1.3

If you are updating an Enterprise Gateway from the 15.4.0, 15.5.0, 15.6.0, 15.7.0, 16.1.1, or 16.1.2 to 16.1.3, then you can use the firmware update option. A firmware update from a release before 15.4.0 to 16.1.3, is not supported.

If you are updating an Enterprise Gateway from a 15.3.0 or earlier release to 16.1.3, you must do a complete product installation.
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 updating to 16.1.3, you will need to add all device drivers and extensions from the new 16.1.3 release level.

Updating from an earlier release of an Asset Gateway to 16.1.3

If you are updating an Asset Gateway from the 15.1.0, 15.2.0, 15.3.0, 15.4, 15.5.0, 15.6.0, 15.7.0, 16.1.1, or 16.1.2 release, then you can use the firmware update option.

If you are updating an Asset Gateway from an older 13.3.0, 14.1.0 or 14.2.0 release to 16.1.3, you must do a complete product installation. A firmware update from an older 13.3.0, 14.1.0 or 14.2.0 release to 16.1.3, is not supported. Alternatively, you can use the firmware update option to first update the older release to 15.1.0 and then do a firmware update to 16.1.3.
This is required to install the supporting libraries and 3rd party support files, which are included in the 15.1.0 firmware update. These supporting files are not included in a 16.1.3 firmware update for an Asset Gateway.

After updating to 16.1.3, you will need to add all device drivers and extensions from the new 16.1.3 release level.

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