Has anyone successfully logged as many parameters as RX7Logger will allow (17)? I was able to log up to nine parameters simultaneously, but selecting anything more than that resulted in a world of pain.

Selecting, say, 10 parameters, and clicking OK displays the parameters without any values, while the Palm (apparently) waits for data, which never comes. The sampling rate (upper left) steadily drops to near zero. Navigating to the parameter selection screen and choosing other (or fewer) parameters doesn't work. The same 10 parameters are displayed without values, with a near zero sampling rate reported. Turning the ignition off and on doesn't work.

Even worse, disconnecting / reconnecting the Palm results in RXLogger detecting an NVRAM checksum error and requesting an ECU reset. Connecting another Palm device won't solve anything. The NVRAM error reappears and you have no choice but to wipe out all settings (see attached).

After ECU reset, the maps and configuration can be reloaded from file. But, an unpleasant surprise awaits if you go to the parameter selection screen under logging. The same offending parameters are displayed and once again you cannot successfully deselect them. And the cycle repeats (ECU reset, reload maps, etc.).

I corrupted two Palm PDAs at the dyno in this manner (m130 and m515). The only solution I found at the time was to reset the ECU and do a hard reset on the Palm, wiping all settings and data in RAM. Then copy maps from a backup (or SD card) to the clean Palm and reload configs & maps into the ECU.

Later on, I discovered a much shorter fix. If you have programmed a parameter preset (1, 2, 3, or 4) previously: go to the parameter selection screen and disconnect the Palm. With the Palm disconnected click on a preset and click OK. The parameters will be displayed with no values. Now, reconnect the Palm and, at last, the values will appear, displacing the offending parameters that wouldn't go away previously. However, if you have not programmed a parameter preset, you're SOL at this point and have to recover via the ECU/PDA reset route.

I'm running an RTek 2.0 in an N351 ECU. I've tried a Palm m130, m515, and an emulator running the m505 ROM. The issue repros with all units if > 9 parameters are selected and you (fatefully) click OK.

Seems unusual that the software lets you select up to 17 parameters but, in practice, cannot display / log more than nine.

Anyone else have similar issues?

 

i know im digging this thread up from the grave but i had this issue ALL THE TIME on my palm t3 and my palm III, i have not had this issue yet with my m100

i am looking at purchasing an m505 because i hate how the batteries of the m100 dont last long (AA batteries)

 

I got a new battery from here
Seems to last a long time. Though I just sent my ecu out for the Rtech
upgrade. Once I'm using it more we'll see how long it lasts. Came with tools to make
it easier to change out also.

I aslo got my Tungston T2 to hook up to my lap top (64 bit) via this usb
with this driver I found online

 

i hope you enjoy your rtek! thanks for the helpful links.

it is always best to buy a used palm but also buy a replacement battery. these things are old and their ion batteries usually dont last long!