Hub those pdf's you listed are for the KRT race kit ecu's which have a totally different way to adjust fueling and ignition and other settings in the ECU, so i think you are chasing pink snowflakes again mate.
jwool, I was a guessing fool, but close to figuring out this GPS coding or better known as the 'timing retard eliminator.' It turns out to be a backuplan. The shop manual says, 'we take safety measures' and they say nothing else. So you have to read between the lines, go way back to 1983 when harley came out with the VOES, or variable (timing retard) operating electronic switch. You put the 2 and 2 together, you windup with generic processing procedures. The flip-flopped.
Ivan comes in with this unit way before the flash thing a few years back. Ivan still uses the same setup, different plugs from 1999 to 2014. I run my same ohm change so the flip flops >>> it's that generic. So now I read a balanced number can turn into a limp, flip from 60mhz to flipping to 50mhz in a limp situation. I'm reading chip cracking can deteriorate down the road. I can see the decimal move in the pc, your octal move on your mapping cells, I see the ascii moves in the truth tables the chip manu has to be handcuffed to, show me the octal number equaling 14.7 so I can accel from there. I type a middle octal number, not cut and paste, I move one number in a cell, it could be out of sync now. Why? Because I did not press the + or - in the cell to match the math. I used an offset cell number not equaling a c&p, or a +/- move so the math jells. Now that number becomes a pink snowflake, the logic gates did read C*B*A + C*B*A = Y, it now reads B*C*A + C*B*A = Y. It hits I don't know how many adders/multiplyers/decoders/the list is long in the processing of a bi number.
It now says both in the kit-ECU and these processing books I'm peeking into: say basically the same thing. 'We will take 'the best' combo, not the 'ideal' number, but it maths close enough to "satisfy' the truth tables." That is generic by the processing alone that is handcuffed to the T-Tables, be it octal or decimal.
My pink snowflake of a guess was when Smoke made a move it hit the 50mhz limp. It mixed a decimal with an octal, meaning, [Don would have to come forth], name his cell number as in using decimal/octal/ect., then if Smoke layered over that move = 50mhz is my best pinky flake. The fix was to match decimal with dec or octi with an octi cell and now 60mhz is back in play.
So here is the clash at the moment, as if you were Ivan, jwool, come in with a unit, try to describe what is going on motherboard wise? So your background is sitting at a keyboard, looking at a monitor, never sniffs flux all day creating a motherboard. To me it says, you are on the monitor side, not the motherboard side of experience, correct? You more work in the coding of it, not the building of that box's miniboard, know what parts to use to make it work the way it does, etc... We'd be on the same page.
You bought some software that is code-able to match the coding of some chip so microsoft and the chip communicate in the same bin, meaning? My reversengineering goes something like this: I do not know what your octal number reps as in the 760mmHg in octal, or 14.7 in decimal? I have a Pa gauge, an AFR meter, the tach and if I match Pa to AFR to Tach to TPS opening, the intersects on your map being 80Pa as the Pa of X the rpm being Y, I intersect the Pa to rpm, I think I can find your octal number as something being close to 14.7 = Z loads the bike's brakes dyno style to hit 14.7 on the AFR meter in a sustained [throttle] setting? See it like I do... In Theory that is?
That means, yes, I am chasing you down [like I chased Ivan's hack] to find the penultimate number and cell move from there. Unless your customers can pinpoint what octal number is 14.7. So, do you see me chasing your software because you wrote it or bought the software and cannot show me where the penultimate pink is? We should be on the same page I explain flip-flop, truth tables, decoders, adders, parallel adder/subtractor systems, ascii truth tables, etc. So did you build the box or had an EE design it with said parts on the mini-board?
So I pink flaked Ivan's move and I'll probably find your octal number soon too. Ivan could not answer my question(s) I solved on my own is why I've come this far. He was on the outside hacking the inside and now you are on the inside. It's a game of hunting down each degree of crank move is each flip of a flip I'm watching is now your moves, jwool. It's all about the breakdown of the (processing) movement, not the performance aspect of it that I'm chasing, jwool. Like you said, I'm looking for that one pink flake in an avalanche = The Penultimate Cell in 60mhz.
It's tuning with a calculator and a scalpel instead if a screwdriver and counting fingers and toes.
I'm not even close to learning the coding process of the forward slashes needed and the other basic moves one needs to memorize like the binary system. Now, I'm going to guess if I pull up the IAP map, that is the acceleration load to swing the fuel to the 13 AFR. I can run a Dobeck, move the pot and I can dip into the 10 AFR's on the fly: I run a blade up from the pot slit to a stable hand dial. I'd have to burn that map over and over to reach the perfect pot-wheel spin I get from the accel pot move. Not only am I low on chip cracking, I am back to the OE map on the fly of a toggle.
So with 4 maps to play with, I have a toggle to the two maps in the pc, I toggle the pc off, I now am back to the stock OE or toggle up the Dobeck. I burn, I 'best' the 4 individual maps, 'best' the ign curve to match as I change one map (only) but you left the others alone? You better equally burn the ign to match the fuel, or you let the tables take the 'bestshot' at that pinky flake of a number in that [one map] cell.
With the Dobeck, I can tune for the day. With a flash, I'd have to work all day to match the sun be setting, and my chip has yet to cool down. Do I still use pig or not? And where is Ivan to answer or give an educated guess/opinion? If I had a dyno in my backyard, I'd have the answer. Ivan has way too many hours to tell [if] a flash is THE move or a pc is THE smoothing agent = The better OA map.
Tormenting the motorcycling community one post at a time
IVAN! Oh, Ivan!
