Hello all.
I am using the Freematics Emulator. On the ISO9141 protocol, the Emulator is not meeting the ISO specification for P2MIN timeout. Is this a known problem with the Emulator?
Regards
Carl
Freematics Emulator, ISO9141 & KWP P2MIN
Re: Freematics Emulator, ISO9141 & KWP P2MIN
Could you be more specific?
Re: Freematics Emulator, ISO9141 & KWP P2MIN
The emulator responds to a request faster than the duration allowed for in the ISO9141-2 specification.
Re: Freematics Emulator, ISO9141 & KWP P2MIN
Hello again. I was busy with other projects, but now I'd like to ask about this again.
The Freematics emulator responds to ISO9141 requests with a P2 time less than 25ms. It is about 20% faster than the ISO9141 specification. This violates the specification. The required P2 time is defined in this language taken from the ISO9141 specification:
"If the message synchronization is achieved only by timing, then P2 min. shall be 25ms and key words 08H 08H shall be used."
Freematics is using keywords 08 08, and using the 55 symbol to sync, so this is a case where the P2 period shall be 25ms.
This timing can be observed with an oscilloscope or bus monitor on the K line.
Freematics engineers, please give me your thoughts on this.
Thank you
The Freematics emulator responds to ISO9141 requests with a P2 time less than 25ms. It is about 20% faster than the ISO9141 specification. This violates the specification. The required P2 time is defined in this language taken from the ISO9141 specification:
"If the message synchronization is achieved only by timing, then P2 min. shall be 25ms and key words 08H 08H shall be used."
Freematics is using keywords 08 08, and using the 55 symbol to sync, so this is a case where the P2 period shall be 25ms.
This timing can be observed with an oscilloscope or bus monitor on the K line.
Freematics engineers, please give me your thoughts on this.
Thank you
Re: Freematics Emulator, ISO9141 & KWP P2MIN
Well, emulator is a bit different from simulator. Emulator makes something work as if it is on a target which is actually not. It does not 100% restore the inside working condition of the target.