I'm trying to datalog with TunerproRT and when I press the record button I get an "error creating log file". Since I have no log files saved, and can't select one to append to, so how do I create a new log file to get started?

John Stricker

 

press the "select log file for rec/play" when the next window opens, type in the name of your new file to log to.

I use:
(350 ALDL 2008 0807 348 ARAP 87 red 23 22 43 idle 55.adl)
engine, year, date, time, bin, car, injector constant, injector, fuel pressure, action taken (idle, cruise 55, WOT).

By using a date/time stamp you get an automatic rev number, this is very helpful when doing multiple test runs. Never have to remember not to overwrite a good log.

Then after the log is stored, it is converted to a .cvs file (it is named again), then converted again to a .xls file. The .xls (MS Excel or Open Office) is able to be graphed and this really shows how things are trending. Open Office.org is Free.

 

Thank you for the response.

I did get Tunerpro to say that it's recording but when I do a playback or export to csv, it all comes back as "0". (Well, not ALL, some things like BLM IIRC show 128 static, but other than a couple of issues like that all "0"'s)

The dasboard and live views work fine, and steady. The data is coming in the ALDL link, it's just not saving it to the file, even though it saves the sessions with new filenames.

Thoughts? Do I need to select what's logged? If so, I don't see anything that would allow me to do that.

I have an appointment in a couple of weeks with the dyno so I'd like to have it logging by then if there's any way possible.

Thanks in advance.

John Stricker

 

Go to TPRT tools "aldl/data logging" push/right click on setup, right click on edit aldl data stream def.
look and see if anything shows up (should be a plus sign in front of aldl sensor data), should be able to see each output and when high lighted.

If not, you need a good ads file.

 

Yes, when I go to setup and edit data stream, I can look at the outputs when I expand the tree.

Keep in mind that I have a good data stream because I can watch it, in real time, while I'm messing with the car, what I can't do is record and play it back or export it to a file.

I thought that it was recording all zero's. I don't think that's true, although sometimes it will. What it seems to be doing is when the record button is activated, it "freezes" the datastream and records whatever value is there at the moment it's pressed.

I'm also having issues with the Ostrich emulator. TunerproRT finds it OK, and it accepts the bins, but the car simply doesn't run the same on the emulator as it does when a chip is programmed. That pretty much makes it useless for any real tuning, unless I can figure that out. I did make the changes instructed on Moates webpage as far as latency and that kind of thing, but it didn't seem to make any difference. I suspect the issues might be one of timing to the ECM from the emulator, but I'm not sure how to correct it. Has anyone run into this, that the car doesn't run the same on the emulator as it does on a chip burned with the same .bin?

John Stricker

 

At the aldl setup screen in Tuner Pro RT, first you have to push "connect to ecm" button at the lower left side. Then at the bottom of the Tuner Pro main screen should be "emulating or not emulating", "hardware found", "ready or not ready", and "aldl connected or not connected".

For a good record it should be "emulating", "hardware found", "ready", and "aldl connected"

Other then this I am out of ideas.

I use a Prominator but do not program "on the fly", but like the 8 bins so I can change a bin "on the fly". That way if it is a dud then I can switch back to one that works. Or when trying a high low middle compare, it is easy to just switch it. Like the Eye Doctor this are that, A or B.

 

Thanks again for the help.

When I have the emulator attached, my screen reads just as you say it should. Emulating, Ostrich found, ready, and connected. I can watch the live readouts just fine, and when I hit the record button it shows that it's recording frames, but when I playback or export to a cvs, it shows either all "0"'s in the variables or it freezes it and repeats at the point I press the record button.

I'm stumped (so far), but I'd really like to get it figured out.

Thanks for the help, I'll just keep plugging away, and I've sent an email to Mark Mansur to see if he has any ideas.

John Stricker

 

As a follow up, I emailed Mark about my difficulties logging. He responded very quickly (within a few minutes, actually) and explained that on SOME computers with SOME systems they don't like to log multiple sessions in one file. He advised that I try to log each session as it's own file and see how that worked.

It worked like a champ. Now I'm happily logging away, as long as I give each session a new file name, which is no big deal.

We also discussed the problems I was having with the Ostrich emulator and he took a look at my .xdf file. It seems (and I must have missed this) that you need to disable checksum to make the emulators work properly, so he made a quick modification to my .xdf file that would allow me to do that and now it, too, works like it's supposed to.

I can't say enough for the help I got here (even though it didn't work completely, it made me look at some things I was doing wrong) and from Mark.

Thanks to all. The car is going on the dyno Sunday and we'll see what we've got and where we're at. I'd like to drive it, but the local authorities seem to take issue with a Northstar'd Fiero with race exhausts doing acceleration runs. I don't really know why, they just don't seem to like it much.

John Stricker