I wanted to let you know that I got this working on all my models. This was the sequence I found successful: Discover new sensors, Stop Discovery, Switch off the plane and radio then switch them back on again and Bingo - it worked! Thanks again for your brilliant tutorials.
FYI just followed your video to install edge TX 2.9.4 and INAV LUA 2.2.4 which are the latest available as of 28/04/2024 & it worked flawlessly. Thank you. Very good tutorial. Will 100% be following your channel!
A very thorough tutorial. I would like to add that you don't have to have telemetry from your model BEFORE you have the iNav Lua installed on your radio. You can do it after. This might cause some confusion for people setting up a new model.
Dude as I always stated step by step guidance is just brilliant.. now again thanks to you latest EDGE TX running INAV for my Nazgûl and chimera 7in you my friend are legendary thank you as always 🛩
How cool is that. Just installed it on Edge 2.10 for a quad with iNav. Seems to be working, although there was a lot of lag for the artificial horizon... dropped the telemetry ratio in the ELRS script and much improved.
Your refresh rate between quad and screen orientation is so faster than mine! I move the plane (atomrc F405 wing board) and I get the movement 5 seconds later :P
Awesome video!! Thanks for putting this together. I have my INAV working, but there is about a 10 sec. lag between the quad and INAV. My setup is a Radiomaster TX16s and Express LRS? Any idea how I can speed up the telemetry data to get almost real time? Thanks.
First of all Your videos are excellent, well presented and easy to follow. I do not think I could figure it all out without you and all of the RUclips presenters. I would like to become a patreon but I would rather pay by the year, exchange rates and getting charged to make the swap monthly. Please tell me how to go about it. I do ask lots of questions. I know you said in the video I might have to invert my stick movements but I fly Mode 1 and no matter what combination I try I am unable to access the configuration screen on the INAV widget? Thanks Mate!
Hi Henry, Patreon offers a custom pledge option: For any new patron looking to create a custom pledge before they join a specific tier, they can do so by visiting the creator’s page and scrolling down to their posts. The Become a patron button will appear, directing them to the checkout process. They can choose the Make a custom pledge option there. Have you seen this page? www.mrd-rc.com/tutorials-tools-and-testing/inav-flight/inav-stick-commands-for-all-transmitter-modes/
@@RCVideoReviews Hi, yes I have seen that page, thank you, I was talking about accessing the INAV menu widget on the TX16s screen. I asked the question on discord and a member gave me the information I needed.(Throttle high, Yaw right to enter menu and Pitch and roll to navigate the menu.) I have never used Discord, thanks to you talking about it so much thought I would give it a try, looks like another great asset for RC. Cheers
I was having problems with my TX16s iNav script before watching this video, and opted to install Edge TX 2.7.1 from scratch on a formatted SD card hoping I could duplicate 100%. All went well except two things; 1) the trick with the stick going to the upper right did not trigger the iNav widget to go into the setup mode, and 2) when I tried executing the lua script directly from the scripts/telemetry folder, it responded with "Script syntax error" and then "?:0: attempt to index a nil value. My previous build I also had problems running this lua script where it was glitchy (flickering at times between screen swaps) when I used the screen 2 telemetry widget, but when I ran the lua script direct from the SD card icon and scripts/telemetry folder it launched as might be expected, although when I backed out of the screen it would trash my custom theme colors, and it would also screw up the shutdown screen, causing the touchscreen confirmation to be redundant. The only other script I have been running is ELRS (which I have yet to reinstall). I assumed my install was bad, and it seems to remain imperfect. Any ideas?
Calibrate your radio. The script doesn't have an opinion about stick position, so if it's not entering setup when you push your stick to the correct position, it might be because you aren't calibrated. I've seen some color issues with this script on my radio. I don't believe there is a userspace method to cure. You should report these types of issues on the EdgeTX and iNav LUA github.
@@RCVideoReviews Thanks for the response; I love the videos as well as the entry jazz.... As for the calibration, that came to mind immediately. I forgot to mention that in my post. It still didn't help, although I'm inclined to wonder if something is at the hairy edge or limit of the calibration (where it's reading 99% of position instead of 100%). I also noticed that the older version that I installed (to avoid the syntax error when executing the script directly) has the ability to edit the variables the same way as you showed, albeit the "return stick to bottom center" message remains on throughout. My solution at this point is to use what I have working in the meantime as I keep my ear to the track and wait until they have another update. I was really surprised to find my TX16 was blocking a lot of the sensors (getting yaw but not pitch or roll as I would bring up the listing with the OpenTX/EdgeTX built in feature without calling up the Lua script or widget). I'm not sure what to make of that.
You can check movement a couple of different ways. The channel monitor would give you an idea of whether your hitting what the radio considers to be 100%. I'd check that. Regarding the other issues, the best thing you can do is report what you see on the respective githubs.
my colors are red and no font/words of info, my ground is not brown, is black.. what i've done wrong? tx16s latest edge tx.. followed your steps for sure. i've found the theme colors is affecting the widget colors, does anyone know do i fix it? it is not supposed to happening.
Based on comments from another forum, I went back to 2,7.0, but that didn't seem to help. Eventually I tried the newest RC of the script, but that didn't help either. Then I tried an older version (1.7.5) and suddenly I got all of my sensor values. With 2.7.0 I only got yaw, but now I have Y P and R even though it seems like there are ongoing theming color crashes.
i do all the video said but i try to move my kwad the artifical horizon indicator is not moving or working. but the stick the throttle stick is working any help.
Ciao ho installato questa fantastica telemetria grazie a te e il tuo video dettagliato….sei molto bravo!!! Però ho montato anche un sensore temperatura che ho visto sempre su you tube…il sensore e lm75 su osd lo vedo ma sulla telemetria della radio no. Uso un aereo e inav 6.1 Cosa ho sbagliato? Grazie😊😊😊
I have been using this on my OpenTx configuration without any problems but having spent the last two days helping a club member configure his system I have an issue that I hope you can resolve. His transmiter is a Radiomaster TX16s MkII running EdgeTx v2.10.1 and the telemetry is all being received OK. I can only find one set of iNav Telemetry files to download (the same one I use for my OpenTx configurations) and that has installed OK on his EdgteTX transmitter but although the basic widget window is displayed a lot of text is missing. For example the gauge headings are not displayed, and as soon as the GPS gets a "lock" the GPS coordinates vanish (displayed in a colour you can't see ?). Do you know of a solution to this, or have I installed the wrong iNav LUA telemetry "system" for EdgeTx ?
If you have telemetry sensors on EdgeTX and iNav LUA isn't displaying them correctly or introducing little errors like the data going blank after a lock, that sounds like an iNav LUA error to me. Go back to the telemetry screen and look for the sensors. If they're still there, then it is definitely an iNav LUA error. Keep in mind, EdgeTX is changing the underlying core of the system. It is up to the LUA developers to keep their scripts current and compatible. There hasn't been active development in OpenTX for some time outside of maintenance, so hopefully these awesome LUA scripts will be updated for the successor to OTX.
Is there any method to fix telemetry data order on main telemetry page??..as when i make delete all sensors-> discover new sensors cycle...it always drop/discover the sensors data/values in different oreder..mixing the values on widget/ custom telemetry screens and I had to always resetup the values on my custom telemetry screens (e.g: Alt value changes to Heading according to the new sensor order ID). Im using tbs crsf in all of my models.
By any chance would you know how to reverse the roll axis in the lua? Meaning when I’m looking at the screen if I roll right it rolls left on the screen, it’s like the plane is coming at me instead of looking at the screen like I’m in the plane flying. Just a little thing that bugs me lol, I just can’t figure out out. Thank you so much
by the way, in 25 min of video, your quad and lua screen going opposite horizen. I have same problem, but when I connect to inav it shows correctly on the pc.
Thanks bro ! I did all this and mint! Guys say..I'm flying and cant look at screen anyway why do I need this screen ! But to get the inav telemetry in FPV goggles doesn't the screen need to be loaded ? Or do I got this wrong..the scrips folder is the inav driver that works in background and widgets folder is just the eye candy ,the screen. When ever I use FB configurator I didn't have to load Betaight lua! Just the ELRS lua. I use to fly a COX spitfire with strings, now look what I'm facing ! lol
I got it all setup but when i plug in my Dolphin lua script says "ERROR in background(): bad argument #1 to 'get value' (string expected, got nil)" What does this mean?
Thanks for your video You have selected CRSF as receiver. Does the same also work with a Frsky D16 Sbus receiver? Or isn't that much sensor data transmitted with the latter?
@@willipreugschat it does but you have to wire the 4. wire to an extra tx/rx Port with a diode.. it is a one wire connection and state the frsky s port in telemetry in the ports
Hello, I have a question regarding updating my TX16s from 2.7.0 to 2.7.1: what will happen with all my settings and models after updating? Should I update SD card as well or just leave it like it is?
Hi John, I have a weird problem that I don't know how to solve. INAV 5.0, EDGE TX From my Telemetry an RXBt flashes 16.1v and 4.7v. Bat% flashes 76% and 0% This gives an alarm from my Telemetry, I think, Low Battery warning. Three questions: I think this alarm can't be there because the battery gives 16.1v. Why is the RXBt and the Bat% blinking? How can I cancel this alarm? I have a video where this is visible. But then I have to send that to your email. Do you know what's going on and how I can fix it? Regards Casper
Unfortunately, I couldn't answer this without experimentation. I would probably delete the sensors, rediscover, pick one, delete the rest and start from there. Usually when it comes to troubleshooting issues like this I try to eliminate variables and focus on one very specific thing at a time. It may require conversation EdgeTX team or iNav team, or both.
@@RCVideoReviews Thanks for the reply, I have soldered the BT module on the pcb inside, But after reading, I believe EDGE is not there yet to get the BT working as today. Open Tx has that option available, but I like my touchscreen working on EdGE TX. Cheers.
@@RcBuddy Bluetooth is supported, but custom build with -DBLUETOOTH=YES With GitPod this can be easily achieved: github.com/EdgeTX/edgetx/wiki/Building-radio-firmware-in-a-webbrowser-with-Gitpod If you're willing to learn how to make your own (it's actually quite simple) you can also add this flag to your build line.
@@RCVideoReviews After some fiddling around on Github, I have now a self build version 2.8.0, with BT enabled, working version on my TX16S. Thanks again for your help. Cheers.
Thanks to the developers. BUT they did not take into account one option. The pilot installs the latest EdgeTX firmware as well as the latest INAV 6.1. But if the pilot has an ELRS version of -1, then there is no indication from FC. The widget does not work. What is the solution? Is it possible to specify in the widget from which sensors to receive information?
I wanted to let you know that I got this working on all my models. This was the sequence I found successful: Discover new sensors, Stop Discovery, Switch off the plane and radio then switch them back on again and Bingo - it worked! Thanks again for your brilliant tutorials.
Nice work!
FYI just followed your video to install edge TX 2.9.4 and INAV LUA 2.2.4 which are the latest available as of 28/04/2024 & it worked flawlessly. Thank you. Very good tutorial. Will 100% be following your channel!
Awesome! Welcome to the channel. Glad it all worked out.
A very thorough tutorial. I would like to add that you don't have to have telemetry from your model BEFORE you have the iNav Lua installed on your radio. You can do it after. This might cause some confusion for people setting up a new model.
Absolutely Awesome. Thank you for the work involved with throwing this video together. It was super helpful.
Glad you enjoyed it!
Dude as I always stated step by step guidance is just brilliant.. now again thanks to you latest EDGE TX running INAV for my Nazgûl and chimera 7in you my friend are legendary thank you as always 🛩
*blush* Thank you. I'm very glad the material is helpful. Cheers!
How cool is that. Just installed it on Edge 2.10 for a quad with iNav. Seems to be working, although there was a lot of lag for the artificial horizon... dropped the telemetry ratio in the ELRS script and much improved.
Yeah, the telemetry rate needs to be increased. That should solve it.
Thank you, just what I was looking for - would not have thought to look for an iNav script to use with BF
Your refresh rate between quad and screen orientation is so faster than mine! I move the plane (atomrc F405 wing board) and I get the movement 5 seconds later :P
Hmmm.....Try what I show in this video and let me know if anything changes ruclips.net/user/liveaNBJzDKAkog
Another superb tutorial video - Thank you!!
You're very welcome!
Great show, missed seeing it live but always try to catch them after. thanks for sharing.
Sure thing. Thanks for watching :)
Fantastic video !!! Thanks once again .. Happy Flying
You're welcome! Glad it helped.
Great video you just got a new sub!!! you sir are the MAN!!! Thank you!!!!
Welcome!
Great Video!!!
Thanks!
Merci pour le partage de ces explications efficaces et explicites. Excellent.
Vous êtes bienvenue. Merci d'avoir regardé la chaîne.
thanks a lot, simple and efficient
You're welcome!
Your video saved me again :) Thank you very much!
You're welcome!
Works fine, thank you much. New 2022 nov radio tx16s and edge TX.
You're welcome.
Awesome video!! Thanks for putting this together. I have my INAV working, but there is about a 10 sec. lag between the quad and INAV. My setup is a Radiomaster TX16s and Express LRS? Any idea how I can speed up the telemetry data to get almost real time? Thanks.
First of all Your videos are excellent, well presented and easy to follow. I do not think I could figure it all out without you and all of the RUclips presenters. I would like to become a patreon but I would rather pay by the year, exchange rates and getting charged to make the swap monthly. Please tell me how to go about it. I do ask lots of questions. I know you said in the video I might have to invert my stick movements but I fly Mode 1 and no matter what combination I try I am unable to access the configuration screen on the INAV widget? Thanks Mate!
Hi Henry, Patreon offers a custom pledge option: For any new patron looking to create a custom pledge before they join a specific tier, they can do so by visiting the creator’s page and scrolling down to their posts. The Become a patron button will appear, directing them to the checkout process. They can choose the Make a custom pledge option there.
Have you seen this page? www.mrd-rc.com/tutorials-tools-and-testing/inav-flight/inav-stick-commands-for-all-transmitter-modes/
@@RCVideoReviews Hi, yes I have seen that page, thank you, I was talking about accessing the INAV menu widget on the TX16s screen. I asked the question on discord and a member gave me the information I needed.(Throttle high, Yaw right to enter menu and Pitch and roll to navigate the menu.) I have never used Discord, thanks to you talking about it so much thought I would give it a try, looks like another great asset for RC. Cheers
I was having problems with my TX16s iNav script before watching this video, and opted to install Edge TX 2.7.1 from scratch on a formatted SD card hoping I could duplicate 100%. All went well except two things; 1) the trick with the stick going to the upper right did not trigger the iNav widget to go into the setup mode, and 2) when I tried executing the lua script directly from the scripts/telemetry folder, it responded with "Script syntax error" and then "?:0: attempt to index a nil value. My previous build I also had problems running this lua script where it was glitchy (flickering at times between screen swaps) when I used the screen 2 telemetry widget, but when I ran the lua script direct from the SD card icon and scripts/telemetry folder it launched as might be expected, although when I backed out of the screen it would trash my custom theme colors, and it would also screw up the shutdown screen, causing the touchscreen confirmation to be redundant. The only other script I have been running is ELRS (which I have yet to reinstall). I assumed my install was bad, and it seems to remain imperfect. Any ideas?
Calibrate your radio. The script doesn't have an opinion about stick position, so if it's not entering setup when you push your stick to the correct position, it might be because you aren't calibrated.
I've seen some color issues with this script on my radio. I don't believe there is a userspace method to cure. You should report these types of issues on the EdgeTX and iNav LUA github.
@@RCVideoReviews Thanks for the response; I love the videos as well as the entry jazz.... As for the calibration, that came to mind immediately. I forgot to mention that in my post. It still didn't help, although I'm inclined to wonder if something is at the hairy edge or limit of the calibration (where it's reading 99% of position instead of 100%). I also noticed that the older version that I installed (to avoid the syntax error when executing the script directly) has the ability to edit the variables the same way as you showed, albeit the "return stick to bottom center" message remains on throughout. My solution at this point is to use what I have working in the meantime as I keep my ear to the track and wait until they have another update. I was really surprised to find my TX16 was blocking a lot of the sensors (getting yaw but not pitch or roll as I would bring up the listing with the OpenTX/EdgeTX built in feature without calling up the Lua script or widget). I'm not sure what to make of that.
You can check movement a couple of different ways. The channel monitor would give you an idea of whether your hitting what the radio considers to be 100%. I'd check that.
Regarding the other issues, the best thing you can do is report what you see on the respective githubs.
I followed your steps but it didn't work. Image is flickering and unstable... Thank you for your help
my colors are red and no font/words of info, my ground is not brown, is black.. what i've done wrong? tx16s latest edge tx.. followed your steps for sure. i've found the theme colors is affecting the widget colors, does anyone know do i fix it? it is not supposed to happening.
Follow the video instructions EXACTLY. I had the same problem at first, fixed it by following instructions closer.
@@TheRyansmall i got it. i was the wrong website with an older version. ty man
Based on comments from another forum, I went back to 2,7.0, but that didn't seem to help. Eventually I tried the newest RC of the script, but that didn't help either. Then I tried an older version (1.7.5) and suddenly I got all of my sensor values. With 2.7.0 I only got yaw, but now I have Y P and R even though it seems like there are ongoing theming color crashes.
Your the best ! I dont know why on BetaF I have no telemetry button to turn on . 2 quads . F722 board and F405Mk2 blug in and nothing is there ! (
I am now on 2.7.8 Edge and the script freeze... it works for a while but then freeze. Several models.
i do all the video said but i try to move my kwad the artifical horizon indicator is not moving or working. but the stick the throttle stick is working any help.
Ciao ho installato questa fantastica telemetria grazie a te e il tuo video dettagliato….sei molto bravo!!!
Però ho montato anche un sensore temperatura che ho visto sempre su you tube…il sensore e lm75 su osd lo vedo ma sulla telemetria della radio no.
Uso un aereo e inav 6.1
Cosa ho sbagliato?
Grazie😊😊😊
I have been using this on my OpenTx configuration without any problems but having spent the last two days helping a club member configure his system I have an issue that I hope you can resolve.
His transmiter is a Radiomaster TX16s MkII running EdgeTx v2.10.1 and the telemetry is all being received OK. I can only find one set of iNav Telemetry files to download (the same one I use for my OpenTx configurations) and that has installed OK on his EdgteTX transmitter but although the basic widget window is displayed a lot of text is missing. For example the gauge headings are not displayed, and as soon as the GPS gets a "lock" the GPS coordinates vanish (displayed in a colour you can't see ?). Do you know of a solution to this, or have I installed the wrong iNav LUA telemetry "system" for EdgeTx ?
If you have telemetry sensors on EdgeTX and iNav LUA isn't displaying them correctly or introducing little errors like the data going blank after a lock, that sounds like an iNav LUA error to me. Go back to the telemetry screen and look for the sensors. If they're still there, then it is definitely an iNav LUA error.
Keep in mind, EdgeTX is changing the underlying core of the system. It is up to the LUA developers to keep their scripts current and compatible. There hasn't been active development in OpenTX for some time outside of maintenance, so hopefully these awesome LUA scripts will be updated for the successor to OTX.
Is there any method to fix telemetry data order on main telemetry page??..as when i make delete all sensors-> discover new sensors cycle...it always drop/discover the sensors data/values in different oreder..mixing the values on widget/ custom telemetry screens and I had to always resetup the values on my custom telemetry screens (e.g: Alt value changes to Heading according to the new sensor order ID). Im using tbs crsf in all of my models.
By any chance would you know how to reverse the roll axis in the lua? Meaning when I’m looking at the screen if I roll right it rolls left on the screen, it’s like the plane is coming at me instead of looking at the screen like I’m in the plane flying. Just a little thing that bugs me lol, I just can’t figure out out. Thank you so much
I'm not aware of any user configurable method to accomplish this. Might need to ping the LUA developer and ask for some ideas.
by the way, in 25 min of video, your quad and lua screen going opposite horizen. I have same problem, but when I connect to inav it shows correctly on the pc.
Thanks bro ! I did all this and mint! Guys say..I'm flying and cant look at screen anyway why do I need this screen ! But to get the inav telemetry in FPV goggles doesn't the screen need to be loaded ? Or do I got this wrong..the scrips folder is the inav driver that works in background and widgets folder is just the eye candy ,the screen. When ever I use FB configurator I didn't have to load Betaight lua! Just the ELRS lua. I use to fly a COX spitfire with strings, now look what I'm facing ! lol
Hi, my horizon (left up) rotates (roll) in the exact opposite direction to the plane in reality. Can it be changed?
Cross post. Answered previously.
I got it all setup but when i plug in my Dolphin lua script says "ERROR in background(): bad argument #1 to 'get value' (string expected, got nil)" What does this mean?
You'd have to ask the developer here: github.com/iNavFlight/OpenTX-Telemetry-Widget/issues
Thanks for your video You have selected CRSF as receiver. Does the same also work with a Frsky D16 Sbus receiver? Or isn't that much sensor data transmitted with the latter?
FrsSky RXs will send internal telemetry only. I'm not aware of a BF/iNav telemetry feed via SBUS. Crossfire is supported out of the box.
@@RCVideoReviews OK thanks. I always thought the 4th wire would carry the flight controller telemetry data and not just the internal receiver data.
@@willipreugschat it does but you have to wire the 4. wire to an extra tx/rx Port with a diode.. it is a one wire connection and state the frsky s port in telemetry in the ports
@@hb9dod Sounds good. Connect to Tx or to Rx, cathode to flight controller pin? Is a 1N4148 ok?
❤❤❤
Hello, I have a question regarding updating my TX16s from 2.7.0 to 2.7.1: what will happen with all my settings and models after updating? Should I update SD card as well or just leave it like it is?
No changes to models and settings from EdgeTX 2.7.0 to 2.7.1. No SD card changes required for that update either.
@@RCVideoReviews thanks, update done 👍
Hi John,
I have a weird problem that I don't know how to solve.
INAV 5.0, EDGE TX
From my Telemetry an RXBt flashes 16.1v and 4.7v.
Bat% flashes 76% and 0%
This gives an alarm from my Telemetry, I think, Low Battery warning.
Three questions:
I think this alarm can't be there because the battery gives 16.1v.
Why is the RXBt and the Bat% blinking?
How can I cancel this alarm?
I have a video where this is visible. But then I have to send that to your email.
Do you know what's going on and how I can fix it?
Regards Casper
Unfortunately, I couldn't answer this without experimentation. I would probably delete the sensors, rediscover, pick one, delete the rest and start from there.
Usually when it comes to troubleshooting issues like this I try to eliminate variables and focus on one very specific thing at a time. It may require conversation EdgeTX team or iNav team, or both.
installed inav lua edge tx froze up
Don´t work with BF with edgetx 2.8.0
Hi sir, how can I get the BT module option enabled in EDGE Tx 2.7.0 ? Thanks in advance.
I believe you have to connect a BT module first.
@@RCVideoReviews Thanks for the reply, I have soldered the BT module on the pcb inside, But after reading, I believe EDGE is not there yet to get the BT working as today. Open Tx has that option available, but I like my touchscreen working on EdGE TX. Cheers.
@@RcBuddy Bluetooth is supported, but custom build with -DBLUETOOTH=YES
With GitPod this can be easily achieved: github.com/EdgeTX/edgetx/wiki/Building-radio-firmware-in-a-webbrowser-with-Gitpod
If you're willing to learn how to make your own (it's actually quite simple) you can also add this flag to your build line.
@@RCVideoReviews Never done such thing, so I'm lost here. But Thanks anyway for trying to help.
@@RCVideoReviews After some fiddling around on Github, I have now a self build version 2.8.0, with BT enabled, working version on my TX16S. Thanks again for your help. Cheers.
Does this work with ELRS receivers?
Yes. ELRS uses CRSF locally which is bi-directional.
@@RCVideoReviews Ok thanks. I've followed everything and not getting anything on the iNav screen. I'm using a Jumper AION mini receiver.
Please join discord and ask there. Link is in every video.
Will ardupilot work with radio master or no
yes just installed it on tx16s with edgetx
@@tsmith6669 can't seemed to find any videos of ardupilot Lua scripts and radio master set up
@@kawasakizx14jomamamoto57 Search for yaapu telemetry
Thanks to the developers.
BUT they did not take into account one option.
The pilot installs the latest EdgeTX firmware as well as the latest INAV 6.1.
But if the pilot has an ELRS version of -1, then there is no indication from FC. The widget does not work.
What is the solution?
Is it possible to specify in the widget from which sensors to receive information?
I think you'll need to check with the iNav widget developer on that one.