It is nice to view, but not that easy to test. I wonder why byte 10 is missing?
Can you post a list of hex bytes, like: "33 44 55 66"
I can put that directly into a Arduino and use it for testing.
Hello,
I managed to use the driver from BM357S with TestControllerDebug, but then the software doesn't knows how to interpret this.
Since is using unilateral flow (Rx only) then some windows are sending TX which the interface cannot interpret.
Below the Hex captures from the debug, and captured screens from the App from Sairus.
This interface cable is handy as with few euros one can implement the cable. I spent around 3 euros in Aliexpress plus programing pic plus soldering time. All done fits on well compacted form, even with through-holes.
From the other thread I believe multiple people implemented the same.
It would be great if it could work in your software as well.
Sairus didn't shared the code for the pic (only the hex for programing it) but shared code for alternative arduino implementation, so most probably using the same concept he implemented in the pic which is way cheaper. We just need on top USB-UART cheap board. Adding the ino code in attachment "Brymen_RS - .ino.txt" as well in case is useful to understand what the code PIC is doing.
Driver: BM357S
Case1: AC voltage
;; COM3: Rx: 01 11 BE E5 FC BE 7C 01 00 A0 BE BE BF 04 00 86 86 86 86 80
Case2: DC Voltage plus AC
;; COM3: Rx: 11 00 BE E5 FC F8 DA 01 20 BE E5 FC A0 08 00 86 86 86 86 80
Case3: DC Voltage + extra digit (500000 counts)
;; COM3: Rx: 11 10 DA FD FC FC E4 F9 00 00 00 00 00 00 00 86 86 86 86 80
Case4: Resistance 400 ohms
;; COM3: Rx: 01 10 E4 BE BE A9 7E 00 00 00 00 00 00 00 10 86 86 86 86 80