After a month or so of looking at the GUI, getting used a few differences I like it. I had a big issue though that I ran out of patience figure out. I just finished up the new motor the last weekend and got it timed and all that. I figured I'd try v5 out and let me car warm up etc with it connected and then do a datalog while I adjust the idle timing, etc. I could not for the life of me get v5 to connect to the ALDL or my Ostrich. I tried v4 out that I've registered and it works fine....?? Is there anything different in that area between v4 and v5?

No differences in connectivity.

Did you set the correct ports and cable types?

It won't connect to the Ostrich? Are you sure you don't have V4 open at the same time as V5? The only thing that could cause it, provided the Ostrich is connected, is if something else is accessing the Ostrich (like V4).

If V4 connects to the Ostrich, V5 will too. The code in that regard is nearly identical.

ALDL is a different story - make sure you're importing your working ADS into V5. If your vehicle requires an extensive connection scheme, then you may need to tweak the resulting imported ADX.

I appreciate the responses. My seutp is rather simple, a serial to usb connection for the Ostrich 2 and a serial to usb for my ALDL. I'll have to double check the ADS/XDF setup in v5. Knowing me I missed something.

The Ostirch 2 is a USB device. Why would you have a serial to USB converter?

My mistake. I have 3 usb's coming out of the ashtray. ALDL serial to USB, LC-1 WB02 serial to USB and Ostrich 2 USB. you're right Mangus. Sorry, I'll fade behind the curtain now

No one is asking you to fade. Did you get it working?

I got it to connect this morning. What I forgot to do was pick the correct .ads file.

Thank you Mangus and others. Great product. I intend on registering v5 soon. I didn't see this covered but are the .bin files backward compatible? Meaning, if I edit/save in v5 are they able to be edited saved in v4?

.bin files, yes. .xdf files, no, and well .ads and .adx are different file types.

Ok here's a quick question, what do I select in the Link Mode drop down box in the DA Association tab to setup the datatracing with my VE Tables? Three options are - Link, Explicit, and Data Type/Units Match.

Explicit works on all of my definitions. Just recheck the units and ranges are correct to match.
[Speculation]
The link data type I believe is to create default associations between items so you don't need to "Explicitly" set ranges to match each other.
Thinking that if an item is setup as Coolant temp TYPE with Celcius as the units, this can associate with the Coolant Temp item in an ADX file.
The view can either be in Deg C or Deg F without making a definition for each range that matches, just set the units to what you want to see. I'd have to recheck the help file to confirm that is the intension of the data type and units selections.

