openrcforums

If you look at the lists above you will see some numbers are missing, these have a name of "UNKNOWN".

Mike.

I see it now - makes sense.

@MikeB ,

How is it going with the 3.4.x firmware version of ersky9x9XT_rom ?
The " + 1 " to the flight mode numbers?

No rush because with my quad and HEX config, 3.4.x is very unstable.

My 550 HEX refuses to calibrate accelerometers and my 450 quad only spins up 2 motors all the way to almost tip-over before the other two decide to kick in.

So I am back on 3.3.3 Craft & Theory mod for now.

The source code is changed and I'm working on doing a formal release of everything.

Mike.

OK, made the jump to ArduCopter 3.4.2 and finally got my new 680pro HEX calibrated.
I loaded v.1764-Mike 04.12.2016 ersky9x-r220 9XT

GREAT JOB MikeB !

Any chance for the "Heading Square" ?

What, exactly, about the "Heading Square"?

Mike.

There is no direction pointer as I have seen on other display photos

I don't understand why not, it is not dependant on anything being present and should always be displayed.
My 9Xtreme shows one, even with no receiver powered on so no telemetry being received.

Mike.

Oh, it is there...always north (up) is what I mean.
I have seen heading displays with a line pointed in other directions than North (up).

We need the heading value for that to work. This is the telemetry value "Hdg". I'm not clear that this is being sent from the information I've just checked back on.
We do have the "home direction" value. This is displayed as the last value on the second line of values in the "DEBUG" menu (UP LONG, then RIGHT a few times). Does this have a value other than 0 for you?

Mike.

No, it is zero
To confirm, second line...last column ?

The second line of numbers, so the third line of the display.
If you have 0 there, when receiving telemetry, then the isn't a "home direction" to process. It may be 0 because the model hasn't moved far enough away for the GPS to work out a home direction.

Mike.

Just took it outside for a decent lock (11 sats)
There is data being passed in that second line of numbers, last column.

MikeB wrote: It may be 0 because the model hasn't moved far enough away for the GPS to work out a home direction. Mike.

DJI F/C NASA-Light, the GPS needs to be 30 feet away from Home before turning on GPS Hold function, so maybe needs to be 30 feet away ?

Bob B.

this is during an entire flight the pointer does not appear

We're in the process of updating the ArduPilot wiki for its passthrough telemetry implementation: https://github.com/ArduPilot/ardupilot_wiki/pull/635

In particular, there's a spreadsheet with the spec: https://docs.google.com/spreadsheets/d/ ... 0EG6rfjNSI

I'll make another pass on the worksheet by tomorrow to make sure all the info is up to date (it's not right now since the IDs are in the 10xx range instead of 50xx).

I followed the spreadsheet link but got "docs.google.com uses an invalid security certificate. ", so I didn't connect to it!

Mike.

Here you go MikeB, pulled it down for you and uploaded here:

Here's the up to date spec for ArduPilot's Passthrough:

Why change the order of values in "5004"? It makes things become NOT backward compatible!

Mike.

Alright!
The directional line is now working with the new ersky9xProvR221a2 firmware.
Now I just need to figure out how it works
Looks like data refresh may have a slight delay with heading updates?

Been having a lot of fun with all the new bells and whistles.
Figured out that pointer function mentioned above.

Did something go wrong with ersky9xProvR221b6.zip released on the 6th?
I am frequently getting "Flight battery low" and/ or "no telemetry" warnings when the alarm limit is nowhere near being set off and/ or receiving telemetry.

I want to roll back but I broke the mini USB port board after the upgrade mentioned above and don't feel like taking my controller apart...again

B7 and B8 relate to Multi Protocol.

I took it apart and loaded ersky9xProvR221b8.zip 13-Mar-2017 15:32
I haven't flown it yet but I will report later my findings

Yes, still randomly hitting "Flight battery low" and/ or "no telemetry" warnings when the alarm limit is nowhere near being set off and/ or receiving telemetry.

I assume these are from a voice alert.
What are your settings for this alert?

Mike.

Yes sir, voice alarms.

"no telemetry" is a built in alarm? - I never set it.

12.9v on a 4S

But my point is, it fires off when the battery has 15.2, 14.8 and 13.9 (wrote down the last random instances).
No "quick spikes" to account for it.

What value are you using in the vioce alert (e.g. Ctot, FasV)?
"No Telemetry" is built in, that's what the "On No Telemetry" setting is partially about.

Please go to the "Logging" menu. Here, each item may be selected for logging or not (a tick box), then down the extreme right another tick appears showing those items that are being received. Each item has a timeout, if it is not received regularly, the tick will disappear until it comes back. Please check to see if the item you are monitoring has a tick that remains present all the time. This is a feature that has been recently added.

Mike.

FasV alert set to 12.9v for a 4S battery.

Everything is selected to log.

So watch the FasV logging while flying?

I think the timeout is 2.5 seconds, so if the telemetry data does not arrive that often, it will keep going to state "lost". You should see this by the tick at the extreme right (after the tickbox) flashing off.
A simple test on the ground could be sufficient, just watch that tick to see if it goes away occasionally.

The timeout is chosen as a balance between a false detection of losing telemetry and not reporting quickly when you have really lost telemetry.

Mike.