Q&A Forum
Anyone having printing issues? Now printer is only printing the run info on the bottom of the graph. I can open a previous run from the file and it prints????
@six_shooter You can turn over to light mode when printing and turn back to dark mode. It could be automatic in the future.
Dark mode on everything else is a good idea, I have not checked how much work it is yet, will do.
hi jostein.
I keep forgetting to turn my BT keyboard off and exhasuting my batteries. is there a way you could make a remote control for IOS and android?
Therer could be a simple shortcut set of buttons like RPM lock, restart, restart, save and close... etc
even if it works only using a web browser.
thank you
@xtcund download the Unified Remote app on your phone and install the server on the PC. This gives you access to the hotkeys from your phone. With the paid version you can also make your own remotes. Unified Remote – Remote Control App for your Computer
thank you 🙂
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.
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 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.
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.
@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.
@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.
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 👍
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.
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.