mista350

I have tried searching this but it appears that i am the only one to have this problem.
I cannot get my ostrich to work with my TBI and 7747 ecu. I am able to burn chips with my burn 1 and flash and burn and they work well. I cannot get the ostrich to work with tuner pro or tuner cat. I have talked with Craig and Mark and they have been helpful and great but I guess my bird brain just doesn't get it. I have been told that I need to set the 8th byte (the one with $0D in it currently) in the bin to $AA. How do i do this? what program do i use? How do I find the eigth byte. I have read a couple of posts that say the same thing but I can't find the part of any program that will let me edit this.
My cars symptoms are
1 I upload and verify with success my edited bin
2 I get a rapidly flashing service engine soon light and an engine that only runs in limp mode.
3 Same results with key on or off

I know it is probably something simple. Can someone help me?


Thanks.

MISTA

funstick

your working with a truck ecm. hmmm 27c512 128k memory. you sure you have everything setup correctly.

mista350

most likely i have it all backwards. Where should i start?

funstick

make sure your emulating the proper size chip first. 27c512 then make sure the red lead on the cable is facing pin number one which would be the notch on the chip facing outwards from the center of the memcal. try that and make sure tunerpro is actually talking to the ostrich. if its not then obviously its not powering up and this could be the cuase of your troubles.

mista350

Tuner pro rt shows the ostrich connected and verifys the bin is loaded into the ostrich. The chip size is something new for me to try though. Thanks.

Mangus

chip size is handled automatically by both pieces of software based on the size of bin loaded.

Make siure you have the checksum disabled and that you have the emulation header plugged into the chip adapter correctly.

Grumpy

In the 42 Mask you need to change 0004 to AA.

You need to use a hex editor to do that. You should be able to find some way to do that in the software you have.

Mangus

Is this 0D or 42? I thought in our emails that you had mentioned 0D.

If its 42, you're confused, and please listen to Grumpy.

honken

I have the ostrich and tunerpro rt 4.0 with the 7747 ecm(2732
Eprom)it works fine. the red line on the kable is pin number one which would be the notch. you need to hang over pin 1,2,3,4
the pin 5 is nr 1 on the ostrich (24 pin eprom).
pin 1 is 1 pin on 27128-27512 (28 pin eprom).
i have real time working without disable checksum.
didenth work with disable checksum (engine light flashing).
the checksum disable are in tools/preference/aldl/emulation.

mista350

it is definitely 42. I don't think I ever mentioned this in any of my emails, I just said that I was trying to use the 7747 ecu. My bad. I figured out how to set the mask Id to AA by adding an extra table in the .xdf at line 0004. Shortly after that I found the button in Tuner Pro rt that disables checksum for you.

However after all of this I still get the flashing Service light.

Honken, I am interested in how you hooked up your cable to the ecu. I installed craigs adapters with the computer right in front of me for reference so I think that I got it right. The red line on the cable is closest the middle of the ecu box towards the second smaller chip. Is this right? My Burn1 chips work flawlessly, so I would think the adapters and holder are installed properly.

I am curious about this overhang you speak of. I don't think it will apply to my situation since I have the 28 pin cable.

Thanks to all for the replies, I am hopefull that I will get this problem fixed.

MISTA,

honken

i have newer hade the g2 adaper only a 24 pin dip socket.
worked on pocket romulator 1 and tunerpro and my ostrich and
tunerpro in real time.


with a dip socket its like this.
red line is pin 1 .
if you have the 2732 eprom vid 24 pin you most hang over
pin 1,2,27,28 . on 2732 eprom
pin 1 on ostrich is pin 1 on the 28 pin eproms
pin 3 on ostrich is pin 1 on the 24 pin eproms


SORRY about the pin 3,4 and 5 (pin numbers wrong)

mista350

Hang it over huh? I am willing to try anything at this point. I think I understand how to hang it over. If it works I will let you know.

Mangus

Do you have a G2 installed in your ECM? If so, you do not need to do this.

mista350

