Q&A Forum
Tuners,
I get a lot of requests for new software features. I will update you guys on the things I am working on, and you can add wishes here. Obviously I will not be able to do all of them, but it is good to see which features many people want.
Bug fixes will normally have the highest priority.
Here are the priorities at the moment (highest pri on top):
- Support for high to low RPM brake sweeps, plus static brake percentage starting point (Done in 3.01.77)
- OBD2 support for engine RPM. This will enable automatic gear ratio calculation and slip can be monitored. It will support Bluetooth and USB ELM327 adapters. Bluetooth is very practical here!
- Use of YourDyno's second RPM input as engine RPM input. The input needs be a 0-5V square wave. So either another YourDyno RPM sensor or a digital signal from the ECU or from an adapter of some sort (for example this one)
- Improvements to the print functionality, with ability to set size of individual windows plus visual improvements (Done in 3.01.77)
- Graph trimming functionality, to remove parts of the curve (typically at the beginning or end of the curve) (Done in 3.01.77)
- Group runs into sessions, with gear ratio, brake setup, etc stored per session (done in 3.01.78)
- Ability to synchronize both Y-axes so the range is the same (done in 3.01.78)
- Option to show Speed instead of RPM
- Option to show KW instead of HP
- Other horsepower correction factor formulas
Cheers,
Jostein
Unit Selection
? , . / . Also, I to . some point it would be great. Thanks for all the hard work you have put into this product Jostein, I don't think I would have built my own hub dyno if I had not come across your control packageCheers
Graham
I'm still hoping for this one day. My preference is to use HP, ftlb, degC and km/h but its not possible with the current options.
As a workaround I have a math channel that calcs 'Wheel FtLb' from the Nm result so my graph now displays HP and FtLb, but the splash screen and results table at the bottom of the graph screen still shows HP and Nm unfortunately.
@rub87 that is a good input and a useful feature.
I will put it on the software todo list. There are a few things there already that are being worked on, so it will not make it to the top immediately, but it will make it fairly high on the priority list.
Hi Jostein,
I already wrote this in an email somewhere beginning summer but I am unsure if it ever reached you.
So I thought it could be nice to have a few basic items like a button and slider in the GUI that can manipulate a (dummy) variable. This variable could then be used in a math formula and/or assigned to an output or CAN out. For example I control my cooling fan and exhaust extraction fan via CAN tied to a formula based on speed and when being in some cars with roll cages it handy to only need to use one interface (remote desktop to the dyno laptop) instead of using misc remotes or wired switches or whatever to control fans or whatever.
driving simulator sounds awesome. normally in the industry we use coast down info which is usually given in a time between certain speeds when coasting down for example 125-115 115-105 down to zero etc which is normally averaged from a number of coast downs on a level road in both directions. from these times and the vehicle mass one then calculates a polynomial 2nd order fit. So one gets 3 coefficients that gives force at the wheel: F(v) = A+B*v+C*v² [N]
I have spreadsheet to calculate times to coefficients and vicaversa. doing things this way is way easier then having to guess frontal area an drag coefficient etc
Drop me a line if you want it.
Correct, a real life coast down on a horizontal road is an easy way to get the frontal area and Cd, as indeed most folks don't have these numbers for their cars.
@admin yes exactly - Manual Torque control brake mode will indeed be nice. The idea was also only to use it in steady state mode without MOI compensation.
Also a safety turn off point could be nice. Just to make sure engine stall will not happen
driving simulator sounds awesome. normally in the industry we use coast down info which is usually given in a time between certain speeds when coasting down for example 125-115 115-105 down to zero etc which is normally averaged from a number of coast downs on a level road in both directions. from these times and the vehicle mass one then calculates a polynomial 2nd order fit. So one gets 3 coefficients that gives force at the wheel: F(v) = A+B*v+C*v² [N]
I have spreadsheet to calculate times to coefficients and vicaversa. doing things this way is way easier then having to guess frontal area an drag coefficient etc
Drop me a line if you want it.
Ok yes thats a whole other use case. Im not used to having ecus where nothing an be adjusted =) so you just want to run 1500 rpm (governed by the PID in the ecu) and ask a certain power with the brake, just like a generator doing 50Hz and varying load. Now it makes much more sense 👍
@madswp, the torque control brake mode is a good feature. A fairly easy way to implement it is to disregard the MOI component, meaning it only works accurately for steady state. To include the MOI * acceleration, a time delay will be introduced in the regulation, which is never good for fast, accurate regulation.
I have a driving simulator made some time ago but there is a bit of work left on it. If there is enough interest then I can resurrect it. It uses the car's speed, coefficient of drag, frontal area and road inclination to calculate the torque, and regulates the brake to that torque.
@bigboostgarage In Germany there are many ppl that own maha or another dynos that works like shit showing fake measurement.. that's real world. anyway if you want to see drivetraing looses you can see it in "Measured Power" which shown the drivetrain loses and you can see if something is wrong or something is changed.
You are comparing apples with bananas now.
"I do not think that could be usefull, for calibration one normally always regulates the rpm and changes the load by the throttle or in the ecu. If you would control on x HP and you would have a slight rpm dip the braking would directly go up and probaly pull you down to 0 rpm w 100% braking rather quickly.
Also if you would brake to x Nm on the wheel or flywheel you will still have not horizontal points when youd change the rpm with your throttle because the friction and pumping losses and engine efficiency is not constant vs rpm."
--->
Heavy diesel industrial engines do not operate by throttle. The "throttle" is only a RPM selector. They keep rpm fully until they reach torque limit inside OEM SW.
When dynoing Industrial Engines you always go from max RPM to min RPM. I understand your thinking, but seems like you are comparing with acceleration-dyno and Live-programmable control units.
"to find MBT timing its way easier to just fix the rpm and the airload (with your foot or rlsolap or whatever) and then do a timing sweep and read where may torque is"
--->
my request comes for OEM control units. Its not possible to adjust anything live these control units.
To Jostein: I still think this will be a very usable feature for us, and all others who are working on heavy offroad engines. To be able to make a setpoint on ex. 100hp steady state (on a 300hp engine), and keep it there even though the retarders are heated up. This will make it possible, combined with datalog, to find optimal calibration points inside OEM sw.
I do not think that could be usefull, for calibration one normally always regulates the rpm and changes the load by the throttle or in the ecu. If you would control on x HP and you would have a slight rpm dip the braking would directly go up and probaly pull you down to 0 rpm w 100% braking rather quickly.
Also if you would brake to x Nm on the wheel or flywheel you will still have not horizontal points when youd change the rpm with your throttle because the friction and pumping losses and engine efficiency is not constant vs rpm.
to find MBT timing its way easier to just fix the rpm and the airload (with your foot or rlsolap or whatever) and then do a timing sweep and read where may torque is.
Hi. I have an idea for yourdyno which could be usefull for us.
A new way to run manual mode: instead of rpm or brake% in manual mode we often need to moniter or dial in ECU calibration at specific engine loads. Therefore it could be very usefull to make a "manual mode" under PID regulation, where we could make a setpoint for 50hp, or 300Nm as and example. In this way we can adjust rpm by engine throttle ánd dial in MBT areas in full table at different engine speeds we set manually on throttle. this way YD will always make a setpoint for the aimed power or torque.
Also it could be nice to have a safety switch off in manual mode, controlled by engine rpm. So no matter what - under 1200rpm dyno will turn off. Just in case engine gets overloaded.
This method is mostly meant for dynoing industrial engines i think.
I have an idea, for example, it would be cool if you could subsequently adjust the engine speed like with Vtech-Performance and the losses are displayed. Here in Germany, everyone thinks you're cheating if the power loss isn't displayed.
thank you 🙂
