IoT Gateway 21.10 Release Notes

deviceWISE View (version 1.3.0)

• Fix defects

• Add dW View package to Enterprise Gateway for AIX

• Line charts can graph data vs time on x-axis

• Add Grouping of Widgets – Allow defining of custom widgets as a template with variables bubbles up

• Update variables to display Hex values for Mitsubishi PLCs

Gateways

Each Asset Gateway license is limited to 5 devices. If you want to add more devices, contact your sales representative and request additional licenses.

• Update installation to use OPKG for Teltonika gateways
• Add support for SUSE Linux
• Add support for Ubuntu 20
• Removed the Enterprise Gateway for WinCPU platform
• Updated MultiTech Conduit AEP files in 21.10.11

Runtime

• Fix defects

• Add logging when someone logs in or logs out for old and new HTTP Server packages

• Reject HTTP login until gateway is fully loaded for old and new HTTP Server packages

• Clean up system logging to reduce the frequency of socket warning messages

• Extend Array Get and Array Set to get or set a number of elements in an array

• Update EULA

• Update OpenSSL library

• Update LibCurl library

Transaction Server

• Fix defects

• SOAP Transport maps - add support for nested structures (using complex XML payloads in SOAP APIs)

• Reduce messages in JMS Listener

Workbench

• Fix defects

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.

• Atlas Copco – Bug fixes

• AWS IoT Core (Technology Preview) – Bug fixes

• Azure – Bug fixes

• BACNet (Technology Preview) –
  • New features
  • Major change to the interfaces
  • Customer application redesign required
• Codesys (Technology Preview) – Bug fixes
• GCP (Technology Preview) – Bug fixes

• Add new HTTP Server

  • Improve performance of HTTP Server

  • Add option to enable basic password authentication

  • Improve content negotiation

  • Add URL encode and decode

  • Create a configuration panel for HTTP server

    • Avoid having users manually editing dwcore.*.properties file

  • Split existing pem file into two files: Cert and Key

• Kawasaki (Technology Preview) – Bug fixes
• LDAP - Temporarily removed from Linux X86 platforms

• Mindsphere – do not use this with 21.10

• Modbus Client – bug fixes

• MQTT Client – bug fixes

• OPC UA Client

  • Bug Fixes

  • Improve enumeration speed

  • Add support for UDT special data types

    • Add ability to read and write UDTs

    • Add subscription for UDTs

  • Introduce ability to enumerate from XML file

• OPC UA Server – Bug fixes

• Siemens – Bug Fixes

• Zaxis (Technology Preview) – Only build for Windows products

The following defects were fixed in this release.

deviceWISE Gateways

MAP-16364 Docker AG - Diagnostics file generation doesn't work

Description: Update diagnostic file generation for Docker. Fixed in 21.10.

MAP-17032 SUP failing when Docker is installed - Update Package Action "Import deviceWISE export file"

Description: Update diagnostic file generation for Docker. All Docker images are now using supervisord, so the race condition between package installation and runtime restart should be resolved. Fixed in 21.10.

MAP-17019 Enterprise Gateway for Raspberry Pi fails to start on-boot

Description: Start-up fixes for Enterprise Gateway for Raspbian. Fixed in 21.10.

MAP-17176 MultiTech AEP deviceWISE Firmware Update Fails with 21.06, 21.07

Description: Fixed issue where deviceWISE 21.06 and later on the MultiTech AEP will not update using a .dwu file. Fixed in 21.10.11.

---

deviceWISE Runtime

MAP-16981 Inconsistencies trying to parse from a String to Timestamp

Description: mkgmtime was platform dependent and it did not work on Ubuntu, so when we parse string to timestamp in GMT, it actually corrupts the timezone settings in the environment variable. We changed it to use platform API timegm function. Fixed in 21.10.

MAP-17077 Local DB Insert --- cannot insert a specific JSON text into a text column VIA action

Description: It was escaping % twice so we had some random characters inside the string. Fixed in 21.10.

