Last night I spent a few hours setting up my MAP based timing maps again. What I'm worried about is the battery on my palm dying, and me getting an "NVRAM checksum" error and loosing my map again.

I thought that if I hotsync'd my palm after saving my configuration on the palm that the timing maps would be backed up onto the computer so that if the palm gets reset I can restore it. I tried this last night and I found that a hotsync doesn't save your custom maps to the computer.

I am wondering if there is anyway to create a backup file of the maps that take hours to create?

Another problem I am having is that I am not able to delete my saved configurations. I forgot to make a few idle adjustments so I tried to delete the configuration I had just saved but the palm said it was unable to find the database file to delete. The only way I have been able to get rid of old configurations is to let the battery die on the palm and lose all of my saved configurations.

Has anyone else not been able to delete saved configurations or back up there custom maps to a pc? Are there any workaround for these problems?

 

What version of the software are you running?

Maps are saved, but only if you save it on the Palm.

Theres the copy in the ECU which cannot be "saved" directly. You can save the current ECU config (which includes maps) to the Palm through the "save" menu item . These maps are backed up when you hotsync to the Maps_-RX7L.pdb file.


How many times have you got the NVRAM Checksum error?

 

I'm using the 2.1 software. I have saved the configuration on the palm, but it is not being backed up onto the computer when I do a hotsync.

This is what I did.
1. Saved configuration on palm.
2. Hotsync'd palm to pc.
3. Hotsynced my backup palm with the pc
4. Check the backup palm for the saved configuration and it wasn't there.

Is there something I am doing wrong?

Any idea why I can no delete saved configurations on the palm? It tells me it can't find the database file?

As far as the NVRAM checksum error goes, I have gotten that error code about 5 times last year, but I haven't gotten it one in the last year.

 

Your "Backup" Palm? Whats that? You can't hotsync two Palms with the same hotsync name to the same PC. The hotsync manager gets confused and it screws everything up.

The problem deleting maps was fixed in 2.1.0 build 4. Are you using something older?
www.digitaltuning.com/software/rtek.zip

 

I have two Sony Clie' S360's. I only use them for my Rtek and figured that my computer wouldn't be able to tell them apart. I guess this is not the case.

I believe that I am using 2.1.1. I guess I need to upgrade.

What types of problems cause the NVRAM check sum error? Could it have been something I did?

 

Checksum errors are bad. They should pretty much never happen. The only thing that could cause them is if a write to the NVRam was interrupted. The only way that could happen is if power was lost to the ECU during a write. (i.e. immediately after you made a change via the software). Nothing you do in the software would be able to cause the error, even if you disconnect the Palm from the ECU.

How often do you get the error?

What is the firmware version (or serial number) of your ECU?

 

At one point, I got the error like once a month. However I it hasn't occurred in the last 6 months( maybe I've just been getting lucky). When I was dealing with the problem, I checked and double checked all the wires to the ecu, especially power and ground and couldn't find any problem. I did find that jarring or tapping hard on the ecu could cause the error. I could tell when the error occurred by the way the car ran. If I plugged in my palm it would say NVRAM checksum error and then say that the ecu needed to be reset. After it initialized, it would go back to normal but I would lose all my maps stored in the ecu. If I let my palm go dead( requires that I charge it a least once every two weeks) since the last time I had the error I would completely lose my maps and have to spend hours inputting them again.

I'm not sure what my firmware version is, I'll have to get that for you, but it's one of the very early ones. I've been with you guys from the start with the 1.7, then I had you upgrade it to the 2.0 to beta test it for you. I did the 2.1 chip upgrade myself.

 

By any chance, did the errors stop at the same time you put the 2.1 in?

 

unfortunately it did not. Actually, it occurred more frequently after installing the 2.1 chip, but then it sort of tapered off, it hasn't happened for months now( about 4-6).

Has anyone else had an issue like this? I've read through most of the rtek forum and I've never seen anything related.

 

i am getting the NVRam checksum error message and it wont let initialize the ecu... HELP

 

Anyone know where to find some decent timing maps for the 2.1 version? Thanks.

 

https://www.rx7club.com/rtek-forum-1...g-maps-885556/