-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
smuview "crashes" the UT-D04 (USB/HID cable with WCH CH9325 chip, USB VID/PID 1a86:e008) #39
Comments
Could you please start SmuView (and sigrok-cli) with the option |
sigrok-cli -d voltcraft-vc840:conn=1a86.e008 -l 5 --continuous ./SmuView-0.0.6-git-7050317-x86_64.AppImage -d voltcraft-vc840:conn=1a86.e008 -l 5 |
I like to mention, that i still like to test possible fixes for this issue or something else that could help me to get able to use smuview. |
After about a year after the bugreport and the issue still existing on even different Linux-Distro, i gave up and got a https://sigrok.org/wiki/Device_cables#UNI-T_UT-D02 cable and use it with a usb-rs232 adapter. I use now Then it detects it and starts working without the need of any configuration in the gui. |
thanks for this post, it helped me indeed getting my UT61E working on MacOS Ventura with SMUVIEW. I had already a serial cable+serial2USB convertor (and had it working with the CLI) but I have an USB cable version on the way, thinking USB might be easier. I guess I'll have to drop the USB cable, when it finally arrives. |
This is somewhat interesting issue i think.
I know about issue #31 .
This is working perfectly fine:
smuview does not work at all with my hardware. I am running SmuView-0.0.6-git-7050317-x86_64.AppImage .
Its crashing the WCH chipset when its been started.
This is the result:
./SmuView-0.0.6-git-7050317-x86_64.AppImage
sr: testo: Failed to get manufacturer string descriptor: LIBUSB_ERROR_IO.
sr: testo: Failed to get product string descriptor: LIBUSB_ERROR_IO.
Then i close smuview and run:
sigrok-cli -d voltcraft-vc840:conn=1a86.e008 --continuous
sr: uni-t-dmm: HID feature report error: LIBUSB_ERROR_IO.
sr: uni-t-dmm: HID chip init failed: -1.
I have to disconnect the usb cable and connect it again to get a working sigrok-cli again.
Running
./SmuView-0.0.6-git-7050317-x86_64.AppImage -d voltcraft-vc840:conn=1a86.e008
does not change anything. I still get the same Error in the command line and no data from the DMM.
My conclusion without reading the smuview code is that smuview does something at the start that crashes the WCH chip. Then smuview and sigrok-cli are not able to read any data from it until reconnect.
The text was updated successfully, but these errors were encountered: