-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Engine Cut not to announce when turbine is normally shut down #6
Comments
Hi Lior, realized the same on saturday. I would support the request. |
I'm afraid this is very difficult. As different users use different trim sources / values. |
@i3dm with Jetcat does it set a different status? |
I don't remember about jetcat but surely not all ecus do this. And any solution needs to be applied to all ecus to keep the widget generic. |
I even thought about doing it based in throttle percentage. But this is still dangerous as stick down may not sound an engine cut alert. |
@i3dm you would know better then me on the ECUs telemetry |
On some ecus throttle off and throttle idle show 0% both. |
If there is no general solution, which fits to all ECU, I would prefer to repeat message 3 times and then stop warning. |
Have you looked at lowering the alert frequency? That you can already do today. |
There is a workaround here. Turnoff engine off warning in the RDT lua, then separately create a logical switch under ethos. Have the logical switch conditional to whatever conditions the specific turbine user requires - e.g. rpm number, arming switch, timing, trim position etc. Special function / Play Track to announce flameout when the above logical switch turns on. It works on ethos V1.5.x. |
Correct. |
Hi @i3dm hope you are well.
Thanks for the fast update with the Lua changes in Ethos 1.5.18.
I did notice on Saturday when I activated the RPM warning that it would continually warn me the Engine was cut even though I did a proper shutdown.
I was wondering if possible that it could only warn if it was a flame out?
(maybe if trim in the run condition then to warn once in stop position then not to warn)
The text was updated successfully, but these errors were encountered: