ini failed

Discussions related to Nissan DataScan I software (NDSI) for Android
Tom
Site Admin
Posts: 647
Joined: 09 Dec 2011, 19:17

Re: ini failed

Post by Tom »

NDSI app is next to be updated. We will be implementing the change in the upcoming update.
OwnerCS
Posts: 18
Joined: 15 Jun 2014, 22:01

Re: ini failed

Post by OwnerCS »

Good to know NDS1 for Android will eventually support 98-99 A32a. I know several owners who are interested in the Android version.
OwnerCS
Posts: 18
Joined: 15 Jun 2014, 22:01

Re: ini failed

Post by OwnerCS »

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. :D
OwnerCS
Posts: 18
Joined: 15 Jun 2014, 22:01

Re: ini failed

Post by OwnerCS »

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 change?
Tom
Site Admin
Posts: 647
Joined: 09 Dec 2011, 19:17

Re: ini failed

Post by Tom »

I'm confused. EF is the default ECU id. I thought the ECU id for A32 was ED. What settings are you using?
OwnerCS
Posts: 18
Joined: 15 Jun 2014, 22:01

Re: ini failed

Post by OwnerCS »

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 required.

For a 98-99 model A32, to get NDS1 to work it takes the - "96 Z Car" option. I have two A32s. One is a 98 model and the other is a 99.

Here's the confirmation post from reallywildstuff that it works.

https://maxima.org/forums/4th-generatio ... ost9129878

Until NDS1 for Android will allow the settings to be changed like NDS1 for a PC with the - "96 Z32" option, the product is of NO use to an A32 owner with a 98-99 model. That's all there is to it. For an A32, it looks like the ECU ID can be ED or EF.

How can I set the 96 - Z32 option on the Android version?

I found an old picture of when I used NDS1 on my 99 model A32.

http://i286.photobucket.com/albums/ll11 ... dk8gag.jpg
Tom
Site Admin
Posts: 647
Joined: 09 Dec 2011, 19:17

Re: ini failed

Post by Tom »

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?
OwnerCS
Posts: 18
Joined: 15 Jun 2014, 22:01

Re: ini failed

Post by OwnerCS »

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.
OwnerCS
Posts: 18
Joined: 15 Jun 2014, 22:01

Re: ini failed

Post by OwnerCS »

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 file" option has been checked. The data logging was started. The app had permission to write to my phone. I have no idea where to find the log.

How about providing a little information about capturing a log if you want me to help DEBUG your PRODUCT.
Tom
Site Admin
Posts: 647
Joined: 09 Dec 2011, 19:17

Re: ini failed

Post by Tom »

The debug files are saved in the Download\DebugLog folder.
Post Reply