IoT Gateway 19.1.7 Release Notes

What's new in the IoT Gateway 19.1.7 release

The latest released build is 19.1.7-002.

Customers using our Windows products should review the section below covering code upgrades and installations.  We moved to a new installation architecture for Windows products with version 19.1.6.

Customer Documentation Reminder

deviceWISE Runtime

  • Linux GUID is added to the system variables
  • Additional certificates are added so that when one expires another can take over
  • Variable Group on Global devices fire even if the value does not change
  • Minor bug fixes

Documentation

Drivers

Navigate 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.

  • Apex Cleco – Fix defects
  • Atlas Copco – Fix defects
  • Bosch Rexroth – Fix defects
  • Fanuc CNC – Release as GA level driver. Fix defects.
  • JLAN – New Prototype level driver.
  • Mitsubishi – Fix defects.
  • OPC UA Client – Release as GA level driver.
  • Rockwell – Fix defects
  • Sick – Fix defects
  • Sturtevant Richmont – Fix defects
  • TCP – Fix defects

Platforms

Removed products and platforms from the build output that are no longer supported.

  • Advantech products
  • AIX 32-bit Platform
  • Cradlepoint IBR600
  • Janus Platform
  • Moxa Platform
  • MultiTech H4
  • MultiTech EV2
  • Netcomm products
  • Telit NSIS Workbench Installers
  • Vanguard
  • Vodafone Machinelink

Transaction server

  • Minor bug fixes

Workbench

  • Add generic check box group field
  • Add option for two rows of buttons in admin panels
  • Improve backup utility

The following defects were fixed in this release.  

Backup Utility

MAP-14021: Backup Utility tool does not trigger scheduled backups

Description: Updated the code and the documentation to make the steps to schedule backups more clear to users.

Build

MAP-14071: Firmware update is blocked for Asset Gateway Linux nodes to build 19.1.6

Description: In the 19.1.6 release, firmware updates to 19.1.6-002 were incorrectly blocked. This was fixed in the 19.1.7 release and firmware updates for Linux nodes are allowed.

MAP-14050: Linux-X64-Snap missing the /www/devicewise folder in staging directory

Description: In the 19.1.6 release, the Javascript API was missing from the build output for the Linx-X64-Snap product. This was restored in the 19.1.7 release.

Documentation

MAP-14102: Update Snap install instructions

Description: These instructions were updated and clarified.

MAP-14054: Rockwell documentation. Unsolicited Logix Listener Trigger Events

Description: Added information about DF1 PLC5 Typed Write and DF1 PLC2 Unprotected Write commands. Added information about Event Variables.

deviceWISE Gateways

MAP-14085: Unable to get files from the staging directory on Ubuntu Core running Snap

Description: Fixed in 19.1.7 by adding the following property to the dwcore.platform.properties file: filesystem.copy_before_send=false

MAP-14022: deviceWISE Enterprise for Windows install does not show the correct gateway name

Description: Fixed in 19.1.7 by using the correct string for the Enterprise Gateway installer dialogue.

deviceWISE Runtime

MAP-14084: Variable Group on Global devices fire even if the value does not change

Description: The problem occurs when multiple elements within an array is subscribed individually. Another memory compare function was added in the 19.1.7 release to make sure the element within the array is changed.

MAP-14082: Deadlock in src/core/service.notification.multi.c [Line 271]

Description: Fixed in 19.1.7

MAP-14075: Mutex deadlock on http server

Description: Fixed in 19.1.7

MAP-14072: Invalid read on within event processor

Description: Fixed the invalid read request in the 19.1.7 release.

MAP-14066: pool put work returning 0

Description: Fixed in 19.1.7

MAP-14053: dwcore does not restart after installing packages on WinCPU

Description: This issue was introduced in the 19.1.6 release. It was fixed in 19.1.7 by using dwrun for WinCPU Transaction Server service management. The WinCPU product was restored as part of the 19.1.7 build output.

MAP-14028: Invalid Read

Description: Fixed Valgrind issue in 19.1.6

MAP-14017: Local DB, if data has reserved chars like %, or "'s" -- insert fails