Yes, I have a G2 adapter installed. I tried the Ostrich with the "hang it over" method with no aparent success. The Service light should not flash rapidly when every thing is OK right?
Another thing when I upload the bin and then try to verify, sometimes it will verify o.k. some times it will verify fail with codes (0) (-4) (-17) does this shed some light on anything?

honken

with the g2 adapter listen to grumpy and mangus not me.

The g2 adapter is a small chip board that convert it to work with 7747. does not need to hang over.

i HAVE NOT the g2 adapter ONLY a d1 24 pin dip socket
(a simply socket of plastic and pins)
i corrected me with the socket pins on my setup only.

The 24 pin dip socket looks like this:

Craig Moates

Certainly if you think the Ostrich is being problematic, let me know and I'll get it taken care of ASAP. I've got a few things I can throw at it, including large hammers if needed.

mista350

Craig,

You have been great. I shipped it back to you one time, you checked it out and sent it right back. It arrived way before i expected it to.

I'm sure it is something on my end. I am the only one in my neck of the woods messing with one of these so E-mail and TGO are my only method of trouble shooting.

The Burn1 and chips work great but I can't get the Ostrich to work.

I often repair CB's and car stereo amps, so i wouldn't think that my soldering job was bad, would the chips work and the ostrich not if I had a cold solder joint? Then there is the fact that it would not work on 2 7747's and 1 8063 ecu . I even bought a refurbed ecu from Advance autoparts and still "no worky" I soldered all of the original pins back in and took it back.

I'm sure the hardware is fine, it's something that I am missing.

Any other Ideas?

DM91RS

mista where in Ga are you located? I have an ostrich on order from Craig and might be of some help when I get it up and running.

DM

mista350

Valdosta, GA. I'm located in the south part of the state. When you get your hardware let me know we'll help each other.

DM91RS

Yep.....you're almost in Flordia.

What chips are you using?

mista350

AT29C256 chips from Craig's web site. They have worked great so far. Where are you located?

Anyone have any ideas on why my hardware won't work?

honken

Mista350
chip size is handled automatically by both pieces of software based on the size of bin loaded.

tunerpro rt 4,0 the latest ???
what xdf file do you have ???
something wrong the xdf file ???

DM91RS

I have one of those chips and a G2 from Craig. I havn't had time to try the chip yet.
East of Atlanta

DM91RS

He also said that he's tried Tunercat with the same results.

honken

I dident have the g2 adapter just a 24 dip socket
removed the orginal 2732 prom put the dip socket in
and connected the ostrich kable on the dip socket with
pin 3 on the ostrich as pin 1 on the ecm.
i hade this setup with the pocket romulator and sofware for some time.
tested tunercat it worked with no problem in real time.
but a ostrich for some month a go for my new engine 6395 ecm
and tested on the 7747 worked fine with rt
the pocket romulator worked to with rt
no problem with real time
cant test if it works with tunercat have the 6395 engine now

honken

the g2 its made for larger chips as AT29C256 and 27SF512.
with the ostrich you load the 4 k bin size not 32-64 k.

how does the start and end adress look when the g2 is for larger bins the ostrich now dose the g2 now that it is smaller bin

enter the start and end adress to 007000 -> 007FFF on a AT29C256 ???

binstack to larger chip ???
if stack do real time work???

DM91RS

I may be confusing matters since I have no experience with the ostrich yet but didn't Magnus answer this?

[/QUOTE]

chip size is handled automatically by both pieces of software based on the size of bin loaded.

Make siure you have the checksum disabled and that you have the emulation header plugged into the chip adapter correctly.

[/QUOTE]

I assume that you only have to disable checksum in Tunerpro RT and not when using Tunercat RT?

Mangus

The Ostrich has a known memory size. TunerPro (and Tunercat) both load the currently loaded bin to the upper portion of emulator memory.

If the Ostrich has 64KB of memory, and your bin is 4K, the bin gets loaded to offset $F000 in the emulator.

Yes, disabling checksums is a good thing with emulation. I believe TunerCat does this automatically within the TDF. TunerPro can be configured to do this too (see the Emulation tab in Preferences).

The checksum does not have to be disabled to simply run the car off of the emulator (if no changes are to be made). It sounds like not even that is working for you at the moment, however. It really could be an issue with the Ostrich.

