Data capture via CP2102 module stopped working
Posted: Sat Jun 13, 2020 10:17 am
I added a CP2102 TTL module (this one: https://www.ebay.com/itm/323388721317) to my DSO Shell in order to be able to receive data on my PC. The TTL module is wired (ground, TX and RX) to J5 on the DSO.
I used my PC with Win 10 and Free Serial Port Monitor to try and capture data. I chose the correct COM port and the options to those specified in the DSO manual (baud rate 115200, data bits 8, parity None, stop bits 1). I left the flow control setting at "Hardware". I started logging, and then pressed the buttons on the scope to start sending data. A ran the logging for a couple of seconds, then I opened the file and everything seems fine (the file contained a section with info on the scope, followed by the y/t data). In other words, everything worked perfectly during this first test.
Then I unplugged the USB and shut off the scope, and a few minutes later I was going to do another measurement. However this time it would not transfer the proper data. Only a couple of bytes were received, and the text file only contains some gibberish like "ÿÿ". I tried again, same thing. Now I can't get it to work like it did in my first test. I only receive handful of strange characters, not real measurement data.
I've tried all the obvious stuff: unplug and replug the USB cable, restart the scope, restart the PC, mapping to a different COM port in Device manager, using a different USB port, using a different USB cable...
What could be the problem when it worked once but won't work again, without changing any settings?
I used my PC with Win 10 and Free Serial Port Monitor to try and capture data. I chose the correct COM port and the options to those specified in the DSO manual (baud rate 115200, data bits 8, parity None, stop bits 1). I left the flow control setting at "Hardware". I started logging, and then pressed the buttons on the scope to start sending data. A ran the logging for a couple of seconds, then I opened the file and everything seems fine (the file contained a section with info on the scope, followed by the y/t data). In other words, everything worked perfectly during this first test.
Then I unplugged the USB and shut off the scope, and a few minutes later I was going to do another measurement. However this time it would not transfer the proper data. Only a couple of bytes were received, and the text file only contains some gibberish like "ÿÿ". I tried again, same thing. Now I can't get it to work like it did in my first test. I only receive handful of strange characters, not real measurement data.
I've tried all the obvious stuff: unplug and replug the USB cable, restart the scope, restart the PC, mapping to a different COM port in Device manager, using a different USB port, using a different USB cable...
What could be the problem when it worked once but won't work again, without changing any settings?