er9x development

[Malapell]

Hi,
Small bug found at item voice menu

VERS: V1.2640-Mike
DATE: 16.01.2015
TIME: 16:37:53
SVN: er9x-r817
MOD: FRSKY 128

Editing a voice menu at second screen the option "On no Telemetry" the text options are wrong

Jordi.

[ReSt]

This is correct, it' a '128'

But there is nearly no additional coding, only moving around and/ or modifying values.
With parameters CPU=128 EXT=FRSKY TEMPLATES=YES N2F=YES HELI=YES BEEPER=SPEAKER
it compiles to exactly 70000 Bytes in the moment. (But be aware, that I have a handful of other modifications locally)

Reinhard

[MikeB]

Voice menu play/mute bug fixed and posted.

Mike.

[jhsa]

Confirmed fixed..

João

[MikeB]

Regarding the menus. On ersky9x, the model index menu makes use of the right half of the top line for an extra menu item. I've just added the extra code to the '128/'2561 to use this for templates.

Mike.

[jhsa]

Thanks Mike.. will need a picture..
Question, you remove them from the mixer then?
Thanks
João

[ReSt]

Thanks

btw. would it be possible to get the timer fields of minutes and seconds back as two separate fields that can be set independantly ?

In the moment it just takes some time if you want to set a timer from 0 to 10 minutes or from 8 minutes back to 4

Reinhard

[jhsa]

No it doesn't.. we are preparing a manual for you

Press and hold menu and then use the directional keys to adjust the timer.. it will change the time in steps of 1 minute
From 8 to 4 it takes 4 clicks.. If you have an encoder is even faster
João

[MikeB]

That's a general change for editing most fields. Press and hold MENU, then the change is in larger steps than 1, mostly 20, sometimes 100, and 60 for a timer.

Mike.

[jhsa]

One that I particular like, is the way we edit values in the fields where we can also select a GVAR, like the expo and rates.
The same procedure as described above for steps of 1 and 20, but then by holding the menu button a bit longer, if no directional key is pressed to edit the field, then it changes to the GVAR.. excellent

João

[ReSt]

O, that's really great

I didn't realize that function.


btw, something else that I didn't realize

What is the "Use Output" in the mixes for ?

Reinhard

[MikeB]

In a mix, if you select a channel (e.g. CH16), then the value of that channel BEFORE limits and safety switches is used. If you turn Use Output ON, then the value AFTER limits and safety is used.

Mike.

[jhsa]

It's the real channel output. Then when that option is on, CHx is replaced by OPx as source to the mix..

[jhsa]

Here is a little section of the new er9x manual. The mixer.. This will probably still have a few changes done to it.. But I'm posting it because of the "Use Output" explanation..
The new manual will be ready soon.. Me and Nigel are doing our best to release it as soon as possible..

João

[Daedalus66]

This is to report a bug in the Templates setup on the basic ER9x for the m64. The version is the test released Jan 25.

The new Template menu item in Model Setup works fine in my m128 9XR, but in the m64 9x, the menu references are displaced. The Safety Switches item gets Templates, the GVARS item gets Safety Switches , etc.until the blank at the bottom gets Protocol.

V1. 3048-Mike, 25.01.2015, 22:34:18, er9x-r817

[MikeB]

This is added via conditional compilation. I first made it conditional on having a '128 (or '2561) processor, then realised it could be on whether templates are enabled. I missed one condition that is still '128.
Will be fixed shortly.

Mike.

[ReSt]

Thanks for the explanation of the "use Output" option

Found a small bug editing a mix, when stepping through the sources with "use Output = ON"

It shows the sequence: PPM1 .... PPM7 OPM8 OP1 .....OP15 CH16

the OPxx options are offset by one position (to early).

"PPM8" is overlayed with "OP" and the output channels count OP0 to OP15 instead of OP1 to OP16

Reinhard

[jhsa]

