er9x development

[jhsa]

  Vendedor: hylbuy ( 22827  )Título del artículoPrecio

Gastos de envío

CantidadTotal de artículos 5pcs DC3V-5V Mobile phone vibrator ultra-micromotor mini motor Vibrating motor ( artículo:221428095143

Gracias

João

[MikeB]

I've added space in the EEPROM for timer reset switches and increased the number of voice alarms to 8.
Unfortunately, by adding the reset switch values, it will have upset the voice alarms you may already have set. I did this so that the voice alarms are the last item in the EEPROM, easy to extend without upsetting anything else.

Just posted an update (untested as I'm sorting the voice module in my '128 9X), with these changes, and, hopefully, also fix the model voice name display.

I'll think on your suggestions, need a bit of time to sort my hardware first.

Mike.

[jhsa]

Thanks Mike.. Downloading
Mike, don't you have a megasound board?? I still have a board or two from HaGeHa, but not the latest versions I guess.. easy to make changes if needed.. I think the changes were to the serial com.. Not sure.. Do you want me to send you one? I would build it for you but I'm going away in the next few days and also need to sort other stuff out.. I could post a board and any component you might not have.. Sd Card holder??
João

[jhsa]

Forgot something before..

- Hardcode the RSSI and TSSI alarms as for the pro? you could perhaps use the RSSI and TSSI settings on the Telemetry2 page?

Thanks

João

[jhsa]

Mike, Please scroll down to the safety switches/Voice switches, And see what happened to the voice switches names

João

[MikeB]

Thanks, I do have all I need, except a couple of SD cards that I'm just going to get.

The biggest problem with anything that needs a setting is the amount of flash it uses for the menu items. The FrSky '64 version is so tight on flash, things may only get into the '128/'2561 versions.

Hmmm, a bit of flash saving that doesn't quite work (on the '128).

Mike.

[jhsa]

you're worried with the flash on the 128/2561 boards??

