Suck on "Waiting for

[undefine-man]

[devices] : Jumper T16 edgeTX 2.8.0 Betaflight firmware : 4.3.0

[Betaflight setup] : Suck on "Wait for API version" when using "Betaflight setup"

[Betaflight CMS] :

[klutvott123]

That means there's no communication. Which rx/tx are you using? Also keep in mind that the FC and RX has to be powered on for it to work.

[undefine-man]

i am using TBS crossfire nano rx and TBS crossfire Micro TX . TBS lua works fine on my remote control.

[klutvott123]

and do you have telemetry enabled in betaflight?

[KAJE1977]

I have the same thing using ghost newest firmware 1.8.0. Using betaflight 4.4. Im on RMTX16s. Telemetry is checked on in reciever tab....

[klutvott123]

@KAJE1977 For the RX/TX, are you using a mode that supports telemetry? I use race250. I'm not 100% sure if msp support is in any of the stable firmware releases for ghost, so you may need to try the latest beta

[druckgott]

I have also a Problem with the script and also telemetry. I have frsky. Protokoll FPORT and Telemetry FRSKY_HUB for BF4.4 Telemetry is aktiv

[klutvott123]

Not familiar with frsky hub, but looks like it doesn't support msp over telemetry.

[druckgott]

On BF4.3 it worked all the way. Do I maybe need to select something differnet?

[klutvott123]

In the configurator firmware flasher, try adding TELEMETRY_SMARTPORT under custom defines.

[druckgott]

That was the solution thx.

Ah I see that you say custom field I only select smartport in the teletry Protokoll field. That worked

Is there any documentation for this fields what's posible?

[KAJE1977]

I have it working now. I put TELEMETRY_GHST in the user defines and reflashed. Maybe it was that or i could have missed something.....

[KAJE1977]

FYI i was also using Race mode which seems to have issues. It will still connect but some of the pages will not load. Other telemetry modes seem to be working fine.

[klutvott123]

Yeah, some of the modes don't work too well for this. Race250 is the way to go for msp over telemetry performance.

[klutvott123]

@druckgott http://betaflight.com/docs/development/API/Cloud-Build-API

I assumed you already had selected frsky hub as the telemetry protocol in the dropdown, and you can only select one protocol so the other one has to go into custom defines 🙂

This will include smartport automatically when you select fport https://github.com/betaflight/betaflight/pull/12314

[druckgott]

perfekt thx

[OCDFPV]

@klutvott123 I am on the latest version of EdgeTX, Betaflight 4.4, configurator 10.9 I am using CRSF. On all of my quads with Kiss FC's and running KISS firmware I have no issues. I am able to see the flight controller on the main page of the LUA Agent Lite. I can control the PID'S and see all relative FC info, but on all of my quads that use the Betaflight firmware I can't see my flight controller on the CRSF Lua Agent Lite. I also tried to use Betaflight Lua (latest version) on those quads, but it doesn't get past the initializing screen. It did initially go through the " compiling phase, but it never loads the FC info. Any idea what my issue could be? Thank you in advance!

[klutvott123]

"initialising" indicates that you're using an older version of the betaflight lua scripts. Make sure you're using version 1.7.0. Also make sure that telemetry is enabled on the "receiver" tab in the configurator.

[OCDFPV]

Thanks for answering my question. I am using betaflight lua scripts 1.7.0. The Telemetry is enabled in the receiver tab. It's only seems to get stuck on " initializing" on quads with CRSF. On quads with the Frsky protocol (RSXR) it works no problem.

[klutvott123]

the "initializing" message was replaced a long time ago and is not present in 1.6.0 or 1.7.0. Install 1.7.0 again and let it overwrite the already existing files on your sd card when copying the new version over.

[OCDFPV]

This is the screen it gets stuck on

[klutvott123]

In edgetx you need to set the baud rate to 400k. see https://github.com/betaflight/betaflight-tx-lua-scripts/issues/467 🙂

[OCDFPV]

I will change it to 400k now and message back

[OCDFPV]

That did it! Thanks @klutvott123 !

[klutvott123]

Nice! Enjoy the BF lua scripts 👍

[haslinghuis]

@klutvott123 maybe add this to documentation to not repeat our self.

Maybe we can add some timeout to the script including a message check documentation for required settings?

[klutvott123]

@haslinghuis Yes, we could add the baud rate to the requirements. I'll look into adding some more info to the init stage 🙂

[TTGG4400]

Is there a custom define that fixes a CRSF setup, like that of undefine-man, the OP? I have that same setup almost - TBS CRSF Rx, TX16S, ETX2.8.0, BF4.4.0 and BF LUA v1.7 - and I get exactly the errors he posted, when I try to run the BF LUA script (which use to work, a few versions back). EDIT - Nevermind - see my other comment below.

[klutvott123]

@TTGG4400 No, all you have to do is select CRSF as the RX protocol in the firmware flasher tab. It depends on CRSF telemetry so that will be included automatically. make sure telemetry is enabled in the receiver tab, and that the baud rate is set to 400k in edgetx.

[TTGG4400]

Thx - I've been doing all of that, except that my baud rate is set to Mode CRSF, 400k, but the Status says "150 Hz 1 Err". WHOOOOHOOOO - I just saw that telemetry on my BFC Rx tab was disabled. However, that was enabled at one time according to my saved CLI. Dunno how it got disabled - Happened once before too. I need to watch what I'm doing. Thx for your help, BTW.

[klutvott123]

@TTGG4400 It's a configurator bug that disables telemetry when changes are made in the ports tab. It will be fixed in the next release

[TTGG4400]

@TTGG4400 It's a configurator bug that disables telemetry when changes are made in the ports tab. It will be fixed in the next release

Wow - thanks a lot for that - I didn't think it was me, but, I wasn't sure. You just removed a lot of self doubt from my daily life. THANKS.

[RipperDrone]

@klutvott123 On a quad with Walksnail digital video on board I am getting to the script initialization point of 'Downloading VTX table', then the script gets stuck (presumably since there is no VTX table nor settings defined when using MSP for digital video). How can I get the v1.7 BF LUA script to work anyways?

[klutvott123]

@RipperDrone The quick solution for now is to keep VTX selected in the cloud build options. You don't have to set up vtx tables or anything.

[RipperDrone]

@klutvott123 Oh, nice one. Didn't think of that. Tried to enforce definition of a VTX table by enabling TBS SA, but no luck getting vtx tables defined unless the actual hardware is responding, it seems. Will try - thx a lot.

EDIT: This did the trick indeed - good to know, though not completely intuitive... :-)

[klutvott123]

@RipperDrone Try the latest nightly. It should work without having VTX defined.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

[github-actions[bot]]

Issue closed automatically as inactive.