Weirdness when loading saves
 

I came out to the car to start her up and just kept on cranking, I had loaded up a save earlier and it acted a little weird, but it did get in there and everything looked right. I checked the starting tab under the ECU setup and it was blank. wtf?

I reset to defaults and it was back, so I reloaded the save which had started up and got me into work earlier and it got to about 50% and lost connection. Palm froze up for a bit but eventually started working again and tried loading the save again, worked fine, but the start tab was cleared out again(flat 0 no curve).

I tried another older save and same thing, loaded fine, but no curve in the start tab unless I reset to defaults.

I just manually entered the start tab and it fired up no problem, but it definitely caught me off guard.

So in general here is what I noticed:
1) From default loading a save will crash around 50%(time out?)
2) once past initial crash and partly loaded it loads fine.
3) When ever you load I load a save point it reverts me to load based instead of map based.(quick check box but have to be careful)
4) I haven't checked since I saved again with the start entered in to see if it stays or goes away after a load.

Just normal quirkiness? I can deal with it, but I am excited for Bluetooth and android hoping to solve some of the weird palm quirkiness.

What palm are you using? I had similar problems with my M515, which often dropped the connection. I had all sorts of weird problems including the start map zeroing out. Twice I tried to start the car only to realize it was getting NO fuel due to this problem.

Since switching to a Tungsten T2 and palm emulator on my laptop, I have yet to see any of the connection problems.

m100, could go emulation on the laptop, but just hoping the Bluetooth connection comes through sooner then later. I guess it could just be a bad m100 connection. Just weird that it is so repeatable.

i have had this happen to me 2 times. once when i had just ran at the track 1/4 mile and i thought i blew the engine cuz it wouldnt crank..

it hasto do with the palm and poor comunication. the m100 has a slow processor. i notice when i click the "tune" button that it takes a few seconds to refresh the tables.

i have a thread here in this section about the palms i have been using. dont use the t3. the palm 100c is ok but had same issue. i havent had this issue yet with my m100 but i have not tried to revert to any other maps or save maps yet.

i can tell you that i did have many issues with this. once i was at a gas station and it did it. battery level on my palm was critically low and i barly made it in time redoing the starting map before the palm died.

The OEM values are:

137 88 49 35 24 16 16 16 16
(thanks to mike who sent this to me)