Diesel Place banner

Scrolling through logs

4207 Views 58 Replies 10 Participants Last post by  05LLY2500HD
I recently discovered that when you scroll through logged data and have a tune open at the same time it will highlight the cells "most likely" used.
Since a lot of tables are based on the GM.MAINRATE I was wondering if there is a way to display the FUELQ_MAIN_DMA instead. Other than that I really wish I had discovered that :cool2: feature a little sooner ... or read the scan tool tutorial :D
1 - 20 of 59 Posts
All you have to do is locate the calc pid link, open it with notepad, and change the parameters to whatever you would like the pid to be.
You can in fact add in other tables if you want, look for the text file called - "cal_link.txt" under \My Documents\EFILive\V7\User Configuration.
You can go add edit that all you want.

The linking from the scantool to the tuning tool save a lot of guess work that is for sure.

Cheers,
Ross
There is no such file in that folder.... could someone send me a copy?
yeah same here. I have cal_favorites, Cal_Setup, and Calc_pids, but no Cal_link.txt.

I got jipped !
oh n/m I found it.

C:\Program Files\EFILive\V7\Configuration It's in there!
So do you just replace all the gm.mainrate's with the FUELQ_MAIN_DMA? I saved a backup of the file just in case, but I just did a find, replace all with the fuelq pid. Hope that was right?


another question is there a way to set and lock the curser? Seems like I always end up moving it when I have it where I want it then go to switch windows it moves on me.
Thanks, found it! Have 3 user profiles, c:\EFILive and then in Program files another EFILive.....
yup same here that's normal.
Replaced all the gm.mainrate with gm.fuelq_main_dma Works just fine and the logs prove it to be correct.
Also replaced the gm.trqeng with gm.dmax_trq_dma. While doing this I noticed that in my cal_link.txt file the rows and columns for the tables B0742-0744 got mixed up.
is gm.trqeng screwed up too?
Kappa9012;1405213; said:
another question is there a way to set and lock the curser? Seems like I always end up moving it when I have it where I want it then go to switch windows it moves on me.
Press F2 to lock it, F2 to unlock it :)

Cheers,
Ross
I have been able to find the torque values from gm.dmax_trq_dma in the base torque table when logging data.
well i glad to see some others have done this, as i was afraid i was changing something i shouldn't. it was the only way i could get a more accurate log of the pilot timing.

Maybe Ross can explain why changing the cal_link.txt" under \My Documents\EFILive\V7\User Configuration does not work. but changing the C:\Program Files\EFILive\V7\Configuration does. and that we are not messing anything up.

can anyone verify that b0722 needs to be linked to gm.pilotrate. or gm.mainrate as A0104. I think they need to be the same. but i can't get anyone to respond in the other thread.


software can be so much fun:eek::
so changing that file makes the numbers used more accurate? on mine if i open the log file and look at it where i was at wot the tune file has 30mm3 at 190 mpa highlighted but the log is showing the pulse width i have in the chart which is 3200 at 100mm3 and 190 mpa.....
Gray Gmax;1406501; said:
well i glad to see some others have done this, as i was afraid i was changing something i shouldn't. it was the only way i could get a more accurate log of the pilot timing.

Maybe Ross can explain why changing the cal_link.txt" under \My Documents\EFILive\V7\User Configuration does not work. but changing the C:\Program Files\EFILive\V7\Configuration does. and that we are not messing anything up.

can anyone verify that b0722 needs to be linked to gm.pilotrate. or gm.mainrate as A0104. I think they need to be the same. but i can't get anyone to respond in the other thread.


software can be so much fun:eek::
It needs to be linked to gm.pilotrate ! A0104 needs to be corrected !
BullydogPowered;1408208; said:
so changing that file makes the numbers used more accurate? on mine if i open the log file and look at it where i was at wot the tune file has 30mm3 at 190 mpa highlighted but the log is showing the pulse width i have in the chart which is 3200 at 100mm3 and 190 mpa.....
First of all you need to make sure you are logging these PID's. Then, when scrolling through your logs you can see where in the table the data came from. The gm.mainrate is limited to 79.x mm³ so anything above that will not display correctly if you do not change your cal_link.txt file. Same for the torque.

Lennart
Lennart;1408274; said:
It needs to be linked to gm.pilotrate ! A0104 needs to be corrected !
Thanks for the response i have asked this question on a couple of threads and you are the first to respond, i have not run the dsp2 much for fear of it being wrong. it could make a pilot pulse width difference of 1500ms or more. and could very well be why i was seeing 10degs errors in my logs.
BullydogPowered;1408208; said:
so changing that file makes the numbers used more accurate? on mine if i open the log file and look at it where i was at wot the tune file has 30mm3 at 190 mpa highlighted but the log is showing the pulse width i have in the chart which is 3200 at 100mm3 and 190 mpa.....
Are you commanding 190Mpa? Make sure you have Metric units selected in both the scan tool and tuning side.
1 - 20 of 59 Posts
Top