Tuning 101 - Thread Merged with Injector Posts

HEUIGuy

New member
Joined
Oct 29, 2016
Messages
22
Reaction score
0
I guess that picking 40 degrees matches other commercial joints so if you just picked it arbitrarily (and since I don't know you) then I suppose I have to take your word. I didn't find any tell-tale signs of a calibration denotation or a "copyright" placed in the binary so it either started out stock or was "ff" 'd out in a hex editor.



I don't know what your latitude is and I don' t know what the weather is like where you are but in the dead of winter here with 15/40 oil, I need way more than 60 degrees to get a decent (perfect) start and warm-up. I had put up a video from last winter here with 200% nozzles at 10 degrees (but it was late morning and it was -6 overnight and below zero most nights) with a pickup that hadn't been started in a week. Some may remember that.

There are only two reasons to ever clamp that value at anything other than where it is stock: (1.) A person has no idea what they're doing when modifying a map and (2.) Is scared to change any of the mapping that has existed since 2001 because it works. Both reasons typically go together and could be classified as the one reason. Maybe where you're at you don't need to accommodate highly viscous oil so you'd never know the difference of stock vs. clamped.


I'm no expert. I do this as little as possible anymore since I realized that nobody is ever happy (the same reason I started doing this in 2008 because I wasn't happy) and that a few people out there are unscrupulous thieves who just want to copy/paste others' work. I'll occasionally write a calibration or two for someone in need who is experiencing issues with others' tuning just to lend a hand but I'm very picky about who gets it and with whom that person may be in cahoots.


Thanks for the input. I will be doing more testing this winter to get cold starts/idle on point. The timing maps are calculated.. could I do better? Yes.. that's why I'm here. To hopefully find faults in my calibrations and correct them. As you probably noticed, the SOI offset is essentially just a VCABO map. I haven't played with it much, but I will add some cold SOI and see where it goes.

I have a calculator (same one you have I imagine) as I am not smart enough to just know off the top of my head what rpm vs injection window and and degrees vs miliseconds at given rpm.


Most everyone around here runs 5w40 year round. I have found better starts with said oil vs 15w40 or 10w30. (Which I do not recommend)

The reason you don't see signs of copying another's file is, I didnt. Have I see files from other tuners? Yeah. I'm sure most that have been doing this for any time have. But I certainly respect the privacy and work those men and women have put into their work.

If you don't mind, I will pm you sometime I have a few questions you might be able to answer, if you feel so inclined.
 

cleatus12r

Member
Joined
Nov 20, 2014
Messages
163
Reaction score
3
Location
Reed Point, MT
Do what works for you. I can't tell you how to tune your vehicle.....if you like it, run it. As an example, nobody else with the injectors I have in one of the pickups will be able to run the tuning I have for them; the latency sucks and putting those calibrations on another vehicle with the "same size" injectors will cause it to be a twitchy, smoky pig.
 

HEUIGuy

New member
Joined
Oct 29, 2016
Messages
22
Reaction score
0
I 100% agree.. that is why I do this. I will certainly work outside my capped parameters and look for better results.
 

superpsd

Active member
Joined
Jun 10, 2014
Messages
1,928
Reaction score
3
Location
Missouri
My basic daily tune is nothing more than a PHP performance tune for stock sticks with a few maps revamped. Works for my setup. I refine it little by little as I go along. So far the SOI maps are much unchanged. I plan to fine tune the SOI after finishing a few things on my setup. Granted there is much less to adjust on a manual truck as you don't have to worry about transmission tuning.
 

superpsd

Active member
Joined
Jun 10, 2014
Messages
1,928
Reaction score
3
Location
Missouri
Not much if any does need changed as it's runs great as is. I have yet to crest making timing adjustments as I am still a novice. The most I tried so far was adding global timing.
 

Charles

Well-known member
Joined
May 18, 2011
Messages
2,729
Reaction score
47
I cap the SOI because I don't like the idea of my truck rodding the block because a sensor came unplugged or crapped out.

That and mechanical trucks making over 2000hp don't even have variable timing. So at the extreme, it's not even required to have timing ever change. Every 800+ hp 12v zipping down the road handing us our asses while towing just fine knows this.

My plan is to make a little module that plugs inline with the 42 pin connector that makes live, real-time measurements for pulsewidth, timing, icp and IPR duty cycle and outputs them to an RCA connector that I will run into my head unit as a "backup camera" input so I can have it on my screen live.

Basically an oscilloscope without all the bs.

Then I can see what the timing actually does on a cold start, and if and where it's actually moving when I make tuning changes to timing. I have little doubt that something is off. I just don't have enough care for the smoke to break out the scope thus far. If it were built into the head-unit, I could see myself flipping over to that view very often.

Who would like to see live... ACTUAL timing while they drove? Not some calculated bs value? I know I was pretty shocked the first time I drove around with a scope bouncing in the seat next to me reading timing! Holy hell did the maps have NOTHING to do with what was ACTUALLY happening!!!

