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

Hello,

We are now testing a unit of NetDCUA5/WCE6 core, and it has the latest updates availaible:
Nboot(1.1) Eboot(11) and WinCE6 kernel v1.09

We are testing again CAN interface and we see exactly the same problem described in this thread (but with ARMstoneA9 cpu):

CAN 2.0B frames on ARMstoneA9/WEC7 received as 2.0A frames in reception.

IN summary, we are sending 29bits frames (CAN 2.0B) but they seems to be transmited as 11bits frames (CAN 2.0A) by the CPU.

Can you confirm if current NetDCUA5 CAN driver for WinCE6 suffers from the same problem? we would need and update then as soon as possible for continue testing the unit.

Thanks.

Hello,

After testing the drivers is does not work in my current NetDCUA5.
I have copied it in \FFSDISK\ ad then in register I have change only path to it:
\HKLM\Drivers\BuiltIn\NetDCUA5\CAN1\ key "dll" from "fs_candrv.dll" to " \FFSDISK\fs_candrv.dll"
and same for CAN2.
Then after reboot, CPU does not receive and transmit any CAN frame. If I return to older path in register, at least it receive frames and send STD ones...

Is it the correct one driver for NetDCUA5?
Is neccesary to modify another parameter/s in the register ?

Thanks

Hello,
with default driver, in serial debug appears:
....
CID: Version 2.4, ActiveKey = Drivers\Active\19
CID: Version 2.4, ActiveKey = Drivers\Active\20
....

But when I point to the new driver in \FSSDISK\ in the register and then reboot, none of this 2 lines about CID appears ... seems the new CAN driver is not loaded...I dont know why (no spelling errors).

I have tried to rename dll and use without prefix "\FFSDISK\" and later with prefix again, and in both cases seems driver is not loaded.
Its very strange, when I received the CAN dll file for the other CPU ArmStoneA9/WCE7 it worked inmediatly only modifying the path in the register.
I dont know why same procedure does not work here.
One solution is to release a WinCE 6 beta kernel for NetDCUA5 with this driver inside in the next days.
The current WinCE6 core kernel is including CF3.5, will be a kernel release for this CPU including CF2.0 ?

Thanks,
It works now, it's loaded while booting and I can receive and transmit EXT frames.
But in debug serial it shows:
....
CID: CID_IOControl(0x8007202c) failed, error=1460
....
continously with every CAN frame received or trasmited, is it normal ??

Hello,
testing again the CAN driver we see we are not able to receive STD and EXT frames from same CAN network. In this network there are devices which transmit EXT and another transmiting STD frames with same baudrate (100kbps), and NetDCU must be able to listen both on same CAN port.
We are using .NET and dll CAN wrapper from F&S that we used previously with NetDCU10 and later with NetDCU14.
Can you tell me how to configure in C# the CAN port to be able to receive both kind of frames ? or it's a driver problem yet ?
We always configure the CAN port in this way with dll wrapper:

-------------------------------------------------------------------------------------------------------------
pCAN1_CCS = new CanPort("CID1:", CanPort.CanAccess.READ_WRITE);
pCAN1_CCS.ReadProperties(out CANprop1_CCS);
pCAN1_CCS.SetCanMode(CanPort.CanMode.CAN_2_0_B);
pCAN1_CCS.SetBaudrate(CANbaudrate1_CCS);

//pCAN1_CCS.SetDefaultFrameFormat(CanPort.CanTransmitFormat.STANDARD); //11bits
pCAN1_CCS.SetDefaultFrameFormat(CanPort.CanTransmitFormat.EXTENDED); //11 or 29 bits

pCAN1_CCS.HandleErrorsViaReturn(true);

pCAN1_CCS.ReadAcceptanceFilter(out CANfilter1_CCS);
CANfilter1_CCS.code = 0;
CANfilter1_CCS.mask = 0xFFFFFFFF; //to allow all messages
pCAN1_CCS.WriteAcceptanceFilter(ref CANfilter1_CCS);

pCAN1_CCS.GetCommMask(out CANmask1_CCS);
CANmask1_CCS = CanPort.CanEventFlags.CANBUS_ALL;
pCAN1_CCS.SetCommMask(CANmask1_CCS);

pCAN1_CCS.Init();
-------------------------------------------------------------------------------------------------------------

Modifying bold lines we are able to receive STD or EXT in NetDCUA5, but never both simultaneouly.
What can be done ??

Hello,
this will not solve the problem... we have this document from several years ago...
The problem is very clear, with our configuration code (previous post) we are able to receive CAN frames in STD and in EXT format in the same network with CPUs like NetDCU10 and NetDCU14 (this one with some issues too).
Then, executing same CAN configuration code on NetDCUA5, which CAN driver is recently working, it is not able to receive both kind of frames simultaneously.
Can you try to reproduce this behaviour and see if there is any can driver problem yet for NetDCUA5 CPU, or tell us what can be wrong in the previous code configuration for not receiving both kind of CAN frames?

I have several questions:
-Do you configure CAN port with CANCheck tool in any special way for supporting both kind of frames in reception?
-Do you change this configuration for receiving i.e. EXT and then change again for receiving STD, or with an unique configuration flags you can receive both? (because changing configuration we are able to receive both too, but we need to receive both with a unique configuration of CAN port in order to distinguish which frame received is EXT and which one is STD).
If it's not neccesary to reconfigure CAN port by CANCheck tool for receiving both EXT and STD, then we assume driver CAN is OK, but then we return to the beggining of our quetions:
-CANCheck is not programmed with .NET and does not use F&S CAN wrapper dll, then the problem could be there...can you then try to use in a .Net project your CAN dll wrapper and try to see if with any combination of CAN flag configuration are you able to receive both kind of frames simultaneoulsy ??

I will test it today again.
Independent of our test application and our enviroment details, the reason of this post was that 2 weeks ago, the CAN driver of the NetDCUA5 was not able to transmiting EXT frames, and after new version, it's able of it.
But, then our question is, using our application programmed in .Net and our network CAN enviroment, why using an older NetDCU10 we are able to receive both format frames without problems, and replacing it by a new NetDCUA5 executing exactly same .Net application (so using the CID1 CAN port configuration as described before) and using same network CAN enviroment, this CPU is not able to receive STD frames in this case only EXT. ?