Hi Bole,

> Have ISO-9141, 14229, 14230
> SAE- J1979, J1850, J2037, J2054, J2178, J2190.
> Paid for this more than 1200 Euro, ISO15765 1-4 costs nearly 500 SFR,
> Why should I pay that much to obtain few dozen adresses ?

Well, first of all, you should have told me what you don't have, not what
you do have. :-) When I pointed you to the standard, you basically replied
that you "have the standards."

Second of all, if you are doing this for a living, you should buy the
standard anyway. To get the addresses you only need to buy ISO15765-4 for
CHF99 = US$77, and there are other interesting things there too. Yes, I
know - the standards are expensive, and I myself feel that it's extortion to
charge in excess of $3 per page, but that's just the way it is.

For 11-bit can, the source/target addresses are implied:

7DF CAN identifier for functionally addressed request messages sent by
external test equipment
7E0 Physical request CAN identifier from external test equipment to ECU #1
7E8 Physical response CAN identifier from ECU #1 to external test equipment
7E1 Physical request CAN identifier from external test equipment to ECU #2
7E9 Physical response CAN identifier from ECU #2 to external test equipment
7E2 Physical request CAN identifier from external test equipment to ECU #3
7EA Physical response CAN identifier from ECU #3 to external test equipment
7E3 Physical request CAN identifier from external test equipment to ECU #4
7EB Physical response CAN identifier ECU #4 to the external test equipment
7E4 Physical request CAN identifier from external test equipment to ECU #5
7EC Physical response CAN identifier from ECU #5 to external test equipment
7E5 Physical request CAN identifier from external test equipment to ECU #6
7ED Physical response CAN identifier from ECU #6 to external test equipment
7E6 Physical request CAN identifier from external test equipment to ECU #7
7EE Physical response CAN identifier from ECU #7 to external test equipment
7E7 Physical request CAN identifier from external test equipment to ECU #8
7EF Physical response CAN identifier from ECU #8 to external test equipment

The standard recommmends using the range from 7E0 to 7E8 for ECM, and 7E1 to
7E9 for TCM.

For 29-bit, we have:

18 DB 33 F1 CAN identifier for functionally addressed request messages sent
by external test equipment.
18 DA xx F1 Physical request CAN identifier from external test equipment to
ECU #xx
18 DA F1 xx Physical response CAN identifier from ECU #xx to external test
equipment

The standard also "strongly recommends" using SAE J2178-1 for physical ECU
address assignments.

>> > Read the CAN section of SAE J1979. Appendices A & B apply to CAN, too.
>
> I have ( more than once, believe me ), and I have spent more time writing
> routines
> to decode negative, wrong or no responses at all, than on writing most of
> the other code.
> And why ? - because there is no single one manufacturer that follows the
> existing
> standards. :-(

That is not true, at least not for legislated diagnostics. And as far as ECU
addresses go, manufacturers seem to be fairly consistent.

By the way, what software are you talking about?

> BTW, HiSpeed is 500KB and LowSpeed is 250KB or ?

The above applies to both 500 kBit/s and 250 kBit/s versions. Low-speed is
<=125kBit/s.

Best regards,

Vitaliy

--
Archives and useful links: http://groups.yahoo.com/group/CANbus
Subscribe and unsubscribe at www.vector-informatik.com/canlist/
Report any problems to <canlist-owner@...>