Getting back to my chip tuning and was able to get the Ostrich 2.0 working with Tuner Pro RT. Have a good basic tune now, starting with the factory maps as the base. I'll do a full write up at some point, but did find some quirks in the xdf posted by Josh at Rogue Tuning, though they are great and he put a lot of effort into making them more human-readable than the xdf posted on the Tuner Pro site.
I am a little stumped by one thing. The Rogue xdf contains maps for 'idle target rpm' and 'idle rpm with a/c on' but neither of them seem to work. I can change the map entries to whatever and the idle rpm stays the same. The XDF has the address for the idle rpm map as x655 and the address for the idle rpm with a/c on map at x199. Does anyone know if those addresses are correct and/or if something else overrides it to keep the idle from moving? It 'seems' like those addresses are just wrong, but I'd be bit surprised that Josh got them both wrong and that no one ever flagged it... Anyone know? @Dave W. or @FTECH9 maybe?
Looking for DME BIN files
- Tom
- Site Admin
- Posts: 8933
- Joined: Fri Jun 25, 2021 2:04 pm
- Location: Silicon Valley, CA
- Has thanked: 932 times
- Been thanked: 3994 times
- Contact:
Hi Tom,
I am looking into this kind of thing for a solid-state ignition system I have in development. Unfortunately, I am in the same boat as you for the moment. I am still trying to adjust the ignition dwell times, the table values in the XDF files I have found online have had no effect. Lucky for me, Josh Cunningham was nice enough to give me some pointers as to where in memory this table is. However, if that falls through, my backup plan is to finish developing an Ostrich like engine emulation device that can read out and analyze the memory locations being accessed by the DME program in real-time. If it comes to that, I should be able to figure out where all the tables and configuration values are in memory. Unfortunately, the best case for this kind of device is months to more than a year before I would have anything tangible.
Did you by chance run across where the factory dwell tables are stored?
Joe
I am looking into this kind of thing for a solid-state ignition system I have in development. Unfortunately, I am in the same boat as you for the moment. I am still trying to adjust the ignition dwell times, the table values in the XDF files I have found online have had no effect. Lucky for me, Josh Cunningham was nice enough to give me some pointers as to where in memory this table is. However, if that falls through, my backup plan is to finish developing an Ostrich like engine emulation device that can read out and analyze the memory locations being accessed by the DME program in real-time. If it comes to that, I should be able to figure out where all the tables and configuration values are in memory. Unfortunately, the best case for this kind of device is months to more than a year before I would have anything tangible.
Did you by chance run across where the factory dwell tables are stored?
Joe
- Tom
- Site Admin
- Posts: 8933
- Joined: Fri Jun 25, 2021 2:04 pm
- Location: Silicon Valley, CA
- Has thanked: 932 times
- Been thanked: 3994 times
- Contact:
The XDF file posted on the Tuner Pro xdf site purport to have dwell maps, but I have not made any effort to confirm they work.
- Tom
- Site Admin
- Posts: 8933
- Joined: Fri Jun 25, 2021 2:04 pm
- Location: Silicon Valley, CA
- Has thanked: 932 times
- Been thanked: 3994 times
- Contact:
I plan to do a more complete guide at some point, but in the meantime wanted to share something I finally figured out about TunerPro and Josh's xdf files. @whalenlg and I have discussed this in the past, and I was always a bit perplexed why he got different TunerPro behavior than I did.
Josh did a great job setting up the xdf file so that is makes sense to human eyeballs. In the WOT map, for example, the entries are shown as AFR number -- 14.7, etc. -- so when you edit the maps you can put in numbers that make sense to you, rather than trying to calculate the actual value that gets burned in the map. The problem I was having is that I couldn't get values lower than 12 to stick. I'd save 11 or even 10, and it would come back as 12 or so. Inspecting the XDF file, I saw that Josh entered 12 as the minimum value. The weird thing was @whalenlg was using the same xdf with the same minimum, but was able to save lower numbers. Fast forward to this afternoon, and I finally found the toggle where you can turn the limits on and off (or change the limits). Here are screen shots showing how/where to turn off or change the limits in case helpful to any frustrated would-be tuner down the road.
Start by opening the map that has the limit you want to change or turn off. Then go here....
And it pulls up this box where you can make the change.
Josh did a great job setting up the xdf file so that is makes sense to human eyeballs. In the WOT map, for example, the entries are shown as AFR number -- 14.7, etc. -- so when you edit the maps you can put in numbers that make sense to you, rather than trying to calculate the actual value that gets burned in the map. The problem I was having is that I couldn't get values lower than 12 to stick. I'd save 11 or even 10, and it would come back as 12 or so. Inspecting the XDF file, I saw that Josh entered 12 as the minimum value. The weird thing was @whalenlg was using the same xdf with the same minimum, but was able to save lower numbers. Fast forward to this afternoon, and I finally found the toggle where you can turn the limits on and off (or change the limits). Here are screen shots showing how/where to turn off or change the limits in case helpful to any frustrated would-be tuner down the road.
Start by opening the map that has the limit you want to change or turn off. Then go here....
And it pulls up this box where you can make the change.
- Tom
- Site Admin
- Posts: 8933
- Joined: Fri Jun 25, 2021 2:04 pm
- Location: Silicon Valley, CA
- Has thanked: 932 times
- Been thanked: 3994 times
- Contact:
Also played around with the idle rpm more today and still don't have control. I noticed in the FocusOBD logger that the ISV showed 93% open at idle, so it dawned on me that maybe the DME was just not able to increase the rpm, regardless of map value, if the ISV had no more to give. So I opened up the idle adjustment screw on the TB to give the ISV more range to regulate the RPM. It still did not allow me to change the idle speed via TunerPro, but I noticed a weird thing. In the FocusOBD logger, the more I closed off the idle screw on the TB, the ISV %open would actually decrease, which is counter-intuitive since you'd sure think the ISV would need to open up more to maintain the same RPM as I reduced the amount of air supplied by the TB idle screw. @FTECH9 -- does that sound right to you? Any chance that logger entry should read %close, rather than %open?
I found the dwell maps in the 24 pin bin at 03F3. There's more detailed info back on page 3 of this thread.FTECH9 wrote: Fri May 23, 2025 4:46 pm Hi Tom,
I am looking into this kind of thing for a solid-state ignition system I have in development. Unfortunately, I am in the same boat as you for the moment. I am still trying to adjust the ignition dwell times, the table values in the XDF files I have found online have had no effect. Lucky for me, Josh Cunningham was nice enough to give me some pointers as to where in memory this table is. However, if that falls through, my backup plan is to finish developing an Ostrich like engine emulation device that can read out and analyze the memory locations being accessed by the DME program in real-time. If it comes to that, I should be able to figure out where all the tables and configuration values are in memory. Unfortunately, the best case for this kind of device is months to more than a year before I would have anything tangible.
Did you by chance run across where the factory dwell tables are stored?
Joe
- Tom
- Site Admin
- Posts: 8933
- Joined: Fri Jun 25, 2021 2:04 pm
- Location: Silicon Valley, CA
- Has thanked: 932 times
- Been thanked: 3994 times
- Contact:
Dave W. wrote: Sun May 25, 2025 10:11 amI found the dwell maps in the 24 pin bin at 03F3. There's more detailed info back on page 3 of this thread.FTECH9 wrote: Fri May 23, 2025 4:46 pm Hi Tom,
I am looking into this kind of thing for a solid-state ignition system I have in development. Unfortunately, I am in the same boat as you for the moment. I am still trying to adjust the ignition dwell times, the table values in the XDF files I have found online have had no effect. Lucky for me, Josh Cunningham was nice enough to give me some pointers as to where in memory this table is. However, if that falls through, my backup plan is to finish developing an Ostrich like engine emulation device that can read out and analyze the memory locations being accessed by the DME program in real-time. If it comes to that, I should be able to figure out where all the tables and configuration values are in memory. Unfortunately, the best case for this kind of device is months to more than a year before I would have anything tangible.
Did you by chance run across where the factory dwell tables are stored?
Joe
Any luck finding the idle rpm location and/or getting x0655 to work? I'm wondering if that's the correct address and if it is over-ridden somewhere?
I looked into it many years ago. Like you, I tried to adjust the idle speed and nothing changed, so I forgot about it until now. I haven't felt the need to change idle speed, so it hasn't been a priority.Tom wrote: Sun May 25, 2025 10:30 amDave W. wrote: Sun May 25, 2025 10:11 amI found the dwell maps in the 24 pin bin at 03F3. There's more detailed info back on page 3 of this thread.FTECH9 wrote: Fri May 23, 2025 4:46 pm Hi Tom,
I am looking into this kind of thing for a solid-state ignition system I have in development. Unfortunately, I am in the same boat as you for the moment. I am still trying to adjust the ignition dwell times, the table values in the XDF files I have found online have had no effect. Lucky for me, Josh Cunningham was nice enough to give me some pointers as to where in memory this table is. However, if that falls through, my backup plan is to finish developing an Ostrich like engine emulation device that can read out and analyze the memory locations being accessed by the DME program in real-time. If it comes to that, I should be able to figure out where all the tables and configuration values are in memory. Unfortunately, the best case for this kind of device is months to more than a year before I would have anything tangible.
Did you by chance run across where the factory dwell tables are stored?
Joe
Any luck finding the idle rpm location and/or getting x0655 to work? I'm wondering if that's the correct address and if it is over-ridden somewhere?
Here's 2 other parameters that might be useful:
'ISV offset with A/C on' Located at X019A. Stock value is h18. I found there's a little too much vibration at idle with the A/C on with a urethane filled trans mount, so I raised it to h25.
'Idle Return Delay' Located at X019F. Stock value is h04. A higher number will slow down the rate of change for the ISV. Too high and the idle might stick at a high rpm. Too low and the ISV might overshoot the target rpm and oscillate. M-tune uses 6. I have a lightweight flywheel so I set this to 9.
Last edited by Dave W. on Sun May 25, 2025 11:54 am, edited 1 time in total.
- Tom
- Site Admin
- Posts: 8933
- Joined: Fri Jun 25, 2021 2:04 pm
- Location: Silicon Valley, CA
- Has thanked: 932 times
- Been thanked: 3994 times
- Contact:
Hard to believe Josh included those addresses for idle if it didn't work for him. I wonder if something is over-riding it and/or if @DannoXYZ might have any insight to share?Dave W. wrote: Sun May 25, 2025 11:21 amI looked into it many years ago. Like you, I tried to adjust the idle speed and nothing changed, so I forgot about it until now. I haven't felt the need to change idle speed, so it hasn't been a priority.Tom wrote: Sun May 25, 2025 10:30 amDave W. wrote: Sun May 25, 2025 10:11 am
I found the dwell maps in the 24 pin bin at 03F3. There's more detailed info back on page 3 of this thread.
Any luck finding the idle rpm location and/or getting x0655 to work? I'm wondering if that's the correct address and if it is over-ridden somewhere?
- Tom
- Site Admin
- Posts: 8933
- Joined: Fri Jun 25, 2021 2:04 pm
- Location: Silicon Valley, CA
- Has thanked: 932 times
- Been thanked: 3994 times
- Contact:
I've decided to leave the Ostrich in the DME for a while to make sure my latest tune does ok as the weather heats up. So far so good, and I do still plan to post a how-to guide here in due course. So that I can button things up with the Ostrich installed, I got an old DME cover and fixed it up to fit the ftech DME and accommodate the Ostrich's ribbon cable. You can tell how old it is from the factory drain holes in the corners. For the ribbon cable, I started by just cutting a notch, but was worried it would eventually abrade the insulation, so made a little rubber grommet on the 3D printer to protect it. Then, of course, I had to powder coat the cover red for an extra 5 horsepower.
Original notch before the grommet
With custom grommet/ribbon protector
Original notch before the grommet
With custom grommet/ribbon protector
