I have done a search so please don't flame. I just could not get a solid answer. Does Tuner Pro Rt work with a USB cable/adapter for data logging?
Mangus?
I just ordered a new Dell laptop and it doesn't have a serial port only a USB, I just want to see how screwed I am when I try to log some data.
Thanks Guys
sorry if this post is a repeat of an earlier post.

 

I can emulate with Tuner Pro with a RS USB cable adapter, but not scan/data log.

Just one more reason for getting a disposable laptop, as opposed to using a good one.

 

Is there any logging program that will work with windows Xp and through a usb?

 

i am struggling with this today. tunercat says no issues with XP and adapter for PP2 or Romulator. the manufacturer of my aldl/serial cable says flat out winaldl does not work with XP. moates adapter may work he says (winaldl). i need to change my com ports in xp to 1/2/3 so winaldl can connect with radio shack serial/usb adapter which i believe is on comport 5. issue is i cant find comports in xp. yes i am dumb. i found them in wind 98 however . if push/shove i load on wind 98. and try again. anyone can offer a tip !!

 

Anyone else find that WinALDL doesn't work with Win XP? I haven't tried it yet because my XP machine is a brand new Dell desktop. I am using WinALDL on an IBM ThinkPad with 96MB RAM and Windoes ME. I had the standard learning curve issues with a new computer, but once I got it all figured out, WinALDL works great.
Just my $0.02...

 

boy do i feel stupid. i was just informed the radio shack serial/ usb needs to be connected for me to find the port and change it to 1/2/3. what the heck do i know about computers.

 

Thanks for the insight, keep me posted.

 

If you have USB and want to play with some USB stuff, I've tested out the new 'ALDU1' ALDL adapter with TunerPro, WinALDL, and DataMaster. Seems to go off without a hitch. Still want to try it our with FreeScan, maybe this weekend.

Not trying to push it, just presenting options. If you've got serial, then there's other options out there for that. Many people have luck with the USB-to-Serial adapters also, once they get them configured properly.

Anyone try PCMCIA Serial cards? That seems like it'd be pretty good. Alternatively, a PCMCIA USB card would address all issues as well.

 

Hey craig is this also with WinXP?
It sounds like a good option.
Do you have to configure any ports or anything like that?

 

Yep, my testbed is WinXP...
Configuration is pretty easy. I'm working on some documentation on what is needed. Special driver install makes it straightforward.

 

I have to agree with Craig. The driver supplied with the USB AutoPROM is REALLY easy to use and the driver documentation walks you through the steps of changing the USB port settings to COM 1,2,3, etc.

 

Sweet, It looks like that is the way I am going to go.
I will go ahead and order my dell laptop then.
Thanks guys!

 

a couple of things:

1) i have successfully used winALDL with my XP laptop using a serial interface
2) tunerpro RT has been known to work with a serial->USB converter for both emulation and data logging, though *I have not done so myself*
3) craig moates offers a straight USB ALDL interface that has been tested on multiple platforms with multiple software platforms.
4) have at it! =)

 

Ive used a pcmcia to serial adaptor for about 2 years now. Works flawlessly. No abnormal disconnects. No muss no fuss. Driver is uber simple and small. I would recommend getting a ruggedized version so that the dongle doesnt get bent or mangled. Anyways theres my 2 cents

 

Has anyone been able to connect with winaldl and their usb version of Autoprom? I tried adjust the baud rates in winaldl and in device manager but no joy.

 

It can be a litte tricky to get it set up. Try the following:

1) Set the horizontal switch on the AP to the 'outside'.
2) Turn the car off, and load up WinALDL. Set the WinALDL to 4800 baud. Make sure the right port (3 or 4) is selected.
3) Select the right ECM in WinALDL and get it ready.
4) Turn the vertical switch to the 'up' position. This presents 10k between A & B.
5) Turn the key on, and look for the green blinking light in WinALDL.

That should do it. Sometimes you have to get the WinALDL up and running before you turn the key on.

 

Yes. My USB AutoPROM works like a dream with WinALDL. Check your switch settings at the back of the AutoPROM. Did you run the USB driver upgrade and the port setting configuration change? If not, you need to.

 

Whats the port setting configuration change your referring to Jeepguy? I installed the driver from craigs website and thats what ive been adjusting port settings for. Im running win Me, maybe thats part of the problem.

 

My little laptop runs Win ME and I can log just fine with WinALDL. If you are using the USB AutoPROM, you may have a few troubles. I think Craig can explain it a little better than I can. I am using my USB AutoPROM in pass-through mode with WinALDL and Windows ME. It works great. I logged data all last weekend off my Jeep with it.
Don't screw with the USB port settings in that driver config window once you get the USB port set up like you want it. There is a button at the top of the WinALDL window that says "Configuration" you need to make sure you have the COM port (1 or 2) selected to correspond with what you selected in the USB port configuration. Now, in that same window at the bottom of the settings is the baud rate. Set it to 4800.
Start logging and have a good time!!!

 

When we talk about the 'ALDU1' ALDL converter I can tell you that Craig use the chip "FTDI FT232BM" and the driver that comes with this chip got some special features.
WinXP put your adapter on COM port 5 or 7 depends of you USB equipment installed on your Laptop.
No one of the Data Logging software accept the COM port 7 or 5.
But the Craig's converter driver got the possibility to change the COM port number and show you the ports that are free at that moment.
See my screen shot how I changed from COM 5 to COM 2.
In addition you can tune the USB transfer size for low boud rates (Our ECM's)
I was able to data logging using DataMaster. See the screen shot for the settings of DataMaster.
I hope that this help you.
Regards,
Cobra289

PS
If I got the time tomorrow I will do a test with TunerPro RT.

How to change the COM port under WinXP:
From Device Manager, select "View devices by type", then "Ports (COM & LPT)". Select the USB serial port
and click Properties. Select the "Port Settings" tab, and then click Advanced. Choose the required COM
port number from the list and click OK.

 

Here is the DataMaster screen shot.

 

It works with Win XP. I did it. My desktop is a Dell with XP and it works fine.

 

Hi Gents,
Today I have run a test with Craig “ALDU1” ALDL converter under Win XP with DataMaster, TunrerPro RT and WinALDL.

Well the results are:
WinALDL run like a charm, no problems.
DataMaster run with out problems.
TunerPro RT will NOT run!!!!!

TunerPro connects with the data stream with 160 boud but spit only “Packet Errors”
With the 1227165 data stream doesn’t connect and with the $6e mask neither.
Maybe is because my EPROM is a $32 mask, but I think that with the standard 1227165 data stream should work for this set-up because it refers to both masks.

Mark can you help us with this problem?
When connects under 160 boud the “Actual sample Rate” start to changing very rapid.

Regards,
Cobra289

 

I have precisely the same problem in TunerPro RT with a 1228746 ($61 mask) ECM. I think it is in the process of being fixed. Ask Mangus about it. It may well be (in my case) the fact that I am using a laptop with the POS Windows ME operating system. That wouldn't surprise me any in the least.

 

I'm not sure I completely follow. What, exactly, isn't working?

straight 8192 baud ALDL data logging with a MAX232 or 2-transistor serial ALDL interface isn't working on a 1227165 ECM using $6E code and the 1227165_6E.ads file? If thats the case, make sure you have the 10k between A & B and if it still fails, make sure its not your cable.

I can datalog just fine under the above conditions.

If you're using a serial->USB adapter and you get functionality using other software, you should have no trouble getting data using TunerPro, provided *your definition file is correct*. If using 160 baud, its critical that the packet size is set up correctly in the definition header. If using 8192 baud, its critical that the connection message information is set up correctly. Consult the TunerPro help and the datastream information for your particular application for more information there. Unfortunately, I don't know all there is to know about every combination out there.

Hope this helps.

 

This may be OT, but exactly how should the packet size in 160-baud struff look? I have mine set at 20 and 0 offset. What about the checksum, monitor , and master settings? Is there a way to tell how those need to be set using the hac or def file?

 

changed the com port setting this weekend on radio shack serial usb adapt and all is well. windows XP. only thing i noticed is that it appeared i needed to have winaldl running b4 i connected to aldl the 2 prongs. if i turned off ign and tried a second session i lost winaldl. then i needed to detach the usb from laptop. reattach, then turn on ign, then reattach the prongs to reestablish start up. only tried for 10 minutes sunday to confirm winaldl/usb/XP is gonna work. not sure of the steps being exact. seems real finicky!! may end up adding a toggle swith on red cable. may need to document the procedure on paper as it took some thought on 2nd connect as to where i went wrong after first success..

 

for 160 baud, the packet offset is 0, and the packet size is the number of bytes in a complete data packet (and this depends on the application).

Checksum doesn't matter, as dump commands aren't being sent. Master should set to true, monitor should be sent to true.

 

I've done that. All I get is a wildly fluctuating sample rate (using AutoProm USB) and packet errors.
Let's take this offline from here, Mangus.

 

Hi Mark,
Please be patient with me, I am an ignorant that tray to leave with your software world. (Believe me, it is hard) but I tray step by step.
Like most others I want fast result (Less reading) but never forget “WE REAL APPRECIATE YOUR WORK AND SERVICE TO THIS COMMUNITY”

I hope that I can explain the set-up correctly.
I have one of the Craig Moates “ALDU1” ALDL converters and I have done data logging with DataMaster and WinALDL with success (ALDU1 set to 10K), after restart Win XP and trying to get data with TunerPro RT I don’t get connection with the 1227165.ads definition file (I have a 165 ECM with a $32 BIN file on the EPROM)

Trying to get connection I changed the definition file for the 1227165-160boud.ads, at this moment I get connected but the “Actual Sample Rate” starts to change very rapid (Impossible to read) and the “Package Error Count” starts to count.

Do I need to select AutoProm because it is a Moates USB converter?
I did select the MAX232.
I have read the TunerPro Help file but I get stuck on the setting of the “Mask ID Offset” and in particular where can I find the “offset” for a 32 mask?

Thanks in advance,
Cobra289

 

The Default ECUs screen, a shot of which you post above, has nothing to do with communication. Lets ignore that for now. =)

