calculatiing Headspeed on taranis
calculatiing Headspeed on taranis
Hey guys so I was trying to find a LUA script that would calculate headspeed based on RPM sensor data from motor. The only one I found does not work and doesnt display correctly. So I am trying to figure out how to do this. I don't know enough programming to fix the script. Is there a way to do this without an LUA script?
If not any good primers on LUA scripting that gives you the basics and such?
If not any good primers on LUA scripting that gives you the basics and such?
Re: calculatiing Headspeed on taranis
2.1 telemetry does that natively with the multiplier/divider.
Re: calculatiing Headspeed on taranis
This is new to me:)
How does RPM relate to the speed without knowing the characteristics of the model?
How does RPM relate to the speed without knowing the characteristics of the model?
RCdiy.ca
Stay Safe & Have Fun
OpenTX Manual http://rcdiy.ca
Paying it forward by sharing my Lua scripts, documentation and videos.
Stay Safe & Have Fun
OpenTX Manual http://rcdiy.ca
Paying it forward by sharing my Lua scripts, documentation and videos.
Re: calculatiing Headspeed on taranis
Headspeed IS RPM... Just need to apply your gear ratio if you measure motor RPM.
Re: calculatiing Headspeed on taranis
I was looking for it cause I thought that it was capable of doing it but couldnt find it. Can you give me a small walkthrough or direct me to a page that describe how to get it set up? thanks!
Re: calculatiing Headspeed on taranis
Once you've discovered sensors you select the RPM sensor, enter to edit settings, and enter multiplier and divider.
Re: calculatiing Headspeed on taranis
OK I am running 2.1.9
this is what I have when I edit the sensor
NAME - RPM
TYPE - Custom
ID - 0500 5
UNIT - rpm
PRECISION - 0.--
BLADES - 1
MULTIPLIER - 1
and there are some check boxes below that
I dont ever see divider not even if I change the TYPE. What am I missing here
this is what I have when I edit the sensor
NAME - RPM
TYPE - Custom
ID - 0500 5
UNIT - rpm
PRECISION - 0.--
BLADES - 1
MULTIPLIER - 1
and there are some check boxes below that
I dont ever see divider not even if I change the TYPE. What am I missing here
Re: calculatiing Headspeed on taranis
"Blades" acts as divider.
Re: calculatiing Headspeed on taranis
ahh ok then thank you
Re: calculatiing Headspeed on taranis
OK so I have been trying to get this working it is making me feel stupid. My Gear ratio is 9.33 Obviously i cannot put in 9.33 under blades and if I just put in 9 the head speed is not correct. What in the world am I doing wrong.....
Re: calculatiing Headspeed on taranis
How about blades 933 Multiplier 100?
Jim
Jim
Re: calculatiing Headspeed on taranis
Awesome thank you. Can you explain how the calculation works. I am a bit confused on it? Is it basically dividing the RPM by 933 and then multiplying it by 100. That works out correct as far as max headspeed is concerned. I just want to make sure I am understanding it totally.
Re: calculatiing Headspeed on taranis
That's how I've been calculating it and I'm pretty sure it's correct.
Last edited by Hankhop on Wed Dec 06, 2023 8:01 pm, edited 3 times in total.
Re: calculatiing Headspeed on taranis
If it is single stage drive, I think you could also simply set the "multiplier" to the number of teeth on your motor pinion, and the "blades" to the number of teeth on your main gear to get the same results as multiplying then dividing the final ratio by 100.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
Re: calculatiing Headspeed on taranis
@kilrah
Has this changed in 2.2?
I see
Name
Type
ID
Unit
Precision
Blades
Auto Offset
Persist
Logs
Has this changed in 2.2?
I see
Name
Type
ID
Unit
Precision
Blades
Auto Offset
Persist
Logs
RCdiy.ca
Stay Safe & Have Fun
OpenTX Manual http://rcdiy.ca
Paying it forward by sharing my Lua scripts, documentation and videos.
Stay Safe & Have Fun
OpenTX Manual http://rcdiy.ca
Paying it forward by sharing my Lua scripts, documentation and videos.
Re: calculatiing Headspeed on taranis
No. Fields appear as intended once the right sensor type/unit has been set.