It would be a great feature if could display min/max values in normal gauges.
I would like to be a be able to press a button and all of my gauges show the Min value, then press the button again and they all show the Max value, then press again and they all go back to Current value.
That would be really great to be able to quickly see important data at the end of a session or in between sessions, without having to hook up a laptop, or create a separate page just for min/max values.
We will consider the feasibility of this feature, taking into account our current memory limitations.
However, the âTextâ control already has the functionality to display the min/max values of ecu.X channels, so you can implement a simple logic:
Gauge with the current value â press the button â gauge is hidden, Text control with the min value is shown in the same place â press the button â min is hidden, max is shown â press the button â gauge with the current value is shown again, and so on.
Project tree:
And then you just assign function values to the visibility channels.
can you tell me the logic behind having this feature for all of the ecu channels and for none of the other channels (analog or canbus input for example?)
Most of the ecu.xy channels are unused, therefore memory/CPU is wasted on checking the min/max of unused channels. And if I want to have similiar functionality for other non ecu.xy channels, I need to use 2-3 functions per channel (?) which makes it very computationally expensive.
Thanks!
Yeah, I know I can do it that way, but it would be MUCH better for the driver if the values were displayed on the gauge. That would allow a much faster and easier âat a glanceâ check for any problems without actually having to read anything.
I understand the memory size constraints. How about this:
Instead of building the function into the controls. Can you just make the Min/Max channels available to use like normal channels?
That shouldnât take up any extra memory, because you wouldnât need to build any new functions or store any new data. It would just be a new way for us to use the data thatâs already there.
If we could select the Min/Max values, then I could just create 2 gauges, one using the Current and one using the Max, and show/hide them with a button function.
If we could just select the min/max values just like any other channel, that would solve the issue. And it would just be a new use for existing data, so it shouldnât take up any extra memory at all.
what i think driver should drive and if there is no alarm it means is all good .
I would say driver need rev counter gear display and shift light thatâs it..
you can set multistage alarms errors or warnings.
1 Like
This is for rally, not track racing. Canât just pull into the pits, the âpitâ could be an hour away in some cases. Driver needs more information to make a decision if the car can be limped home, or better to just stop and save the engine.
Alarms can be missed. And checking the peaks after the fact has additional driver uses too. Example is a driver can check their top speed from the last stage to gauge performance.
Even some dumb analog gauges from 40 years ago came with a âpeakâ button on them. Thereâs no good reason a modern digital gauge shouldnât be capable of the same thing.
It might sound obvious without knowing the whole system, but in fact, it is not as trivial as you think.
Whenever we make changes to the system, we always have to ensure backward compatibility so that we do not break any existing projects.
We will consider both your request and @LSL1337âs input, and we will try to find a solution that meets your requirements.
However, I cannot provide you with a timeline â there are many other tasks already in the queue, so it may take some time.
Until then, you will need to use the workaround I suggested earlier. Also, Greg mentioned the use of alarms â why are you not convinced to use alarms as he described?
I have a question about this solution..
It works fine for built in data like ecu.* or adu.* but how about analog / digital inputs ?
For example I have 2 wheel speed inputs, one is VR other one Hall type. VR is on front wheel for speedometer / odometer, I`d love to see vmax and vavg for that input after i have compleated the stage.
Same for oil / fuel pressure inputs.
I dont see option for Value source for these chanels.. Am I doing something wrong or I am missing some additional steps to atchieve this ?
Do you need Vmax for both sensors?
In general, the min/max functionality works only for ecu.* channels.
Not sure if I understand. You have a pressure sensors connected to the analog inputs and want to assign its value to ecu.* channels related to oil or fuel pressure?
If that is the case, there is no simple way to do this at the moment. We might consider adding such functionality in the future, but not in the near term.
There is a possible workaround if you have a free CAN2 port. You can connect it to CAN1 and send those values from CAN2 to CAN1, then override the ecu.* channels in the CANbus Input.
For vmax no, one is wheel driven signal and Hall is on driveshaft for traction control / slip percentage calculations.
is it possible to log min / max / avg for number channels ?
I have pressure sensors connected to adu and just want to log them + would be a nice feature if i could see also min / max / avg of these channels
You can do it in project tree. But without storing this value, so it did not survieve the ADU restart.
As mentioned earlier in this thread - we will consider in future to add such possibility, but due to other tasks it has to wait.
To get average values I recomend you to use Ecumaster Data Master - you can get everything what you want from collected logs there.
Avg speed you can calculate in project tree.