MAP-16998 Invalid read on _remtrigger_action_notify_pool

Description: Fix invalid read in remtrigger in version 21.10.

MAP-16794 High Memory usage by DW Asset Gateway on MT Conduit mLinux

Description: The OPC UA client requires a larger memory footprint. However, we also found and fixed some issues that caused memory growth in 21.10.

MAP-17039 Import with state not working for triggers via SUP

Description: Some gateways do not have the staging/system directory. Also, the trigger start failed due to the lack of user security context. The import will now start the trigger as admin. Fixed in 21.10.

MAP-16875 Gateway Node crashed in LAB - V21.08

Description: The object passed back to the Callback functions was the device instance. Fixed in 21.10.

MAP-16936 Missing trigger Data Events

Description: This problem was introduced with updates to the publisher in 21.07 related to MAP-15059. We reverted the change to use logic from versions 21.06 and earlier in 21.10.

MAP-17087 DeviceWISE data mappings cause node crash after updating from older 32-bit version to newer 64-bit version

Description: Mapping logs rely on the publisher, so moving to 21.07, 21.08, or 21.09 allowed the publisher bug to affect it. Customers can use 21.06 or 21.10 to address this issue.

MAP-16987 Variable Groups are triggered more times than they should

Description: We corrected a defect in a code path that has never been executed because the devices never go disabled. Changes for MAP-15685 in 21.09 enabled this code path. Wrong handle was passed instead of the indirect_id. Fixed in 21.10.

MAP-16975 Gateway Node Crashed - 21.08 64-bit version - Runtime exception caught: [0xC0000005]

Description: Fixed a race condition where the channel callback happens at the exact same time as the session disconnects. We were double freeing a session. The session was referenced again by channel even when it's in the process of getting deleted(freed), channel later on dereference the session again. Fixed in 21.10.

MAP-17101 Error in reading a time stamp value from DB

Description: We were not parsing the msec on localdb select. Switched to use strptime3 for msec. Localdb select will retain msec resolution in 21.10.

MAP-16921 Transaction Action block fails and returns an Error Code that does not have a description

Description: Add missing error message description for code 4854 : Http Connection Timeout. This message was updated in nls file in 21.10.

MAP-17158 Array GET/SET

Description: Fixed an issue that accessed wrong element in the array.

---

deviceWISE View

MAP-17108 Two deviceWISE View issues

Description: Fixed the following issues in dW View version 1.3 in 21.10.

1. State text is displayed when the State Value type is selected with Value Cards.
2. A pop-up indicating properties can't be loaded are shown when the Event_Active_Production display is loaded.

---

Transaction Server

MAP-16956 Oracle Select with "LIKE" in where clause returns 0 rows

Description: Add LIKE Support for Decimal, Numeric, Float & Real datatypes in 21.10.

MAP-17107 SOAP Transport maps do not support nested structures (Issues using complex XML payloads in SOAP APIs)

Description: Fixed Nested Structure Variable Count Issue for SOAP Webservices response in 21.10.

---

Tunnel Manager

MAP-17130 Tunnel Manager leaks user's sessionId as unexpected parameter to tunnel.historyWorkbench

Description: Fixed Tunnel Manager sessionID leak in 21.10.

MAP-16882 Enhanced demand write validation failure

Description: A variable with a parentheses in the name will now resolve to correct type. Fixed in 21.10.

MAP-17123 Editing an existing SOAP transport map cannot be saved when service/port is blank

Description: Updated code so that the existing SOAP transport map can be saved when the service/port is blank. Fixed in 21.10.

MAP-16931 Transports Panel shows payload of ASCII

Description: Fixed Workbench issues associated with editing a Transport Map for an HTTP Transport, with the From Enterprise panel using the XSD option. After editing the Transport Map and viewing the From Enterprise panel the fields for the XSD Format option, the Format field showed as “ASCII”. This was corrected in 21.10. Also note that the XSD had an embedded table. The workbench correctly calculates the output variable counts for the outer and inner tables.

