PEAK-System Forum

Hi Keneth,

Channels are made on the fly, based on the current amount of devices attached to a computer. Unfortunately, PCAN-BAsic doesn't receive active information about plug-ins/plug-outs, so cache will not work.

Ok, I understand.

Based on your request and those form other customers, we did ...

Dear U.Wilhelm,

thanks for your answer.

It was not my point to affront you or your company. In my introduction I wrote that could be improved
and that's how I meant it. And before writing this post, I have carefully thought about the points,
because I know that an improvement must never break ...

Hi,

I'm currently extending the PeakCAN plugin in QtSerialBus for CAN FD. While working on it, I noticed some places that could be improved in the PCAN-Basic API.


The Parameter TPCANBitrateFD in CAN_InitializeFD should be const char* instead char * . Otherwise the compiler complains when I pass ...

Hello,

I am having a problem with the Qt CAN example, it runs perfectly on windows and I am able to send and receive messages. On Linux I i installed the PCAN driver and tested it and it works, but when I use the Qt CAN example I always have an error when connecting to the peak can device: "A ...

Hi, I need to come back to this topic after long time, because I'm not satisfied yet.

Please note that a "channel" is an internal combination of several PCAN-Obejcts and states, tha have to be created and/or checked. This includes driver calls, objects creation, interprocess communication, memory ...

Hi,

you state that Windows XP is no longer supported with PCAN-Basic 4.0.3 and newer, which is totally acceptable for me.

However, I'm searching for the latest version of the API compatible with XP (which should be 4.0.2, correct?) I'm fine if you don't give support anymore, but I need to download ...

Thanks for your help, Keneth.

As I'm not the author of the PassThru software I'm always caught between two stools

It looks different vendors handle the specification in different ways. But as I'm just the tester I think we can close this topic for now.

Sorry, but I'm still having this problem. I think the filter looks good, or am I wrong? What else could I try?


14436078 ; PassThruOpen ; STATUS_NOERROR (0x00) ; PARAMS={pName=NULL, *pDeviceID=81} ; GetErrorText={"Function call successful"}
14436281 ; PassThruConnect ; STATUS_NOERROR (0x00 ...

Thanks a lot Keneth, I'll try that!

Hi Keneth,

thanks for your answer.

Most likely this is the problem. I'm not sure I removed the call to filter function after not receiving anything; but if the API then assumes a "closed" filter this could not help :)

To get a fully open filter, I assume I have to set pMsgMask to 0?

Best regards ...