I can't emulate and scan in TunerPro v4. This is the USB version of the Autoprom. It's one or the other which is semi-frustrating seeing as it's pointless having emulation when you can't keep an eye on what the computer is doing.
Even when not emulating, just using the Autoprom as the chip, it still won't let me connect to ALDL .
Any idea's or is this just impossible and I need 2 computers to do what I want to do? I've got a Romulator I could try using with TunerCat and have TunerPro datalog with the Autoprom but I'm falling in love with this Autoprom.
Did I mention I love USB? Power and serial all in one, geez is this thing easy to pull out and get running. No more messy parallel cables, power wires, ribbens for seperate emulator, scanner, and burner. to Craig for the awesome product... but

 

i am haqving a problem with connecting to the ecm with my aldl cable. i have hear that they are having a problem with the software (at least that is what i was told by other members here) i just purchased tunercat so i will see how that works out.

 

Point of reference XP or 98?

I have intermittent probs with 98 and 3.09 with emulate, aldl, and table edits all at same time on my laptop at least.
Seems to only happen when swapping windows.
Seemed worse with 4.0. So I haven't taken time to test it out and tell Mangus. Since he is currently focused on XP.
Usually locks up TP and the USB port so I have to reboot to get communications back.
I also noticed that 3.09 at least won't connect if the usb is using com 6. I had a hub hooked up when I found this.

 

John - let's (you and I) play some mastermind here and try to figure this out.

The AutoProm is very well tested with $6E (both Craid and I own $6E cars). It is likely something simple.

The first thing to do is put a known good chip in the car and make sure its running.

With the chip installed, try to connect to ALDL.

In passthrough mode: Horizontal switch away from the USB port. Make sure TunerPro is configured to use MAX232 as the interface type. Vertical switch in the upper most position. With 4.0 it should connect on the first hit (it will timeout after 15 seconds if no connection is made).

