I am trying to get the ve.Text mode to work, for parsing the data which my SmartSolar MPPT 75/10 is sending out.
I have a setup consisting of a SmartSolar MPPT 75/10, a 100W panel and a 12ah Lifepo4 battery. Connected to it (via a dc-dc adapter) is a raspberry pi zero w with a MA3232 converter (converting the RS232 signal to ttl) which is connected to the ve.direct port on the charger.
I am trying to keep the hardware footprint as small as possible, which is why I would like to use the raspberry pi serial console and a custom made (short) cable.
Another point is that sometimes drivers from chips connected to the usb-hub affect the dwc-otg driver of the hub. Causing it to hang, which is bad, since the wifi is also connected via the usb-hub...
So to avoid these problems I want to use the uart console of the pi.
Therefor I made my own ve.direct to RS232 cable as specified in the documentation.
But if I connect from the pi to the serial console (with the help of the MAX3232 converter) I do not get a nice textual representation of the values, as I would expect.
Instead I get this:
I also checked with a usb-to-rs232 converter on my laptop, but the output was the same.
When I tried with an usb-to-ftdi converter I got the desired text output, so what is the difference between the MAX3232 and the FTDI chip?
Does the FTDI do something else with the data?
On the protocol faq page I saw a reference implementation of a framehandler, do I need to run the data through this one first?
I am a little lost here, since all implementations of ve.direct parsers I was able to find online rely on a usb serial interface...
SmartSolar MPPT 75/10 Firmware: v1.46
Bluetooth Interface FW: v2.23