search

kolinger / rd-usb

Web GUI for RuiDeng/Riden USB testers (UM34C, UM24C, UM25C, TC66C)
GNU General Public License v3.0
223 stars 29 forks source link

UM25C Not showing up in setup list. #51

Closed Inigma77 closed 1 month ago

Inigma77 commented 1 month ago

Its me again, after weeks of shipping my UM25C has finally arrived, I went to go test it out but had some issues getting it to connect to my raspberry pi 5. I eventually solved this issue by installing blueman as the stock bluetoothctl refused to connected. Now when i open up rd-usb and try to set up my UM25C it says:

Result:
no device found, try again.

Now i know my unit is good i have tested it with my android phone and it works fine, i know the connection to the pi is fine as blue man is reporting strong links, what I suspect is that my workaround to get it to connect to the pi is messing with the setup though I have no idea how to verify this. I can add any troubleshooting needed but just not sure what to add currently as it isn't giving any errors just not seeing the device.

Inigma77 commented 1 month ago

I took a long shot and chose UM25C Serial and that fixed it, I'm getting data through now. I think the way the pi was handling the connection was just viewing it as a serial port so the rd usb could not recognize it. Imp not sure if this happens with all raspian build but might be worth adding to the readme :)

kolinger commented 1 month ago

I just tried on my Raspberry Pi 5 with raspbian (headless) and it works as expected, via the UMxxC option (not the Serial one).

Always remember - the Bluetooth has ability to be very funny and what can happen is - that if you use the meter via other means then the rd-usb gets refused access silently because "it's already used", if you want to use Bluetooth directly make sure the Raspberry is not connected to the UM by any other means, it's not paired/bound or anything like that, because any other existing connection may result in "not found" because "already in use".

If the rfcomm bind method works for you then just use it - the only reason for the direct Bluetooth is - that you don't need to mess with rfcomm or manual scanning and dealing with addresses, but if you don't mind to find the address and to use CLI then the direct Bluetooth don't give you anything extra thus you can use the Serial method just as well.