Q&A Forum
Post run brake functions.
I would like to see an option to set a max braking for the emergency brake. I use this emergency brake as a handy manual brake control to slow the roller manually but I don't need the full braking capacity. Might be good to also be able to choose the time the brake is applied.
I would really like to see a post run deceleration mode. So when logging is complete the brake slows the roller with a controlled declaration rate to a target rpm.
So I might finish run at 12000 rpm, the brake would then slow roller at - 2000 rpm/s and at say 6000 rpm the brake would release and coast. So 3s after completing the run I'm back at 6000 rpm and ready to do another run.
I believe sports devices has this function.
Regards
- 2teng
Post run brake functions.
I would like to see an option to set a max braking for the emergency brake. I use this emergency brake as a handy manual brake control to slow the roller manually but I don't need the full braking capacity. Might be good to also be able to choose the time the brake is applied.
I would really like to see a post run deceleration mode. So when logging is complete the brake slows the roller with a controlled declaration rate to a target rpm.
So I might finish run at 12000 rpm, the brake would then slow roller at - 2000 rpm/s and at say 6000 rpm the brake would release and coast. So 3s after completing the run I'm back at 6000 rpm and ready to do another run.
I believe sports devices has this function.
Regards
- 2teng
Good inputs. I will add more deceleration options.
Just thinking it may be beneficial to see the seconds to do a power sweep when setting up the rpm/sec and start/stop rpm, in the brake options.
Cheers
Good afternoon, could you add a "target" option in the graphs? For example, if I have a graph with turbo pressure, I can draw a target line or a margin to see the results faster by comparing the measurement and the target line. Thank you!!
Hi, This can be done today. Make a Math channel with a fixed number, for example like the attached picture if you want an AFR target. Then drag this channel over to the same graph as the AFR channel (if not by default).
I tried this, exactly like your picture and described, and I don't get anything on the graph. Version 3.3
Never mind. It just won't populate the target unless I do a new run. I was opening past CSV runs. It does work.
Would it be possible when doing an 'RPM Curve' run to still be able to manually define the auto start and auto stop rpm? The way it works now is that these values are greyed out and automatically set to the min and max rpm in the rpm curve defined in the brake control window. Especially the stop rpm is a bit tricky as I do the runs from high rpm downwards and this make the curve always look weird like with a pig rail at the lowest rpm. if I could just define the stop rpm before the end of the curve I think I would always produce a clean slice.
@admin any updates or progress with my suggestions above?
Thanks
Would it be possible to have a mode to use the software more like a steady state engine dyno? Controlling the hydraulic dyno I built to make a monotonic rpm trace is a bit tricky so I thought maybe one could add a feature when one can brake the engine manually at a certain rpm till it is stable then record for x seconds, then manually set the next rpm, record for another x seconds then complete the run a show the results as points where the x second data is averaged.
now I often get runs where there is a bit of a pig tail in the curves 😀
Hello,
I second Rub87, we definitely need a "mapping mode", for ECU mapping.
It will be usefull for ECU mapping, where we setup RPM and load to the desired point, press a "record" button, and proceed to the next point.
I see it implemented in the manual mode, where recording is selectable.
Or even better: it could be implemented like the latest sequencer, with a table and a "Record" and "Next RPM" buttons.
We fill the RPM table. The sequencer is started and it apply the first RPM. We can adjust the ECU settings, press "Record", and then "Next RPM" to go immediately to the next RPM in the table. It will be a lot faster when the table is filled with the same RPM values used by the ECU tables. At the end, it exit as usual, showing a interpolated curve.
Angelo
@angelo, it is a good idea to implement this as an extension to the Sequencer. So instead of time advancing the run, you press a button to advance to the next line in the Sequencer. Recording on/off is already implemented.
Hello Jostein,
It is exactly what I need. Using the sequencer is better. I can insert some points with low RPM/low load, to add some cooling down phase.
I see it like this: if Time cell is filled with 0, next step is validated by the button. If it is filled with a value, the sequencer apply the RPM for the defined value.
The "next" button should be also a keystroke. It will allow to drive this behavior only from the keyboard, key pad or the mini input device, which I can't remember the name.
Angelo
Hi,
And obviously, recording should be done only when RPM is stable enough.
Or it is done by a second button/keystroke, so we can choose manualy when we want to record or not. So if the checkbox is checked, it records automaticaly. If it is not, only pressing the button/keystroke can record.
Angelo
@angelo Yes that should be a definable time over which the data is averaged. that way channels that are noisy or have an oscillation will not impact the quality or accuracy/repeatability of the measurement. At work we generally average points 30 seconds and this only after min 120s stabilization time. that way results are trustworthy and repeatable.
off course 30s are probably for a home user a bit excessive but yes if recording time over which the data is averaged is user definable everyone can choose the time what he likes
the recorded data could then be viewed and plotted in a discontinuous way like here for example when mapping an engine at WOT w 500 rpm breakpoints.
1000rpm xx nm yy hp
1500rpm xx nm yy hp
2000rpm xx nm yy hp
Hello,
About recording automatically or manually, this behaviour could be extended to the manual mode. The keystroke for recoding will be common to both modes.
I plan to develop a device which will act as a keyboard, with a knob and some switches. Something very simple and efficient based on Teensy 4. It will act as a USB keyboard device. This is why the "Record" and "Next" functions in the sequencer should be a keystroke.
Angelo
I have a request, well it looks like I have two... lol
I like to run "dark mode on everything on a PC", this isn't the main request I have, but expanding the dark mode to envelope more of the GUI would be nice, instead of being limited to just the graph areas.
Anyway, my actual request is to be able to run dark mode in the software, but be able to print in light mode, to save on ink.
+1! Same request! Thanks
I have a request, well it looks like I have two... lol
I like to run "dark mode on everything on a PC", this isn't the main request I have, but expanding the dark mode to envelope more of the GUI would be nice, instead of being limited to just the graph areas.
Anyway, my actual request is to be able to run dark mode in the software, but be able to print in light mode, to save on ink.