M

Grumpy

Just as a sanity check, can you go back to a known chip that does work?.

When something takes this much time to figure out, it can sometimes mean the obvious has been overlooked. If the stock chip works, and close examination shows no problems, I'd suggest letting Craig, and his big hammers, have a go at it.

DM91RS

I received a "package" from Mr. Moates this afternoon. First thing that I want to say is that Craig is great to work with and will do his best to please you.

First....I plugged the ALDL1 into com port 1 and opened Winaldl. Cranked car and started displaying data. Works as advertised no problems. No serial adapter to usb BS. I will try it later on a faster 8625 that I'll be "attempting" to tune on a pickup.

Second....plugged ostrich in, opened Tunercat RT, connected to emulator, loaded bin, cranked car. Then changed idle (gotta start somewhere), it responded as ordered, saved bin, unplugged usb cable and drove car with zero problems. Awesome!!

These products work as claimed so far without a hitch! (Even for the binary challanged as myself!)

mista350

Yes, I think I will send the Ostrich and my ecu to Craig for testing.
I have the car running well on a modified bin loaded into a chip. (running too well, our local sheriff took it for a test drive and broke the speedometer. He never would confess how fast he was going but it was way more than 120 mph i'm sure)

I removed the factory chip from it's black plastic holder and plugged it in, it works, however the highly modded motor barely runs with it. Thanks to all who posted suggestions. I'll let you guys know how it turns out.

MISTA350

DM91RS

Glad to hear that it's running well.

What type engine and car are we talking about?

mista350

It is a 1988 IROC Camaro.
1998 Vortec 350 block and heads, honed, reringed, CompCams mild cam, Performer RPM intake, Holley 670 TBI, MSD ign. goodies, Headers, no cats, Flowmaster, 2025 stall converter, more to come when I get the chip right, needs paint and an interior.

I am trying to use the 7747 computer, instead of the cars 8063, because I read that it was more documented, and potentially easier to tune.

Just as a side note, I ohmed out each set of pins on the cable and each set checked good.

Street Lethal

iTrader: (16)

DM91RS

Sounds about like my setup as far as engine mod's except that I still have a 305 with a stock throttlebody.

What cable are you ohming out?

By the way I got the dreaded flashing engine light after hooking up the ostrich tonight. I load the bin, then it says sychronized but when I try to read the contents of the ostrich it says " the file in it is no longer valid". I reinstalled the chip and it works fine.

WTF?

I'll try it again when I have time.

mista350

I ohmed the 28 pin cable that connects the ostrich to the ecu. All pins checked out fine.

Flashing Service light sounds like the same problem that I am having.

File no longer valid sounds familiar. Down load the latest version of TunerPro Rt. Try using that. It seems to have more control over the .bin and its settings than Tunercat.

Which computer(ECU) are you using in the car?

P.M. me your phone number if you want and we could help each other out with these problems.

DM91RS

File no longer valid sounds familiar. Down load the latest version of TunerPro Rt. Try using that. It seems to have more control over the .bin and its settings than Tunercat.

Which computer(ECU) are you using in the car?



I have TP but havn't had time to look into using it yet.

Comp is 8746 as comes in a 91 RS

PM sent

Later DM

mista350

I'm curious to know if it worked normally when you tried it again.

Craig Moates

The issue of 'File no longer valid' when using TunerCat has been fixed. It was a firmware bug, and the new firmware is downloadable, just check the site. Hope this helps!

DM91RS

mista350...

No I have not at this time.


Craig...

Thanks I will try that.

DM91RS

Firmware updated.

Thanks Craig.

Hopefully will have time try it later today as I now have the def files for both my ecm 61 and a pcm E6.

mista350

Problem solved!

Turns out there was a minor glitch in my Ostrich. After Craig got his hands on it and found out the problem, he boxed me up a new one and sent it out to me.

I hooked it up, and it worked perfectly the first time I tried it.

Many thanks to Craig for all of the answered E-mails and Phone calls.

Thanks to Mark Mansur for responding to the many E-mails.

I would also like to thank everyone who responded to this post.

Let the Real Time Tuning Begin!!


MISTA350

DM91RS

So far so good here also........I guess the firmware update did the trick. The car has been running on the ostrich since Monday

SB406

I am having a VERY similiar problem with my serial autoprom. I can datalog with winaldl and burn chips with an older version of tunerproRT. However, when I try to emulate or data log with the newest version of tunerproRT, it's a no go. I didn't try to emulate up until this point because older versions of tunerproRT didn't support my 1227747 ecm for emulating/datalogging. Any time I try to emulate with tunerproRT, I get a fast flashing SES light. Datalogging with TunerproRT tells me that it's recording, but I get no readings from any sensors on the screen. To make things worse, Now I can't even burn a chip with the new version of TunerproRT without getting an error message. I tried eliminating the checksum with no success.

Any ideas?Mark?Craig? I'm a bit frustrated. Right now I put a known good chip back in the G2 adapter and it's running fine.
By the way, what's up with the 'xdf' file needed in the newest tunerproRT package? I just told it (tunerproRT) to derive one from an .ecu file that I had been successfully using.

I've got a 7747 ECM, G2 adapter, & serial autoprom

Mangus

The latest version should work fine with your 7747. Load the correct ADS file, make sure TunerPro is set up to use the correct COM port, and go.

Regarding chip burning... what are the symptoms? You say no error message, so does it report success? Verification?

SB406

With the old version of tunerproRT there was no problem with burning...it worked like a champ. However, with the new version of TunerproRT, I get an error message when trying to burn.

Tunerpro recognizes & connects to (or at least says it does) my autoprom, but whenever I try to command it to do something (burn a chip, read a chip, emulate, datalog) nothing happens. I tried changing the com port, but I don't think that's it because it worked fine before with the old tunerpro version.

I'm gonna try again tonight starting fresh. I'll remove the program from my laptop & reinstall. Maybe I'll try burning a chip with my desktop and the new tunerpro as well. I'll keep you posted. Any other suggestions are welcome.

-Thanks,
Mike

Mangus

Mike - you're not giving me much to work with here. Does it give you an error message or does nothing happen? Those are certainly two different things. If it gives you an error message, what error message does it give you? Can you go back to the older version of TunerPro and confirm that it still works correctly?

SB406

Mark,

I uninstalled tunerpro RT and removed all related files from my laptop. Then I reinstalled TunerproRT v400, checked the Com Port, & changed some com port settings as outlined on Craig's website to work better with slower laptops.

Low and behold, I can read & program chips! I can also Datalog with tunerproRT in passthrough mode. I'm totally excited about that.

However, I can still not emulate. Tunerpro connects to the autoprom and says it is emulating. When I say to upload current bin to emulator, tunerpro says it was a success and goes back to saying it's emulating. I tried disabling the checsum at location 008 and then at 004, both showing no change. Meanwhile, the SES light is still flashing fast showing no change. As soon as I drop a known good chip in, the SES light turns solid and I can run the engine perfectly.

While (unsuccessfully) trying to emulate I have NO chip in the zif socket, the ribbon cable is in properly (red wire to the inside where notch goes), and the switch on the autoprom is toward the serial cable. When I datalogged, the switch was in passthrough mode. I'm going to try it with the switch set to emulate tonight (I did all the previous stuff during lunch here at work and forgot to try datalogging with the switch in the other position).

Right now I'm thinking I have a bad ribbon cable. I wil hit it with the ohm meter when I get home. Any other suggestions are welcome.

By the way, is there any way to monitor my spark counts with tunerproRT's ALDL datalogging?

Thanks for all of your help,
Mike

Mangus

It could be a bad ribbon or even a bad emulation output stage, both of which you should contact Craig about.

Regarding logging additional items in the ALDL output, that depends on whether those items are being output by the ECM in the datastream. If they are, you can add them. See the help file and the apporpriate .ds file for your application.

M

SB406

Well, I checked out the ribbon cable and all connections are good. I'm going to contact Craig about sending my autoprom in for a checkup. As much as I hate to lose burning capability for a while , I really want this thing to emulate. Thanks for all your help.
-Mike