NVram error followed by no response (2.1)
 

So I finally got the motor back together and was excited last night thinking I would be able to get this baby started again well once I got to the rtek software to make sure my map was just like I left it I started getting an nvram error then it would try to reset and give me a message saying there was no response from the ecu. This had happened to me before i took the motor apart but one day it started working fine and never did it again. I made sure all grounds are right but still the same results.

any ideas?

For anyone that might be searching with the same issue. I replaced my laptop (palm emulator) with a tungsten 3 and purchased a cable from pocketlogger. So far the issue has not happened again. The emulator seems to always have some type of issue. It's also a lot faster to input things on the palm plus it doesn't require my passenger to have a laptop on his her lap. The things I go through for not spending the money to update to the Bluetooth. =\

Ran into the same problem today don't know what's going on

Ive had 0 issues using my laptop to emulate a palm pilot for tuning the RTek in my Tii or vert. What palm firmware version were you using in POSE? Ive used M500 since the beginning and its been great.


Do you have a copy of your current tune saved to your palm? Made sure the cable is firmly into the bottom of the palm? Has it worked for you before properly?

well it happened again and my palm had been dead for so long it lost my tune....
starting from scratch i suppose

I feel like this is becoming a more common occurrence. I have no idea what causes it as it's so random. If I had to guess, I think the fact that the Palms typically sit around long periods of time and then have dead batteries when you go to use them plays a role. The memory in some Palms, as we know, gets erased if the batteries die. It is certainly possible for the batteries to get low enough that some memory is retained and some is not causing memory corruption. Then you change the batteries and the Palm works, but is still corrupt.

Well i have now regrounded my ecu using 12g wire, Weather tight crimps, 1200 degree safe heat sheathing, and dialectric grease per recommendation and grounded it to a location I can reach when needed so if this happens again I'll be saving for aem engine management or possible a tungsten t3 since I don't know if I can trust this palm vx

I Have had 3 handspring Visors do this. seems like corrupt data like turbo2ltr said is a likely cause.

it does it even with the palm not connected though. car dies and or runs badly, I plug palm in to see why and boom nvram error. only conclusion I can come to is bad ecu/daughterboard.

so this consistently happens to me after driving for more than 20 minutes. im at the point that im about to sell the car. I cant even leave town with it before it shits the bed and I have to reload all the settings back into the ecu. ive checked and replaced all the grounds, I replaced the ALT. im at a loss as to what to do at this point.
my only thought now is bad ecu because it happens even when the palm isn't connected. someone help me please I love this car but I cant drive it outside of to work and back