ERSKY9X Coding

[jhsa]

Ok, thanks Mike..
I don't see any extra options, so how can we test this?
I tried creating a new model without configuring the telemetry com port or anything else but the protocol, but I had to configure all manually.. So, I guess this is not what the new auto function is meant to do? I think I'm not quite getting the purpose of this..

Thanks

João

[MikeB]

Currently, it is specific to using the Multi module. Based on the Multi protocol settings, it selects the required telemetry protocol Frsky 'D', FrSky 'X', DSM, AFHDS2A etc.

Mike.

[jhsa]

Thanks, If you manage to implement it for the other protocols as well, I think the "AUTO" setting should be placed in the Telemetry menu under "UsrProto". It makes more sense?
Even now, if Multi wasn't selected, "Auto" could be ignored??

João

[jhsa]

Mike, you allow a protocol called DSM2 (it Should reallt be called DSM?) for the internal module, but if you use DSMx as "UsrProto" in telemetry, we can only select COM1. I have just found this out as a couple times I have noticed my COM port changing from 2 to 1, and I didn't know why. I found out that every time the DSMx is selected as "UsrProto" the COM port is changed to 1 and we cannot select 2.

João

[MikeB]

I think that might be left over from the original implementation of the Orange module for the 9XR-PRO that uses the internal antenna.
The whole telemetry selection needs a bit of an overhaul!

Mike.

[jhsa]

The whole telemetry selection needs a bit of an overhaul!

Mike.

Aggree

Another problem.. Trying to set an hall switch as RPM sensor. The sensor is an Allegro A3144. It is open collector and the internal transistor switches to Ground when a magnetic field is present. oXs has the internal pullup active on Pin 8.
Please watch the short video inside the zip file. For experimenting, I connected a push button to the oXs instead of the hall sensor. I believe that the reading is correct. Just tried a signal generator here, and it seems on the video I'm hitting the button at about 2Hz, but the numbers on the screen, should be updating, not flashing in my opinion??

Thanks

João

[MikeB]

That could well be working correctly. When I put some code into oXs for the RPM I think it measured the time between pulses to get the RPM value, but if the time exceeded a certain amount then the RPM was considered to be 0, so 0 was sent.
It may just be you can't keep pressing the button fast enough to avoid this so the displayed value swaps between a value (120 or 150) and 0 resulting in the flashing you see.
If the oXs sends 0, I'll display 0.

Mike.

[MikeB]

I think the time has come to remove the old "FrSky" specific alarms on A1 and A2. They were only put in to set alarms in the DJT module, although they have been carried forward to allow them to be used on the radio rather than in the module.
With the voice alerts I can see no real reason to keep them. They have gone from er9x already (to save flash space!).

Mike.

[jhsa]

That could well be working correctly. When I put some code into oXs for the RPM I think it measured the time between pulses to get the RPM value, but if the time exceeded a certain amount then the RPM was considered to be 0, so 0 was sent.
It may just be you can't keep pressing the button fast enough to avoid this so the displayed value swaps between a value (120 or 150) and 0 resulting in the flashing you see.
If the oXs sends 0, I'll display 0.

Mike.

The oXs send the value in Hz I think.

From the oXs description:

**** 7 - RPM (rotations per minute) sensor settings (optional) ***************************************************************************
* It is possible to measure RPM using a sensor connected to pin ICP (=PB0, = pin 8) of OXS.
* This sensor must provide a level change (0 - Vcc) on this pin each time a blade passes in front of it.
* The number of blades is an important parameter to set up but this is done on Tx side.
* To activate this function, uncomment the #define MEASURE_RPM line below.
* Note: The digital pin 8 (PB0/ICP) is the only one to be used to measure RPM.
* The value calculated by oXs is in Hertz (and not in roration per minute)
************************************************************************************************************************
//#define MEASURE_RPM

And I have just put 2 magnets on a wheel attached to my mini drill. You are right, it reads normally without flashing. I am not sure it is reading correctly though. I have set it to 2 blades because I have 2 magnets. Will have to compare with a RPM meter. I know a friend from my club that has one.

I can see I will have problems to attach the magnets to the engine, or spinner.. Only at 3000 RPM one of the magnets just shot across the room

João

[jhsa]

I think the time has come to remove the old "FrSky" specific alarms on A1 and A2. They were only put in to set alarms in the DJT module, although they have been carried forward to allow them to be used on the radio rather than in the module.
With the voice alerts I can see no real reason to keep them. They have gone from er9x already (to save flash space!).

Mike.

Fully agree.

What about the "GpsAltMain" alarm??

Thanks

João

[MikeB]

