When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I've been playing around with the emulation feature in TunerproRT and it's been doing some weird stuff...
- The fans got disabled. I was driving around and noticed the temperature hitting 220F. When I shut the car off and uploaded the bin to the Ostrich without the emulation turned on, the fans re-activated.
- The charcoal canister purge solenoid apparently got deactivated. Came home and there was fuel dripping out of the vent valve. Opened the gas cap and got a big "whoosh" out of it. I have to assume the canister purge got deactivated.
- Couple of times earlier, the check engine light would come on and the car would start running like crap, until I shut the engine off, uploaded the bin without emulation and then restarted the car.
Is there some setting or something that's off in TunerproRT that I need to change for the Ostrich II?
It doesn't do this without emulation activated. But the problem is without emulation, the editor windows close when you save your change, which is a PITA. I'd prefer to be able to use the emulation, but this funky behavior makes it prohibitive.
I've never seen/used that before and having it checked looks like it would do the trick or what I've done in the past is load a saved bin with "AA" in place of the mask ID which essentially disables the checksum.
So I realized I had to change the 08 to AA in the XDF file. So I tried that.
This time I was playing around with it in my driveway.
Still doing strange stuff with the fans... sometimes the fans don't come on at all (in which case I can see that they're not even being requested by the ECM). Another time, the high speed fan comes on but never turns off.
Never did this before with Tunercat RT. Just for some reason with Tunerpro RT.
I tired a different ECM to rule out the ECM, but no dice. Still does it.
Turns out you do need to change the 8D to AA. Not the way I did it above my previous post.
Haven't test driven the car yet, but hooking the laptop up to the Ostrich, I can generate a emulator vs RAM contents verification failure if I don't upload a the bin with AA before starting emulation.
It seems the order of operations necessary for emulation is...
1.) Open Tunerpro
2.) Open bin I want to start emulating with
3.) Change location 0x08 to AA and upload to Ostrich
4.) Activate emulation
When I follow those steps, I get successful verifications.
I'll have to try this out with the engine running and see if it works.
Turns out you do need to change the 8D to AA. Not the way I did it above my previous post.
Haven't test driven the car yet, but hooking the laptop up to the Ostrich, I can generate a emulator vs RAM contents verification failure if I don't upload a the bin with AA before starting emulation.
It seems the order of operations necessary for emulation is...
1.) Open Tunerpro
2.) Open bin I want to start emulating with
3.) Change location 0x08 to AA and upload to Ostrich
4.) Activate emulation
When I follow those steps, I get successful verifications.
I'll have to try this out with the engine running and see if it works.
Don't know if you're using a ZIF socket at the ECM for cable connection, but in a conversation some time ago with Moates, he recommended not using that form of connection. Seems vibration, improper cable length, connection properties of the ZIF, etc. may lead to random issues as you are seeing. If you aren't having them outside of emulation, then never mind.
Despite the recommendation, I always used a cable and no chip. At times, would experience no fans + other oddities but the car would run fine. Shut engine off and restart and/or reseat the cable in the ZIF and all OK. Can't explain it, just happened.
Don't know if you're using a ZIF socket at the ECM for cable connection, but in a conversation some time ago with Moates, he recommended not using that form of connection. Seems vibration, improper cable length, connection properties of the ZIF, etc. may lead to random issues as you are seeing. If you aren't having them outside of emulation, then never mind.
Despite the recommendation, I always used a cable and no chip. At times, would experience no fans + other oddities but the car would run fine. Shut engine off and restart and/or reseat the cable in the ZIF and all OK. Can't explain it, just happened.
Thanks Elky. No ZIF socket here. The Ostrich goes out to a ribbon cable that terminates to a plug that physically plugs into chip adapter.
It never did this kind of stuff w/o emulation. So I'm assuming it's related to the emulation and how I was performing it.
I haven't had a chance to take the car out yet to try out my above post. Maybe this weekend.
Something about Tunerpro and emulation. Not sure what else to do at this point.
Any other suggestions? Otherwise I guess I just don't do emulation.
What I'm also noticing also is that sometimes it takes two restarts to clear the error. On the first restart, sometimes the secondary fan comes on and stays on permanently (I have the secondary fan wired into the ECM like the Y-Bodies). So I'll have to shut down and restart again to behave normally.
The SES light doesn't come on either, so I never know if I have the problem occurring until I start seeing the coolant temperature climb.
Ok, I played around with it a little more today and I think I found a work around.
If I load the Ostrich with the bin from Tunercat prior to start up, I can then close down Tunercat, open Tunerpro and then start emulating to my hearts content without issues. In fact I don't even have to do the AA in the checksum. It works fine.
For some reason the issue only arises when I start the car initially with the Ostrich loaded from Tunerpro.
I'll have to try it again in a few days and see if I get the same results. But today at least, the issue appears to be resolved (knock on wood).