With this thread I am asking for help in establishing serial (RS232) communication with my thermal imaging cores. It's essentially the current roadblock I had in my project for over a year (
https://www.eevblog.com/forum/thermal-imaging/thermal-camera-for-filmmaking-and-photography/).
I do have some documentation for the cores including pinot and serial commands. I will later on post of excerpts of those.
I explained my issue in the linked thread, but I wanted to post a threat just on this issue to give it more reach. The main problem I am having seems to be that the camera core is not recieving my commands.
I wired up the serial output, serial input and 0V to the Rx TX and GND pins on my RS232 USB interface and turning the camera core on gives me the a status message from the camera of software and hardware versions. Followed by "DSP:>"
If I set the baud rate to 115200 as indicated by the documentation the camera only responds with "camera baud is 9600".
I strongly believe that I am recieving signals from the camera correctly as this is both expected behaviour as per documentation. Said documentation also details how the camera can receive commands via a data or via text format. And no matter what text commands I send nothing happens. There is no response and "reset" also triggers no restart of the core.
I measured a connection from the input pin to the ground pin when connected to the usb interface. This is one point I am unsure about. If I connect the interface to itself, I do get the expected ping pong loopback.
Open questions are: what does the DSP mean here? I suspect it might be a password or handshake that it is waiting for, but I haven't found any refence to such functionality in my documentation. The only DSP mentioned is about how the camera core can control lens Focus via commands. Which is likely what is was doing. The camera was wired up to all tree pins mentioned as well as had a motorized lens system. I even have a controller joystick with a focus knob. I will append this section of the documentation later this weekend.
Options I currently have left:
-try to communicate via "data" commands
-try a different serial interface
-get a scope and find how far the signal goes
I would like to know if I am missing anything here as I haven't worked with serial interfaces before and I don't have much equipment right now to go deep. As this project has been stagnant for a long while, I am determined to progress with it, especially if that means buying new equipment like a scope that can decode serial.
Vipitis