I’m working on connecting a raspberry Pi to the S500 but I want to use my own software so that I can incorporate other devices like GNSS and maybe a water velocity sensor. I program in c++ (using QT) and have connected several devices using serial ports. This leaves me with some questions about where to start with the S500.
- I think that I prefer USB to serial so that I don’t have to build any wire harnesses. I have connected to the USB ports of other devices as serial ports, might that also work with the S500?
- If USB to USB does not work, I have a usb to serial port that I frequently use with my PI through the USB port…can I connect this type of serial port to the 3.3 v serial port of the S500 or will differences in voltages be a problem? - I suspect that the serial port converter has a MAX 232 or similar IC in it.
- what are the serial settings? I read somewhere in the docs that 115 kB is the transfer rate, but what are the data bits, stop bits and other serial protocol?
- I haven’t used the ping protocol before, but it looks fairly simple if I make the connection - just send ‘B’ and ‘R’ and the appropriate command structure and then listen for the response from the S500 controller, right? It would be nice to have a simple example message that I could send for a test to see if the controller is speaking the same language as my PI.
- It looks like testing should be done with the transducer in water to prevent damage to the transducer - can I simply put the sensor in a dish of water while I am doing preliminary software testing (just testing for response and not valid depths)? Can the wire / entrance to the transducer be submerged without risking damage, or is it best to mount the transducer with O-ring installed first (I realize that the controller should not get wet, but I don’t see this as a risk because of the long transducer cable)?
I would love to use ethernet because I know data transfer will be fast if I want to look at a waterfall signal, but I don’t I have the skill set for that yet.
Thanks in advance to your answers to my many confusing questions. Hopefully, I’m not going about this all wrong.