2byte to 1byte load mod
#1
2byte to 1byte load mod
Hey All,
Just thought I would post up a quick image of the next mod to be included. It's not very "cool" but should save some headaches:
So what I have done is reduced the 2byte variable and stuffed it inside a 1byte variable - why? 2 reasons:
1) Save 1byte of logging - speeding up logging is always good!
2) Stop the hi/low byte order mismatch error as seen above at the 1590.7 mark.
How:
Simply divide the real 2byte load by a factor (yes it will be customisable) and put it into 1byte which is logged like normal.
My factor is 1.2, which means we can log a load of upto 306 (255*1.2). A bigger factor equals higher load logging capability but also means less resolution.
The factor in the ROM needs to equal the factor in the EvoScan formula!
Cheers
D.
Just thought I would post up a quick image of the next mod to be included. It's not very "cool" but should save some headaches:
So what I have done is reduced the 2byte variable and stuffed it inside a 1byte variable - why? 2 reasons:
1) Save 1byte of logging - speeding up logging is always good!
2) Stop the hi/low byte order mismatch error as seen above at the 1590.7 mark.
How:
Simply divide the real 2byte load by a factor (yes it will be customisable) and put it into 1byte which is logged like normal.
My factor is 1.2, which means we can log a load of upto 306 (255*1.2). A bigger factor equals higher load logging capability but also means less resolution.
The factor in the ROM needs to equal the factor in the EvoScan formula!
Cheers
D.
#2
Evolved Member
iTrader: (17)
Join Date: Nov 2005
Location: NNJ
Posts: 2,544
Likes: 0
Received 0 Likes
on
0 Posts
Thats a very "cool" idea, lol. How much accuracy is lost with this method, assuming you want the ability to log up to 340 load?
I'll just be happy to get rid of the annoying errors of 2 byte load.
Can you do this with all 2 byte data?
I'll just be happy to get rid of the annoying errors of 2 byte load.
Can you do this with all 2 byte data?
#3
Basically to find out your "factor", you get your max load and divide it by 255.
ie 340 / 255 = 1.333333, now round it upto the closest .1, so 1.4
so 255*1.4 = 357, so you can log upto 357.
A factor of 1.4 would go in steps of 1.4, ie 0, 1.4, 2.8, 4.2..... so you loose a "little" accuracy, but I think its ok
Yes we could do this with any of the 2bytes, essentially this is how RPM works already, ie 255*31.25 = 7968, so 31.25 is the factor for MUT21.
ie 340 / 255 = 1.333333, now round it upto the closest .1, so 1.4
so 255*1.4 = 357, so you can log upto 357.
A factor of 1.4 would go in steps of 1.4, ie 0, 1.4, 2.8, 4.2..... so you loose a "little" accuracy, but I think its ok
Yes we could do this with any of the 2bytes, essentially this is how RPM works already, ie 255*31.25 = 7968, so 31.25 is the factor for MUT21.
Trending Topics
#9
Evolved Member
iTrader: (17)
Join Date: Nov 2005
Location: NNJ
Posts: 2,544
Likes: 0
Received 0 Likes
on
0 Posts
I think the gains are worth the slight loss in resolution. If you are off by a few points in load I don't think that really matters. So long as it is within 5% or so I would say that is still ok
#13
So basically the new formula in EvoScan would be:
- for "load 11bit4": 1.2x
- for "load MUT 2byte mod": 1.2*0.3125*x
Am I right? Cause if I am, it would explain why I see load values which seem kinda low compared to the boost I'm running...
Thx a lot for help on this point
- for "load 11bit4": 1.2x
- for "load MUT 2byte mod": 1.2*0.3125*x
Am I right? Cause if I am, it would explain why I see load values which seem kinda low compared to the boost I'm running...
Thx a lot for help on this point
#14
no - forget 2byte load or load 11bit4.
Code:
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.2*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="0.1" Notes="" Priority="1" Visible="False" />
#15
Evolved Member
iTrader: (3)
no - forget 2byte load or load 11bit4.
Code:
<DataListItem DataLog="Y" Color="" Display="Load 1Byte" LogReference="Load" RequestID="41" Eval="1.2*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="0.1" Notes="" Priority="1" Visible="False" />
and logged next to 2byte load, and nothing... Am I missing something???