Confirmed on m128.. Good catch

João

[MikeB]

Fixing, I see it's on ersky9x as well (same code!).

Mike.

[MikeB]

After some thought, it seems that having a default idle position that may be set to +100% is not as safe as it might be. This might be set by mistake, so I've removed that option, but added the option of setting throttle reverse on a per model basis, instead of in the general settings.

At the moment, I've removed the setting in the general settings, so if you want throttle reverse you have to set it in each model.
Should we have the general setting as well, then reverse the throttle if either the general setting is ON or the model setting is ON?

Mike.

[jhsa]

You mean people could choose their standard throttle direction, and then reverse the standard also in every model if required? that sounds reasonable without giving it a good thought..

João

[LTMNO]

Assuming you have used the serial interface to transfer files, just connect up in the same way.
It looks like your batch file is correct for using this.
I use eepe, I configure the burn|configure menu as:
Programmer - arduino
mcu m328p
Port - com3 (yours may be different)
Extra Arguments -b 38400

Then just use the "Flash Firmware to Tx" button.

Mike.

Thanks Mike, didn't think about using eepe.. I need to open my radio and expose the programming interface and pull out my trusty cable I built back in the day for the Hans Board.

Oh Nostalgia...

Cheers.

[LTMNO]

Alright, I was a little delayed today.. but was able to get the radio apart and ready for soldering.
Just to confirm... I always like to check twice, three times before commit.

So apparently I have been using the Pin7 and Pin8 on the MegaSound connected to my Mini-Stereo-Jack Connector as follows:


And when I wanted to add files to the SDCard I just use my FTDI Adapter and connecting Rx/Tx/GND I am able to upload the files.

From reading previous thread on RS232 Serial Interface connections it says to use Pin7 and Pin8 on MegaSound. ( Confusing )

Right now, the Pins 5 & 6 are free and I was assuming I can connect these to the M128 Chip?


Pin5 and Pin6 on the MegaSound need to be connected to :



Am I correct?
Can I follow thru on this?

Thanks?

[LTMNO]

Based on this.. was I right?


Pin 5&6 to PC
Pin 7&8 to M128

[KAL]

Pin 5 and 6 to PC only if you have a real rs232 device (not TTL).
For FTDI you have to use Pin 7 and 8 for both PC and m64 (128/2561).

Klaus

[LTMNO]

Thanks KAL, so does this mean I can have both connected at the same time when using EEPE via my Mini_Stereo_Connector.
eepe is handling where and what to do? or I assume when you boot into Bootloader... that takes one path vs the other?

If so,
Pin7 to Tx (Pin28)
Pin8 to Rx (Pin27)

[KAL]

Yes,

Pin7 to Tx (Pin28)
Pin8 to Rx (Pin27)

The only thing is to power up the 9X with either open throttle or a wrong set switch.
Pin27 and Pin28 are connected to the left vertical trims and this trim settings may be
altered while data ist send from PC to megasound. The "error state" prevents this.

...eepe is handling where and what to do? ...

It's not eepe. As far as I see it's megasound which knows what to do ...

Klaus

[LTMNO]

Coolbeans, i will commence the soldering after 8pm as the kids are home and my time is gone... back at 8pm EST to finish the job.

Cheers!

[LTMNO]

I thought I would post this link here instead of retyping the post.. but my findings from testing M128 connected to Pin7 and Pin8 on the MegaSounds along side of the FTDI Adapter for Serial Connectivity does not work as expected to...

viewtopic.php?f=5&t=948&p=92247#p92247

[MikeB]

If you look at the circuit above, you will see that pin 7 is connected to the processor via (schottky) diode D1. You could try connecting your FTDI signal via another diode, rather than connecting directly to pin 7, or connect the processor pin 28 via another diode.

So, connect another diode to the processor side of D2, and the free end to one of your signals. My original design had this as a third serial connection for logic level inputs.

Mike.