ERSKYTx (was ersky9x) Questions

[jhsa]

Joao
Yes its the same here - I'm down to two loose screws only

I guess replacing the 12 way connector is a serious bit of work?

Give yourself two clear days to replace it ?

regards
Hans

Half hour job working slowly I would say

João

[mrozilla]

I hooked two wires, one of the RXD from the transmitter to the pin number 1 in the connector Futaba and TXD to pin number 4 in the settings is as follows:
FrSky Met
BT Telemetry OFF
FrSky Com Port 2
Invert Com 1 OFF
COM2 Func. Telemetry
COM2 Baudrate 57600

Shows me only RX and TX and although I would still tension, because daltego in FrSky sitting jumper XA1, but unfortunately on the apparatus A1 and A2pokazuje only 0.00

I have a 9XR PRO, DJT, D8R-II Plus (Telemetry)

[MikeB]

Have you set the range for A1/A2?

Mike.

[mrozilla]

Hmm, setting A1 channel etc. I did not move, I guess, that I have something there ustawiić, but I do not know what. I 3S 5200mAh pack.

[MikeB]

Try changing:
A1 channel 0.00v
to:
A1 channel 13.2v

Mike.

[mrozilla]

Whether the first parameter is to be like the actual value of the battery for example. 11.1v and the other comes out about 4,5 whether to set the first value of about 25V so that the second parameter that displays the telemetry was like actual value of the battery or 11.1v

When set to 13.2V in the telemetry is displayed A1 = 5.

[MikeB]

OK, how is the 11.1V battery connected to the receiver?

Mike.

[ReSt]

I'm trying to get telemetrydata (Vario) onto my TGY9 with AR9x board (No FRSKY modules!) and ERSKY9x_rom versions of the firmware.

I have it working on my versions of ER9x.

My receiver module outputs UART TTL level (3.3 Volt) that I feed into COM1 of the board.

The data protocol is pure Frsky Hub protocol and the received data looks like the following:
0C5D605E0605D55E061FFA5E0620065E02175D605E5E1016015E2132.....

For ease of reading CR/NL inserted,
...605D5
5E061FFA
5E062006

5E02175D605E
5E101601
5E21325D60
5E30FFFF
5E0605D5
5E061FFA
5E062006
5E02175D605E

5E101601
5E212E5D60
5E30....

These datablocks are repeated and they always start and end with 5E. No surrounding 7E.

I had no luck to display anything on the radio up to now (Telemetry setup UsrProto=FrHub)

Is there a setup that already decodes this datastream and if yes, what must be set up to do so?

Reinhard

[MikeB]

I believe you have specific code (N2F conditional compilation true) in er9x that supports the raw hub protocol. Currently, this does not exist in ersky9x.

Mike.

[ReSt]

That's correct.

I have been trying to implement it in Ersky but up to now with no success (having set the Protocol to FrSkyHub in telemetry setup).

In the very beginning of
'void processFrskyPacket(..)' i inserted a peace of code starting with
"if (g_model.FrskyUsrProto == 0)
{ ...} " that calls frsky_proc_user_byte(packet[j])

and in void frsky_receive_byte(..)
following the
"else // Not DSM" line
"if (g_model.FrskyUsrProto == TEL_FRSKY_HUB)
{ ...} " with the code to decode the hub stream

I'm not even sure that this are the correct places where I put it in.


Reinhard.

[MikeB]

The main reason FrHub is present is to help with the telemetry from a MULTI module, it assumes normal 'hub' frames in full, not just the raw hub data.
What is needed is another option "HUBRAW", that simply passes the raw telemetry bytes directly to "frsky_proc_user_byte".
I'll see about adding this.

Mike.

[ReSt]

That would be phantastic

At least for me ;=)

Reinhard

[MikeB]

I think this is working on a 9XR-PRO, tested on COM2. It should also work on a SKY/AR9X board, and on both COM1 and COM2. I'll try to test these tomorrow.

Mike.

[ReSt]

ok, waiting for your outcome

Reinhard

[MikeB]

I haven't had much time today, but I did check COM1 works on the 'PRO, so it should all work on SKY/AR9X.

Mike.

[MikeB]

I've posted test versions for SKY/AR9X and 9XR-PRO with "HUBRAW" telemetry option in. I tested COM1 on an AR9X board.
At present, there may be a limitation on the setup regarding the baudrate. You will likely need to have PPM as the module protocol to force the baudrate to be 9600.
I tested this using a real FrSky hub wired directly to the appropriate COM input.

Mike.

[jhsa]

Mike, are there any other changes that need testing, or just the HUBRAW?

Thanks´

João

[MikeB]

No other changes.

Mike.

[ReSt]

I have installed the 'HubRaw' version and do get the telemetry values from my vario

There is a small problem remaining, as i continously have a beep of about half a second every 1.5 seconds (roughly guessed)
It beeps as long as telemetry is ok and stops, without the telemetry signal.

Reinhard

[MikeB]

I'm not getting any beeps on my test on a 9XR-PRO on COM1. It could be something to do with RSSI (or TSSI), since these are not present in the raw hub protocol.

Mike.

[ReSt]

Wouldn't TSSI be independent from an incoming telemetry signal ?

Reinhard

[MikeB]

It is normally reported by the Tx module using the telemetry data stream.

Mike.

[jhsa]

If receiving the telemetry signal directly from a device into the radio shouldn't the RSSI and TSSI be deactivated in the protocol (radio)??

João

[ReSt]

RSSI could possibly be measured from the remote sensors and be part of the transmitted data.
But it should not beep if it is not available. "RSSI Warning" and "RSSI Critical" to "OFF" should already do that.
Maybe we need a "TSSI OFF" also.

Reinhard

[MikeB]

What have you got set in the telemetry for the "Alt Alarm"?

Mike.

[ReSt]

Alt Alarm is set to off.

I just noticed, that when I set VoltThres =0.00 the alarm will go off.

That's good enough for me. No need to do anything else.

btw what is this voltage threshold used for?

Reinhard

[MikeB]

That's for the lowest cell of a lipo, as sent by the lipo sensor. If the lowest cell is less than VoltThres(hold), then the alarm sounds. As with the "Alt Alarm", it isn't really needed now, just set a voice alarm to do the same thing.
I probably should remove both of these now, but I left them for backward compatibility in case anyone was still using them.

Mike.

[jhsa]

I think that there are a few that could be removed

João

[mrozilla]

Unfortunately something with this parameter A1 me is wrong. The range of TX and RX telemetry shows properly, and when the A1 will set as it says on the forum to 13.2 this screen telemetry 9XR Pro have A1 = 5.0, and yet it is not the battery voltage. The battery has a range of 11.5V 12.6 V-parameter A1 does not change.

Can anything else displayed on the screen telemetry addition to A1, RX, TX, without adding additional sensor?

9XR Pro / FrSky DJT / D8R-II Plus / Naza Lite@v2

[jhsa]

No, it is not possible to read telemetry without sensors
The D8R-Plus has already a voltage sensor in it, and when the jumper connects the A1 pin to the 'x' pin, you are connecting the A1 pin to the internal voltage sensor. That means it will display the receiver/BEC voltage, therefore you have a reading of 5V. For the battery voltage, you need an external sensor..
DO NOT connect the battery voltage to the A1 and A2 pins directly or you will blow the receiver up..

João