Configuration file doesn't register in Windows

[hardbyte]

Originally reported by: Colin Heinzmann (Bitbucket: DepthDeluxe, GitHub: DepthDeluxe)

---

I am trying to use the PCAN interface on Windows 7 with python-can and have followed the configuration instructions (i.e. https://bitbucket.org/hardbyte/python-can). When I try to "import can", I get the following error message even when I have explicitly stated to use the pcan interface in the configuration file.

WARNING:root:Kvaser canlib is unavailable.
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Function was not found in library
WARNING:root:Kvaser canlib is unavailable.
ERROR:can.serial:You won't be able to use the serial can backend without the serial module installed!

My can.ini/can.conf file contains:

[default]
interface = pcan
channel = 1

The Kvaser canlib missing error is also strange because while I was trying to fix the issue, I installed the Kvaser canlib SDK.

My Python version is 2.7.10 (32-bit) and I'm running Windows 7.

---

• Bitbucket: https://bitbucket.org/hardbyte/python-can/issue/30

[hardbyte]

Original comment by Caleb Smelser (Bitbucket: calebs, GitHub: calebs):

---

I am experiencing the same issue, except I am trying to use socketcan_ctypes on a Raspberry Pi running Raspbian.

[hardbyte]

Original comment by Tynan McAuley (Bitbucket: tymcauley, GitHub: tymcauley):

---

I believe that this issue has been resolved as of commit 3be5ee9. Please confirm that this is the case, and we can close this.

By the way, these were only warning messages, so they shouldn't have affected functionality in any way. They're definitely annoying, but you didn't have any issues with using the library, did you?

[hardbyte]

Original comment by Caleb Smelser (Bitbucket: calebs, GitHub: calebs):

---

I was getting that long string of "not found" errors plus an error traceback ending at the raise e on line 52 of interface.py.

Traceback (most recent call last):
File "/home/pi/python-can/test.py", line 16, in
producer(10)
File "/home/pi/python-can/test.py", line 9, in producer
bus = Bus(can_interface)
File "/home/pi/python-can/can/interfaces/interface.py", line 52, in new
raise NotImplementedError("CAN Interface Not Found")
NotImplementedError: CAN Interface Not Found

With interface.py from 3be5ee9 I no longer get the long string of not found errors, but I still get that traceback with NotImplementedError: CAN Interface Not Found. I installed python-can according to the instructions but have yet to succeed in even using the program to spam a virtual bus.

[hardbyte]

Original comment by Brian Thorne (Bitbucket: hardbyte, GitHub: hardbyte):

---

[kvaser] Ratchet up log level for canlib. Closes #30

Logging was sometimes going to the root logger as well.

[hardbyte]

Original comment by Brian Thorne (Bitbucket: hardbyte, GitHub: hardbyte):

---

Sorry I didn't read this issue closely enough. I don't have access to a windows machine with any CAN hardware, is anyone else able to debug this?

[felixdivo]

Is this still a problem? I currently do not have a Windows machine connected to a CAN controller.