I'm working on a project to replace the controller for a PTZ security camera, and our current setup has a homemade controller sending movement commands to (and receiving acknowledgment from) the camera over RS485 serial communication. The data sheet shows the commands in hexadecimal format (0xFB), and when I connected to the serial bus with my PC's port emulator, I would see the same "FB" shown in the monitor pane.
For the new controller I'm making, the PLC is intended to communicate with the camera through an Ethernet-to-ASCII (RS485) gateway. During bench testing though, when I have the port emulator's monitor set to hexadecimal, the messages appear as "35 35 35" or something to that effect ufone call packages, but when set to a string, it'll show only as the decimal value of the hex value I transmitted from the PLC (I'll see "255" instead of "FF").
I need to wait until after the July 4th holiday to run the question past the camera manufacturer's tech support, but with the gateway transmitting characters in ASCII as opposed to the format the original controller is using, am I overthinking this, or do I need to buy a new gateway?
For the new controller I'm making, the PLC is intended to communicate with the camera through an Ethernet-to-ASCII (RS485) gateway. During bench testing though, when I have the port emulator's monitor set to hexadecimal, the messages appear as "35 35 35" or something to that effect ufone call packages, but when set to a string, it'll show only as the decimal value of the hex value I transmitted from the PLC (I'll see "255" instead of "FF").
I need to wait until after the July 4th holiday to run the question past the camera manufacturer's tech support, but with the gateway transmitting characters in ASCII as opposed to the format the original controller is using, am I overthinking this, or do I need to buy a new gateway?
