CAN protocol issue in OBD-II Emulator

[przemhb]

I am just taking my first steps with the OBD-II emulator. I am trying to use it with CAN protocol set. To test it I use STN1170 based OBD-II/BT interface and Maxhaust engine sound generator. Both use CAN protocol for communication. The STN1170 is a multi-protocol interface with CAN support, among dozen others. It works just fine in my car, and uses CAN to connect (verified).

For some reason both the Maxhaust and STN1170 interface are unable to communicate with the Freematics OBD-II Emulator. No matter CAN speed nor address length. If only I switch protocol to one of KWP2000's or ISO9141-2 everything works. Every PID is being read by Torque Android App.

What I am missing? Why CAN communication doesn't work for me?

[stanley]

Our emulator does not actively generate CAN traffic. This is a bit different from real situation. It only responds to queries. That's the difference between emulator and simulator.

[przemhb]

Thank you for your reply.
1. Why then it works in KWP2000 and ISO9141 modes?
2. Apps like Torque while connecting try to read basic information about the car, like VIN for example. So they send requests. After the connection is established they indeed merely listen to CAN traffic to read live data. Hence I'd expect Torque would be able to connect, but unable to refresh monitored PIDs. Am I right?

[stanley]

ISO9141 is like serial communication. Sniffing or listening is not possible.