Ultimate 7e-256k builds

new builds are up guys, but looking at things there hasn't been any actual code changes (the only commits were protocol descriptions) since silpstream did the last builds (thanks again for volunteering bud ) so there is no point in updating your tx's this time round, with that in mind i've not updated the op

Edit 2: Well I dont know whos build it is (65ec105) but I have all switches and pots functioning and I have FrSky-X!!! So freaking cool! I just came in from flying (albiet for 2 minutes) my mini-tri with my mini transmitter (without buddy-boxing threw my X9E or D10 mind you)! This community is so awesome!

Gentlemen,
What would it take to get HexFet's FrSky-X build into the U7E? I've finally gotten around to throwing a CC2500 into my U7E and tho it's working great for D series FrSky receivers I'd really like to actually start using my 7E again to fly my mini tricopter and it's an X4R (and cant be swapped to a D4R because of the serial port configuration it's FC is running).


Haven't updated in a while so I'm gonna go ahead and load the most recent build tonight, the 7E will still get use (it's delegated to my wife's plane mostly) but I'd really be happy if it was atleast in the works... How many other people do we need to ask for the same thing before it gets bumped up in priority?


Edit: I see Hexfet has a 256k 7E build of his FrSky-X build but it doesnt include the extra switchs / pots. Maybe I'll request he include that code instead of you guys include his code. Either way I'll be a happy camper!

Edit: This problem is solved, for some reason adding the " extra-switches = nostock" line to my existing HW.ini file didnt work, deleting it and replacing the file did work though so I'm g2g, just need me some FrSky-X.

BTW what happened to the protocol directory the stock 7E requires? Has that been gone since the beginning?


Hey guys, sorry for 2 posts in a row.

So I've just updated and I lost the use of all 4 extra 3-way switches (A - D) and what's strange is in the input monitor Hold and Fmode are both showing again tho NONE show ANY movement, neither of the stock switches (which are obviously gone) nor SWA - SWD. The Pots however do function fine.


I cant revert as computer problems over the past month mean no saved copy of whatever build I had on there last when it all worked.

glad to see your sorted bud, and yeah as the u7e has more space the protocols are compiled into the firmware like most other devo tx's, so there's no longer any need to build the protocols as modules and store them on the flash, hence no protocols folder

Hi guys I also still enjoy very much my ultimate and switches, I am currently running this firmware from Goebish;
www.deviationtx.com/forum/protocol-devel...-it4?start=280#52530
(It also has AFHDS 2A test build)

Next step would be to add the voice module is it included in the Utimate 7e, any news here ? wa salo some discussion connecting it to another pin, to save the ppm port.

Hi guys, running 65ec105

I had a MAJOR problem today that my tx got stuck in USB mode (at the field when I was flying) and when I finally got home and plugged it into my computer my computer popped up and said it HAD to be formatted before it could be used...


I had been flying for about 27 minutes (3 batteries, but tx left powred at model battery swaps) all perfect, I had been datalogging and was just about to try a long range flight so I wanted to quickly test my failsafe. I held the model, throttled up so it thought it was flying and switched the Tx off [the models FS functioned perfect] so I went to switch the u7e back on and that's when the USB icon was on screen and nothing I did changed that. I even unplugged the battery for about 2 hours and tried again and it was still stuck in that state and then when I got home my computer said what I put above.


Luckily I had another tx with me and luckily it happened when it did. I'm positive it had something to do with datalogging as I had been changing settings there immediately before that flying session. unfortunately all logged data was lost in the format.

that doesn't sound good! I wonder if you ran out of space on the flash, or if a read/write error corrupted the file table or something different altogether? I'll see if I can trigger the same error and I'll post back

I dont think I ran out of space, not sure how fast it should fill up but less than 10 min before I still had 16k bytes left and all I was logging only 4 parameters:

Enable with SW C1
rate 1Sec
Select none
Timer 1 on
TelemRSSI on
TelemVAmp on


This is on FrSky-X protocol

HappyHarry wrote: as always if you find any bugs post them on the bugtracker here >>

Deviation Bug Tracker

Where ?

Update on my issue above: it happened AGAIN!

Still a large number of bytes left for logging, logging same parameters too. I did notice both times my battery was under 5v however not low enough to sound / give me a warning (above 4.8 where I have my alarm set) so I know it's not simply dying.


I have not reformatted yet as I'm hoping for a way to recover the log file. If it was an actual SD card I'm confident I could access and save (and repair if necessary) the file but being as how my computer refuses to do anything other than format I'm not sure what steps to take.
Can anyone help me with that?

this doesn't sound good, I've not managed to reproduce it but I'll try again. does it only happen when you power off the tx while logging data?

for revovering the data on the drive i'd try using linux and something like photorec/testdisk and see if that can repair/read the partition.

HappyHarry wrote: does it only happen when you power off the tx while logging data?.

Yes


Silpstream could you do me a newer build (an update to 65ec105)?

I think this is a file writing issue, the tx is writing to the flash when you turn off the tx and this corrupts the fat table, one of the devs will have to look at the logging code and add in a way to tell it to stop writing when the shutdown signal is sent.

as for a new build there has been no real additions to the codebase to warrant a new build bud (only a channel expansion to an little used protocol), hence why I've not updated my builds

there were some new protocols added to the nightly so i've updated the build, the link is in the first post

this build includes silpstreams most recent fixes for the switchmods code which are currently waiting in the pull request queue on top of tonights nightly. additions to this nightly build include the protocol for the eachine E010, the protocol for the FQ777-124 with the ssv7241 rf chip, as well as the addition to the hubsan protocol to support the h301.

enjoy

HappyHarry wrote: there were some new protocols added to the nightly so i've updated the build, the link is in the first post

this build includes silpstreams most recent fixes for the switchmods code which are currently waiting in the pull request queue on top of tonights nightly. additions to this nightly build include the protocol for the eachine E010, the protocol for the FQ777-124 with the ssv7241 rf chip, as well as the addition to the hubsan protocol to support the h301.

enjoy

Thanks HH!
But I can't find 'protocol' directory in zip file.

no probs bud as the u7e has more space on the mcu it doesn't require the protocols to be built as modules and stored on the flash, so there is no need for the protocols folder

HappyHarry wrote: no probs bud as the u7e has more space on the mcu it doesn't require the protocols to be built as modules and stored on the flash, so there is no need for the protocols folder

No wonder!
Thanks for explanation.

Hi again gentlemen.

In my 7e builds I can't hold rt/Lt or up/dn to have it roll threw menus / selections continously, I have to press the button one time for each step I take. I thought this was strange but I couldn't remember for sure. I used my 10 yesterday and set up a new model and had lots of menus to navigate and it rolls threw every selection just fine.

Is the lack of scrolling by design or a bug?

it works ok for me bud, long press scrolls through the options on all screens i tried. is anyone else having this issue?