Production Camera The Production Camera in this case broadcasts data to one of it's Ethernet Ports. The challenge is that this is not really an unsolicited message because the data is not sent to the PC's port, so the device is not creating an Ethernet connection. It's also not exactly a solicited message because the Camera does not respond to any particular commands for data. To set this up correctly it had to be done as a solicited message transmitting a null character. Once the connection is made to the Camera's port it starts to send it's data to the UCON, ignoring the null character.  Once the null character is transmitted and data starts to return in a single stream for all the tags. The stream needs to be captured in the read buffer using the Read Response command and looks for a caradge return (0x0D), line feed (0x0A) to identify the end of the message. This message also has a leading character that is not part of the data to be put into tags, so the Move Buffer Pointer command is used to point to the second byte for the data1 tag. The Data1 tag is configured as a specific data type and will read up to the correct number of bytes for the data type.  The Buffer Pointer is now pointing at the byte following the Data1 tag information. This byte has a comma separator in it which we don't want to read so we Move the Buffer Pointer one byte again to start at the next tags information. This same format is then followed for the rest of the tags. There are other devices like this that will ignore the null character, but some will return an error and not return the data. Some devices will send an error, but when data is ready will send it through the connection. If this is the case long time-outs need to be set in the server to handle the wait time. Please contact us for assistance with this type of device.