MAP-17112 Count for Transaction Map variables is wrong in child table

Description: Fixed issue where a SOAP Transport with a .wsdl file that contains a parent table with a child table. The Transport Map prompts the user to provide the number of rows that the table will contain. With this value it updates the Count field associated with the Mapped Variable. The Count field for the child table was not being calculated correctly. The map count hierarchy was corrected in 21.10.

---

Drivers

MAP-16986 Approximately every 50 minutes Azure IoT Hub connection enters S&F state

Description: Will not switch to Store and Forward on token rotation. Fixed in 21.10.

MAP-16782 Update diagnostics file to capture BACnet diag files

Description: Update diagnostics file to capture BACnet diag files and put them in the correct folder. Fixed in 21.10.

MAP-16999 Valgrind Leaks in dwkawasaki driver

Description: Fixed Valgrind leaks in 21.10.

MAP-16991 dwkawasaki crash in Linux-X64 Node

Description: Changed the stack size of status thread to fix crash in Linux X64. Fixed in 21.10.

MAP-17070 Modbus - 'bitno' bits 0 though 7 return the value '-1'

Description: Modbus XML files support bit offsets within Word based registers. Fixed in 21.10.

MAP-16749 'bitno' Bit Number Causing Trigger Validation Fail (Modbus XML)

Description: Initial changes to save the bitno in custom instead of vinfo for bool created from holding in xml. Fixed in 21.10.

MAP-16760 The VIN field is too small for PowerMACS controllers

Description: Allow up to 40 characters for the Atlas PowerMACS controller VIN if version is < 2 on the MID0052 message. This only affects the Atlas Copco driver. Fixed in 21.10.

MAP-17017 License unavailable for Device[TCP]

Description: Corrected handling of licenses so that the TCP listener device now uses and releases licenses appropriately; customers should not see an error message acquiring licenses in the Exception logs when there are sufficient licenses available. Fixed in 21.10.

MAP-17029 OPC UA Client Driver -- after starting --- goes disabled

Description: Some servers are not able to service the number of items that can be read at the rate they claim. To correct increase the read timeout to 10000 and reduce the Max Nodes Per Read to 100. Fixed in 21.10.

MAP-16897 OPC UA Server subscriptions are failing when the Admin password has been changed

Description: Corrected issue to allow OPC UA Server subscriptions after changing the Admin password. Fixed in 21.10.

MAP-17085 DEVICE_ADD_VINFO error messages need to be more descriptive in FanucCNC driver

Description: Added device and variable name to error message when device_vinfo_add fails in 21.10.

---

New HTTP Server (Technology Preview)

MAP-15556 HTTP Server still accepts connections when stopped from deviceWISE View in same browser

Description: The new HTTP server does not have this problem as soon as the flag is changed to not running, all operations will stop immediately. Fixed in 21.10.

MAP-16496 Enterprise node crashing in the area of HTTP server

Description: Fixed with new HTTP server in 21.10.

MAP-16139 Inconsistency in HTTP Total License Count

Description: Fix system var to show total license count + free. Fixed in 21.10.

MAP-14695 HTTP Server - ERR_CONTENT_LENGTH_MISMATCH

Description: Fixed memory leaks in 21.10.

MAP-16982 Setting up the deviceWISE for a GCP Service Account leads to "File not found"

Description: Fixed in 21.10.

MAP-15587 deviceWISE View can hang Asset Gateway nodes due to lack of pool threads

Description: Fixed in 21.10 by using the newer HTTP Server.

MAP-16839 deviceWISE Crashing When Editing in deviceWISE View

Description: Introduced an error in 21.07 when a publish can crash when doing a null check on the last element. Fixed in 21.10 by reverting code and going back to logic used in 21.06 and earlier releases.

MAP-16878 dwhttp response slow and sent in chunks

Description: Replaced polling with interrupts in new HTTP server. Fixed in 21.10.

MAP-16879 dwhttp missing certificate causes HTTPS server to fail to start

