31st October 2022 (Europe 1) - Developer Documentation
Skip to content

31st October 2022 (Europe 1)

Scope

We have worked hard to deliver a great MindSphere experience. These release notes are relevant for MindSphere release by October 2022 and include new and adjusted features or fixed issues. If you find other issues, please give us your feedback by contacting our MindSphere Support.

MindSphere Remote Service

Applicable for

  • MindAccess IoT Value Plan
  • MindSphere Packaging and Pricing

What's new?

  • File transfers via UI are now recorded in the MRS audit log.
  • User documentation now outlines additional connectivity setups and hints in sections "Advanced Connectivity" and "Troubleshooting".
  • User dialogue for removing Service Assets in secondary device networks was enhanced.
  • Usage of Proxy Unaware protocol routing as provided by MRS Engineering Option was improved reducing the need for TIA cloud connector.
  • Connections from a Service Network to a Device Network may now be configured such, that the establishing of such connections demands approval by the responsible Site Owner. Configuration is done in MRS V2 during the definition of a Protocol Application, and approval is available to Site Owners via the "access requests" page on the left side of MRS V2.

Note

Most functional extensions of MindSphere Remote Service become only available under new MindSphere packaging and pricing. So please reach out to your Sales representative to have your subscription to IOT value plan upgraded accordingly.

System Requirements for MindSphere Remote Service (MRS)

Browser-based access to MindSphere Remote Services App on MindSphere

  • Microsoft Windows ® 10 version 1909: Google ChromeTM (version 68 or newer)
  • recommended screen resolution: 1280x1024 and 1920x1080 with zoom level 100%

Requirements for service personnel's PCs hosting MRS Service Endpoint (former Operator Client) as entry point for network-to-network access

  • Service Endpoint (Operator Client) can be downloaded from MRS
  • Validated Hardware

    • Processor: x64-based (Intel or AMD)
    • Display size / resolution: 1280x1024 and 1920x1080 with zoom level 100%*
    • Disk space occupied by Operator Client: 32MB
  • Validated Operating Systems and Browsers

  • Microsoft Windows ® 10 Version 1909
  • Linux ® Debian 9
  • Linux ® RedHat 7.6
  • Google Chrome TM version 68 or newer

Requirements for accessed devices hosting MRS Device Endpoint (former Device Client) as end point for network-to-network access

  • Device Endpoint (Device Client) can be downloaded from MRS
  • Validated Hardware

    • Processor: x64-based (Intel or AMD)
    • RAM: 0.5GB
    • disk space occupied by Device Client: 32MB
  • Validated Operating Systems

    • Microsoft Windows ® 10 Version 1909
    • Linux ® Debian 9
    • Linux ® RedHat 7.6

Known issues

  • Service Assets may be serviced without upfront registration by means of On-Demand Devices via MRS V.1. Such On-Demand Devices have an expiration date, and they will show up in the MRS device tree until then. The expiration date is not enforced, so manual de-registration is necessary.
  • Configuration changes are tracked in audit trail and system logs. Selected changes could be also be propagated via email notifications, which are not available for connection establishment.
  • It is recommended to have "Lock Connectivity" targeting an entire site deactivated when working on the related Service Asset to ensure its proper setup.
  • In rare occasions a gateway device might not display devices in secondary networks, which are connected to it. Please restart the gateway device or add another device.
  • Notification on successful deletion of devices in secondary networks, which are connected to an IPsec router, might not disappear, even though the device was successfully deleted - please relaunch MRS.

Except where otherwise noted, content on this site is licensed under the Development License Agreement.


Last update: November 18, 2022