jankae
LibreCAL does not appear in programs
I have a LibreCAL and it does not appear in the LibreCAL or LibreVNA gui.
It appears as 2 drives, and a serial port as usual, and when sending *IDN?\r\n I get:
LibreCAL,LibreCAL,5mNkR0uHIyoA,0.2.3<\r><\n>
But it does not appear in the LibreVNA 1.6.2, nor in Librecal 0.2.3. I upgraded the firmware to 0.2.3 on the device to see if that would help, but I still do not get the cal to appear in the GUI:
Any help appreciated.
Are you by any chance using Linux and have forgotten to set up the udev rule? That would explain the problem. But your screenshot looks very much like Windows.
This is in Windows.
With Best regards, Thomas S. Knutsen.
Please avoid sending me Word or PowerPoint attachments.
søn. 13. apr. 2025 kl. 17:20 skrev Jan Käberich @.***>:
Are you by any chance using Linux and have forgotten to set up the udev rule? That would explain the problem. But your screenshot looks very much like Windows.
— Reply to this email directly, view it on GitHub https://github.com/jankae/LibreCAL/issues/29#issuecomment-2799994355, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBYNPDNZ3JNIWNFC2PAPVD2ZJ6DNAVCNFSM6AAAAAB3BFS62WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJZHE4TIMZVGU . You are receiving this because you authored the thread.Message ID: @.***> jankae left a comment (jankae/LibreCAL#29) https://github.com/jankae/LibreCAL/issues/29#issuecomment-2799994355
Are you by any chance using Linux and have forgotten to set up the udev rule? That would explain the problem. But your screenshot looks very much like Windows.
— Reply to this email directly, view it on GitHub https://github.com/jankae/LibreCAL/issues/29#issuecomment-2799994355, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBYNPDNZ3JNIWNFC2PAPVD2ZJ6DNAVCNFSM6AAAAAB3BFS62WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJZHE4TIMZVGU . You are receiving this because you authored the thread.Message ID: @.***>
Which Windows version?
The LibreCAL uses WCID to automatically load the correct driver (Winusb). For older windows versions this feature does not always work.
Does the LibreCAL show up in the device manager?
You could also try installing the Winusb driver manually for the LibreCAL using Zadig: https://zadig.akeo.ie/
Did you manage to solve this?
Not been able to solve this. Computer is Win10, I have re-installed the driver, and downloaded new versions of the LibreVNA GUI and LibreCAL GUI without any sucess. It works correctly on a win11 computer.
It shows up as 3 devices as far as I can determine:
- USB composite device
- USB mass storage device
- USB Serial device (com port)
There is no difference between my win10 computer where it does not work, and my win10 computer where it works when it comes to how it appears in device manager.
It should show up 4x in total in the device manager.
2x as a mass storage device:
1x as a virtual COM port:
1x as a vendor specific (custom) USB device:
The last one is the important entry because both GUIs connect to it.
Any update on this? I'd like to help but do not really know how since I can not replicate the problem and I am not entirely clear on what the problem is based on your description.
I'm lacking the vendor spesific USB device. I have not been able to fix that with reinstall. Any suggestion on how to install it manualy?
Okay, at least that explains why the programs do not find the LibreCAL. I have to admit that I do not really have any idea why the vendor specific USB device is not showing up. The other USB devices are being detected, so the USB enumeration must work. And even if you do not have a driver installed it should still show up as a USB device (maybe with some indication that Windows does not know what to do with it).
If you were on Linux I would ask for the lsusb -v output. Maybe you can find something equivalent for Windows?
Or maybe try another Windows machine if you have access to one? Just to check if that makes any difference.
Could you please test with the newest v0.3.0 version? There were some bug fixes related to the USB library. I do not have high hopes that they fix your problem (because I do not understand what causes it in the first place) but it might be worth a try.
Closing due to inactivity. If there is new information, I am happy to re-open