Description: In previous releases the sql statement was constructed using a regular sprintf with %s, which does not escape special characters. With the 19.1.7 release, we use sqlite_vmprintf to support %q and it will properly escape special characters.

Drivers, Proxies, and Packages

MAP-14156: SET VIN Trigger Action does not migrate from older deviceWISE version

Description: Triggers that contain the SETVIN action created in deviceWISE versions prior to 17.2.5-002 will be broken when they upgrade to newer versions of deviceWISE. The feature to allow dynamic device names in the Open Protocol actions, MAP-11423, introduced this error only on the SETVIN action. All of the other actions handled the migration from older versions to newer versions correctly. This was fixed in 19.1.7

MAP-14138: Ability to separate Rockwell CIP Listener Messages from Debug Logs

Description: This change was to move Rockwell Unsolicited log messages to their own logging category. Debug logs are filled with messages about PLCs disconnecting. There are so many of these messages that error.log and debug.log are useless. We also defined Rockwell driver as its own log category in log.properties. Log levels were lowered on some messages and the move of Unsolicited messages to another file will help us isolate Rockwell messages. This was fixed in 19.1.7.

MAP-14108: Atlas PowerMACS won't start

Description: PowerMACS with Revision level of 1 was sending over a blank frame as we were clearing the buffer that was already sent. Result was the device would never start. This was fixed in 19.1.7.

MAP-14106: Cleco Driver: Trigger Event is not the same name and actions must be refreshed

Description: Code was introduced with MAP-13508 in the 18.3.2 release that broke backward compatibility with the Cleco and Sturtevant drivers. The fix put in for that issue was to change the Trigger Event name from MID0061 Last Tightening Result to MID0061 Rev 3. Last Tightening Result. This was done because an earlier change was made to look for a Release level in the event name, so we could support other release levels. Adding the Rel 3. in the event name caused old triggers to no longer work on the latest version. To fix this we restored the name back to what it was. We also modified the logic that checks the trigger action name so that if it can't find a Rel value in the name it will default to the Rel 3 (release 3) level. This will provide backward compatibility. This was fixed in 19.1.7

MAP-14045: Crash in tr50.connection.c

Description: This was not really a crash. It was just a warning message indicating that we are freeing a null pointer. We added a check to the tr50.connection.c to do a null check before freeing. This was updated in 19.1.7

MAP-14042: OPC UA Client Watch Window subscriptions cause read errors with Tags As Structs enabled

Description: We updated the status code and timestamp for a subscription when we are notified by the server that its status has changed. This was updated with the 19.1.7 release.

MAP-14029: OPCUA timestamp should be updated when the server notifies a subscription status change

Description: Updated to store the timestamp into cache in case bad status of variable in data change received. Updated to publish to publisher module in case of bad status of variable in data change received. In case of bad status of variable, value is filled from cache in addition to setting of variable status to ERR_DEV_BAD_DATA to have the latest proper value in watch window as the watch window implementation will not process the variable status. Updated to complete the publish request only after the status of variable in data change received instead of monitor request callback.If variable status is bad, monitor request to server will be deleted and updated the subscription failure to publisher. These updates are included with the 19.1.7 release.

MAP-14014: OPC UA Client Valgrind invalid read seen using Watch Window with Beckhoff and Kepware server when server restarts

Description: Updated to fix the valgrind invalid reads when the server disconnected in the middle. Updated to use the hash value from the new pointer address for OPCUA device instead of DW_DEVICE device pointer and device name. We have the un-subscription requests which occurs after a “device stop” and sometimes after restarting of device from disabled. This is where we are accessing the invalid pointer if we use device name as hash as it is same for both devices created before disable and after restarting. This was fixed in 19.1.7.

MAP-13955: Sick CLV driver issues

Description: Fixed in 19.1.7

MAP-13625: SICK CLV Listener doesn't allow reconnections

Description: The Sick CLV driver was not allowing a previously connected Scanner to reconnect. We also fixed Memory Leaks and added additional diagnostic variables to the variables panel in the 19.1.7 release.

MAP-14133: FANUC CNC Driver allows write to invalid index in PMC registers

