28
6
Communication Functions of the LAN Interface
BVS SC-_1280Z00-07-0_0
SMART
CAMERA
IO
english
The UDP sockets provide a similar functionality as that provided via the fieldbus interface. Port
36701 is used in all cases.
To establish the connection, the camera expects a Connect message, then it starts to send out
status updates and result data. If a client no longer wants to receive any additional data from the
camera, he dispatches the Disconnect message and then closes the socket.
The camera responds to a Connect message with a Connect response; in addition, the camera
then sends a status message to the client so that the client is informed about the current status
of the camera.
The camera supports only one active client. If a UDP connection exists, it is being exited as soon
as a new request is placed by another client.
Invalid messages are ignored by the camera.
The message elements consist of unsigned 32-bit numbers (UINT32) and byte strings. They are
transferred using the little endian format. The lowest value byte is transferred first in this case.
There are three different categories of messages:
1. Messages from the camera to the client
a. Status
b. Result containers
2. Messages from the client to the camera
without a response
a. Disconnect
b. Set time stamp
c. Setting input data
d. Set sequence number
e. Trigger application
f. Start application
g. Stop application
h. Trigger reset
3. Messages from the client to the camera,
which then sends a response after the
action is complete.
a. Connect
b. Switch application
c. Query application
d. Get the time stamp
All messages have the same structure.
Length in bytes
Structure
Description
4
UINT32
Magic Number: 42565350
hex
4
UINT32
User data length in bytes
4
UINT32
Message ID
4
UINT8[]
User data
Messages that do not meet the specified format (wrong "Magic Number", wrong length,
unknown message ID), are ignored by the camera. The "Magic Number" is used to avoid inad-
vertent transfers. It is recommended to watch for a correct "Magic Number" at the receiving
point when programming the client software.
6.1
General
Information
6.2
Structure of
the Messages