Description: Added status to both HTTP and HTTPS server. Fixed in 21.10.

Generally Available
Device Driver	Version
AcraDyne driver	1.1.2
Advanced Display Protocol	1.0.1
Apex Cleco driver	1.9.2
Atlas Copco driver – updated in 21.10	3.6.3
Azure – updated in 21.10	2.1.6
Beckhoff driver	2.1.6
Danlaw	2.12.2
Estic driver	1.1.2
FANUC CNC Driver	1.3.0
Fanuc driver	2.3.1
Industrial driver	Updated with each release
Ingersoll Rand driver	1.3.2
LDAP – do not use with Linux X86 and 21.10	1.1.1
Lua	1.1.2
Mitsubishi driver	3.3.6
MindSphere– do not use with 21.10	2.0.4
Modbus driver– updated in 21.10	2.10.5
Modbus Server driver	1.1.8
MQTT driver– updated in 21.10	2.0.7
MTConnect driver	1.2.7
NMEA GPS	1.0.3
OAuth2	2.3.0
Omron driver	3.7.5
OPC-DA Client driver– only Windows x86	2.6.1
OPC-DA Server driver– only Windows x86 – updated in 21.10	1.1.5
OPC-UA Client driver – updated in 21.10	4.0.0
OPC UA Server – updated in 21.10	1.2.1
Rockwell driver	2.19.0
Rockwell ControlLogix driver	Updated with each release
Schneider Electric	2.9.0
Siemens S7 driver– updated in 21.10	2.11.1
Stanley Tools driver	1.1.2
Sysmon	1.0.2
TCP Listener	2.3.3
TR50	2.5.3

Pilot Ready
Device Driver	Version
Bosch Rexroth driver	1.8.2
ROC Plus driver	2.0.2
SNMP driver	1.1.0
Sturtevant Richmont driver	1.8.2
deviceWISE View – updated in 21.10	1.3.0

Technology Preview
Device Driver	Version
AWS – updated in 21.10	0.2.3
BACnet / IP driver– updated in 21.10	3.1.0
Barcode Scanner	1.1.0
CODESYS driver – updated in 21.10	0.6.0
CTI (Control Technologies Inc.) driver	2.1.4
Dell Edge Gateway (Linux 64-bit)	0.5.0
EDU (not built for Windows 64-bit)	1.0.0
E-Sensors	1.0.0
File Watcher	1.0.4
Google Cloud Platform (GCP)– updated in 21.10	0.3.2
GrovePi driver(Only in Raspbian directory)	1.0.1
HTTP Server - new in 21.10	0.5.0
IBM Maximo	1.1.0
J1939 IXXAT device Driver	1.1.0
JSON	0.5.1
Kawasaki – updated in 21.10	0.6.2
ScanTools OBD-II	1.0.0
Pepperl+Fuchs	1.0.1
Sandbox	1.1.2
Serial	1.2.0
SICK CLV Scanner	1.1.3
Telit SmartIO	2.2.0
Virtual	1.3.0
Xirgo	1.3.0
Zaxis (only built for Windows products)	0.5.1

deviceWISE Enterprise Gateway products

• Software Products
  • AIX 64-bit (Version 6.1 and Version 7.1 and Version 7.2)
  • Linux 32-bit (CentOS 6)
    • No CentOS 5 Support
  • 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 32-bit (Windows 7, Windows 10, and Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016; Windows Server 2019 )
    • No support for Windows Home Edition
  • Windows 64-bit (Windows 7, Windows 10, and Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016 64-bit, Windows Server 2019 64-bit )
    • No support for Windows Home Edition
• Embedded Products
  • Dell Edge 5000 - WindRiver Linux 7; Ubuntu Server
  • Mitsubishi MES Interface IT **** We discontinued this with 20.1.10 ****
  • Mitsubishi WinCPU ** Supported through 21.06 **
  • Rockwell ControlLogix
  • Siemens ERPC **** We discontinued this with 20.1.10 ****

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
  • Windows 64-bit (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 - **** We discontinued this with 20.1.10 ****
  • 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* - **** We discontinued this with 20.1.10 ****
  • Systech SysLINK SL-500 
  • Teltonika TRB Gateway (Requires glib c build from Teltonika)
  • Teltonika RUTX Router(Requires glib c build from Teltonika)
  • 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.

MAP-14633: Segfault crash on CalAmp RevG when doing a Local DB Select action

Description: When executing a trigger with the Local DB Select action on a CalAmp RevG, the node will crash with a segfault. The crash seems to only occur when the Return Result as Array parameter is set to True. No other platforms (including CalAmp RevC and CalAmp CDM-5030) exhibited this behavior.

MAP-14696: SSL Certificate Expired

Description: The self-signed SSL Certificate expired. Updating the certificate will not help because browsers are blocking all self-signed certificates. The user should provide their own valid certificate through properties when using deviceWISE HTTP server or else the browser may not allow HTTPS requests. The following properties described in Properties file management are available to configure the certificate used by the HTTP Server. For adding properties:

1. To change cert file, add/modify http.ssl.cert_file to point to a cert in PEM format relative to $INSTALL_PATH#/dwcore directory. By default, deviceWISE ships with a dummy certificate. http.ssl.cert_file=cert/server.pem
2. The cert file can have a passphrase to it. The user can add the property "http.ssl.cert_pass" to specify the passphrase. http.ssl.cert_pass=PLAINTEXT

MAP-14751: Node failed to install SUP due to file_chmod failure

Description:  chmod failed because we used it on a command instead of just the executable.

MAP-15556: HTTP server does not terminate existing connections when stopped from deviceWISE View in same browser

Description: Session count may not reset when stopping the HTTP Server until browser completely terminates all connections or until sessions expire (default 5 minutes).

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.

Asset Gateway for MultiTech rCell

MAP-17179 MultiTech rCell Firmware Update fails on recent MultiTech firmware versions.

On MultiTech rCell devices running MultiTech OS firmware versions greater than 3.x, updating devicWISE using the DWU through the Workbench fails.

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 endianness 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 endianness 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 WinCPU

MAP-17091: WinCPU does not support latest version of OpenSSL library

Description: WinCPU is not supported on releases after 21.06. The platform uses an older Microsoft Embedded Windows operating system that is incompatible with newer versions of the OpenSSL library.

Asset and Enterprise Gateway for Linux

MAP-17041: LDAP driver crashes when using Linux X86 products

Description: The LDAP package was removed from all Linux X86 products in 21.10.

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 Restarting a Node.

MAP-15124: Can't install older version of Gateway software on Windows

Description: Windows customers attempting to install an older version of deviceWISE products need to uninstall the newer version of deviceWISE first.

MAP-16801: Firmware Update fails intermittently on Windows Platforms

Description: For 21.08, Firmware updates of Windows products may have intermittent failures so the “dwu” files were removed from the 21.08 release.

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 end-of-life is 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.

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:

• https://docs.oracle.com/database/121/NETRF/sqlnet.htm#NETRF2016 (See the section on SQLNET.ALLOWED_LOGON_VERSION_SERVER. )
• https://developer.ibm.com/answers/questions/177075/after-upgrading-to-oracle-12c-database-i-start-get.html
• https://mikedietrichde.com/2017/04/24/having-some-fun-with-sec_case_sensitive_logon-and-ora-1017/.

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.

deviceWISE View – Technology Preview

MAP-16403: deviceWISE View Toggle breaks states using the BOOL variable being toggled

Description: Local variables are all string type. For Boolean comparisons use the value "1" or "0" instead of "true" or "false".

MAP-16890: deviceWISE View sometimes get stuck on Loading splash screen on first login

Description: The Loading splash screen may sometimes get stuck and will need an additional page refresh to properly update the page.

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

MAP-15099: Linux 64-bit FANUC CNC Driver does not work on CentOS 7

Description: The only Linux 64-bit environment supported by the Fanuc CNC driver is Ubuntu Server.

MAP-14436: OPC UA client and OPC UA Server do not coexist on the same node

We do not support running the deviceWISE OPC UA Server on the same node as the deviceWISE OPC UA Client.

MAP-14610: OPC UA Server retains old stopped devices when browsed by clients

Description: When devices used by the OPC UA Server are stopped, those devices are no longer exposed to clients. In some rare instances, variables from those devices are still exposed but they cannot be accessed since the device is stopped. Restarting the server will clear those device variables.

MAP-15573: MQTT extension doesn't build for AIX64 in 20.1.10 release

Description: The MQTT package for AIX does not include the MQTT updates found in other platforms for the 20.1.10 release. Enterprise GW for AIX64 in 20.1.10 uses the MQTT package from 20.1.9.

MAP-15628: OPC DA Server on Windows 64-bit crashes on start of server

Description: The OPC DA Server and the OPC DA Client are not supported on the Windows 64-bit platform. We will investigate how to add support for these drivers in a future release.

MAP-15585: MQTT extension doesn't load for WinCPU in 20.1.10 release

Description: The MQTT package for WinCPU does not include the MQTT updates found in other platforms for the 20.1.10 release. Enterprise GW for WinCPU in 20.1.10 uses the MQTT package from 20.1.9.

MAP-15838: SNMP Trap Receiver causes Linux nodes to crash

Description: The SNMP Trap Receiver will not work on Linux platforms. Receiving trap messages will only work on Windows 64-bit and Windows 32-bit products.

MAP-15862: SNMP Driver does not fail a write and misleadingly shows write is completed

Description: When writing SNMP variables, sometimes the write will timeout but will not show an error message. Check the value with a read after the write to ensure the write has actually occurred if the write seems to take more than 5 seconds.

MAP-17080: OPC UA Client XML files do not support double byte characters

Description: These characters can be interpreted as having a null character, which causes the XML document to be prematurely terminated.

MAP-16857: OPC UA Client with Startup Improvements cannot handle Unified Automation matrix array

Description: Multi-dimension arrays, also known as Matrix data items, are not supported with the 4.0.0 release of the OPC UA Client. These tags will be displayed, but attempts to read or write elements within the Matrix will fail.

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 24.01

Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 24.01 build level before starting their deviceWISE application.

For Windows Enterprise Gateway products:

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

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.6 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 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.

Upgrading a Windows Enterprise Gateway product from 19.1.6 or later to 24.01

A firmware update from a release for Enterprise Gateway for Windows before version 19.1.6 to 24.01 is not supported. You must do a complete product installation as noted in the previous section.

If you are updating an Enterprise Gateway for Windows 64-bit products from the 19.1.6 release or later, then you can use the firmware update option.

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

For AIX, Linux, or WinCPU Enterprise Gateway products:

If you are updating an Enterprise Gateway from a 17.2.3 through 21.09 (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 24.01, 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 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.

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

20.1.9 is the final release for VxWorks-based gateways and got removed from builds beginning with the 20.1.10 release. If you need assistance, please contact us here.

Updating from an earlier release of an Asset Gateway to 24.01

Customers updating from 21.05 or earlier release, will need to update both the deviceWISE runtime and the package files to the 24.01 build level before starting their deviceWISE application.

For Windows Asset Gateway products:

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

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.6 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 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.

Upgrading a Windows Asset Gateway product from 19.1.6 or later to 24.01

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.

If you are updating an Asset Gateway for Windows 64-bit products from the 19.1.6 release or later, then you can use the firmware update option.

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

For AIX, Linux, or WinCPU Asset Gateway products:

If you are updating an Asset Gateway from a 17.2.3 through 21.08 (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 24.01, 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 24.01, you will need to add all device drivers and extensions from the new 24.01 release level.

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

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

20.1.9 is the final release for VxWorks-based gateways and got removed from builds beginning with the 20.1.10 release. If you need assistance, please contact us here.