You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing to note, like Spektrum (and unlike OTX/ETX), you should be able to get the core surface mapping from the function mixers. You still obviously need the Outputs portion as well for Forward Programming.
@mawzthefinn You are correct... at minimum i need the outputs so that i can display the name to make it easy to select channels in Forward Prog.. Specially if the MM is mapping from AETR->TAER. Ail:Ch1->Ch2, Ele:Ch2->Ch3, Thr: Ch3->Ch1
My plan is still to port the UI where you set the what Ch is use for each surface (Wing and Tail settings/mix).. Later on, if i can get all that info from the Radio will be great. Still could be dificult to understand the intent of a mix, specually the not usual ones..VTail, Taileron, Delta, two Ail, Canard, Canard-Aileron, etc.
Verified and working as expected.
The only thing is that "module" class is not documented in the LUA doc, but was able to inspect its methods/functions via code.
I need to retrive more information about the current model.
1. info about the output channels.
Propose API: model.getOutput(i) where "i" is the channel number.. similar API to model.getCurve(i)
2. Current module Information
The Options comming from the /scripts/multi/main.lua:
The text was updated successfully, but these errors were encountered: