Scanner not found

[geogis56]

In Arch Linux, using the command sudo bc125py import --csv channels.csv results in the message [ERROR] No scanner found . Using the command sudo modprobe usbserial results in a message that usbserial is not found in the kernel directory. Both pyserial and pyudev are installed. Using this tool on a Debian machine worked without error. Only on Arch did I experience the issue, which likely has to do with the kernel modules.

[itsmaxymoo]

This issue created as a result of email conversation. PySerial does not find device on Arch. Will investigate once I get some time.
Thanks.

[pascalla]

I'm getting this issue on a Debian based OS (Raspberry PI OS), I am using a UBC125XLT but the protocol seems to be the same according to the documentation. Any thoughts?

[itsmaxymoo]

@pascalla Please run the program as root with the verbose -v command line option, and paste the output. If it's just a matter of allowing the model string and everything else is the same, then it should be an easy fix.

[pascalla]

@itsmaxymoo I managed to get it working with a minor tweak.

For anyone else who may stumble across this, you can get this working by changing the model number to "BC125XLT" on these lines

bc125py/bc125py/con.py

Line 230 in c2e3b44

found_ports.extend(glob.glob("/dev/serial/by-id/*BC125AT*"))

and then running with the legacy detection flag

I think something may be slightly different as couldn't global locking/unlocking seemed to be very temperamental! Wouldn't show as locked out on the scanner (or be locked out) but would show on the list using the GLF command in shell. However I don't think that is an issue for this repo.

[itsmaxymoo]

@pascalla That is suggesting it may be just an issue of enabling the different model... Would you mind sending me the programming manual for your specific model?

[pascalla]

@itsmaxymoo I haven't been able to find a specific manual for my modelm most of the references on forums/github lead to it being the same BC125AT Operation Specification

[itsmaxymoo]

@pascalla it appears the difference between the two models are the range of frequencies they support, being that they are essentially the same thing for different countries. I am thinking of a way to efficiently integrate this into the software.