Hope to use this LUA on FLYSKY Nirvana14 #30
Comments
|
Hi, |
|
I'll leave this open waiting for more info from the OpenTX team |
|
@dengboheng what flight stack do you run? Ardupilot? |
|
@qba667 is the DIY multi module supported on the NV14? |
|
@yaapu I added support for multi-module last Friday. |
|
@qba667 that is good news and I must say you're doing a great job! My widget will crash a real radio for sure because of off screen writes but the simulator can probably survive such calls :-) |
|
@yaapu try this out: |
|
@qba667 thanks, target simu is working fine, once you release multi module support I'll need a real radio to do proper testing, simulators are fine but a bit forgiving, especially on the memory side :-) |
|
@yaapu multi is out - at lest test build. I will ask FlySky about radio for you, but probably in next week because now they have public holidays for more than 1 week. |
@qba667 that would be absolutely great, thank you. It's not clear to me how your OpenTX version relates to other I see around, yours is 2.1.8 while I see latest UndergroundFPV is 2.2.2, mine it's just curiosity since I haven't been following NV14 threads. more thanks from somewhere south of you ;) |
|
It is all based on 2.2.2 because of that UFPV is named 2.2.2, FlySky decreased the version number from some unknown reasons (maybe feature set not complete). What is in this repository is something between 2.2 and new official 2.4 because 2.4 will be based on new UI that was introduced in this project. |
|
This totally makes sense and explains why the LUA API is aligned with OpenTX 2.2.x feature set |
|
@yaapu touch events are now passed to widgets. |
|
@qba667 congrats, this is sweet! I glanced through the code, your passing events to the selected widget only and if I touch another widget you select it first, correct? Did you define gestures as well or plain touch events with coordinates and perhaps touch "duration"? |
|
@yaapu that is right. Over weekend I tried to force the touch controller to produce gestures, unfortunately it won't output anything. There is already existing TouchManager class that can be use to detect and translate touches into gestures. This must be addressed anyhow. |
|
@qba667 gestures will be needed when the lcd subsystem will be fast enough to zoom and rotate in real time which I'm afraid will be a long time from now :-) right now it's hard to keep a 10Hz fps |
|
@yaapu Is there any status updates on this, I have an NV14 and I'd be interested in contributing the code needed for this but I'm having some trouble figuring out the specifics of the build system, for one is it possible to build and run this without using the companion app compiler? As the companion app doesn't support the NV14 as you've mentioned earlier. Mind you, I've never owned another OpenTX RC so I'm not even sure what the process is supposed to look like :-). |
|
@qba667 I compiled the https://github.com/open-flysky/Flysky-OpenTX-Test-Branch/, and I got it running on my NV14 just fine. However widgets are still a mystery to be, the included Counter and BattCheck widgets don't work. They complain about refresh() trying to call a table, this turned out to be about the table returned from create being called. I made that callable but that didn't seem to make them work, as a matter of fact it doesn't seem the refresh lua function is called at all? I'm sure I'm missing something obvious, but it makes it tricky even starting to try and get this working :). |
|
Alright, appears I've located the bug inside the test branch. I've got a fixed build where widgets work again as expected (bug was introduced in open-flysky/Flysky-OpenTX-Test-Branch@624101c). I'll attempt to open an issue over there. Sorry for polluting this bug with it |
|
@Bas-moz Hi, I did not work on this, the simulator was working though so no need for the whole companion app. |
|
@yaapu Yeah. I figured :-). I actually got things working and building after I fixed a bug in the firmware code. I have the main HUD and general mesaages working although there's indeed a lot of layout work still to do. Although the HORUS implementation seems to be a little hacky as well I'd like to eventually get it into a state of sufficient quality that it can be upstreamed. Once I get something sort of working I'll post the WIP at least so other NV14 users can play with it. Hopefully I can get the firmware fix in as well. Thanks for your reply! |
@Bas-moz can you elaborate on this, I'm always open to improve my code |
|
@yaapu By all means! FWIW I've mostly been working on the HUD so far. But I was referring mostly to the strange interaction between the 'widget' (which has its own dimensions), and then overwriting the whole LCD, for the NV14 this seems like it's probably the wrong approach and I would actually constrain the size of the widget to the 'actual' widget on the device. (otherwise you end up overwriting the device's own immutable buttons). The positioning of a bunch of things also seems to be absolute where it could be relative to other specified values (i.e. test positioned relative to the HUD position rather than an absolute position on the LCD). Maybe this is harder than it seems though, since I'm still playing with it! :) For one file I was also making the mistake of editing the 'preprocessed' file, which made things appear hackier than they actually were once I figured out the directory structure and how to use the preprocessor correctly :-). |
|
Curious if there has been any movement on this. Just installed EdgeTX on my (now defunct) UndergroundFPV Nirvana. I always loved this radio but put it aside when things went sideways. I even moved over a 6pos switch to replace one the the VRB pots. It is looking good but sadly, no @yaapu YAAPU. I did manage to get your telemetry script working, albeit wonky in appearance. |
|
Hi, indeed now it should be doable, I don't have a radio to test it though. I guess I will eventually support the NV14 on edgetx |
|
Aside from all the drama that came with it, it really was a great radio. Awesome to see it get a second life in EdgeTX. If I can assist, I'd be happy to help.
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Alessandro Apostoli ***@***.***>
Sent: Friday, November 26, 2021 1:18:37 AM
To: yaapu/FrskyTelemetryScript ***@***.***>
Cc: Mark ***@***.***>; Comment ***@***.***>
Subject: Re: [yaapu/FrskyTelemetryScript] Hope to use this LUA on FLYSKY Nirvana14 (#30)
Hi, indeed now it should be doable, I don't have a radio to test it though. I guess I will eventually support the NV14 on edgetx
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#30 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABPMHKJA5CEEFXYQBUCDCNTUN4RD3ANCNFSM4H63JO2Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
finally getting there
|
|
EL18有可用的遥测脚本吗 |
|
Is there a telemetry script available for EL18? |
not ready yet, very soon |
|
Wait for your good news |
|
hi all, please download latest zip from github and test :-) |
|
ok
…---Original---
From: "Alessandro ***@***.***>
Date: Wed, Feb 1, 2023 17:41 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [yaapu/FrskyTelemetryScript] Hope to use this LUA on FLYSKYNirvana14 (#30)
Closed #30 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
okay, thank you
…---Original---
From: "Alessandro ***@***.***>
Date: Wed, Feb 1, 2023 17:41 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [yaapu/FrskyTelemetryScript] Hope to use this LUA on FLYSKYNirvana14 (#30)
Closed #30 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Nirvana 14 has the same level of hardware configuration as frsky Hours X10 and also runs Opentx.
The text was updated successfully, but these errors were encountered: