You can use the automatic reconnect feature for GigE Vision cameras (GV models) or via the uEye transport layer (UI models) if the physical connection has been interrupted and restored, e.g. in the event of voltage problems. If the reconnect feature is enabled, the camera is automatically reopened. If you have set that a UserSet is to be loaded when the camera starts up, the previous status of the camera is also restored.
Fig. 273: Camera connection is disconnected
Fig. 274: Camera connection is restored
If you change the IP address of a camera, the camera is automatically restarted and the ID loses its validity. You must update the camera list and search for the camera again, as the reconnect feature cannot be used in this particular case.
If you make a change to the network adapter, we recommend to stop all running applications and to restart the applications after the change. |
Settings in the transport layer
The reconnect feature is enabled or disabled for all cameras in the system via ReconnectEnable.
•Reconnect is currently disabled by default for GigE uEye+ cameras (GV models).
•Reconnect is enabled by default for uEye cameras (UI models) and cannot be disabled.
For the reconnect, you can use ReconnectRemoteDeviceAcquisitionRestartEnable to set whether the image acquisition should start automatically after the connection has been restored.
Module / category |
Node |
Description |
---|---|---|
Enables or disables the reconnect feature. |
||
Indicates whether the image acquisition of the RemoteDevice is automatically restarted after reconnection. |
||
Indicates whether the configuration of the RemoteDevice is restored after reconnection. Currently standard for |
||
Number of registered "EVENT_REMOTE_DEVICE_CONNECTION_STATUS_CHANGE" events. |
||
Indicates whether the reconnect feature is enabled or disabled. |
||
RemoteDeviceConnected |
Indicates whether the RemoteDevice is currently connected. |
|
Number of RemoteDevice detachments since the device was opened. |
||
Number of RemoteDevice reattachments since the device was opened. |
You can register callbacks either in the DeviceManager or in the interface. Events are only transmitted from the time of registration. If no callbacks are registered, the event is lost.
Enabling reconnect and logging events on/off (genericSDK)
genericC++ |
---|
void OnSystemFound(const std::shared_ptr<const peak::core::System>& foundSystem) |
Enabling reconnect (comfortSDK)
comfortC |
---|
peak_interface_technology interface_technologies[] = { peak_interface_technology_GEV, peak_interface_technology_U3V, peak_interface_technology_UEYE }; |
Messages for disconnecting and reconnecting (comfortSDK)
comfortC |
---|
peak_MessageQueue_EnableMessage(hMessageQueue, NULL, PEAK_MESSAGE_TYPE_DEVICE_RECONNECTED); |