Skye1500CHEVY89

I cant get this equipment to work together
They will work on the solo.... but not at the same time....
I have the ostrich 2 and aldl1 to usb from Moates, 3 usb plugs on my hp mini laptop, serial to usb com ports configured. The Datalogger likes to do this thing where it will work sometimes on its own. And some times not at all. I must also and... I only have the g2 adapter placed in where the factory chip seats... may have something to do with it, but then why does emulating work like a charm??? Idk I need help... defeats the purpose of buying both if I can't figure out how to get both up and going all together. Trust me I have searched and searched. Ecu seems fine.

Six_Shooter

iTrader: (2)

Have you disabled checksum in the bin?

Skye1500CHEVY89

How does that relate to what I'm experiencing? I'm also still rough on these terms. If checksum disabled than that results in..?

Six_Shooter

iTrader: (2)

If you have not disabled checksum, the ECM will revert to LHM (Limp Home Mode), and not send data out of the datastream. This may be why you're able to use either the emulation or the datalogging, but not both, though the emulation should also fail, since like I said the ECM will be in LHM, without checksum disabled. You can sort of get around disabling checksum by turning emulation off (so real time changes/uploads don't happen) but upload the entire bin.

Disabling checksum disables the internal check...sum. Googling the term and/or checking the stickies at the top of the forum will have better explanations of what checksum is. But basically anytime a change is made, no matter how small, the checksum is changed, and if checksum is still enabled the expected result and the actual result will not match, and... boom... LHM.

Skye1500CHEVY89

Well I'm about to that point where I'm just going to just trash this tbi since no one around will help me. I know I'm ****ing stupid but come on... holley 670 cfm 2 brrl tbi for a 400hp engine..... I'm a dumb ****.

Six_Shooter

iTrader: (2)

Pretty sure I was trying to help you...

But if you're ready to give up after only a couple posts then I suggest you do so. Even after you get the emulator and datalogging to work together you'll have more questions. If Carb is that much easier then by all means...

Tuning an EFI system takes a bit of patience and plenty of reading and research.

JP86SS

iTrader: (1)

Could use a port sniffer (monitor) and see what the communication looks like on each port while you are trying to make it work.
Google "serial port monitor" for some free ones to try.
Do the comms individually for EMU and Logging, then compare when both are active.
Be certain they are setup for different ports, Also try with one of them being comm 1-4. (One that doesn't conflict with mouse/keyboards)
Adjust buffers for more fault tolerance (In windows properties)
Sometimes the lower ports work better than al virtual USB type ports.

Skye1500CHEVY89

Okay. I'm sorry sixshooter. I'm more referencing to the people that are supposed to be my family. I've been studying this with no help from anyone for over 6 months or so. Keep in mind I'm 23 years of age. Got my g.e.d. I'm understanding some of the stuff. But like I said I'm still trying make since of all this.... the guy from tbichips said my engine should make around 360-375hp. I'm trying to understand where to enough begin.... increased fuel pressure should then be around 33psi? 85 lb injectors at 21psi to 106.6lbs at 33psi? I'm using the 42 mask for 7747 5.9 xdf and 5.2 adx. Patched no egr. Patched spark and bpw. How do I correct for fuel increase. I've read about sync vs async. But how would I force sync fueling for idle? Or even force open loop? So many questions. My Internet searches aren't helping me to much.... I will try to figure out how to disable checksum. That would take it out of limp mode so that it isn't checking the system correct? Cause the more you change the Bin parameters, the more the checksum changes, therefore limp mode cause checksum doesn't match? Correct me if I'm off.....

Skye1500CHEVY89

Okay so I'm sure I disabled checksum. Changed mask id to AA? That is what i found to do online. Emulator says it verifies. But still no datalogging? Just keeps saying it's "connecting."

Skye1500CHEVY89

Is there anything I'd have to change in the baud rate settings between control panel and tunerpro for datalogging aldu1?

JP86SS

iTrader: (1)

USB comm port troubleshooting:
From the Ostrich 2 page:
Could go up to that or reduce somewhat if the problems still exist using 2 ports at once.
There is also a note about a socket booster if not using a MEMCAL ecu.
If yous does have a MEMCAL, it should be on the G2 adapter at all times.

If all your items seem good then you will need to look at the port communication with a monitoring software package.
The PC will send a request and the ECU will respond with a defined set of hex characters and then data items.
Watching that occur in real time will point you towards the answer of running both ports simultaneously as you can run them individually and see the stream of hex, then see what changes with both running.

Changing port settings blindly when both items already work individually is not targeting a solution, just making frustration.

Skye1500CHEVY89

Okay so I had the latency set at 16ms... supposed to be at 1ms. Restarting laptop to see if that was the whole deal. (:

Skye1500CHEVY89

No memcal. It's a 7747 ecu. I have attached a g2 and socketbooster.

Skye1500CHEVY89

Aaand my laptop over heated. It's only a poor Wil dual 1.6 hz processor. I gotta take it easy on er. Haha

Skye1500CHEVY89

Not changing blindly. Changing according to what I'm being told.

anesthes

iTrader: (12)

I used to have these problems too with Tunerpro.

I ended up using Tunercat for tuning and Datamaster for logging, and never had an issue. Unfortunately Datamaster is no longer sold.

-- Joe

Skye1500CHEVY89

Okay should I just unistal the drivers and do it over? I'm at a stand still. Datalog will not work.

Skye1500CHEVY89

How do I get ecu out of limp mode? I tried disabling checksum but no idea if it worked. If I change it in the correct place.

Six_Shooter

iTrader: (2)

Yes, Mask ID = AA is checksum disabled.

When you are using the emulator, have you actually uploaded the bin to the emulator using the blue up arrow?

Skye1500CHEVY89

Yes, I have checksum disabled if that is true.
Yes, I have bin uploaded to emulator.

Six_Shooter

iTrader: (2)

And datalogging works with the original PROM installed in the ECM?

Skye1500CHEVY89

I have not tried with the original prom, concerning original is for the 305 I had, and now have a 377ci stroker.

Six_Shooter

iTrader: (2)

The way your original post reads is that you had it working with the original PROM... since you said that each device would work independently of the other... How can you know the ALDU1 works by itself, if you haven't tested it with the original PROM? *confused*

You can simply check to see if the laptop will connect with the original PROM with the key on but engine off. You can see if values like the TPS change when you move the throttle or coolant temp changes, when you unplug and plug in the CLT sensor.

What is the CEL (Check Engine Light) doing when you try to use the Ostrich and you turn the key on? Does it flash once then stay on, or does it flash rapidly? Does the fuel pump prime for about 5 seconds then shut off, or does it simply turn on and stay on?

Skye1500CHEVY89

It worked with the bin file I put on with the 28 pin chip I purchased from Moates. I hope it's not a fault with the chip... the more I read things online the more bad scenories I'm coming across. I do have an extra ecu. I think it came with I 350 chip from a van... or something.

Skye1500CHEVY89

Okay yeah I took moates advice and put a new 350 bin file on my 28 pin chip and datalogger works again, with the chip, however it still doesn't work while trying to do both, uploading same file to emulator to datalog along with.

Six_Shooter

iTrader: (2)

What is the CEL doing when you are using the Ostrich?

Skye1500CHEVY89

I unsure of what the CEL is??

Skye1500CHEVY89

I just did a search and I didn't find much. Is there some place to find all these definitions?

Skye1500CHEVY89

I thought about it... CEL = Check Engine Light?... lol correct me if I'm waaaayyy off lol

Six_Shooter

iTrader: (2)

Yes, that's it.

Skye1500CHEVY89

Well at this point... I don't even want to turn my engine over because the rpms are way to low and the tune is sooooooooooo off. Sounds like a dump.

Six_Shooter

iTrader: (2)

You don't need to start the engine to see what's going on with the CEL, so what is the CEL doing when you are using the emulator?

Skye1500CHEVY89

Okay cool... I'm on my way with my dad right now to get his newly rebuilt driveshaft. So I'll check as soon as I get back.

Skye1500CHEVY89

No CEL, just a solid SES.

Skye1500CHEVY89

I'd hate to be a debby downer, but I'm starting to think that I'm never going to get this tuning stuff figured out. I don't know where to start.

Six_Shooter

iTrader: (2)

If it's just a solid CEL, with no flash at key on, that means that it's not reading the emulator (or corrupt bin) and you'll never get data when that happens.

Which way is the red strip on the emulator ribbon cable. Red stripe towards the smaller chip, or away from the smaller chip?

Skye1500CHEVY89

Hmm.. the red stripe is towards the calpak (smallchip)

Skye1500CHEVY89

Okay so I just switched the emulator to 28, 28, pin mode. I turned key on. And the SES light flashed once and then stayed solid.

Six_Shooter

iTrader: (2)

That's good, you should be able to get data now and run the vehicle on the emulator.

Skye1500CHEVY89

So is the SES the same as the CEL?

Six_Shooter

iTrader: (2)

Yes.

I prefer "CEL", because "SES" is close to "SRS", which is a very different thing.

Skye1500CHEVY89

Awe some so yes It did flash once with emulator attached. But I'm still where I can't get datalogger to connect while emulating.

Skye1500CHEVY89

Datalogger will connect with chip in.

Skye1500CHEVY89

I might just start tuning with separate operations.
Datalog, use calculators to make blm changes to ve, emulate the changes to run engine, burn chip with changes, datalog how chip runs engine. And so on and so furth.... man, seems like it's really defeating the purpose of having all this equipment.