ok so. i went out to the track tonight to tune my ecu. did a few runs and data logs

after my first run, i tried tuning but it kept saying unknown table size. and it kept saying this and my 3d graph was WAY OFF . like really really outragiously bad...

it kept doing this. i tried re-loading the map, since i was smart and saved it to my palm . so i re-loaded the saved map and it did it again. and again. and again.

i finally hit the reset button on my palm tungston t3 and it stopped doing it , for a while..

it continued giving me problems all night.

at one point i went to start my rx7 and it wouldnt start. the whole entire start up map was completely 0'ed out and i had no fuel on start up. i had to go in and re-do that little line graph so i had fuel on start up... how embracing is that?!!? i even needed a jump start since i killed my battery tring to diagnose issue.


when i am not in a hurry, the ecu works fine. but when i am out and really getting deep down and dirty with the thing it is a nightmere to work with....

also, it kept disconnecting and re-connecting at first. before i stared having unknown table size errors.

if i didnt save my map. and re-load it, i would have been in some pretty bad trouble, if i didnt realize what had happend . i could have been going down the track 10psi and POP! because the map was wrong..

 

Typically it's a display error, not an actual change in the ECU. It would take a lot of time for the Palm to update every cell in a map. It would be very unlikely to have the map spontaneously change massively. If somehow the map in the ECU actually got corrupt, the checksum would not pass and the Palm would say "checksum failed" and require you to perform an ECU reset.

Users have reported mixed results with the T3. We can't find anything wrong using our T3, but there are enough complaints about connection issues and weirdness that it's worth noting. You may want to make sure the contacts on the bottom of the Palm are clean.

The unknown table size error means that the ECU feels it knows what ECU it's connected to (therefore knows the sizes of the maps) and when it was sent a map from the ECU, it was not the size it was expecting. It usually means that there is a connection problem and some data was being dropped. But it seems you already knew there was a problem with the connection.

The zeroed out start map seems to be a bug in the map loading code. Are you sure you have the latest pocketlogger version? 2.1.3 Build 5

 

everything you said does make sense. i have build 4. i downloaded it 2 weeks ago from a link in one of your posts. i think it possibly could be 5. but i am sure it said 4. my lap top AND palm are dead from using it all last night, and i was to lazy to plug in. so i'll get the for sure answer when i get some charge on them...

lame excuse i know

as long as i have some sort of new starting map i'll be happy. this is the 2nd time the starting map has been wiped out leaving me paniking trying to figure out what went wrong.

as far as the palm t3 goes. yeah, its kind of scarry trying to view the 3d map and seeing such huge spikes all over the place instead of the smooth map i created. im sure it was possibly because it got corupt signal from the ecu. and im sure the ecu's values were unchanged. but i couldnt be positive.... and i wasnt about to chance it.

with all the problems i had last night , im kind of put off. expecially cuz i was trying to impress my friends but all that was happening was comunication error, wipped out starting map causing me to get a jump start cuz i killed the battery AND having to re-load my saved map 2 times because i kept seeing an odd map pop up randomly while it showed a blue connection in the corner...


of course. i will keep playing with it. and continue to just save my progress and keep working at it.

 

Thats too bad, because I really haven't had many issues except trying to load saved maps and the occasional lost connection from coming unplugged. Cheapy, Palm Vx not sure which build, but I haven't updated it in fear of screwing up my maps. Be careful letting your batteries get too dead, as I've heard you can lose everything on the palm and have to reload the software and all maps.

Good luck...

 

yeah if mine gets past 15% battery life i just stop doing anything.

this one time. right after my starting map was lost, i was at a gas station filling up. and i realized i didnt tune for hot start. so i tried starting and it wouldnt. and the palm kept dieing because the battery was so low. wow that sucked. i finally got it tuned and drove home. would have sucked if i couldnt get the rx7 started all because the starting map was lost.

 

