datalogging problem - new user :)

bildorn · Post by **bildorn** » Wed Dec 20, 2006 8:46 pm

I am using tunerpro rt with a ALDL cable to serial & a radioshack serial to usb converter. I know the radio shack cable works, because it works with my romulator.

i have the comm port set to 7 for in tunerpro RT & on my computer. In tools/preferences i can get the test the cable button to say everything is OK ??? but i dont have anything show up on the screen when connected.

I am using 1226870_160baud_85_Fcar.ads & 1f.xdf file from moates. The ads file says its not tested in a running car in the notes section.

are there better files for my 85 tpi system? am i missing something or not doing something right?

helllllllllllllllllllllllpppppppppppppppppppp!!!!!!!!!!!!!!

Post by **Mangus** » Wed Dec 20, 2006 9:58 pm

160 baud monitoring uses a much lower baud rate than your romulator. It could very well be that the serial->usb converter isn't working for you. TunerPro opens the port at 4800 baud for this, which works with most, but I know that some don't like it that low.

You might try WinALDL and see if it works with your setup. If it does, you know it's probably the definition that is the issue. If it doesn't, suspect the converter.

Snohomish, eh? How'd you fare in the winds? We had no power for a couple days.

bildorn · Post by **bildorn** » Thu Dec 21, 2006 10:18 am

we lost power until sunday night about 7pm. so almost 72 hours. i have 5 acres & no tree damage, because were at the base of the hill.

thanks, i'll try downloading winALDL tonight. I'm trying to avoid re-pinning the harness & changing out the computer because it works just fine. I just want more low end power

Mangus wrote:160 baud monitoring uses a much lower baud rate than your romulator. It could very well be that the serial->usb converter isn't working for you. TunerPro opens the port at 4800 baud for this, which works with most, but I know that some don't like it that low.

You might try WinALDL and see if it works with your setup. If it does, you know it's probably the definition that is the issue. If it doesn't, suspect the converter.

Snohomish, eh? How'd you fare in the winds? We had no power for a couple days.

bildorn · Post by **bildorn** » Thu Dec 21, 2006 5:09 pm

winaldl didnt work either.

i had to switch to com3 for the cable & it wont work in tunerpro now either. it used to find the cable, just not data log. now it wont find it either.

now what? stuck buying a 80$ cable from moates just to check it?

thanks for your help.

Mangus wrote:160 baud monitoring uses a much lower baud rate than your romulator. It could very well be that the serial->usb converter isn't working for you. TunerPro opens the port at 4800 baud for this, which works with most, but I know that some don't like it that low.

You might try WinALDL and see if it works with your setup. If it does, you know it's probably the definition that is the issue. If it doesn't, suspect the converter.

Snohomish, eh? How'd you fare in the winds? We had no power for a couple days.

bildorn · Post by **bildorn** » Sat Dec 23, 2006 5:57 pm

I GOT DATA!!!!!!!!!!! only with winALDL using a new cable & driver. but i cant get tunerpro to datalog. even if the ADS file was bad you would think i would get something on the screen.

know that i have the text file, now what do i do with it

not easy to view it.

bildorn · Post by **bildorn** » Sun Dec 24, 2006 4:49 pm

I got Tunerpro to work too. but i'm having a hard time getting consitent files that i can get any meaningful data from. i dont get knock counts or load or degrees of retardation in my data.

bildorn wrote:I GOT DATA!!!!!!!!!!! only with winALDL using a new cable & driver. but i cant get tunerpro to datalog. even if the ADS file was bad you would think i would get something on the screen.

know that i have the text file, now what do i do with it not easy to view it.