On 09/27/11 09:35, Damien R. wrote: > On 26/09/11 18:40, Oliver Hartkopp wrote: >> >> There is no SFF flag!! >> >> if you look at the can_id in struct can_frame at check the CAN_EFF_FLAG: >> >> CAN_EFF_FLAG is set -> EFF frame >> CAN_EFF_FLAG is clear -> SFF frame >> >> When working with SFF IDs (11 bit) the CAN_EFF_FLAG is always cleared. > > Yes of course, but I associate !CAN_EFF_FLAG = imaginary SFF flag. > Anyway, I did not express myself properly. > > So, I meant that the CAN_EFF_FLAG is set and the specification say that it is > a 11 bit ID.
This is a contradiction. Of course you can only use 11 of 29 bits ... but EFF is 29 bit by definition. > So, this frame is not CAN 2.0 A and not CAN 2.0 B compliant, > isn't it? CAN 2.0 B covers SFF & EFF frames (even together on one medium). Regards, Oliver _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