But yeah, you're right the problem is the m64. At some point the other boards will have to overtake it in features.. You already did the impossible with the stock CPU
Maybe if you remove the other voice switches (won't be needed anyway) as you said, there is enough space in the m64. they can also be removed from the other boards as they will only confuse people in my opinion.. The new way to do the audio, voice and haptic is so much better..

How many custom switches are on the m64 firmware? if you implement the new voice alarms, maybe you could reduce the number of C switches by a little as they won't be needed for alarms??

João

[MikeB]

Just posted an update with the voice switch names corrected. I still save the flash space on the M64 but not on the '128/2561.
I've got my stripboard MegaSound board installed and working in the '128 now so I can test properly again.

Mike.

[jhsa]

It looks like all is working. I just have to turn the radio on to know that, as it takes ages to stop talking all the switches positions and alarms ha ha ha Annoying But funny

João

[BBvideo 425,350]https://www.youtube.com/watch?v=z3L2R6J8pqQ[/BBvideo]

[MikeB]

I'll have to look into why, I thought I had copied the fixes for that across. Is it doing this for the voice switches and the voice alarms?

Mike.

[jhsa]

I deleted the voice switches.. will check on the other radio now..
On the video it was with the new alarms

João

[jhsa]

On my other radio using the old voice switches, it seems that only the switches (flaps on IDx) are playing at startup. The other radio (on the video), using the new voice alarms, plays it all

João

[andrewju]

Mike,

I have a very strange issue on the er9x-2561 r814 (I use the latest one with fixes for rotary encoder). When I'm in telemetry screen, the radio sometimes goes to the settings menu (the new index screen) by itself. I mean, I do not touch anything at all, just watching the telemetry screen and then the Index menu pops up. Sometimes it happens several times a minute, sometimes it doesn't happen at all. I have a feeling it may depend on telemetry data coming from the model, as I was experimenting with the OpenXSensor and FrSky GPS when I saw this behavior... Sounds crazy, but I didn't see any other dependency.

And one more question (this one is probably simple): how do I keep the backlight 'always on' when the BL is connected via a MegaSound board? If I set the BL timeout to 0 seconds, it just switches off. And the 'Backlight invert' option doesn't seem to have any effect at all when MegaSound option is selected...

[MikeB]

How do you get to the telemetry screen? from the settings menu, or by stepping through the menus left or right? (or either!).
I'm testing on the '128 version, I'll try the '2561 version later, I'll need some time to set it up.

For the backlight, just set a "Light Switch" with the value of ON (last item in the list).

Mike.

[andrewju]

Oh, understood about the 'light switch'. Thanks!


I may have used the settings menu before I got to telemetry screen. But it's most likely that I got to telemetry by pressing up/down and then left/right...
BTW, I think I only saw this issue while I was on the telemetry screen with Latitude / Longitude data, and only when my model was switched on. I just tried with the model switched off, and I didn't see that issue... Hmm...


P.S. Also, I don't see GPS coordinates on the screen (Lat/Lon = 0) with FrSky GPS V2 (S.Port version). I thought the GPS didn't get a lock... But after some time, the Altitude information appears - so GPS receiver should be locked... May it be related?

[andrewju]

Mike,

I'm almost 100% sure the issue is related to telemetry data received from the model. In fact, I now think it's not the GPS that is causing this. I just made an experiment with an X6R receiver and an OpenXSensor connected to S.Port.

First, I switched the radio ON and selected a telemetry screen. I didn't switch my model ON, yet. I left the radio like that for almost 10 minutes - the screen didn't change and everything worked fine. Then I powered up my model (without touching the radio). Some telemetry fields appeared on the screen (T1, RPM, Alt, A1). A few seconds later the radio showed the Index Menu, the cursor moved from Display down to AudioHaptic, and then went back to Display again - I didn't touch the radio at all!!!
I pressed 'Exit' button, so the telemetry screen appeared again. A minute or two later when I looked at my radio - it showed the Index Menu again....
I exited back to Telemetry screen. This time the radio stayed there for some minutes (maybe 5 minutes or so). But then my radio suddenly jumped to the 'GLOBAL VARS' screen of the model setup.

It looks like the radio interprets some data as key presses... Which is, in fact, quite scary in a real flight...


Then I switched everything off and connected FrSky GPS instead of the OpenXSensor. While redoing the same test, the telemetry screen was rock solid and didn't jump anywhere. I need to make more tests with the GPS, but maybe this 'sporadic screen jump' issue is caused by the OpenXSensor... Unfortunately, I don't remember which SW version is loaded to my OpenXSensor. I just remember I flashed it some months ago with the latest SW available at that time.
Still, I think the S.Port data stream should not confuse the radio itself, even if it transmits something unexpected...

I'm ready to make any other tests, if needed... Just tell me what I need to do.


EDIT: this post was updated with some more details following my tests.

[andrewju]

Hmm... now I have OpenXSensor connected to my model, and a telemetry screen open on the radio for about 5 minutes (even longer). The screen doesn't jump to the settings menu anymore... Weird...

P.S. I didn't drink any alcohol, I'm certain about it!

[MikeB]

If you can let me know which telemetry data you are sending from the OpenXSensor that should help.

Mike.

[andrewju]

I used an OxS config with most settings at their default. If I'm not mistaken, this is the list of fields transmitted (I admit, I should have disabled most of these):

#define ADC2_ID 0xf103
#define BATT_ID 0xf104
#define T1_FIRST_ID 0x0400
#define T1_LAST_ID 0x040f
#define T2_FIRST_ID 0x0410
#define T2_LAST_ID 0x041f
#define RPM_FIRST_ID 0x0500
#define RPM_LAST_ID 0x050f
#define FUEL_FIRST_ID 0x0600
#define FUEL_LAST_ID 0x060f
#define ALT_FIRST_ID 0x0100
#define ALT_LAST_ID 0x010f
#define VARIO_FIRST_ID 0x0110
#define VARIO_LAST_ID 0x011f
#define ACCX_FIRST_ID 0x0700
#define ACCX_LAST_ID 0x070f
#define ACCY_FIRST_ID 0x0710
#define ACCY_LAST_ID 0x071f
#define ACCZ_FIRST_ID 0x0720
#define ACCZ_LAST_ID 0x072f
#define CURR_FIRST_ID 0x0200
#define CURR_LAST_ID 0x020f
#define VFAS_FIRST_ID 0x0210
#define VFAS_LAST_ID 0x021f
#define GPS_SPEED_FIRST_ID 0x0830
#define GPS_SPEED_LAST_ID 0x083f
#define CELLS_FIRST_ID 0x0300
#define CELLS_SECOND_ID 0x0301
#define CELLS_THIRD_ID 0x0302
#define CELLS_LAST_ID 0x030f

It doesn't mean all of these values are being calculated - in fact, I only have the MS5611 sensor connected to Arduino.

Here's my entire OxS config: http://pastebin.com/raw.php?i=54LJKZLD

[Kilrah]

What's transmitted isn't what you pasted, it's this:

Code: Select all

#define SETUP_DATA_TO_SEND    \
                        DEFAULTFIELD , ALTIMETER , 1 , 1 , 0 ,\
                        DEFAULTFIELD , VERTICAL_SPEED , 1 , 1 ,0 , \
                        DEFAULTFIELD , CURRENTMA , 10 , 1 , 0, \
                        FUEL_FIRST_ID , MILLIAH, -100 , 390 , 100, \
                        CELLS_FIRST_ID , CELLS_1_2 , 1, 1 , 0

[andrewju]

Ah, thanks a lot, Kilrah!

Did you ever notice any similar issues with OxS and er9x?

[Kilrah]

Well I don't use er9x, so no

[jhsa]

I do but I never noticed it.. and I fly always with a telemetry screen displayed on the radio. Well, lately more the custom telemetry screen. Does it happen there too?

João

[andrewju]

I'm now checking it with the custom telemetry screen. By now I didn't see the issue.

So far I saw this issue mostly on the GPS screen (the one with the Latitude / Longitude values), even if there is no data from the GPS sensor. And it also happened a few times on the other telemetry screens.

While testing it today, I see it doesn't happen immediately. I mean, I have to leave the radio for 5-10 minutes before it jumps to the settings screen... Not sure what affects this...

[jhsa]

I will test it in a while with my oXs vario and voltage.. So, i should just leave it on one of the telemetry screens but not the custom one right?

João

[andrewju]

Leave it on the GPS screen with Latitude and Longitude info. Maybe it's just a coincidence, but this seem to be the 'most problematic' screen for me...

[jhsa]

Ok, I don't have a GPS but will do it
By the way, I will be testing in HUB mode as I don't have S.port equipment.. That could exclude the HUB protocol if it doesn't happen to me..
João

[andrewju]

Well, in my case it happens when GPS is not even connected. So GPS is not a must.
But S.Port vs. HUB could make a difference.

BTW, Mike, shall the S.Port GPS be supported by er9x? According to the FrSky manual, the GPS sensor sends Altitude, position, speed, and UTC time. As far as I remember, only the Altitude was displayed on the screen when GPS was connected... Do I need to do any settings in order to display the rest?

[andrewju]

João, I just had the same issue when I was on the custom telemetry screen. So if you didn't have it before - I guess your setup is not affected.

[MikeB]

I'm working on it. Lat and Lon weren't processed do to lack of space on the M64. Adding the code to the '128/'2561 versions.

Mike.