Description: In releases before 19.1.7 the following error condition existed. It was fixed as part of the 19.1.7 GA release. This is an error condition test case where the wrong index is specified by the user. This can be done with the Demand Read/Write action. For example the first valid index for PMC.K.900-999 register is [900]. If the user tries to use a variable such as "PMC.K.900-999[0]", the driver will actually write to "PMC.K.0-99[0]".

MAP-13783: Setting invalid SM and SD register sizes causes Mitsubishi Q CPU device to disable

Description: We have several changes in the Mitsubishi MELSEC driver to fix the SD & SM issue when user sets the value higher than available in PLC.

• There was an error when we implemented async to check the unsolicited in 19.1.5.

• Corrected to check only response flag for unsolicited instead of using melsec_frame_status which checks more than the response flag.

• Added btree check to check whether device stopped before going into socket receive to avoid any delay if device already stopped.

MAP-14069: Update OPC UA Client driver name to add word Driver for consistency

Description: The name that will appear in "Packages" was changed from "OPC UA Client" to "OPC UA Client Driver" to maintain the consistency with other drivers as per JIRA Description.

Transaction Server

MAP-14068: Transaction Server - Error Parsing HTTP Transport JSON Result

Description: In 19.1.7, we fixed errors when Parsing and when Encoding with array of JSON objects.

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

The following drivers are fully supported and deemed "Generally Available" with this release.

Driver Name Version
Atlas Copco - updated in 19.1.7 3.4.6
Beckhoff   2.1.4
Apex Cleco - updated in 19.1.7 1.6.5
Danlaw  2.12.2
FANUC CNC - updated in 19.1.7 1.2.2
FANUC 2.3.1
NMEA GPS 1.0.2
LDAP 1.1.1
Lua  1.1.2
Mitsubishi Electric - updated in 19.1.7 3.3.1
MindSphere 2.0.0
Modbus Client 2.8.4
Modbus Server  1.1.5
MQTT Client 1.3.0
MTConnect  1.2.6
OAuth2 - updated in 19.1.7 2.3.0
Omron  3.6.7
OPC DA Client 2.6.0
OPC DA Server 1.1.5
OPC UA Client - updated in 19.1.7 2.4.3
Allen-Bradley (Rockwell Automation) - updated in 19.1.7 2.17.5
Siemens 2.10.3
Sysmon 1.0.0
TR50 - updated in 19.1.7 2.0.5

The following drivers have a "Pilot Ready" status.

Driver Name Version
Pointer  1.12.0
Emerson Rocplus  2.0.2
SNMP 1.0.0
Sturtevant Richmont - updated in 19.1.7 1.7.5
TCP - updated in 19.1.7 2.2.1

The following drivers and packages are "Prototype" level.

Driver Name Version
Advanced Display Protocol 1.0.1
BACnet IP  2.2.0
Banner Engineering 1.0.0
Bosch Rexroth - updated in 19.1.7  1.7.4
CTI  2.1.4
Davis 1.0.0
Escort Memory Systems (EMS) 1.0.0
E-Sensors 1.0.0
Fuji 1.0.0
GrovePi (Only in Raspbian directory)  1.0.1
Hawkeye (MicroScan Systems)  1.0.0
Hue 1.0.0
iCaddy 1.0.0
Lora (Semtech) 1.0.0
ScanTools OBD-II 1.0.0
Oramoc 1.0.0
Pepperl+Fuchs  1.0.1
Pike Aero 1.0.0
Sandbox 1.0.0
SICK CLV Scanner - updated in 19.1.7  1.1.0
Sigfox 1.0.0
SQElectronics 1.0.0
Symbol 1.0.2
Virtual  1.3.0
WebMI 2.0.0
WSAPI 1.1.0
Xirgo 1.3.0
Z-Wave 1.0.0

deviceWISE Enterprise Gateway products

  • Software Products
    • AIX 64-bit (Version 6.1 and Version 7.1 and Version 7.2)
    • Linux 32-bit (CentOS 5 and CentOS 6)
    • Linux 64-bit (CentOS 6 and CentOS 7)  
      • No CentOS 5 support
      • Full - for deviceWISE Enterprise Gateways for 32-bit Linux installed on 64-bit CentOS Operating Systems (requires 32-bit glibc, e.g. glibc.i686 on CentOS 7)
      • Full - for deviceWISE Enterprise Gateway for 64-bit Linux 
    • Windows (Windows XP SP3, Windows 7, Windows 10, and Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016 64-bit)
      • No support for Windows Home Edition
  • Embedded Products
    • Dell Edge 5000 - WindRiver Linux 7; Ubuntu Server
    • Mitsubishi MES Interface IT
    • Mitsubishi WinCPU
    • Rockwell ControlLogix
    • Siemens ERPC

deviceWISE Asset Gateway products

  • Software Products
    • Linux 32-bit (CentOS 6)
      • No CentOS 5 support
    • Linux 64-bit (CentOS 6 and CentOS 7)
      • No CentOS 5 support
      • Full - for deviceWISE Asset Gateways for 32-bit Linux installed on 64-bit CentOS Operating Systems (requires 32-bit glibc, e.g. glibc.i686 on CentOS 7)
      • Full - for deviceWISE Asset Gateway for 64-bit Linux
    • Linux 64-bit (Snap)
    • Windows (Windows 7, and Windows 10)
      • No support for Windows Home Edition
  • Embedded Products
    • B+B SmartWorx Spectre V3
    • CalAmp LMU-5000 (Rev C and Rev G)
    • CalAmp CDM-5030
    • Cisco 829  
    • Cisco IE 4000
    • Cypress CTM-200  
    • Dell Edge 5000 - WindRiver Linux 7
    • GateTel EZMoto V2
    • Mitsubishi CCPU
    • MultiTech Conduit (with Serial and GPIO and cellular modules)
    • MultiTech Conduit AEP for AT&T**
    • MultiTech OCG-D (Models H5)
    • MultiTech rCell (Model MTR-LAT1-B07)
    • Option CloudGate (Models CG0192 and CG0112 with v1.x or v2.x firmware)
    • RedLion (Pilot Ready)
    • Siemens (MicroBox, NanoBox)*
    • Siemens IoT 2000 (Wired only)
    • Siemens ERPC*
    • Systech SysLINK SL-500 
    • USRobotics 3510
    • Vantron VT-M2M-LV 
    • Xmodus XM1710E (Pilot Ready)

Limited Release** features

* - 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.

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.

Hot-Edit of Started Triggers

MAP-11421:  deviceWISE crashed when Editing and Saving a Started trigger

Description:  Intermittent issue where deviceWISE crashed when attempting to Edit and Save a Started and Loaded trigger

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-12085:  MultiTech OCG platform Local I/O initialization failure  

Description:  Local I/O features do not work in releases from 17.1.13 through 17.2.8.  This was fixed in 17.2.9.   

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.

MAP-10092:  No TR50 S&F disk storage type support for Option CloudGate V1

Description:  TR50 S&F support is present, but the S&F disk storage type is not available.

Asset Gateway for USRobotics

MAP-10662:  No TR50 S&F disk storage type support for USRobotics

Description:  TR50 S&F support is present, but the S&F disk storage type is not available.

Device types

MAP-9212: Be aware of endianess when importing or exporting Global Variables device and data values

Description: When exporting a Global Variables device with its data values from one node and then importing the Global Variables device and the data values into another node, the endianess of the nodes must be taken into consideration. For example: exporting from a big endian node (Power PC) and then importing into a little endian node (X86). The numeric data values will not be correctly represented in the imported node.

After the import, the Global Variables device should be edited, and the data values reviewed and modified.

Enterprise Gateway for Siemens 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-9820:  VxWorks-based Enterprise gateway platforms lose SQLServer Connectivity after Windows updates

Description:  Windows updates add new items to the Windows cipher suite and change the default order of items within the cipher suite.  This prevents a successful connection with SQL server. 

Workaround:  Move this cipher suite “TLS_RSA_WITH_AES_256_CBC_SHA (53)”, to the top of the list of cipher suites.  See the More Information section on this Microsoft page for instructions to configure the SSL Cipher Suite Order Group Policy setting :  https://support.microsoft.com/en-us/kb/3161639.  Using this method retains the order of the cipher suites across subsequent Windows updates.

MAP-11664:  VxWorks-based Enterprise gateway platforms cannot process empty ResultSets from an Oracle Stored procedure 

Description: If you execute an Oracle database stored procedure transport map that returns result sets in output parameters the transaction action will fail if the result set output parameter is null.

MAP-11665:  VxWorks-based Enterprise gateway platforms cannot process empty ResultSets from a SQLServer Stored procedure 

Description: If you execute an SQLServer database stored procedure transport map that returns result sets the transaction action will fail if the result set is empty.

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.

MAP-10766: Logon credentials for the Windows Services "deviceWISE Transaction Engine" and "deviceWISE Core" are reset after deviceWISE upgrade or downgrade

Description:  If you change the logon credentials of the deviceWISE Windows Service entries which include "deviceWISE Transaction Engine" and "deviceWISE Core", they will be reset to the default service credentials after a firmware update to a newer or older version. 

Workaround: Navigate to the services panel and re-enter the logon credentials after the firmware update and restart the service entries.

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.

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.

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 its 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 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.

MAP-9082:  Null Macro test: Select fails when a default timestamp of format 01/11/12 12:45:00.000 is used in place of a NULL value returned

Description:  If you need to specify a default value for SQLServer datatypes for DATE and TIME when using the following enterprise gateway products: 

  • Mitsubishi MESInterface-IT
  • Enterprise Gateway for Siemens ERPC

then you will need to use a long value that represents milliseconds since 1/1/1970 instead of the default format 'mm/dd/yy HH:MM:SS.sss',

MAP-11311:  AIX java8: SSL Error when attempting to connect to SQL Server 2008 and below

Description:  The database transport on deviceWISE Enterprise Gateway for AIX and AIX64 cannot complete a connection to SQLServer 2008 running on Windows XP due to incompatibility with SSL. The workaround is to access the SQLServer database on a newer operating system.  

MAP-12324:  VxWorks platforms: Failure to connect to Oracle 12c server with SQLException: No matching authentication protocol

Description:  VxWorks-based platforms with Oracle database transport fails to connect to the Oracle 12c server with the following error:   "java.sql.SQLException: ORA-28040: No matching authentication protocol "
The issue is caused because Oracle 12c is configured to use a default minimum authentication protocol of 11 and the VxWorks-based gateway product uses an older unsupported JDBC driver tied to JDK 1.5. This is equivalent to an Oracle 8 client and consequently uses an Oracle 8 authentication protocol.

Workaround:

  • Configure the sqlnet.ora file with the following parameters to allow a version 8 authentication protocol.
    • SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
    • SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
    • SEC_CASE_SENSITIVE_LOGON=FALSE
  • Restart the server for these changes to take effect.
  • If you are planning on using an existing login id from the VxWorks runtime you will need to use PL/SQL and alter the password of the user to force the server to rehash passwords with compatible versions.
    • A recommended approach would be to create a new login id and specify those credentials on the Oracle 12c Transport on the VxWorks runtime.

Reference links:

MAP-12453:  Accessing a HTTP or SOAP server that presents an untrusted server certificate

Description:  Starting with Enterprise Gateway version 17.2.3, the HTTP and WS_SOAP transports have changed their behavior when establishing an HTTPS connection. The server needs to present a server certificate that is signed by a globally trusted CA. Otherwise the transport will receive a SSL Handshake Exception.

The workarounds are:

  •  Update the server certificate on the HTTPS server with one that is signed by a trusted CA.
  •  Create a java key store that includes the server's CA certificate using the keytool utility. Then specify this key store in the transport panel 'Keystore' and 'TrustStore' fields.
  • A less preferred option is to add the Organization/Company's root CA certificate to the 'cacerts' file. Note that this file will be replaced when the enterprise gateway product is re-installed.

MAP-12885:  MySQL Connector/J 8 version of the JDBC driver is incompatible with the Enterprise Gateway DB transport

Description:  The mySQL Connector/J v8 JDBC driver has changed the package name of the class that implements the driver. Use the mySQL Connector v5.x JDBC driver instead to enable mySQL support in the enterprise gateway.

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 re-queried

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 IoT Portal platforms' time. 

