2.6 Automatic Rebooting / Restarting of X Devices
Beginning with V02.14.00, the plugin is able to reboot X devices in certain situations.
The intention is to support the user in such cases, that changing certain device or system settings require
restarting the whole device chain. In these case the reboot is done automatically by the software such that it
is no further action is needed by the user (here, powering off and on the X device chain after changing
certain settings and doing a hardware initialisation).
The automatic reboot is done per (X) system (ethernet connector). It requires, that ALL X devices that are
connected on the same ethernet interface have a firmware of V02.12.00 or newer.
The reboot command is sent in following situations:
Changing the IP-Address settings from the PlugIn's options dialog (and at least one device responded on
that command)
At the end of the hardware initialisation.
In the situation of (1), the command is sent always!
This is due to the fact, that it possible to call the command for changing the IP-Address independent from
any configuration, hardware detection or initialisation - therefore it is unknown, how many or which devices
are connected to the bus or not.
In the situation of (2), the command is executed directly after the hardware initialisation in following
situations:
The system is a X system, meaning there is at least one X-Device in the system
All configured X devices do have a firmware version of V02.12 or newer installed and
Prior to the initialisation on of the following has been done
The system parameter "Internal time synchronisation" has been changed
The front number of any X device has been changed
The device type has been changed into any of the X device types
The configuration has been loaded and is yet not initialised
A device has been manually added
The options dialog has been closed with "OK" (this automatically reloads the configuration and such the
situation above is encountered)
However, there are some limitations and drawbacks:
The X-PlugIn does not know anything about the devices, that are NOT in the configuration but are connected
to the same ethernet connector.
Therefore, it is possible, that all devices in the configuration have a firmware V02.12 or newer, but there are
further devices connected with firmware smaller than V02.12. In such situations, the PlugIn does send the
reboot command on the bus. However, the devices not supporting the command do not restart. This leads
into the situation, that the IP addresses / bus master / PTP operation mode are set new in the rebooting
devices but not in the others. After such situation, the device chain has to be restarted manually by powering
off and on the whole chain. Otherwise, the communication is corrupted and the whole chain is no more
working!
Further, the reboot is always executed in above situations since the plugin does not know
the device states (hardware) after loading or manually editing a a configuration. Therefore, the reboot is
done always.
The rebooting itself takes approximately 6 seconds. If changing the IP address, the process takes a bit
longer, since the PlugIn does not know, which devices are connected and has no information about the time,
when the devices are restarted and ready for measurement again. Therefore, a time out value of 10s is used
here.
To Next Page
Loading...
Need help?
General