That's an option to use the GPS altitude reading instead of the barometric altitude as the main altitude value. It's really a "select altitude source" option.
It may not be needed any more as it was probably used for the 400 feet fixed altitude alarm.

Mike.

[jhsa]

I believe there is a source now for GPS Alt? So, if needed, a voice alarm can be created?
An Alt source would probably be a good idea. then we could select BARO or GPS. perhaps allow also A1/A2??

João

[MikeB]

I think I need to keep GPS Alt. With this set, not only do you get the GPS altitude as the main Alt. value, you also therefore get the automatic (and manual) offset to display height above ground. So it is useful.

Mike.

[jhsa]

Yes, but it could be an altitude source just like the current source?

João

[MikeB]

I might rename it on the menu. Rather moor work to add other possible sources as well.

I'm removing the legacy alarms on A1 and A2, they really are not needed any more. As a "bonus", the ratio setting that is currently 0-255 will be extended to 0-1000 allowing greater scaling of the input. This means the "type" option (v, -, V, A) won't need to use the 'V' to double the voltage as the ratio will handle that anyway.

Mike.

[jhsa]

Mike, talking about increasing ratio, what about the mix weight? You said you might be able to increase it to about 250 or something??

Thanks

João

[MikeB]

That's been in recent test versions already!

Mike.

[jhsa]

Oh, I didn't see it. It wasn't mentioned on the test version description I guess will check it in a while then

Thank You..

[jhsa]

Mike, shouldn't the offset also be allowed the same value?

Thanks

João

[MikeB]

Maybe!

Mike.

[jhsa]

Mike, is not the first time that a voice prompt plays without me touching the radio. This started to happen a few weeks ago. Already reported it.
I'm at the field now, after flying switched the model off, the radio spoke the normal stuff like telemetry lost, etc.. After a while it told me the model battery and the radio battery that I have programmed on PB1. I didn't touch the button. Actually, i didn't even touch the radio..
As I said, it is not the first nor the second time that this happens.

By the way, I can't see the multi version nor the LQi anymore in the multi protocol menu.. Did you remove it?

Thanks

João

[MikeB]

I haven't removed the LQi or version. LQi only displays for FrSky D and X.

Is there anything obviously common with the voice messages? e.g. all triggered by PB1 or some other "extra" switch.
Do they all have a similar setup that is different from other voice alerts?

Mike.

[jhsa]

I remember some time ago I also i also heard an flaps 1 and flaps up voice. Flaps are on the 3 position Ele switch..

I will keep an eye on it..

The model I have just flown has a D8R-II Plus bound to the multi module. I haven't seen the LQi and the multi version..
Will power the model again.

João
EDIT: I have just powered the model again, and the information now is there. Don't know what happened before..

[jhsa]

Mike, you posted a test version yesterday, and it says that it implements flashing the multi module using ersky9x. But I guess it isn't using the idea you've posted on RCG today, correct?

Thanks

João

[MikeB]

No, it uses the optiboot bootloader I was already using, needing the bind button to be pressed at power on.

Mike.

[jhsa]

Thanks Mike..

João

[MikeB]

That idea I posted is all working!
At least, on a 9XR-PRO I just used to test it.
It even works without changing the optiboot bootloader.

Mike.

[jhsa]

Great Can't wait to testing it

João

[jhsa]

Mike, some guys at the ArUni RCG thread are having some trouble. They are installing this board in some single stick radios/cases, and according to them the space is quite tight. So, they try to install a simple encoder instead of the 7 way with the directional keys. The problem is that they can't change the main screens only with the encoder. They need the directional keys for doing it.
I wonder if it would be possible to implement something to solve that problem? Not easy I know.. I have been thinking about it and didn't come up with a possible solution. Even a stupid one I think I'm losing qualities
I was going to say press menu or center button short to enable screen scrolling with the encoder, but then I remembered that if you are on a telemetry screen a short press brings up the reset Alt and offset popup. So, not possible this way

Perhaps double press to start? another double press to allow the encoder to move to the next page of the same screen?
then a timeout where this would stop working to avoid changing screens by mistake? Not convinced this would work.

An option in the main popup ("Change MainScreen??") leading to an index menu of all screens? people would just select the screen or sub screen they would like to go? This just occurred to me actually, and I quite like it. This would solve their problem, and probably other problems too..

Thanks

João

[MikeB]

I've just posted test version 'c1'.
This fixes a problem on the Taranis QX7 relating to switches SC and SH.
It also, for testing, allows the telemetry timeout to be extended up to 10 seconds.
The option for flashing a multi module using a serial bootloader in the module is extended to handle the Orange DSM module.

Mike.