DashCommand and (PPE) OBD-II hardware (Wi-Fi) Interface issue with PIDs

[sgodb]

I purchased two weeks ago the DashCommand v3.0.1 (build 2761) for iPhone along with the Palmer (PPE) OBD-II hardware (Wi-Fi) Interface.

It initially works well with my 2005 Mitsubishi Colt (imported directly from Japan).

I create my vehicle in Vehicle Manager.
Connect to the Wi-Fi interface and gets all correct readings for most PIDs.

However, here are 2 problems:

1) Whenever the OBD-II hardware (Wi-Fi) Interface is restarted then it won't be able to get any valid PIDs (even RPM). The only solution is to re-create my vehicle in the Vehicle Manager. Then it works again until the Interface is restarted or re-powered.

2) Overnight, the Interface will somehow go in sleep mode? In the morning the green light is no longer blinking and it won't "wake up" after the car starts. I have to disconnect the DB9 cable and re-connect. Then the light will start blinking again. Again, problem stated in 1 will happen.

Thanks for any help,

Eric
Singapore

[John@PPE]

I've never seen this problem. You should not have to recreate the vehicle every time. You also should not have to revalidate the PIDs, but have you tried re-validating instead of recreating the vehicle?

Also, are you filling in the VIN? Or does that get filled in automatically? Does it change after you disconnect and reconnect?

[sgodb]

Workaround working okay. Revalidate the PIDs will allow all correct readings for most PIDs except SAE.MAP.

I have not fill in the VIN. It also does not get it automatically.

I think the workaround is acceptable for now. I will do more research and open a new post when I have more info. My Mitsubishi is a domestic Japanese model so it may not help.

It is a great product, continue the good work!

Eric