If passthrough mode works, next try AutoProm mode: Horizontal switch towards the USB port, vertical switch in the up posiiton. TunerPro should be configured to use the AutoProm as the ALDL interface type. Again, it should connect right up. In AutoProm mode it might take a few connection attempts (I haven't worked out the bugs there yet).

Once you get connected, next focus on emulation.

First upload a known good bin to the emulation buffer. Verify it back and make sure it checks out. If so, try running your car. If the car isn't running correctly in this "known good" state, there may very well be an issue with the AutoProm emulation output stage. Contact Craig and he'll get you squared away. If you have an older Autoprom, there have been some emulation hardware improvements that he can put in place (if necessary).

(To all The AutoProm is not a simple device, nor is the software interface for it. There are lots of variables at play here. If you're having problems, be very specific about what the problem is, what specific actions cause it, what code ECM/code mask you're using, and what you've tried to solve it.

TunerPro should work fine with Windows 98. Win98, unfortunately, isn't the most stable OS, so I'm sure there are issues that aren't present in XP. I've run into many crashes that have nothing to do with my code (many related to display drivers). Please keep me informed of any crashes you run into on 98, and send me as much info and support files as possible. This helps me make TunerPro better.

 

BTW, it's Jo(no h)n you should know that by now.
Computer; Compaq Presario 3045us, Windows XP SP1, USB 2.0
Autoprom USB version on virtual com1 WHEN in "autoprom" mode AND "bypass" modes.
Using TunerPro RT V4 Build 4.00.2601.00
I can connect using the supplied ads file in "autoprom" mode ONLY when the chip emulation header isn't plugged into the ecm. I haven't tried "bypass" mode yet seeing as I'm trying to emulate and scan at the same time.
I've uploaded the bin to the Autoprom using TunerPro and then installed the header into the zif on the Autoprom to verify with Flash'n'Burn. It's working fine.
BTW, the checksum routine is disabled using $AA in the mask and the emulation works! But like I said, it's either one or the other .
I don't know if I can be any more clear than that. It'll time-out when I'm emulating and even when I'm not. The ONLY time I can't connect to the ALDL is when the Autoprom is plugged into the ecm. If I remove it and let it dangle and use a chip, it works. I can still "emulate" and upload to the Autoprom from within TunerPro while datalogging but what good is it when it's not plugged into the ecm!

 

i am all confussed over this whole thing. i am using the ostrich unit and when hooked up to tunerpro it sees the unit. i than open up the bin and i can upload it to the ostrich. i have the car running with that bin but my problem is that i cant hook up to the car with the aldl cable. what am i doing wrong. its like it doesn;t see the cable so i cant do any datalogging. as far as the emulating goes i have that part working fine. i am also using xp and my laptop meets all the requirements.

 

another thing mangus, when you say the switch away from the usb, i am assuming you mean the switch on moates aldl cable to usb box. what position is away and which one is towards. also is the fan supose to be running when the cable is hooked up to the aldl. it runns when the switch is in one position and not the other

 

We're talking AutoProm, you're talking Ostrich. Two different products. No horizontal switch on the Ostrich or ALDU1.

 

Yes, Jon, not John. Slip of the finger (I type on auto-pilot - fingers often go where its most common to go).

So, you can emulate successfully and you can datalog successfully. But not both.

Interesting. I'll have to think about that. The two systems are mutually exclusive.

 

Go to the web site and download the latest build. You're a few behind. I don't believe this will fix this specific issue, but it fixes a bunch of others and ensures that we're all on the same page.

 

I also cannot connect to my ECM using ALDL. I am using the Ostrich and the ALDL to USB converter box from Moates on a 730 ECM. I have tried running Win2K and Win 98. On windows 98 it will not connect nor can I have both pieces of hardware plugged into USB at the sime time, otherwise 98 locks up. On Win 2K, I have no problems with both plugged in, but I have tried connecting to the ecm with the factory EPROM and also tried using the Ostrich with no success. I have double and triple checked all my port settings and hardware connections. I am using the most current build. Just for the hell of it I tried using 160 baud and it did connect but showed all my fields as saying "Throttle Position Voltage" or % I forget, yet showed no data. I am sure that this is because it was never meant to connect at 160 though. Anyhow I am at my wits end, I have been searching and reading about similar problems, but have not found an answer. Hope someone can help. - Bob

 

Bob -

Can you tell me what ECM and mask this is?

Others have seen the Win98 lockups with the USB driver. Unfortunately I didn't write the USB driver. It's a stock USB driver from FTDIChip. They aren't the greatest drivers, but unfortunately they're what we're left with for the moment.

M

 

730 ECm 8D AUJP.

Also, Here's a quote from you in another thread: "TunerPro does not "detect" ALDL cables. Figure out what COM port your cable is installed to (for MAX232 it's almost always COM1) and configure TunerPro to use that port. The latest version of TunerPro includes a cable test feature in the preferences. Try it out to make sure your cable is working properly (disconnect it from your car first)."

Since my computer has both USB AND serial... Do I have to use a serial cable and/or COM1? I currently have it set to COM4 becuase thats what it says it is using for the usb connection in my device manager.

Also, when I run the test to check the cable, it doesn't seem to matter what com port I pick in Tunerpro, COM's 1-4 all say it checks out, alhtough I didn't try 5 and up. - Bob

 

And another thing, on the computer with Win2k I seem to be having some errors with Com1 and 2, it says that they aren't working and need to be replaced???? But since I'm using Com4 does this matter? And if it does then why did it connect at 160 baud? And why on the Win 98 machine did it not connect at all even though it had NO Com errors.?!?

 

hey mangus sorry to be a pain here (you seem you to very busy) i have a quick question. i finally got the aldl cable hooked up and tunerpro was able to see it. i than started to datalog and after the session i went to reveiw it and there was no infomation just the header on the spreadsheet was there. am i still doing something wrong. its a 165 using 6e with moates ostrich and aldl cable. i need to record data to send out so i can get this thing tuned cause right now its not even drivable

 

Did you select a file to record to first? You have to select a file, then hit the record button.

 

yes i created a file first to record it to. btw what type of file should it be.

 

Enough about him... back to me now Did you read my replies?

 

sorry 79_efi i will butt out of your post