PATCH: NLTS + Valet + KnockCEL
Dec 5, 2007, 11:53 AM
#917
Newbie
Join Date: Sep 2006
Location: Riverside CA
Posts: 56
Likes: 0
Received 0 Likes
on
0 Posts
Great, so how do I fix that? This also explains my confusion earlier. God damnit 
DISCLAIMER:
If you don't understand ANY of this DON'T FLASH, please ask questions in this thread! Also if you get ANY WEIRD/UNEXPECTED results then flash back to stock! If your car explodes don't blame me
Help???
DISCLAIMER:
If you don't understand ANY of this DON'T FLASH, please ask questions in this thread! Also if you get ANY WEIRD/UNEXPECTED results then flash back to stock! If your car explodes don't blame me
Help???
Open up your ROM’s, your current one and the modified one provided by tephra
Now we need to copy all of the tables from your current ROM over to tephra’s patched ROM, to do this highlight all the fields and copy them, then highlight all the fields on the tephra’s patched ROM and paste them there. Check your scaling too, if you or a tuner changed that make sure you change that on tephra’s patched ROM or that will be off as well. Do this for every single table in the entire ROM! If you do not check everything then you can miss something important and your car will either not run right or cause damage!
Make sure you copy over you Immobilizer! If you do not your car will not work!
Finally after you make all the changes (you should not have made any changes to your original ROM just copied everything from it to Tephra's modified ROM) save the file as whatever you want and flash it to your car. Start it up and enjoy NLTS!
Dec 5, 2007, 07:28 PM
#919
Thank you so much for helping me out.
Basically I get the "BIN" file and how I must use that as my map and copy everything. My bin files would not open properly because my Win Zip was messed up. I deleted it and re-downloaded it, it all works now. NOW I am concerned that my scaling is off. It is tuned on that, some of my maps (I have collected MANY from many different tuners and cars) have the 513 scale, some are blank. I am not sure if it SHOULD matter but my current map and tune has nothing in the injector scaling table as shown below. I don't get that.
Both are Injector Size Scaling, not sure why they are different or not having anything there would effect it.
Dec 8, 2007, 03:00 PM
#925
I CAN edit it or is that a Typo and you mean't CAN'T?
I really don't know why I cannot edit it and it is really bothering me.
Is it just screwed or can I fix it? What exactly is wrong?
I tried everything with it and it simply refuses to be edited. Will this cause problems with my tuning?
I really don't know why I cannot edit it and it is really bothering me.
Is it just screwed or can I fix it? What exactly is wrong?
I tried everything with it and it simply refuses to be edited. Will this cause problems with my tuning?
Dec 8, 2007, 06:13 PM
#928
the XML just provides pointers to the data in the .bin.
Technically a screwed XML won't affect a .bin unless you change something... However its better to get a working XML before you flash your car... that way you can check the values of things..
Technically a screwed XML won't affect a .bin unless you change something... However its better to get a working XML before you flash your car... that way you can check the values of things..
Dec 8, 2007, 06:18 PM
#929
If you have a 13 or 14 type ROM you cant adjust the injector scaling without adding something to the xml (a new def by a different name). I am pretty sure I sent that to you like A LONG TIME AGO when I sent the first map way back in the day....mebbe not.
Dec 9, 2007, 07:40 AM
#930
Hi Dave,
I have been looking at your NLTS/CEL/valet code to see how it will incorporate with realtime stuff, and it seems that they will go fine as long as we don't use the same bits of RAM (we were but I can move mine!)
It was interesting to see how you had jumped out to your routine and worked the CEL variable.
With your &HCC value for the knock cel flash with your shiftr x 4 timing loop, it looks like we have 12.75 cycles, rounding down to 12 this means the XOR will leave the CEL in the state it started, but it might leave it on if we used a value other than CC that when divided by &H10 would result in an odd number?
Looks like the routine is being called about 100 times a second, looks like the routine that eventually calls the appropriately named longsub_inj as Bez calls (which processes MUT and loads else) it is called from a compare match timer which is why our logging is throttled back.
I was wondering about speeding up logging/realtime mapping by calling it from a more frequently called loop, but it seems a lot of the loops are throttled in some way. Did you time any other of the loops?
Cheers,
John
Tried to PM, but your quota is full.
I have been looking at your NLTS/CEL/valet code to see how it will incorporate with realtime stuff, and it seems that they will go fine as long as we don't use the same bits of RAM (we were but I can move mine!)
It was interesting to see how you had jumped out to your routine and worked the CEL variable.
With your &HCC value for the knock cel flash with your shiftr x 4 timing loop, it looks like we have 12.75 cycles, rounding down to 12 this means the XOR will leave the CEL in the state it started, but it might leave it on if we used a value other than CC that when divided by &H10 would result in an odd number?
Looks like the routine is being called about 100 times a second, looks like the routine that eventually calls the appropriately named longsub_inj as Bez calls (which processes MUT and loads else) it is called from a compare match timer which is why our logging is throttled back.
I was wondering about speeding up logging/realtime mapping by calling it from a more frequently called loop, but it seems a lot of the loops are throttled in some way. Did you time any other of the loops?
Cheers,
John
Tried to PM, but your quota is full.
Last edited by jcsbanks; Dec 9, 2007 at 07:43 AM.