We are recently having CAN frames problems in reception with NetDCU14 and latest WinCE6 kernel v1.08.
More in detail, we have communication on both CAN ports simultaneously in our system:
CAN1: configured with 29 bits header and 100kbps speed and with about 40 messages/second bus load.
CAN2: configured with 11 bits header and 500kbps speed and with about 50 messages/second (20 for TX and 30 for RX in the NetDCU14).
What we have detected is that randomly a message with all 8 bytes = 0 appears on NetDCU14 in CID2 in reception rutine (we use F&S CAN dll and .Net in VS2005). Sometimes it takes one minute and sametimes it takes more minutes in the communication proccess, but it finally always occurrs.
That means, from structs:
public struct CanEvent
public int arbitration;
public CanPort.CanTransmitData data;
public CanPort.CanEventFlags event_type;
public uint lost;
public CanPort.CanTime time;
public struct CanTransmitData
public byte dlc;
public uint id;
public byte msg;
public byte rtr;
we obtein data.msg=0 for all 8 bytes received in this message on CID2 with the configuration described.
With a CAN monitor connected to the network we are sure that no CAN mesages are sended by any netwpork node with all bytes set to 0, so we assume it can be a problem with CAN dll driver of this kernel release of NEtDCU14.
Can you confirm something about or try to reproduce ?