nisscan.com

The beta version v1.151 WORKS. It connected right up.

Tom wrote:
> The debug files are saved in the Download\DebugLog folder.
Tom - I emailed the logs to the yahoo account. Let me know if you received them and if I need to capture new or additional logs.

Thank you,
Craig

OwnerCS wrote: > Tom wrote: > > There is not need for the "96 Z Car" option on the Android app. > > It should connect fine to both types of ECUs. > > > > Can you get the debug log file for a failed connection? > > Yes. I'll be glad to. Let me see if I can find the log on the phone. The "Save debug ...

Tom wrote:
> There is not need for the "96 Z Car" option on the Android app.
> It should connect fine to both types of ECUs.
>
> Can you get the debug log file for a failed connection?

Yes. I'll be glad to. Let me see if I can find the log on the phone.

Tom wrote: > I'm confused. EF is the default ECU id. I thought the ECU id for A32 was > ED. What settings are you using? It depends on the A32 year model. On NDS1 for years 95-97 the default code works fine - just like it does on the 91 Q45. I've tested it on a 97 model. No special code override ...

Ok. Just installed Lite version 1.5. ECU ID came up as ef - FTDI connection seems to be working. Tried to connect and still get the ini error on the 98 model A32. Somehow, I must not be making the right setting changes for the 96 z-car and connection ID- EF. Is there anything else that I need to ...

Tom wrote:
> NDSI app is next to be updated. We will be implementing the change in the
> upcoming update.

Thanks Tom! My phone just updated with the new release. I'm on my way outside now to give it a try.

Good to know NDS1 for Android will eventually support 98-99 A32a. I know several owners who are interested in the Android version.

What year is your car?

Tom wrote:
> OK.Thanks for the info. We will look into implementing ECU Id option in
> NDSI Android app.

Hey Tom - Any progress on providing the ECU ID option for Android?