Christoph Schueler

First of all, I'm glad you're using RasPI / SocketCAN like I do; in this case my infamous [xcpdump] (https://github.com/christoph2/xcpdump) may useful, it's just like the "official" *candump* but showing...

Well, I think I've tracked down the issue, but it shows some interesting behavior of python-can (not sure if it is intended) : If one just passes `fd = True`...

OK, now *pyxcp* behaves like required by Autosar. Add the following to your config: ``` MAX_DLC_REQUIRED = true MAX_CAN_FD_DLC = 64 PADDING_VALUE = 0 ``` Note: The last two values...

Wait a minute, I've published a draft by mistake, the changes are not yet pushed!

Ok, I hope it works for now. And yes, the new-school build is still WIP.

The first one was (now fixed) an installation issue, the required package [python-can](https://github.com/hardbyte/python-can) was missing. Just run `pip install python-can` `isExtendedIdentifier` works correctly, `CAN_EXTENDED_ID` **IS** defined as `0x80000000`, i.e. Autosar-style.

I've just added a tiny script -- [pyxcp-probe-can-drivers](https://github.com/christoph2/pyxcp/blob/master/pyxcp/scripts/pyxcp_probe_can_drivers.py) -- giving you an overview whats on your system.

No, that's not intentionally; I'm trying to incorporate new functionality (a recorder for XCP frames (mainly measurements)), but the GitHub actions build works not as expected, which prevents upload to...

0.18.15 is now available on PyPI, versions 3.5 to 3.10, currently only **win_amd64** Other platforms, esp. Linux are still WIP.

Hi guys, No, I haven't forgotten the documentation issue. First of all: re-formulating the ASAM spec in my own words is certainly the wrong way to go. To make a...