MAP-10092:  Option CloudGate V1 failed when running TR50 S&F disk storage type tests with error storage->create_storage failed [-33533]

Description:  TR50 Store and Forward disk storage type is not supported on Option CloudGate V1 gateways.

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-5158 Package 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

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-9022:  Cannot read variable when its name exceeds 128 characters on OPC UA Client

Description:  A variable's location name can be a maximum of 128 characters long.  The variable location name consists of the parent structure names plus the variable name.  Renaming a variable to fit the 128 character limit will allow you to read and write to the variable.  A variable with a location name greater than 128 characters long will not be able to be accessed, and will return an "Error: Variable does not exist" error.  This page has more information:  Accessing device variables.

MAP-9303:  OPC UA Client driver increases core handles and memory usage during StartStopStress test (Linux)

Description:  Attempting to start and stop many OPC UA clients on Linux causes the node to crash.

Workaround:  Limit the number of OPC UA devices per deviceWISE node to five.

MAP-9176:  OPC UA Client driver increases core handles and memory usage during StartStopStress test (Windows)

Description:  Attempting to start and stop many OPC UA clients will result in leaked memory. For reference, starting and stopping 15 clients constantly for 3 hours results in ~15MB lost. Restarting a node will clear this leaked memory.

MAP-9968:  BACNet Version 1.2.0 does not support Linux x64 platforms

Description:  BACnet is not supported on 64-bit Linux platforms.

MAP-10011:  Node crashes when disconnecting Ethernet cable when trigger is reading BACnet device variables

Description:  A problem has been seen in the lab where the system restarts if the network connection to the BACnet device is lost during the device start process

MAP-10145:  OPC-DA Client cannot write UINT4 value 2147483648 and greater

Description:  The largest unsigned integer value that the OPC-DA Client can write is 2147483647.

MAP-12201:  Atlas Copco Trace Data trigger fires even though a tightening wasn’t performed.

Description:  Testing in the lab has found instances where a Trace Data (MID0900) message is being sent by the Atlas Controller to deviceWISE, even though a rundown hasn’t occurred. This causes a started Atlas Copco Trace Data trigger to fire, if it is associated with that controller. The Trigger’s Result Data Identifier Event variable can be used to determine if this is a duplicate Trace Data message.

MAP-12442:  OPC-UA Client driver does not run on NetComm, CalAmp LMU5000 RevC, and Lanner

Description:  The OPC-UA Client driver is not supported on all platforms. Refer to the OPC-UA Client driver documentation at Supported OPC-UA Client environments.

MAP-12780:  Rockwell MicroLogix 1100 and 1400 devices get stuck in Stopping state on Siemens ERPC

Description: After several variable reads and writes, stopping the device might result in the device being stuck in the Stopping state, then resetting after about 10 minutes.

MAP-13702: OPC UA Client Certificate Security does not work on VxWorks-based platforms.

Description: OPC UA Client Certificate Security feature is not enabled for VxWorks-based platforms.

MAP-13859: FANUC CNC Driver Macros floating point value write -12.3456 results in -12.3455999

Description: There is a limitation when representing floating point numbers because of Int4 precision. The max Int4 value is 2147483647, and this limits precision.

MAP-13860: FANUC CNC Driver random write failures to Macros at 500 and 98000 range on NCGuide device

Description: This is an intermittent problem with the NCGuide simulator software.

MAP-14146: FANUC CNC driver reading and writing wrong Tool Offset type

Description: We found that the Tool offset type would not write to the correct offset depending on the range provided. We removed the Tool Offset feature in 19.1.7 and plan to correct the implementation in a future release.

Backup before upgrading!  You should do a Backing up and Restoring a node's configuration of 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 19.1.7

For Windows Enterprise Gateway products:

Upgrading a Windows Enterprise Gateway product from a version before 19.1.6 to 19.1.7

We moved to a new installation architecture for Windows Asset Gateway and Enterprise Gateway products with version 19.1.6. These Special Notes apply to a one-time transition from a Windows Gateway version before 19.1.6 to a Windows Gateway version after 19.1.6:

