- 07 May 2021
- 11 Minutes to read
Secomea RDM 6.0 build 15432
- Updated on 07 May 2021
- 11 Minutes to read
Software Release: Secomea RDM 6.0 build 15432 - Public release
Release Date: 2015-10-23.
(c) Copyright 2015, Secomea A/S. All rights reserved.
Scope and production information
This is Secomea Remote Device Management release 6.0 build 15432.
This release note describes changes since release 5.11 build 15175.
SiteManager 3349 - Hardware, DIN mount, integrated WiFi Client
SiteManager 1149 - Hardware, DIN mount, integrated WiFi Client
SiteManager 3439 - Hardware, DIN mount, 4-port switch, integrated 3G
SiteManager 1439 - Hardware, DIN mount, 4-port switch, integrated 3G
SiteManager 3429 - Hardware, DIN mount, 4-port switch, ext 3G (USB)
SiteManager 1429 - Hardware, DIN mount, 4-port switch, ext 3G (USB)
SiteManager 3239 - Hardware, DIN mount, integrated 3G
SiteManager 3339 - Hardware, DIN mount, integrated 3G (new model)
SiteManager 1039 - Hardware, DIN mount, integrated 3G
SiteManager 1139 - Hardware, DIN mount, integrated 3G (new model)
SiteManager 3339 4G-CN - Hardware, DIN mount, integrated 4G (new model)
SiteManager 1139 4G-CN - Hardware, DIN mount, integrated 4G (new model)
SiteManager 3229 - Hardware, DIN mount, external 3G (USB)
SiteManager 1029 - Hardware, DIN mount, external 3G (USB)
SiteManager 1129 - Hardware, DIN mount, external 3G (USB) (new model)
SiteManager 3129 - discontinued - last public release is 5.11
SiteManager 3034 - discontinued - last public release is 5.11
SiteManager 3134 - discontinued - last public release is 5.11
SiteManager Embedded 6110 - Software, for Windows XP, 7 and 8
SiteManager Embedded 6111 - Software, for Linux Operation system.
SiteManager Soft 6040 - Software, - last public release is 5.11
SiteManager PC 6240 - Software, - last public release is 5.11
LinkManager 6041 - Software
GateManager software release 6.0 or later is required to fully utilize
the features of RDM release 6.0 and later.
LinkManager Mobile software is released as part of the GateManager server,
and is not covered by this release note.
- Highlights of this release
New product SiteManager 1139 4G-CN and SiteManager 3339 4G-CN with support
for Chinese 4G/LTE standards.
LinkManager now supports Windows 10.
Layer2 support (for initial device discovery and configuration).
Support for GateManager 6.0 "fast data tunnels".
LinkManager dynamic bandwidth adaptation for better end-to-end data flow.
Support for UNICODE characters in appliance name and domain tokens.
- New features and improvements
Add support for Windows 10. (#6988)
Add support for generic "Layer2" agents. (#6630)
This feature allows programs, such as Siemens TIA portal and Schneider
SoMachine, which rely on low-level, non-routable discovery and control
protocols, to connect seamlessly through the LinkManager and SiteManager.
Notice that using a Layer2 agent typically has lower throughput than
using a dedicated agent for a device, since end-to-end buffering and
throttling for Layer2 protocols is less effective than for higher
level protocols based on TCP and UDP.
Layer2 agents use a "yellow shield" icon to remind the user that these
agents should only be used for special purposes like device discovery,
pairing of new devices, etc.
Notice that doing a
to a SiteManager will not include
Layer2 agents; if a connection to both normal and a Layer2 agents is
required, use an agent group. However, an agent group may only include
one Layer2 agent; if more than one is used, the result is unpredictable.
Add support for "Fast Data Tunnels" via GateManager.
This feature has a lighter load on the GateManager, and reduces data
buffering and throttling inside GateManager which improves end-to-end
performance over "unbalanced" lines between LM/GM and GM/SM. (#6471)
In addition, LinkManager has a new Connection Speed Control (CSC) auto-tune
feature, which dynamically adjusts the transmission speed to the available
end-to-end bandwidth through the Fast Data Tunnel.
The LinkManager Console will show the currently available bandwidth and there
is also a user option to temporarily disable (and restart) CSC if the
actual bandwidth "auto-tune" seems to be too aggressive.
Add mouse-over to explain
appliances in LM console. (#6793)
Check if some other Secomea Software (such as TrustGate SoftClient) is
already running on the same PC when installing LinkManager, and offer
to Abort (cancel LinkManager installation), Retry (after shutting
the other Software down), or Ignore (continue running both at own risk).
LinkManager GUI now supports using UNICODE characters in passwords
and the integrated CHAT feature. (#6761 #7231)
SiteManager 14xx models now includes 5 agents (not expandable). (#7080)
SiteManager 34xx models now includes 25 agents, expandable to 100 agents.
Add support for "Fast Data Tunnels" and "auto-tune" via GateManager
[see above]. (#6471)
Add support for generic "Layer2" agents [see above]. (#6630)
SiteManager GUI now supports using UNICODE characters in input fields
and the integrated CHAT feature.
When writing UNICODE into the configuration, they are converted using the
generic HTML 〹 format, which is compatible accross all SiteManager
releases and models. (#6761)
The appliance name and domain token fields may now contain up to 250
characters (after conversion to the 〹 format).
Notice that the field values may be truncated by the GateManager
depending on the server's limits (typically 48-64 UNICODE characters
or 128 ASCII characters). (#6881)
Add "Always + Static Routes" choice to the DEVx "Auto-subnet agent" settings.
When selected, this enables forwarding of traffic from a LinkManager to any
of the subnets specified in the SiteManager's Routing > Static Routes which
have a gateway on the corresponding DEVx interface. (#7072)
Append [Mobile broadband] instead of [3G] to SiteManager model name
when a (USB or internal) modem is detected. (#7149)
Allow using "DEV1", "DEV2", etc as aliases in IP/Hostname configuration
Allow static IP configuration of WiFi client interface. (#6617 #6856)
Avoid browser's offering to save passwords which are not related to the
user login (e.g. Web proxy password).
You may notice that password fields on the SiteManager GUI will be
cleared temporarily when clicking on the "Save" button. (#6684).
To reduce confusion about the default password, it is now identified as
(MAC address) rather than (Serial number), since the physical label on the
SiteManager does not explicitly identify the printed "MAC address" as a
serial number. (#7024)
Use the MAC address as default WiFi key in client mode. (#6933)
Local certificate (for EasyTunnel) is now SHA256 signed.
Remove per-agent and per-relay "Encr" options to remove the risk of
sending data unencrypted due to a user mistake. (#6471)
Improve validation of EasyTunnel settings, and disable the feature
if any of the values are deemed invalid. (#7122)
No longer send interface link up/down audit log events to GateManager.
Add support for GateManager Discovery Service. (#6471)
Add "No SiteManager Embedded license" message on SETUP wizard. (#6970)
Show "Pending SiteManager Embedded license from GateManager" message
until SM-E has connected to a GateManager for the first time (#6965).
Show "Deleted on GateManager" when applicable. (#6965)
Add online help for "agent parameters". (#7099)
Added SM-E status API: (#7082)
A HTTP request "http://127.0.0.1:11444/icon" will now return the "icon
state" and mouse over text of the (possibly non-existing) tray icon.
Add support for new variant of Huawei E303/E3131. (#6838)
Add support for Huawei EC3372. (#6649)
Add support for Forge SLM630. (#6992)
Add support for several other USB modems.
Add APNs for China Telecom. (#7161)
New Device Agents:
Generic > Layer2 (#6630)
Beckhoff > Embedded Agent [SM-E only] (#7079)
Bihl+Wiedemann > USB (#7058)
Danfoss > USB CAN adapter (#6862)
Exor > Jmobile (#7063)
FlexEm > USB HMI (#6842)
IFM > USB CAN adapter (#6231)
Kvaser > USB CAN adapter (#6862)
Parker > PAC Controller (#7127)
SAIA > USB PLC (#7156)
Sick > Ethernet (#7057)
Updated Device Agents:
- Allen Bradley > USB PLC (#6949)
- GE-IP > QuickPanel+ (#7043)
- IDEC > USB (#5537)
- Hirschmann > Ethernet (#6922)
- Mitsubishi > Ethernet (#6875)
- Omron > Ethernet HMI (#6798)
- Panasonic > USB PLC (#7118)
- Pro-face > Ethernet (#7036)
- Rockwell > USB PLC (#6949)
- Schneider > Ethernet (#7016)
- Wago > Ethernet (#6877)
Removed/obsoleted Device Agents:
- Secomea > SiteManager FTP -- use Generic > FTP instead (#7091)
- Bug Fixes
The LinkManager Installer has been optimized and should run a lot faster
for a fresh installation.
When the LinkManager Installer is used to upgrade an existing LinkManager,
it will now uninstall all previously installed versions of various drivers,
so that only the newly installed drivers exist when the installation
completes. This means that it may take some additional time to upgrade
to LinkManager 6.0, but future updates should run much faster.
The GateManager administrator login link now uses https protocol. (#6687)
In a dual-UPLINK setup, an operational GateManager connection was typically
reconnected after approx. 1 minute after (re)starting the SiteManager.
Now, this only happens during probing. If the first GateManager connection
is using a lower priority UPLINK interface, and a higher priority interface
becomes operational. (#4726)
Improve compatibility with some WiFi Access Points, where SiteManager
previously failed to get an IP address. (#6267)
When doing a WiFi scan, say "No IP Address" instead of "Connected" unless
SiteManager has actually been assigned an (operational) IP address. (#6208)
On the Setup Wizard, show WiFi Down in "Red" instead of "Green" (#6208)
Fix display of frequency and signal quality of integrated WiFi. (#6208)
Don't retry modem setup if SIM code is wrong or missing. (#6898)
Stability fixes for SiteManagers with integrated WiFi. (#6828)
The IO port status was sometimes missing on the GateManager > Alerts page.
A long-time running SM could fail to connect via PPPoE or using SMS-Wakeup
via 3G. (#5460, #6613)
Fix missing detection of 3G modem in some cases when another USB device
is plugged in. (#6231)
Fix rare situation where the SiteManager could fail to reboot itself.
Fix inability to upgrade SiteManager firmware due to too little free
memory to load and validate the firmware upgrade image. (#7017 #7228)
Include "available memory" information in extended status.
Do not start (and show error for) a Generic > Device agent with no
specified ports or services. (#6366)
Automatic "device service detection" would continue to run after disabling
an agent using that feature. (#7140)
SMS Wakeup Parameters field is now marked as mandatory if UPLINK Mode is
set to SMS Wakeup. (#6315)
No longer log receiving of malformed UDP packets in the system log. (#4546)
Improved Ethernet driver stability under heavy network load. (#7173)
Specifying a WiFi SSID but no WiFi Key would continuously reboot the
SiteManager every 5 minutes. (#6933)
Setting UPLINK2 mode to SMS Wakeup was cleared by restart. (#6918)
Disable UPLINK load-balancing on SiteManagers (since they only have one
UPLINK Ethernet port). (#6664)
Fix minor memory leak when accessing the SM-E GUI. (#6789)
Fix Ping and Restr checkboxes misalignment on GateManager > Relays page.
Fix missing connection cleanup after failure in SM-E for Linux. (#7009)
- Upgrade information
Starting with release 5.2, the SiteManager firmware file format has been
extended to include digital signatures, and once updated to this revision,
it is not possible to downgrade the firmware to an older version than 5.2
via the SiteManager web GUI, as older SiteManager firmware files do not
have the required digital signatures.
If - for some reason - you need to downgrade to an older firmware without
the required digital signatures, you can use the "Upgrade firmware"
command in the GateManager portal.
Note that all Software products - LinkManager, SiteManager Soft,
and SiteManager PC - must be upgraded by running the corresponding
Setup program using an administrator account.
Except for SiteManager Soft, you must use the Setup program corresponding
to the Windows architecture (32 or 64 bit).
LinkManager and SiteManager PC come with a set of Windows drivers that
will be installed or upgraded when running the Setup program. You may
have to confirm the installation of these drivers.
First time you start the LinkManager after the upgrade (or after a new
installation), you may be prompted to accept the installation of
Secomea's CA certificate as a trusted root certificate. You should
allow this to prevent Windows from looking for new drivers on the
Windows Update site each time you establish a serial or USB connection.
SiteManager Soft requires VMware to operate, also after the update.
- Known issues or limitations
SiteManager WiFi supports WPA/WPA2 and TKIP/AES encryption.
WEP is not supported.
WiFi access points that require web page login are not supported.
Note that using the PPI option requires optimal bandwidth for both
the LinkManager and the SiteManager. This is due to the PPI protocol and
Step7 software by design do not take into account the delays (latency)
that may occur when relaying the communication over long distances.
The Siemens Step5 agent requires optimal bandwidth for both the LinkManager
and the SiteManager.
When UNICODE is used in agent names, the output under Log > View will
show encoded versions of the names, so they are not legible to the user.
When connecting to a Layer2 agent with LinkManager on Windows XP, the
Layer2 adapter will only be operational after a restart of the Windows
If the LinkManager has been restarted you need to reboot your computer to
reenable the layer2 support. (#7254)
The LinkManager account name is used as the LinkManager's appliance name
in the GateManager portal and in the LinkManager console. If the account
name includes UNICODE characters, these are shown as ~ in the corresponding
LinkManager appliance name.
Even though it is possible to configure and connect to multiple USB agents
on a given SiteManager, it is currently not possible to use more than one
device of any given type (there is currently no way to differentiate
between such identical USB devices).
Due to restrictions on secure web-site certificate authentication, most
modern browsers may prevent you from accessing https based services via
the LinkManager's Go To Appliance functionality in the non-activated
state (Domain view).
This is because the Go To Appliance function uses a different IP address
than the actual IP address of the remote device, so the browser suspects
that the target device's certificate (typically self-signed) may be a
There is no easy way to get around this problem, so you will have to
follow the somewhat tedious procedure of your browser to bypass the
warnings and connect to the device anyway.
Note: You should not store the certificate permanently in Firefox.
Go To Appliance in GateManager and LinkManager Mobile does not have this