As mentioned in my build thread, my ECUtalk is having connection issues. Since the ECUtalk was last used, NIStune has been installed, and the ECUtalk cable has been cut to make removal easy for my setup. The wires have been joined with lugs, including the shield. When the car is turned to ignition, the screen lights up but displays: "Cannot connect, going to main menu" A search around reveals that this fault can occur with a bad connection with the ecu and the plug. I double checked the plug today, pulled it out and then put it back in and re-tightened. I tried the ECUtalk again, but got the same result. Another search revealed that the issue also can happen with a badly installed NIStune board. Checked that today and it looks fine. I know it's not just my unit that's damaged, as I tried another ECUtalk and got the same result. Thoughts?
Yeah I read that, was the board ruined? I haven't even used the car since it was installed, obviously. Any signs to tell it's fried? Didn't smell and couldn't notice anything burnt when I pulled it out.
Could be that not all the jumper pins have a solid connection. Or the bridging resistor not having a solid connection. First type 3 nistune I ever did had a similar problem. Ran like a bag of shit, cel sort of very dimly came on and couldn't connect with consult. Redid all the connections and it was good as then. Pull the ecu and check the soldering job.
Yeah ecu is pulled, I inspected them all but it looked alright, I might try give them a once over just in case.
My ECUtalk/Ipaq combo worked well on my ecu when it had a Z1 chip. After the Nistune daughterboard was installed and re-flashed with my old Z1 data (temporary set-up til a dyno tune could be done), the ECUtalk/Ipaq still worked. After I had a dyno tune done on my Nistune, I again had zero problems with my ECUtalk and ECU. Perhaps a dumb question but what has been flashed to your Nistune ECU so far? A duplicate of your old chip data, oem chip data or dyno tuned data?
