CAN 2.0B frames on NetDCUA5/WCE6 received as 2.0A frames in reception.

Hello

to your first point:
at 11. November 2014 Mr. Derksen please you to give him more details about your test and enviorment. I think this is the only way to come to an end with this issue. So i please you to send him the desired information, because he tried to receive both message formats and it worked without problems.

to your second Point:
at 20 March 2013 i send you a "CanPort.dll" which should fix this issue. I please you to test it, but i got no answer until today.
We add the overload "public intReadEventData(out CanEventev, out CanTransmitFormat fmt)" were
public enum CanTransmitFormat{
DEFAULT, // Send in default format
STANDARD, // Send in 11 bit format
EXTENDED // Send in 29 bit formate
} should contain the infomation about the format. Does this not work?

Ok. thanks for this Information.

Quote from jopomo

Thank you for your appointments about "Align" and "MaskActive", I will investigate a bit more about this.
However, I have never modified any of this register values for previous CPUs models we have used before.

Well, if new features are added, you sometimes have to do some more settings, too.

Quote

First:
Let's suppose you have to program a simple CAN monitor that must be able to detect only if the message sniffed is type EXT or STD in a network where it is connected, and then show this property in a column. How do you do this whith
NetDCUA5 + C# + dll CAN wrapper from F&S ? Would be necessary to prepare the register ? To my understand it would be only necesary to fix CAN baud rate to network rate, CommMask and Acceptancefilter in order to sniff any message in the bus... right?

But to set the acceptance filter values, the right alignment of the IDs is already important. Otherwise you will not set the filter to the value that you intended. So yes, it is already necessary to set align in the registry correctly to do this.

Quote

Second:
Let's suppose first problem is solved and we are able to receive in this sample any kind of CAN messages, one thing missing in the WinCE dll CAN wrapper from F&S is a flag indicating the type of CAN message received, while this is something present in others WIN32 API CAN dll for .Net,
How can be distiguished if received message is EXT or STD with your WinCE .Net CAN wrapper?

Yes, there was an error in a previous version. Now function ReadEventData() returns a second value (as an additional out parameter) the type of the message.

Your F&S Support Team