DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
Can someone explain what this is/is for and how do you set it up to be useful. Thanx for any and all help.
__________________ A.S.E. Certified master mechanic Land Of The Free, Because Of The Brave http://www.cardomain.com/id/liquidh8 My rides: 81 Buick Century Wagon, 86 GN Turbo engine, 2004R, 3" DP, 3" Duals w/Magnaflows, CAI, Lots of porting, powdercoating, 18 lbs boost, more to come!! 79 Malibu Wagon-Vortec headed 350 w/tbi, 2004r, 2800 stall, n2o, 4 wheel discs, pro-touring suspension, killer PPI, J/L audio system 64 Chevelle Convertable SS-not done 302, w/muncie
Wifes Ride's 70 monte carlo-350, Taken apart awaiting resto
IT IS NICE
Connect/associate your VE table definition to MAP (X) and RPM (Y) of your ADS file.
Open your VE table editing box open and then run a datalog.
The cursor will highlight the cells as your logging.
Bring up the monitor screen and set one of them to view the BLM, observe the BLM value as the log plays and adjust the cells.
Just one of many possible uses.
Setting a threshold value for a constant is easier when you can watch the value. Constants bring up a window next to the constant editor box.
The only issue I have with it is that once you do an association to an item, your files must not be moved or the association is lost.
I was not able to find the location of the "path" statement that defines the location of the ADS reletive to the location of the XDF.
For now its best to put the files into the folders below TP so they stay reletive to each other.
Originally posted by JP86SS I was not able to find the location of the "path" statement that defines the location of the ADS reletive to the location of the XDF.
For now its best to put the files into the folders below TP so they stay reletive to each other.
It's in the XDF header under the ALDL Asooc. tab (select any item and hit Ctrl + F2). Paths are stored in relative form, so as long as you have XDF and ADS in the same path relation, they can live anywhere.
Fixed issue with Function object editor - X/Y combo box changes do not allow OK/Apply
I just found this on your site. I guess i should upgrade to V.4.13?
Im one of them people that just likes to keep what ive got. No changes. Diffrent is not good.
91GTABird, i would recommend getting 4.13, it works quite well & with no problems for me so far, but if for some reason you decide you don't like it, you can always reinstall you older version.
You must set the axis "lables" in the definition to either Integer or Floating point to allow it to work.
The datastream info is a number and has to be able to look up the value. If it is a "string" it can't work.
there's a good description in the help file.
(Magnus always reminds me of that )
QUOTE]If it is a "string" it can't work.
there's a good description in the help file.
(Magnus always reminds me of that )[/quote]
Note to anyone not familiar with the help file. It contains just about any answer to your Tunerpro questions. Im guilty myself of forgetting to refer to the help file first.
I don't understand, I have tried every combinataion of integer floating point etc.. and have read the help numerous times, and the x and y axis aldl link buttons STILL will not highlight so that I can click on them. Where are you guys going to get this to work? I am running the most current version. I am getting irritated because I'm sure it's right in front of my face but yet I've wasted the last 2 hours trying to figure it out.
ok, I've been playing with it. And I am not having very good luck. I've tried to get the main SA table and the VE1 table linked so I can datatrace. BTW, using the 7747 xdf and the _42 ads file. If I change the map to floating point, and the rpm x 100 to integer, or floating point, the datatrace on references the map, it doesn't correspond to the rpm. i.e., the map cells highlight correctly, but it is always in the 3200 rpm column. Anybody have any idea's, or maybe a snapshot or their settings?? I would be great if I could get this to work.
You have to use a log file and ADS file that is for your appliation. Are you doing that?
Yes I am. I managed to get the MAIN SA table to work, But I am still having a problem getting my VE as % (ve1) table to work. I also got the coolant comp table to work. For some reason the rpm is reading right in the ve1 table, but the map is. The x and y axis' are right too, I opened the toolbox just to make sure I was referencing the right axis.
The problem may in in the ADS file.
I don't see any other reason why it wouldn't work. Confirm the calculations on those items are not out of the numerical range indicated in the XDF.
Well, I tried 3 different ADS files, and tried every combo of floating point, integer, string that there was and to no avail. All I get is the yellow highlighting the cells in the 3200 rpm column, They move around to the right KPA rows, but they don't highlight the correct corrosponding column. I'm at the end of my rope, any other suggestions????
I don't have a log file for the 7747. Can you shoot one to me?
I'll take a look and see if I spot anything.
I got the cells to move around using an $8D log file and changing values in the datastream so they would numerically display as if they were the correct readings from a 7747 log.
Use the minitors to show you what values are being displayed for RPM and MAP.
If they are not moving or out of the numerical range of the item, then you'll need to find out what is doing that.
Could be the XDF scale factors or the ADS calculations.
Fixed 'em up
The row labels in the XDF were set to read as RPM x 100 so the values were much lower than the data that was coming in.
displayed values were still calculating as full numbers, that's what was throwin' you the curve.
yeha, 160 baud, lol. Thanx JP I owe you big time, I guess I need a fresh input on it. I totally missed that. Thanx!! What do ya think of those VE tables?? lol, big injecters and cam got me all screwy. The data tracing should help. Thanx again