modifying tehra patch
Thread Starter
Joined: Nov 2008
Posts: 171
Likes: 0
From: Forever with BIG
2 byte load can be added to any rom, but there is no point to it with 1 byte around (which you will have to have a tephra rom for).
The fortunate part about everyone wanting to do something is that it is for a reason, and provides a wide testing base of people with different methods and issues. This is how bugs get worked out. If you were to pay someone to write the patches for you and you alone.... guess who would be the tester?
Plain and simple is following the heard when you can't make waves of your own. You don't have to use any of the mods from the tephra rom that you don't want to. They can all be functionally disabled, and will not cause any interference with the normal operation of your rom.
Both of these points say 2 things:
1) You will not be addding anything you don't want. If you don't want it, hide it from view or functionally disable it. It will be like it never happened.
2) The path of least resistance is generally that of the masses. This is also generally (not always) the path that is most likely to be right.
The silly part about your 9 times out of 10 comment is that it is true. However 9.99 times out of 10 these answers are already here on the forum, well documented and tested. For anything that doesn't fit that bill, it is probably not a simple answer, and isn't documented as such for a reason. That's not to say that asking questions will never get us anywhere or that we are near "project completion", but there is a bit of a line in the sand between what is an "easy" (aka already answered) question and what will stimulate more growth in a specific area or the project overall.
As an open source community, the way to "pay your way" is to help the project, not monetarily fund a very small part of it (you probably couldn't pay enough for this stuff anyway, and that is not a comment on your pay grade, but on the value that is being provided for free).
The fortunate part about everyone wanting to do something is that it is for a reason, and provides a wide testing base of people with different methods and issues. This is how bugs get worked out. If you were to pay someone to write the patches for you and you alone.... guess who would be the tester?
Plain and simple is following the heard when you can't make waves of your own. You don't have to use any of the mods from the tephra rom that you don't want to. They can all be functionally disabled, and will not cause any interference with the normal operation of your rom.
Both of these points say 2 things:
1) You will not be addding anything you don't want. If you don't want it, hide it from view or functionally disable it. It will be like it never happened.
2) The path of least resistance is generally that of the masses. This is also generally (not always) the path that is most likely to be right.
The silly part about your 9 times out of 10 comment is that it is true. However 9.99 times out of 10 these answers are already here on the forum, well documented and tested. For anything that doesn't fit that bill, it is probably not a simple answer, and isn't documented as such for a reason. That's not to say that asking questions will never get us anywhere or that we are near "project completion", but there is a bit of a line in the sand between what is an "easy" (aka already answered) question and what will stimulate more growth in a specific area or the project overall.
As an open source community, the way to "pay your way" is to help the project, not monetarily fund a very small part of it (you probably couldn't pay enough for this stuff anyway, and that is not a comment on your pay grade, but on the value that is being provided for free).
fair comments, so for the less then expert how does one go about ensuring the 2byte - 1 byte eval matches that in evoscan and is set up correctly?
Registered User
Joined: Nov 2007
Posts: 1,507
Likes: 2
From: Trinidad
shoot me a PM and i can get it done for you.
the 2byte to 1 byte does not need any calibration once your below 300 load. if not you need to change the scaling in ecuflash from 1.2 to 1.3.
in order to log 1 byte you need to make sure its in evoscan. see thread: Tephra's Mod V5.10
its all there.
the 2byte to 1 byte does not need any calibration once your below 300 load. if not you need to change the scaling in ecuflash from 1.2 to 1.3.
in order to log 1 byte you need to make sure its in evoscan. see thread: Tephra's Mod V5.10
its all there.
Thread Starter
Joined: Nov 2008
Posts: 171
Likes: 0
From: Forever with BIG
hi, thanks for your help regarding the above mods. if i can ask i have a couple of questions regarding installing the complete patch.
on the first page of the thread regarding v5.10 under "changes" https://www.evolutionm.net/forums/ec...d-v5-10-a.html tephra says he has included 2 byte load yet if i add this patch to my definition file when opening his modified .hex file there is no mut table, is this correct?
also he says he has included 2byte to 1 byte load yet when i open the .hex file in ecuflash there is no category anywhere that states 1 byte load is this also correct? im assuming it is yet others say if you go over 300 load you must change this factor from 1.2 - 1.3 in both ecuflash and evoscan, yet like i say there is noting in ecuflash that mentions this let alone being able to change it. i realise i only need 1 or the other but looking at this i wont have any way of logging either load value
attached is my 90550001xml with my mut table removed and his patch applied does this look correct and will i be able to log either 2 byte or 1 byte load with it????
on the first page of the thread regarding v5.10 under "changes" https://www.evolutionm.net/forums/ec...d-v5-10-a.html tephra says he has included 2 byte load yet if i add this patch to my definition file when opening his modified .hex file there is no mut table, is this correct?
also he says he has included 2byte to 1 byte load yet when i open the .hex file in ecuflash there is no category anywhere that states 1 byte load is this also correct? im assuming it is yet others say if you go over 300 load you must change this factor from 1.2 - 1.3 in both ecuflash and evoscan, yet like i say there is noting in ecuflash that mentions this let alone being able to change it. i realise i only need 1 or the other but looking at this i wont have any way of logging either load value
attached is my 90550001xml with my mut table removed and his patch applied does this look correct and will i be able to log either 2 byte or 1 byte load with it????
Thread
Thread Starter
Forum
Replies
Last Post