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.
The more I use the tuner/logger the more I appreciate it. So I was running 4 80# injectors with a 160# fifth injector. Saturday I did quite a bit of hwy cruising so turned off the fifth injector and optimized fuel for better gas mileage. I left the house and had the idea, pulled into a parking lot and couple minutes later I was set.
Tonight I replaced the 160# fifth injector with an 80# fifth injector, turned up fuel pressure to 4 bar, quick calculations, made software change and tune was pretty much spot on. I am amazed how quickly I can tune the car with different setups.
Overall I am just thankful for this awesome tool! Thank You Rogue!
Did a bit of testing and it is a pretty useful tool with the Rogue Logger. By exporting out the Logger files to csv, you can combine with GoPro video. Here is a quick test video.
Bringing this old thread back from the dead - I CANNOT for the life of me get the TunerPro RT software and Rogue DME Logger to connect to my laptop. New PC with Windows 10, followed Josh's instructions to a T and running AEM adx file - it flashed DA: Connected/Data Error constantly. Zero help to actually log. Has anyone has similar connection issues with a solve?
Hey Mark_
Engine is running yes. Brand new PC Laptop and gave me options for COM 1 and COM 3 initially. {COM 1} and COM 3. Based on both the LR and Rogue instructions it said choose the highest numerical value which I did. Now when I go back to tools/preferences etc to set it up there are no options so I'm guessing COM 3 is the only one viable. I'm at a loss and have started from scratch twice with the download/setup.
What version of TunerProRT are you using? This is what I'm running and it works.
If you just recently downloaded TunerProRT then you probably have Version: 5.00.9159. I had problems once before with a newer version so I went back to the .8944 build. Can't say that was really the issue but I've stayed with the older version because I know it worked for me. I might try the new version because it supposedly fixes issues with docking and un-docking tabs.
Nope. Tried two previous versions, fresh download and install and rechecked parameters. Same issue. Switches between DA:connected/data error constantly.
Sigh....
Well that's got to be frustrating for sure. I downloaded/installed the current version, v500_9159 today. It works just the same for me.
Interesting that when I tested the COM port interface using TunerProRT I got a cable not found error but it still works when I start the car and log data.
Soon as you connect your USB cable to the DME Logger box (it doesn't have to be connected to your car) the FTDI chip inside negotiates with your PC to assign a virtual COM port. You can use the Windows Device Manager to watch that happen. For my laptop, there are no COM ports assigned until I connect the DME Logger box, then COM 5 pops up. Using different USB ports on your laptop might result in different COM port assignments also. It's easy to know for sure what COM port gets assigned by watching it happen real-time with Device Manager.
So I’ve been using the logger for some time now and I’d like to try the tuner out. How do you go about getting the base map on to the Ostrich? Is that even necessary? It looks like the chip has to come out to plug the ribbon cable in?
So I’ve been using the logger for some time now and I’d like to try the tuner out. How do you go about getting the base map on to the Ostrich? Is that even necessary? It looks like the chip has to come out to plug the ribbon cable in?
If you have the LR version of M-Tune these bin files might not be exactly what you need? If you have an EPROM programmer you should be able to copy what's in your M-Tune chip & use that as your starting point. A programmer will let you copy the chip contents and save it to a .bin file.
I've only played with tuning of the stock chip using Joshua's DIY tuner tools but I imagine it's the same or similar for M-Tune tuning. And yes, the chip board has to come out in order to plug in the Ostrich EPROM emulator.
Which M-Tune setup are you running? Post back some details if you get it working.
Big news - got it to connect finally after playing with the ProTuner settings and COM port adjustments a few billion times. Not getting the realtime WB02 gauge to read yet so another hurdle but hoping to be logging here shortly.
05-27-2013, 10:52 PM