I used a palm m500, havent had any problems with it except at night when I cant see the screen lol, so I bought a t3....and the headaches came flooding in. Connection issues, map erasing, and sometimes I had reinstall the rtek program all over again. I switched back to the M500 and no problems. The good thing I like about the m500 is that it uses AAA batteries, I can just run to the store and buy them.
The main issue that I had with the T3 was that it kept disconnecting. When ever I do a a logged run, it always disconnect. It disconnect even when I am changing the fuel cells.

 

heres food for thought. i dont think palm makes the serial connection cables for this palm device, the t3. thus the cables are china made . the palm t3 is ment to be on a docking station, not just some cable jammed up under it.


i have limited the connection issue using velcrow on my guage cluster surround. you have to use little screws to hold the velcrow to the surround. but i put the soft velcrow on the back of the t3 as well as the cable.

the 2 little pins arnt enough to keep good contact on the bottom of the t3 while driving or messing with it. but by me adding the velcrow and putting it up on my guage cluster, it limited movement.

didnt solve the issues 100% , i obiously still have issues when i remove the t3 and work with it in my hand. but while its up on the guage cluster its "ok"


i do have reset issues which causes you to have to re-install the program. and i do have issues where it just freezes. i also have a short battery life.

all in all. i believe i will be switching back to a different palm. i came from a palm III and it was very premitive and the touch screen was not accurate and i was not able to pin point on my datalogs. so i switched to the t3 for its sleek design.

i want to say its 49% the data cable and 49% the t3 itself. and 2% being the rtek with its starting map delete.


all in all the rtek is still my favorite. but its dependence on palm devices, leave it at the mercy of a crappy palm connection.

 

Palm did make cables for the T3 (they are impossible to find nowadays) and trust me when I tell you the china cables are 100% better. The original Palm cables were horrid. They did not have the support tab behind the connector so they were always very loose and fell out all the time.

See how there is no tab in the back?

 

why is the t3 on the compatibility list.

i bought 2 refurbished T3 palms and bought your hot sync cable and it wont stay connected long enough to do anything, maybe a minute at most before it starts jumping between the X and the -()- . its pitiful if i would have known that " some people have had connection problems i wouldn't have bought it. i would have bought a cheapy palm that would work a 100% of the time.

 

because. the t3 IS compatible, hardware /software are compatible with the pocket logger software and the rtek hardware.

the problems is that the t3 is not the best palm to have, like the palm III or other palms. its dependant on the palm device problems, not an rtek problem.

you cant blaim rtek for a problem that the palm is having.

known issues are always addressed by pocket logger. and if not then they have nothing to hide and say that it is a known issue and its being worked on. as stated above .


i have always had help when i needed it when i had to contact pocket logger.

just so happens, that the t3 has a downside to it. its so sleek and thin and the cable can only connect to a very small surface area. and its not probably listed as a known issue under the palm compatibility because not all users experience issues with the t3. i know 85% of the time my palm is just fine. notice how many posts i have in this section and this is my first real bitching post about the connector .

its also probably not reported on the palm compatibility list because it souly depends on the palm' device software.its the connection surface, and the manufacture of the data cable, as well as how you mount your palm while driving or you if you have slightly modified your connector by bending the tabs a little.

i had to slighly modify my connector to ensure the little tab springs were giving enough force to get an "ok" connection. and like i stated above i had to use velcro when i mounted it to my dash and help suport the cable...


t3 is ok. but, not the best to use because of its poor connector.

simply put


if you dont like your t3, i'll gladly buy them off you for back up. since my battery isnt the best.

 

I have the Palm III and it works fine until the sync cable stopped working. I tore it apart and found some of the worst soldering I have ever seen, random wires not used and such, I resoldered and deleted unused wires and it has worked fine ever since. I want to put in a carputer and have the palm emulator on it, that would be sweet.

 

i didnt really have an issue with palm III other then the touch screen was not sensitive enough to read the data log line graph. and editing fuel maps was rickety because the touch screen didnt have enough points on it. really shaky touch screen

 

FWIW, I got a Palm Vx off of craigslist for $5 haven't had any issues. Good luck...