Dash Commands dasboard hangs up after few minutes of use

[mirekmal]

Weston, John, thanks for responce! Well, I inspected Kiwi and seems to be OK. No visible signs of 'cold' soldering, damaged wires etc. Unless something wrong with ICs on the board nothing that can be spotted on the dongle. I did not made inspection of OBD connector - did not yet figured out if it can be opened.
One think more that comes to my mind is iPhone itself. Well it is 3.5 years old, jailbroken 3G model with iOS 4.21, so rather slow device (and I'm planning to replace it with 4S in some future, but not now yet). Usually when I connect to wireless network there is icon in iPhone status bar showing connection. If it is connecting to Kiwi I can only check via Settings that it is connected, but no connection indicator in status bar. The difference might come from infrastructure vs. ad-hoc connection type, but I'm not sure - have no experience with ad-hoc connections. So maybe it is something directly between iPhone and Kiwi that is not working fine... Rev, as it attemts to reconnect, might cover the issue...

[Weston@PPE]

I've used my personal 1st gen iPod Touch with DashCommand many times, and I could almost never hold a connection with a Kiwi. I can't remember having any issues with an OBDLink WiFi though. Still an ad-hoc network, just a different piece of hardware.

With a device that old, the bigger issue loading dashboards. Sometimes on slow devices, it can take so long to load a skin that the vehicle thinks we've disconnected. The skin you made on DashXL.net wasn't very big though, and I doubt you'll see this problem.

[TCSF]

ON YOUR VEHICLE SETTINGS TRY INCREASING THE OBD-II RESPONSE TIMEOUT.

I have not tested this extensively, but I have not had a random disconnect with my Kiwi since I increased the value of this setting to 300.  Dash Command doesn't seem to run any slower on my IPhone 4 using this value.  I haven't tested this for a long trip nor have I tested a lesser increase to find out what the minimum increase is that will work.  I talked with the Kiwi people perhaps a year ago and I think I recall them advising setting a bit longer timeout value on something.  Since Dash Command would not let me increase the value of the Keep Alive Interval, I tried increasing the OBD-II Response Timeout.

Yeah, I know, real scientific, but it seems to be working.