Closed babldev closed 3 years ago
That´s true. With version 0.9 the replacement for Windows data type DWORD
(which is frequently used by PEAK´s PCANBasic API) was changed from unsigned long
to UInt32
. On Windows the data type long
is 32-bit wide, and on Unix based system it is 64-bit wide. With this change the data types matches on all OS.
This issue is also tracked in the python-can project. Meanwhile PEAK added the PCBUSB library to their Python wrapper. My suggestion is to take this one instead of the patched one from the python-can repo. And of course the latest PCBUSB release.
thanks for the clarification, I can work with @kail on the python-can patch
After upgrading from the 0.8.1 working driver to 0.9.0+, message timestamps are corrupted when accessed using https://github.com/hardbyte/python-can
0.8.1 (working)
0.9.0 (broken)
Did the serialization of timestamp offsets change in this release? https://github.com/hardbyte/python-can/blob/291af86e3898229a8bacebd82f4ff7a8b81a41c0/can/interfaces/pcan/basic.py#L505-L518
My setup: MacBook Pro (15-inch, 2018) macOS Catalina 10.15.4 (19E266)