VTX adjustment Vortex 150 script crash

[malelo1960]

If i go into the vtx settings on my taranis x9d plus and want to change parameters the script crash immediately.
An error window shows "Script syntax error BF/X9/vtx.lua:192 attempt to index field '?' (a nil value)
I have to restart the taranis to get rid of the issue.

[milindur]

On which parameter change does the script crash? Which settings are visible, when entering the VTX menu? Is "Dev" set to None or anything else?

[malelo1960]

Hello Christian, first thanks for your reply. There are no settings visible. In the moment i switch to the vtx screen via menu the error message are there. Please see photo. I have to switch the taranis power off to get rid of it. All other menu screens are ok. Please excuse i didnt have a lot of experience with my x9d plus. I have it since 3 weeks. Normal telemetry data, pids, filters and so on are all there. Only the vtx menu dont work. The S-Port from my frsky x4rsb is connected to the tx port on the vortex 150. UART2 is set to S-Port, Telemetry is enabled in Betaflight. The betaflight version of the vortex 3.2.2. ( The last available from ImmersionRC) Von: Christian Andersen [mailto:notifications@github.com] Gesendet: Montag, 27. August 2018 20:01 An: betaflight/betaflight-tx-lua-scripts Cc: malelo1960; Author Betreff: Re: [betaflight/betaflight-tx-lua-scripts] VTX adjustment Vortex 150 script crash (#162) On which parameter change does the script crash? Which settings are visible, when entering the VTX menu? Is "Dev" set to None or anything else? — You are receiving this because you authored the thread. Reply to this email directly, <#162 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AovfB0ToEt-KUyFs364OFMWQw4ktYxoAks5uVDP1gaJpZM4WM5dY> mute the thread.https://github.com/notifications/beacon/AovfByNSCC1-JsPinC_j1RDafezaRJyTks5uVDP1gaJpZM4WM5dY.gif

[milindur]

Are you using the latest version of the betaflight LUA scripts (v1.0.2)?

[malelo1960]

Yes, im using the latest lua.script.

[stale]

This issue / pull request 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.

[stale]

Automatically closing as inactive.