The cap however...... spot on. What you set that value to is exactly where it gets capped.

If you want to know what you timing is, just set the cap to what you want and ask for lebbentybillion degrees elsewhere...

Then you'll know how your truck actually drives with XX degrees of timing.

If I had a dollar for every time someone told me they were running 9 degrees in a file that was more like 50+.

I would wager that anyone who hasn't watched CPS and High Side bank 1 on a scope while driving probably only thinks they know their timing. Unless someone else already calibrated their template to a scope reading for them.
 

cleatus12r

Member
Joined
Nov 20, 2014
Messages
163
Reaction score
3
Location
Reed Point, MT
I would wager that anyone who hasn't watched CPS and High Side bank 1 on a scope while driving probably only thinks they know their timing. Unless someone else already calibrated their template to a scope reading for them.

It's not that hard. I did it in late '05 back when the whole "blue CPS" wagon was rolling along. Back then it was what all the cool kids were doing and I couldn't handle not knowing if there was any difference between the two that were available. Then again, I wasn't tuning yet and happily rolling along in a popular calibration based on the Evolution 100HP setting.
 

cleatus12r

Member
Joined
Nov 20, 2014
Messages
163
Reaction score
3
Location
Reed Point, MT
Too late to edit......

It's not that hard. I did it in late '05 back when the whole "blue CPS" wagon was rolling along. Back then it was what all the cool kids were doing and I couldn't handle not knowing if there was any difference between the two that were available (edit: vs. an optical crankshaft sensor since taking a "timing" reference using two different cam sensors wouldn't give very useful data). Then again, I wasn't tuning yet and happily rolling along in a popular calibration based on the Evolution 100HP setting.
 

Charles

Well-known member
Joined
May 18, 2011
Messages
2,729
Reaction score
47
Too late to edit......

It's not that hard. I did it in late '05 back when the whole "blue CPS" wagon was rolling along. Back then it was what all the cool kids were doing and I couldn't handle not knowing if there was any difference between the two that were available (edit: vs. an optical crankshaft sensor since taking a "timing" reference using two different cam sensors wouldn't give very useful data). Then again, I wasn't tuning yet and happily rolling along in a popular calibration based on the Evolution 100HP setting.

Did you notice anything odd about the timing on the scope?
 

cleatus12r

Member
Joined
Nov 20, 2014
Messages
163
Reaction score
3
Location
Reed Point, MT
Back then, I wasn't interested in the actual "timing" of the calibration. I was running at an idle and just long enough to graph the optical pickup vs. the cam sensor high to low transition vs. the injection command. Obviously the injector command didn't change from one sensor to the next but there was a very slight change in cam position vs. crankshaft position and while I don't remember the actual values being that I did this 11+ years ago, the blue one was giving the PCM a later switching point for a given crankshaft position. I wasn't monitoring the high side either since the injectors are low-side switched; I didn't need to see all the flyback voltage from each injector on the high side.

Back to your question, the injector command on the scope was happening WAY before anything should have been happening based on the "windows" in the camshaft sprocket likely due to calculated injector latency. I never graphed FDCS at the same time although it only makes sense to assume that the commanded injection event sent to the IDM is based on the previous revolution's position data. However, seeing anything "odd" wouldn't have struck me as odd at the time since I wasn't really aiming to get actual timing values as I knew they weren't static (as you would like to see) and I wasn't interested in getting caught spending too much time with the dealership's optical pickup over the weekend. Mostly standard peak and hold appearance from what I remember but no time measurements were made so I have no actual timing numbers.
 
Last edited:

Charles

Well-known member
Joined
May 18, 2011
Messages
2,729
Reaction score
47
Back then, I wasn't interested in the actual "timing" of the calibration. I was running at an idle and just long enough to graph the optical pickup vs. the cam sensor high to low transition vs. the injection command. Obviously the injector command didn't change from one sensor to the next but there was a very slight change in cam position vs. crankshaft position and while I don't remember the actual values being that I did this 11+ years ago, the blue one was giving the PCM a later switching point for a given crankshaft position. I wasn't monitoring the high side either since the injectors are low-side switched; I didn't need to see all the flyback voltage from each injector on the high side.

Back to your question, the injector command on the scope was happening WAY before anything should have been happening based on the "windows" in the camshaft sprocket likely due to calculated injector latency. I never graphed FDCS at the same time although it only makes sense to assume that the commanded injection event sent to the IDM is based on the previous revolution's position data. However, seeing anything "odd" wouldn't have struck me as odd at the time since I wasn't really aiming to get actual timing values as I knew they weren't static (as you would like to see) and I wasn't interested in getting caught spending too much time with the dealership's optical pickup over the weekend. Mostly standard peak and hold appearance from what I remember but no time measurements were made so I have no actual timing numbers.


It's cool that you checked the CPS outputs vs actual mechanical crank movement but if you didn't ever actually watch outgoing timing while driving and comparing that to what you had asked for in your tuning software, why did you respond to my post like you had?