If you are upgrading a Gateway for Windows product to version 19.1.7 or later, you must do the following:

  1. Perform a node backup of deviceWISE
  2. Backup all files used in the Staging Browser folders or properties files that were added outside of the original deviceWISE installation. (For example: C:\deviceWISE\Runtime\staging and C:\deviceWISE\Runtime\dwcore)
  3. Uninstall the (pre-19.1.6) version of the Enterprise Gateway for Windows product
  4. Install deviceWISE Enterprise Gateway for Windows or deviceWISE Asset Gateway for Windows using the given installers.
  5. Copy the files backed up from step #2 contained in the Staging Browser folders or properties files to the new installation folder. (For example: C:\Program Files (x86)\deviceWISE\Gateway\staging and C:\Program Files (x86)\deviceWISE\Gateway\dwcore)
  6. Restart deviceWISE
  7. Restore your node.
  8. After updating to 19.1.7, you will need to add all device drivers and extensions from the new 19.1.7 release level.
Upgrading a Windows Enterprise Gateway product from 19.1.6 to 19.1.7

If you are updating an Enterprise Gateway for Windows from the 19.1.6 release, then you can use the firmware update option. A firmware update from a release for Enterprise Gateway for Windows before version 19.1.6 is not supported. You must do a complete product installation as noted in the previous section.

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

For AIX, Linux, VxWorks, or WinCPU Enterprise Gateway products:

If you are updating an Enterprise Gateway from a 17.2.3 through 19.1.6 (inclusive) release, then you can use the firmware update option. A firmware update from a release before 17.2.3 is not supported.

If you are updating an Enterprise Gateway from a 17.1.14 or earlier release to 19.1.7, 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, however they are included in a complete install.

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

A firmware update from 16.1.8 or earlier to 19.1.7 is not supported for CentOS 7 or  systemd installations.  A full installation is required.

Updating from an earlier release of an Asset Gateway to 19.1.7

For Windows Asset Gateway products:

Upgrading a Windows Asset Gateway product from a version before 19.1.6 to 19.1.7

We moved to a new installation architecture for Windows Asset Gateway and Asset Gateway products with version 19.1.6. These Special Notes apply to a one-time transition from a Windows Gateway version before 19.1.6 to a Windows Gateway version after 19.1.6:

If you are upgrading a Gateway for Windows product to version 19.1.7 or later, you must do the following:

  1. Perform a node backup of deviceWISE
  2. Backup all files used in the Staging Browser folders or properties files that were added outside of the original deviceWISE installation. (For example: C:\deviceWISE\Runtime\staging and C:\deviceWISE\Runtime\dwcore)
  3. Uninstall the (pre-19.1.6) version of the Asset Gateway for Windows product
  4. Install deviceWISE Enterprise Gateway for Windows or deviceWISE Asset Gateway for Windows using the given installers.
  5. Copy the files backed up from step #2 contained in the Staging Browser folders or properties files to the new installation folder. (For example: C:\Program Files (x86)\deviceWISE\Gateway\staging and C:\Program Files (x86)\deviceWISE\Gateway\dwcore)
  6. Restart deviceWISE
  7. Restore your node.
  8. After updating to 19.1.7, you will need to add all device drivers and extensions from the new 19.1.7 release level.
Upgrading a Windows Asset Gateway product from 19.1.6 to 19.1.7

If you are updating an Asset Gateway for Windows from the 19.1.6 release, then you can use the firmware update option. A firmware update from a release for Asset Gateway for Windows before version 19.1.6 is not supported. You must do a complete product installation as noted in the previous section.

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

For AIX, Linux, VxWorks, or WinCPU Asset Gateway products:

If you are updating an Asset Gateway from a 17.2.3 through 19.1.6 (inclusive) release, then you can use the firmware update option. A firmware update from a release before 17.2.3 is not supported.

If you are updating an Asset Gateway from a 17.1.14 or earlier release to 19.1.7, 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 Asset Gateway, however they are included in a complete install.

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

A firmware update from 16.1.8 or earlier to 19.1.7 is not supported for CentOS 7 or  systemd installations.  A full installation is required.

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