In earlier TunerPro versions, explicitly linking the two files (and the fact that I wasn't handling things well in code) caused a lot of confusion. Further, changing the linked definition or having the relative pathing incorrect on the end-user's computer caused the explicit link to fail, thereby rendering data tracing non-functional. This was a source of a lot of "support" emails for me and posts for those of you in these forums kind enough to provide support.

In V5, the definition author can set each XDF item and each ADX item to have a "stock" data type and unit. If the XDF and ADX is created with these values set for each object in the definition, then TunerPro can match the data up automatically. This alleviates the need to explicitly link an XDF file to an ADX file, and makes it easier for the end-users of the definitions to enjoy data tracing.

In the future, these links will also become more important if/when I implement auto-tuning. Before you get your hopes up too high, such a feature is a ways down the road, and is very complex and difficult to do correctly. So don't hold your collective breath quite yet.

Hey there
Love V5 great pruduct. I have to ? thought. One is concerning Data tracing for playback of log files this would be helpfull because it is hard to look at the computer while driving.
The second question involves super AUJP. I am running this bin and have my wide band O2 display as data that uses a extra pin out on the ecm. I can see this Data in the AIC step window of my Datamaster software. This I set up a while ago with the great help from JP86SS contributions.
Iwas hoping for a quick primere on seting this up as a dashbourd display in V5.
Thanks Dave

Data tracing while playing back a log does work.

If you have it working while connected to the ECM, it will work while playing back a log file.

If you can see the WB in DM then this was already done in your bin file:
Setting up word 37 in the "Values" list in the ADX definition is all that is needed.

Create a new item (just below the KA IAC steps is best place)
Enter description etc and then your scale and offset values.

Once that is done you can edit the Dashboard definition and select the WB output for display.
Set the ranges on AFR so the gauge looks best in the "Values" section and do the gauge display parameters for location and "look" within the dash definition.

Your right as soon I opened the dashboard for super AUJP there was the WB meter.
Still having touble though with data tracing on play back of logs. When I am playing a log file and press the data trace button on lets say the spark table nothing happans accept for a error comes up in a little box in the lower left corner of the table.
Thanks Dave

v5 has taken me a little time to figure out but I'm getting there.

Can anyone tell me how to keep the dashboard from going back to default setting when I close the TunerPro?

Yeah, that one took me a bit to figure out too...

YOu need to edit the ADX directly.

In the tool bar, you will find under Aquisition, "EDIT ADX", click on that, go to the dash board, and change the variable on the gauge you want to change to the new variable, save ADX, and everything should be good.

In the next build, I'll add the "scannerpro" behavior or prompting you to save the ADX when you've edited the dash via the context menu.

Thanks guys, that fixed me right up.

Mark, you have outdid yourself again. Great work!!!!

I datalogged today in V5 and I'm having a couple of problems. 1st problem is my WB AFR is not reading out anything in v5. It just stays stuck on a default setting and doesn't move. My Lm-1 is programmed for 0-5v output to ecm pin A3 with 0v=7.35 and 5v=22.39. I selected WB option for LC-1 in flag tables. Second problem is my playback recording stops playing every few seconds or so and then resumes. Anyone else have this issue?

The WB is not a V5 issue, confirm the setup in the bin per my PM.
Be sure bit for input pin A3 select is on and use the "raw" input instead of any selected sensor. Should indicate something if there is actually output from the LM-1.

If you are not seeing error counts go up at the point where the data stops I would suspect the laptop.
I had some issues with stopping/starting when playing logs but I believe it was my laptop using shared memory for the video. Try turning off monitor screen (closing it) or other background screens when playing and see if it helps. Lots of things to update on the screen and background processes may be causing the hiccups.
Might be some BIOS settings to help with that as well. Careful in there though.
Stuttering on my laptop occurred but was fine when played back on my desktop.
That's how I narrowed it down.

Also keep in mind that stuttering during record will also show up as stuttering/pauses during playback.

Thanks for the advice guys. I'll test it again and report back. Awesome work on the V5 though. Love it!

Does it have built-in support for the NVSRAM module? Both ALDL monitoring and on-the-fly calibration updates.

I've got it working

The setup was pretty easy really, Check your mail for some notes on what I found today.
Still will need some tweaks but is functional just using MonteCarSlow's interface. I have already done some automation of it so it uploads with just a hotkey so its very promising. Just need to stop logging when hotkey is pressed then go back to logging. No disconnect or "Release" of hardware needed, just the connect/disconnect logging button is used.

I'll post the setup here so everyone can use it.
------------------------------
To use with TP V5.5197,
Create a Custom tool
Name = NVSRAM Tools
Tool Path = C:\Tcl\Bin\Wish.exe (Substitute your actual path if needed)
Cmd Parameters = C:\ blah \ blah\ RTP4-Tool.Tcl (This file's location)
Create a keyboard shortcut (What ever you like)
--------------------------------
With the AP I do both and can also use two different ports.
My bench uses AP on USB Comm4 with Comm1 doing ALDL on serial cable.
It's really getting fun now, need to change my motor so I can start over with a new challenging tune

Thanks Magnus for this functionality!

Sure. Even better would be to do it "natively" by making use of the new plug-in interfaces that I will be sending to a few people who have asked for it.

Oh, so that must be why I can't find a way to use the "plug in..." selection in TPV5, and couldn't find any other way of making a plug in.

im very new to this tuning thing so sorry for stupid questions or not understanding alot of the lingo. im just wondering if there's a way to get the dashboard to give me a gauge of timing advance? and if so can someone walk me through step by step?

i know im new to this but i sure am enjoying this program!! thanks mangus for what it means coming from me

right click on any one of the six values of the dashboard, it then gives you the option to choose from a list. Spark advance has 2 options, top dead center and ref. pulse.

all i get from the list besides the normal ones is bpw and bpc. am i missing something?

Any chance of creating a dashboard how to? Those dashboards are awesome, yet I have no clue where to start.

If you look in the Tuner Pro Message board, under the Scanner Pro forum, there is a Dashboard how to in there, that mostly also relates to Tuner Pro V5, TP RT V5 just has some more features, like colour customization.

Anyone running TP5 under Linux/Wine? I know some in the past ran V4 under Wine. I tried running TP5 and the program would not start. Anyone know how to make it work?

im hoping to find the hex locations and values to insert the sa and pw values then im datalogging on a 8747 ecm with tunerpro...

Well guys here's my first shot at a dashboard. I worked on this for hours. I still dont know how in the hell the one guy fits so many values on his dash as I had trouble getting these to fit. Hopefully he'll send me the source code so I can check it out

LMK what you think. Should be pretty much everything I'll need for tuning except my wideband. As soon as I get my LC-1 up and running I plan to feed it into RT and make a place on the dash for it as well.

Looks good. :thumbup:

The next dash won't take so long, it's the first one that always takes the longest.

yes it does... my first one took a good 90 minutes to look somewhat decent, then i came up with this in roughly 10 minutes...

I love the dash layout! Is their a share point for them?

depends what you mean by that... luckily mark made them easily to plow through in notepad and you can basically copy/paste into another ADX and all you would have to do is choose what vales/flags go into what guages.

I guess I was thinking they were independed files due to the "imported dash" line under v5 dash. I'm just making the switch from v4 to v5 so I'm behind the curve.

How do you select the bit when adding bitmasks to the adx?

Hi Guys,
great work with this new version on Tuner Pro! Looks great but I just wish I could use it!

I'm getting the flashing ALDL Error (Green/Red) in the connection status. I see that some others had problems with this as well. I tried the fix of adding a pause but I'm either doing it wrong (very possible!) or its just not working?

I've added a "listen for silence". I added this In Mode 1 ALDL Dump Request Macro is that right?? I've then tired various different values in Silence Lenth and Timeout. And also tried it as the first command and the last. Nothing seemed to change at all.

The data that it does collect is good data so it is connecting sometimes. I'm using the ALDU1 setup. I've been using V4 for a couple of years no with no problems at all. I do notice that I get some error counts while not charging the laptop but it was liveable.

If anyone could explain in real basic terms what I have to do I would be forever grateful!

Try adjusting the latency in the APU1 driver (in device manager, select the port and selet "Advanced." Moates recommends 1ms, but try experimenting with values between 1 and 16.

-M

Taken me a while to get back to this. I've tried everything suggested now but I'm still cursed with a flashing connection/aldl error box. I'm stumped!

What files are you working with exactly?

From the sig he's using V4 with the 730.
The problem I had originally was the command macro was repeating too quickly causing the flashing as you described. May be the same issue.
Magnus instructed me to put a delay in the connection macro so the first set of data can be read in before the next set starts.

Open the ADX editor (Data stream editor, not the XDF)
Click to drop down the "Commands" item.
Select an item in that list (turn it blue)

• Click "Add New Item" at the bottom...

A small box will appear asking what type of item you want.

• Select "Listen for Silence" (a new item will appear in the list)
• Rename it to "Pause" (or leave it as is, really doesn't matter)
• Type something in the "Unique ID" box "DelayMacro" or something else.
• Leave "Silence Length" at zero, Make "Timeout (ms) = 5

Now you will need to save the definition file.

• Re-open the ADX editor, go to the "Commands" again.
• Locate the connection or "Dump Request" macro and highlight it.
• On the right side of the dialog box, Click "Add New"
• Select the "Pause" item you just created in the previous step.
• Highlight the item and then use the "Move Up" to make it the first item in the macro. (Can also be the last but I like it on top)
• Save and close.

Try logging with the 5 ms setting, Increase it if data still does not come out clean. I did not notice any decrease in data rate until I hit 50 ms or more IIRC. I also had no increase by reducing the value so there is plenty of room to experiment.
Try to find the best value for your setup.
I have one laptop that works at 2 ms very well and on my other it won't run on anything smaller than 5.
Must be some USB hardware drivers and timing issues.
HTH

Done exactly as you said but still no joy -

starting to think its this notebook though (EeePC 701SD) as for some odd reason I can't connect to the ALDL at all in V4 or V5 without BOTH the ALDL and Ostrich plugged into the USB ports. Without the Ostrich being plugged in I get a confirmed cable OK in setup, but connection stays at "Connecting". As soon as the Ostrich is plugged in the connection turns blue and data starts coming down.

Done exactly as you said but still no joy -

starting to think its this notebook though (EeePC 701SD) as for some odd reason I can't connect to the ALDL at all in V4 or V5 without BOTH the ALDL and Ostrich plugged into the USB ports. Without the Ostrich being plugged in I get a confirmed cable OK in setup, but connection stays at "Connecting". As soon as the Ostrich is plugged in the connection turns blue and data starts coming down.

That would be true, The Ostrich IS the running program.
Can't get datastream without a running program in the ECM.