PEAK-System Forum

As previously mentioned, this is intended to be handled officially via the TRANSPORT_LAYER_CMD command. We are aware that this may not be implemented by all ECUs—whether because they are not 100% XCP-compliant or because they are designed for use with a protocol other than CAN.
Adding additional ...

Hello,

ok, as I see you have your solution. This is the more important.

Please note that we have implemented this API to comply with the official XCP specification. It provides—in the form of functions—all the services described in the XCP documentation. Furthermore, since our products operate ...

Hello,

if I understood well, you want to define different DAQ-Ids for several ECUs. This is possible and it is explined in the chapter " Introduction \ About XCP \ XCP on CAN" . In short words, you can define one ID for each ECU to get DAQ messages. Having this like that, you should then get them ...

Hello,

I think you are mixing up stuffs here. Note that you are using the method PCANBasic.GetValue with the parameter PCAN_CHANNEL_FEATURES . This parameter returns an unsigned integer, a flag value which has the features bit-coded. You can see this in the help:


Features.png


But you are ...

Hello again,

please use the examples without modification and check how communication is done. Note that there are 2 examples, one server and one client. Let the server run in a channel, and debug the client in another, then you will see the communication (ISO-TP and UDS).
You should go to code ...

Hello,

yes, it is possible to receive ISO-TP/UDS messages and CAN classic frames from a UDS initialized channel, simultaneously. This use case is fully covered by the existing PCAN-UDS 2.x examples, specifically samples 13 and 14 (13_server_uds_and_can / 14_client_uds_and_can). They demonstrate ...

You're welcome!

Closed

Hello,

note that the bit rate used by PCAN-View must passt exactly with those used by PCAN-Basic. PCAN-View may show you for example 500 kBits, but they are a lot of combination for that.
Bitrate500_80Mhz.jpg
Now, at the time PCAN-Basic was designed, there were only hardware using bit rate based ...

Hello,

Thanks for sharing your suggestion.

We understand your need, but unfortunately we cannot offer this for technical reasons. Calls to python scripts mean a big overhead for the CAN communication and performance lost.

Hello,

now I see. Yes, this seems to be a (very old) bug. Indeed a CloseHandle is failing. This will be fixed by the next release.

Thank you for bringing this to our attention.