Describe the bug
The can_sontheim module prevents the can.detect_available_configs function from the python-can library from working as it raises an exception

To Reproduce

• install python-can-sontheim module
• Run can.detect_available_configs()

Expected behavior
The sontehim bus should either be reported as available opr unavailable

Screenshots, Traceback, MRE

Cannot load SIE MT_API for Sontheim: The Sontheim API is currently only compatible with the 32 bit python interpreter
Traceback (most recent call last):

  File "C:\Python\lib\site-packages\spyder_kernels\py3compat.py", line 356, in compat_exec
    exec(code, globals, locals)

  File "c:\users\matth\documents\github\python-can-bluetooth\examples\bluetooth_tx_example.py", line 18, in <module>
    print(can.detect_available_configs())

  File "C:\Users\matth\AppData\Roaming\Python\Python39\site-packages\can\interface.py", line 176, in detect_available_configs
    bus_class._detect_available_configs()  # pylint: disable=protected-access

  File "c:\users\matth\documents\github\python-can-sontheim\can_sontheim\_canlib.py", line 406, in _detect_available_configs
    error_code = _CANLIB.canGetDeviceList(byref(devices_struct))

AttributeError: 'NoneType' object has no attribute 'canGetDeviceList'

Desktop (please complete the following information):

• OS: Windows 10 64 bit
• SIE Adapter: CANfox

Additional context
N/A

Is your feature request related to a problem? Please describe.
The module currently relies upon a 32 bit DLL libray, meaning that a 64 bit installation of python cannot use the driver.

Describe the solution you'd like
Investigate some sort of wrapper that may allow the use of a 64 bit python installation to access the hardware drivers (e.g. MSL-LoadLib)

Describe alternatives you've considered
Keep library 32 bit only

Additional context
N/A

All Can Sends have the Extended ID set to True even when the message has is_extended_id=False

Copied a local instant of can-sontheim/_canlib.py and edited some lines to correct

    def send(self, msg, timeout=None):

        assert msg.dlc <= 8

        msg_struct = CANMsgStruct()

        # configure the message. ID, Data length, ID type, message type
        msg_struct.l_id = c_long(msg.arbitration_id)
        msg_struct.by_len = msg.dlc
        if msg.is_extended_id:
            msg_struct.by_extended = c_ubyte(1)  # 00000001   Corrected to 1, was 2.
        else:
            msg_struct.by_extended = c_ubyte(0)  # 00000000   Corrected to 0, was 1. 
        if msg.is_remote_frame:
            msg_struct.by_remote = c_ubyte(1)  # 00000001
        else:
            msg_struct.by_remote = c_ubyte(0)  # 00000000

This correction enable non-extended id sends. Also tested extended_id and seems to work (traces in IFM Maintenance Tool confirms).

Will be using a local copy for my projects for the moment.

Thank you.

Describe the bug
I have an application that runs fine in Python, but fails when passed through PyInstaller
Has anyone managed to get their application running through PyInstaller (one file or one directory)?

Could there be a problem in the package definition that PyInstaller does not link it correctly.
I'm trying to find information here before checking with PyInstaller for more troubleshooting.

Errors in console :
Error initializing CAN Bus : Unknown interface type "canfox"
Also tried interface="sontheim"
Both interface settings runs fine with Python, but fails when converted to an Executable.

Desktop (please complete the following information):

• OS: Windows 10 64 bits
• SIE Adapter: ifm EC21112 with ifm driver installed in Windows
• Python 3.12.2 32 bits, also tried 3.11.8 - 32 bits
• Visual Studio Code for IDE
• running with a venv on the project

• PyQt5, python-can, python-can-sontheim, pyinstaller
  

Additional context
Add any other context about the problem here.