Those of you using Moates AutoProm have *2 choices* when it comes to ALDL communication. I will try to outline them here, please read carefully (twice, even):

OPTION 1) Use hardware passthrough mode. Hardware passthrough mode (which is set by placing the horizontal switch on the backplane to the outside position - towards the outer edge) basically turns the AutoProm into a simple interface cable, and doing so *bypasses the AutoProm "brain"*. In passthrough mode, if you wish to use TunerPro (you can use any ALDL software you choose), you must set the ALDL interface device type to "Max232" (since the autprom uses MAX232 chips for interfacing).

Once the AutoProm is setup for passthrough mode as described above, you can then begin datalogging as though the AutoProm is a simple interface cable. You can use WinALDL, TunerPro, Moates ECM852, or what-have-you.

*note that you cannot emulate or chip burn when in passthrough mode*.

OPTION 2) Use "Software Mode". To use software mode, the horizontal switch on the AUtoProm back-plane must be in the inside position (towards the middle of the backplane). In software mode, the AUtoProm itself does the data parsing from the car and sends the data back to TunerPro. *ONLY TunerPro can be used for ALDL interfacing with the AutoProm in software mode*. To set up TUnerPro to communicate in AutoProm Software Mode, select "AutoProm" as the ALDL Interface Type in the preferences window.

Once the AutoProm and TunerPro are setup to communicate in software mode, you can use TunerPro's ALDL Comm tool to communicate with your car, provided you have the appropriate definition file for your application.

Now, back to my day job... =)

M

 

Okay. I'll give it a whirl tonight. I think I may see where I went wrong. I'll let you know later tonight.
Thanks, Mark!

 

Another quick note:

if using the AutoProm in software mode, you'll see the faster (and erratic) sample rate when doing 160 baud if there is any communication problems (you should see a normal .66 hz or so sample rate under normal, successful communications). This is because the AutoProm fills in missing bytes and sends them back to the software. What this means is even if the AutoProm only sees 1 byte of data when it should be seeing 20, it fills the missing 19 bytes in with zeros and immediately sends them back to the software, hence the much faster sample rate.

You shouldn't see such a high sample rate in passthrough mode.

also, once you lock the '165 in 8192 mode, you can't go back to 160 baud logging without first powering down the car (completely, key-off) for 20 seconds. Upon power up, it will begin transmitting 160 baud data again. (I know you're not using a '165 jeepguy, but others may be).

 

I think that we have some misunderstanding.

I don’t have a AutoProm.
I have a USB to ALDL converter “ALDU1”.
It use a "FTDI FT232BM" that is a type of MAX232 I think!

Maybe is that the problem. I didn’t power off for 20 sec. after I did data logging with DataMaster (was lock at 8192 boud).

Regards,
Cobra289

PS
It is bed time for me. (Europe)

 

for the ALDU1:

1) in tunerpro preferences, select "MAX232" as the ALDL interface type.
2) select the com port installed by the FTDI driver (usually COM3).
3) load the 1227165_6E.ads aldl definition (8192 baud) into the ALDL comm tool
4) hit "connect"

it may take a couple connection attempts (though it only takes 1 for me usually), but you should start getting data!

M

 

...and the source of the packet errors??? Does the software recognize this and log an error? It would make sense because I was receiving zeroes on just about everything. The CTS was reading -40.00F when I was hooking up with TunerPro RT. Everything else was a zero...I think. I was getting a 0.66hz sample rate, but zeroes pretty much across the board.
Is this a def file problem? If so, I bet I screwed it up somewhere. Sheesh...

 

yes, it detects packet errors by cross checking the checksum of the packet. errors can indeed be a result of invalid packet length configuration in the definition file. try different values.

 

Okay. I'll give it a shot and let you know how it works this weekend. I'll post another 8746 def file if I get it fixed.

 

Hi Gents,

I have given today a try for Data Logging with TunerPro RT and it was a SUCCESS.

Mark your software ROCKS. Thanks for your advice.
I did change the “Target Sample Rate” to 8 Hz. One click and it was connected.
Second tray after waiting of 19 sec. two click and it was connected.

TANKS TO ALL AND IN PARTICULAR TO:

Craig Moates for making the USB to ALDL converter that works.
Mark Mansur for the splendid software TunerPro RT.

See screen shot for the TunerPro data logging.

CONCLUSION:
Using a 1227165 ECM on a 305 TPI from ’87.
The USB to ALDL converter did the work without problems (Don’t lose the time with USB to serial converters)
I was able to data logging with TunerPro RT; DataMaster and WinALDL.
I did change my file system from NTFS to FAT32 (no science behind that, but just in case)

Regards,
Cobra289

 

Good to hear, Thanks Cobra289 for keeping us up to date.

 

AWESOME. I love to hear success stories. they make all the hard work worth it!