Hi,
We are active pcan adapter users.
We used to use PCANLight wrapper and in its source code we could read that the filtering is not guaranteed.
In PCANBasic we did not found any comment about it.
We still have serious problem with filtering.
I do not know where the problem could be, but the filtering seems have serious bugs.
We have the following tests:
We tried it with PCAN usb adapter with PCANLight and PCANExpress card with PCANBasic.
------------------------
The same GOOD behavior with PCANBasic and PCANUsb dlls:
sending ext 0x214 PDO :
Ext filter 200-3FF
Ext filter 200-400
Ext filter 300-400
we can receive it.
------------------------
The same WRONG behavior with PCANBasic and PCANUsb dlls:
sending ext 0x1FF PDO:
Ext filter 200-3FF
we cannot receive it.
Ext filter 200-400
we can receive it.
------------------------
The same WRONG behavior with PCANBasic and PCANUsb dlls:
sending sdt 0x214 PDO
ext filter 200-10000400
we can receive it.
ext filter 200-00100400
ext filter 200-01000400
ext filter 200-400
we cannot receive it.
The same WRONG behavior with PCANBasic and PCANUsb dlls:
sending ext 0x214 PDO
std filter 200-400
std filter 0-1
we can receive it.
std filter 200-3FF
we cannot receive it.
------------------------
Receiving std message while using std filter is always working as expected.
I hope I wrote my problem to the right forum.
PCAN filter
Re: PCAN filter
Hi,
thanks for the info. When using the filter option with the PCANBasic or PCAN-Light API, you have to take care that you cannot mix up standard and extended IDs in one filter function call. So when you have a CAN system with both kind of messages, you have to open the filter for std Ids and ext Ids in different filter function calls. To understand the filter mechanism of our API please download the NXP SJA1000 manual, to see how the filter is working in the CAN-Controller (ACCcode, ACCmask) in an 11 and 29bit ID system.
When using 11bit (std) Ids only, our driver uses a build-in software filter to prevent unwanted messages when you open an ID range. This option will not be possible with the 29bit (ext) IDs.
To help you with your problem it will be helpfull to know which driverversion, dll versions, and OS you are using.
Also some code will be helpfull to understand the problem. So if you have any more questions regarding that filter problem, please send us an email to support@peak-system.com.
regards
Michael
thanks for the info. When using the filter option with the PCANBasic or PCAN-Light API, you have to take care that you cannot mix up standard and extended IDs in one filter function call. So when you have a CAN system with both kind of messages, you have to open the filter for std Ids and ext Ids in different filter function calls. To understand the filter mechanism of our API please download the NXP SJA1000 manual, to see how the filter is working in the CAN-Controller (ACCcode, ACCmask) in an 11 and 29bit ID system.
When using 11bit (std) Ids only, our driver uses a build-in software filter to prevent unwanted messages when you open an ID range. This option will not be possible with the 29bit (ext) IDs.
To help you with your problem it will be helpfull to know which driverversion, dll versions, and OS you are using.
Also some code will be helpfull to understand the problem. So if you have any more questions regarding that filter problem, please send us an email to support@peak-system.com.
regards
Michael
Re: PCAN filter
Dear peak Team
The forum is such a great idea and tool ,as shown in this post
it shows information that is relevant to all of us using the
products!¨
This is great place to share problems and knowledge

The forum is such a great idea and tool ,as shown in this post
it shows information that is relevant to all of us using the
products!¨
This is great place to share problems and knowledge

Peter Erasmus
Automotive Engineering
Switzerland
Automotive Engineering
Switzerland