openrcforums

I started with IBus to implement a multi-switch for the receiver: in one channel a status code is encoded, and on the ibus of the rx a µC decodes that to enable some mosfet-switches. This is of interest to the ship model builders. With Ibus I have to transform decimal values v of 0...1023 to (2*v) -...

Can you give me a clue how to implement a lua-function to set a bitValue directly?

My problem is, thatI want to transport a 10-Bit value [0,1023] exactly to the receiver. The SBus range on the FrSky receiver is [172,1810] So i calculated: v = (bitValue * 2048) / 1638 - 1024 but that gives me to much rounding errors. Using FlySky and IBUS-Output it works as: v = (bitValue * 2) - 10...

If I use FlySky e.g. FS-iA4B RX with Sbus-Output enabled, I get different min/max values if I do the same with e.g. a FrSky R8X receiver.

Where do this difference come from?

How to fix that - if possible?

Hi all,

I like to find an input by a user supplied name, then get its id by getFieldInfo() and use it in a widget script, e.g. to fill the options.

I tries that in compainion 2.3.9, but neither getFieldInfo("name") or a search over all inputs via model.getInput() works.

Any ideas?

I saw a new branch called "tx16s-sbus-in". Looks like the right thing. Is it already worth trying?

I have already a functional implemential for the sport-protocol, but only for the polling of sensors.

Does anybody have a description how the push-messages are implemented in the sport protocol? So, what does the RX send a sport package, if openty issues such a sportTelemetyPush() function.

Thanks.

The LUA option works: a mixer script can pickup the values from the serial interface. So far, so good.

Are there any activities ongoing towards the "SBUS-Input" option? (see also aboce post).

Thanks!

Yes! Mike Ok, thanks Mike. Looking at the other options. I checked the source code for the auxSerialInit(). and aux2SerialInit(). Here I see the menu options: "telemetry mirror", "telemetr input", and "LUA". But I don't see the "SBUS-Input" option, that is pr...

The multi-protocol module sends the trainer data using the telemetry signal. When using the "MULTI_TELEMETRY" build option then the data sent includes a header indicating what the following data represents. One option for the type of data is trainer data. Mike You mean Type 0x0d ? From mu...

Kilrah wrote: ↑Fri Jun 26, 2020 5:30 pm SBUS stream on pin2 is not supported on the color LCD radios, unlike the B/W ones this is not an uart pin.

But if it is not supported, how does then multi-trainer work? The module has to feed the data-stream into the TX16S somehow.

Multi-trainer is where you use both an internal and an external multi-protocol module. Set the protocol on the external module to be one of the "receive" protocols, e.g. FrSky_Rx. Bind this to another Tx, then the control data from the other Rx will be the trainer input data for the T16. ...

For the TTL serial port I cant select "telem mirror". This seems to work, as it shows the payload (without header) of the telemetry data send from the MPM, I think. So in case of FlySky AFHDS2A ist starts with 0x06, ... The other option for the setting is "telemetry in". Does tha...

If I understand you correctly, there is no SBUS input for the TTL serials? A bit strange, because I can select this option. What do you mean with multi-trainer? Feed SBUS on the module tray pin 2 (usually used for telemetry)? Do you have any information to LUA-serialRead() ? (see other question I po...

Just want to popup this quetion and add another option: bluetooth. Inside the TX16S there is a place to attach a BT module. Has anyone information an this? Which module type? Can this be trainer input? How to use in general?

In the release notes of 2.3.8. I read that there is a nes function: serialRead().

I wonder, how I can configure the BaudRate and the interface to use.

Is there any docu on this?

Ok, thank you.

In some scripts I saw lcd.getText() with a color attribute added, e.g. SMLSIZE + GREY. I think the battcheck widget had that. This isn't documented and I was wondering if one could use that.

You have to activate the telemetry simuator in the sim as well. little tickbox in the left to corner of the telemetry sensor simulator screen :). testscript (run as telemetry, discover sensors): return { background = function() setTelemetryValue(0Xabcd,0,101, getValue('thr'), 0, 0, "wm01"...

Is it possible to set the text-forground color with lcd.drawText()?

The writing part (widget): local function background() local b = setTelemetryValue(0Xabcd,0,101, 42, 0, 0, "wm01"); if (b) then print("add ch1"); else print("set ch1"); end end The written value is visible in the telemtry screen. The reading part (mix script): local fun...

Well, I checked your example. Writing / reading gvars works fine, but clutters the gvars oviously. setTelemetryValue() / getValue() dows not work for me, since getValue() allways returns 0 for the name used in setTelemetryValue(): the sensor is created, I can see it in the telemetry menu, but getVal...

Well, I can get the value of a sensor with getValue(). How Do I set the value?

Isn't it better to use model.setGlobalVariable() / model.getGlobalVariable() ?

Thanks

Well, that is really bad! writing / reading a file seems to be a quite of overhead. Are you you sure, that there is not other pssibility? (in the poist above I meant global-lua-script-variables, not global vars in the sense of OpenTx). The widget i wrote (ab)uses some trims to emulate buttons and pr...

I used to use global variables to exchange data between telemetry scripts and mixer script.

Now I want to do the same with a widget and a mix-script. Looks like the global var of the widget is not seem from the mix-script.

How can one achieve this?

Thanks!

Simple question: where can I activate mixer scripts in companion. I used "lua" in the profile, but I am missing the tab for the mixer scripts.

Any help?
Thanks!

MikeB wrote: ↑Thu May 28, 2020 6:51 pm Or nobody reading this knows!
I don't have a T16S so I don't know (and I use erskyTx anyway).

Mike

My hope was to reach some of the devs here, because in the past I got very valuable and useful information here.

Either the question is too simple or just dumb, or it requires a lot of explanation ...

Nobody to give me some clues?

Isn't there anyone to answer these question? In general it would be nice to know, where I can provide serial (SBUS) trainer input and where to get telemetry output. Maybe there is a summary, where I can get this kind of information? Would be very happy, if someone could guide me ... (perhaps also to...

In the hal.h I found information that these ports are AUX and AUX2. Looks like they were intended to be used with BT and GPS.

Can anyone shed a little bit more light on them?