Results

MindConnect Hardware Release Notes

General

  • MindSphere provides a highly reliable system, however the MindConnect can be affected by system internal incidents.

  • The MindConnect system sends data into the MindSphere. If the data provider (e.g. OPC server) is not available a value "0" with a bad quality code will be sent up. To see the quality code in the IoT model it is necessary that the quality code is always turned on at the creation of aspects.

  • We recommend to use an OPC UA server as data source with a certificate.

  • For a connection to MindSphere Region China 1 the MindConnect Nano/IoT2040 has to have a firmware V3.3.00.04. or higher.

MindConnect Nano

What's new?

  • Within this release, we have enabled OPC debug logs via UI for debugging.

  • It is now possible to auto-update your device by marking it as auto-toggle.

Known issues

  • The read performace of the OPC UA events are reduced in this release. This can cause some lost OPC UA events if the device is already at the performance limits.

  • It is recommended to restart MindConnect Nano/IoT2040 after changing system time via SetSystemTime USB command to make sure that data collection can continue correctly.

  • The connection to a SIMOCODE, SIMOTION, SINAMICS OPC UA Server cannot re-establish automatic if the used Firmware has a MiniWeb version <V5.1. It is recommended to upgrade to a new FW version of the SIMOCODE, SIMOTION, SINAMICS device.

  • RestricedDeviceConfiguration: Any Boolean type values need to be set as string values (as shown in the documentation).

  • With the latest release, MindConnect Nano and Iot2040 boxes with firmware older than V03.03.00.00 b003 version, will no longer support configuration updates. You can still do an online or offline firmware update to keep using the Nanobox with more and extended features released in final version.

  • Command functionality ( BiDirectional communication): Write Bool values : :"true" and "false" values are expected.

MindConnect IoT2040

What's new?

  • Within this release, we have enabled OPC debug logs via UI for debugging.

  • It is now possible to auto-update your device by marking it as auto-toggle.

Known issues

  • The read performace of the OPC UA events are reduced in this release. This can cause some lost OPC UA events if the device is already at the performance limits.

  • It is recommended to restart MindConnect Nano/IoT2040 after changing system time via SetSystemTime USB command to make sure that data collection can continue correctly.

  • Currently, the performance of the IoT2040 is limited. If your configuration is at the limits (30 data points per second / 6 data provider / 10 events per second), then it might cause some read limitations.

  • The connection to a SIMOCODE, SIMOTION, SINAMICS OPC UA Server cannot reestablish automatic if the used Firmware has a MiniWeb version <V5.1. It's recommended to upgrade to a new FW version of the SIMOCODE, SIMOTION, SINAMICS device.

  • RestricedDeviceConfiguration: Any Boolean type values need to be set as string values (as shown in the documentation).

  • With the latest release, MindConnect Nano and Iot2040 boxes with firmware older than V03.03.00.00 b003 version, will no longer support configuration updates. You can still do an online or offline firmware update to keep using the Nanobox with more and extended features released in final version.

  • Command functionality ( BiDirectional communication): Write Bool values : :"true" and "false" values are expected.

MindConnect Software Agent

What's new?

  • It is now possible to auto-update your device by marking it as auto-toggle.

Known issues:

  • File transfer needs to be re-configured after firmware update, if it had been configured before.

  • If you have used MindConnect Software Agent V03.06.00.00 b008 for a longer time, it is recommended to install a newer MindConnect Software Agent version by using the InstallShield setup, instead of updating the firmware by either online, or firmware update.

  • InstallShield setup has to be used to install an older MindConnect Software Agent version. This is because, the downgrade to an older version is currently not supported MindConnect Software Agent.

  • Old MindConnect Software Agent installations have to be uninstalled before new MindConnect Software Agent version can be installed by using the InstallShield setup, in case of an upgrade setup will show a message and abort afterwards.

  • Encrypted onboarding is not possible in this release

  • While adding, modifying, or removing an MindConnect Software Agent (MCSA) VM in MCSA setup all running MCSA VMs will be stopped and re-started after the setup process has finished

  • During setup of the MindConnect Software agent you will be prompted for the memory usage. As the default is quite high (16GB), please adapt this to your needs.

    If you do an installation update, this will be not asked again, so you have to adapt it within the HyperV application.

Chap. 1.2.2