I'm not saying the maps you used then or now are wrong, or that you don't know what timing you're commanding, I'm just saying mine damn sure were wrong and I did NOT know what timing I was commanding even though before I scoped things I thought I did. Timing rose way, way faster than mapped, and the total values were way, way higher.

I haven't checked the recent templates I've gotten from Bill in the last few years but they seem a million times more accurate by ear.

But without ever scoping it I wouldn't have been able to calibrate my ear in the first place. And my gray truck with a carpet floor takes more timing for the same feel as the red truck with no carpet, lol.

As for the way the PCM handles real-time injection timing, the windows in the gear are offset ahead of the mechanical crank positions by a fixed number of degrees. Injection control is not handled on the previous rev, the fixed offset allows the event to be controlled real-time for the current event. I also struggled to figure out how you set advanced timing ahead of a trigger event. You offset the trigger. If you offset the trigger 90 degrees advance and you wanted 30 degrees of timing, you would wait 60 degrees worth of time after the trigger event was recorded.

John at Swamps showed me this on the full electronics mock up he had at home years and years ago where he had a cam gear spinning on an electric motor, pcm, idm and injectors all on a test board together, "running" while he could vary rpm with the electric motor and test actual live signalling and outputs. It was the first time I watched those signals on the scope.

It wasn't until I set my own scope in my seat that I was shocked at how F'ed the timing was compared to what I had expected.


On Edit:

On my DAC stuff, I did actually open a file with my old software and hacked up templates and again in the new software with new template and the maps I looked at looked very different! Exact same file. So something has definitely changed between what I used to use and what I'm using now in the template department.
 
Last edited:

truckpullin_75

New member
Joined
May 27, 2011
Messages
141
Reaction score
0
Location
Olney, IL
I have been following this thread and although I don't have much to add, I did see where Jim and others were having issues viewing a 224kb file when they have the 256kb definition or vice versa. I found on PHP's website Bill has provided a conversion tool that will switch the file from one to the other. I've ran into this before as my definitions are 256kb while my Hydra customers (I'm a PHP dealer) need 224kb files, or rather 225kb after encryption, to work without stalling after switching to my tweaked files from the included free tunes. Here is a direct link to the conversion utility download.

https://store.gopowerhungry.com/custom-diesel-form?id_attachment=11
 

cleatus12r

Member
Joined
Nov 20, 2014
Messages
163
Reaction score
3
Location
Reed Point, MT
I've ran into this before as my definitions are 256kb while my Hydra customers (I'm a PHP dealer) need 224kb files, or rather 225kb after encryption, to work without stalling after switching to my tweaked files from the included free tunes.

There's your problem. The Hydra uses the 0,1,8,9 256K (257 after PHP's encryption algorithm) file size. If you put the 8,1,0,9 224K TS Performance chip calibrations on a Hydra it's no wonder they don't work. The only reason the calibration size for those would be 225k is if someone were trying to use Sniper-encrypted calibrations.
 

truckpullin_75

New member
Joined
May 27, 2011
Messages
141
Reaction score
0
Location
Olney, IL
There's your problem. The Hydra uses the 0,1,8,9 256K (257 after PHP's encryption algorithm) file size. If you put the 8,1,0,9 224K TS Performance chip calibrations on a Hydra it's no wonder they don't work. The only reason the calibration size for those would be 225k is if someone were trying to use Sniper-encrypted calibrations.
You can run either on the Hydra, it will just stumble switching from one to the other if you use both. The tunes on PHP's server are actually 224kb/225kb format as are their emailed tunes.

The Hydra itself doesn't care which you use. I was just referring to those using Minotaur to look at the calibrations uploaded here that need the same hex code but in a different mdf format to match the definitions they own.
 

cleatus12r

Member
Joined
Nov 20, 2014
Messages
163
Reaction score
3
Location
Reed Point, MT
I need to eat crow. I was wrong and got the answer from Bill. The Hydraflash software internally takes care of the 224k-256k bank ordering and padding changes although the files actually progammed on the Hydra are always 256k. Carry on.
 
Last edited:

N2GN2

New member
Joined
Jul 13, 2012
Messages
158
Reaction score
0
Location
Montana
What MFD value have you found to give a smooth idle? I have some chop that isn't there when cold.
 

Countrycar

New member
Joined
Jul 27, 2013
Messages
248
Reaction score
0
Location
Texas
You can run either on the Hydra, it will just stumble switching from one to the other if you use both. The tunes on PHP's server are actually 224kb/225kb format as are their emailed tunes.

The Hydra itself doesn't care which you use. I was just referring to those using Minotaur to look at the calibrations uploaded here that need the same hex code but in a different mdf format to match the definitions they own.
I'm trying to understand this. I have a Hydra with GH tunes now. So for example, if I get 4 tunes from say DP tuner (different format) and burn them to the Hydra, I know my truck will stumble from the GH tune to the first DP tune, but once I'm in the DP tunes will the truck switch between the DP tunes themselves and continue to run/Switch in & out without interruption?
 
Top