lincomatic
Well-known member
- Joined
- Jun 10, 2011
- Messages
- 316
Coincidentally, I tried to fit in a V*A kW number today, but didn't like the way it would affect the readout.
Basically, to fit it into 16 characters, I have to do, for instance,
393.5V273.5A-75.
298.0V256.0A-3.2
285.5 -75.5 -.45
It's either no spaces, or no units. Note the varying decimal precision in the KW number.
which is better? I don't like either style, partly because the decimal point needs to move around in the kw value while it's fluctuating wildly. Maybe I'll try it today, anyway, to see how it looks.
In the KWh remaining value, I also implemented the variable decimal places, but it changes slowly, so it's not so noticeable.
BTW, I have considered using Tony's GIDs * 75 factor instead, but I like 281 to display as 22.5 rather than 21.1.
In the end, it doesn't really matter which factor you use, once you get used to it, and it's rather easy to change.
Here is the relevant line from the code:
#define KW_FACTOR 80.0F // 80 is from phil, tonywilliams prefers 75
Basically, to fit it into 16 characters, I have to do, for instance,
393.5V273.5A-75.
298.0V256.0A-3.2
285.5 -75.5 -.45
It's either no spaces, or no units. Note the varying decimal precision in the KW number.
which is better? I don't like either style, partly because the decimal point needs to move around in the kw value while it's fluctuating wildly. Maybe I'll try it today, anyway, to see how it looks.
In the KWh remaining value, I also implemented the variable decimal places, but it changes slowly, so it's not so noticeable.
BTW, I have considered using Tony's GIDs * 75 factor instead, but I like 281 to display as 22.5 rather than 21.1.
In the end, it doesn't really matter which factor you use, once you get used to it, and it's rather easy to change.
Here is the relevant line from the code:
#define KW_FACTOR 80.0F // 80 is from phil, tonywilliams prefers 75