Taranis full ?

[nicholgd]

Hi,
I think I have filled up my Taranis. I have just added another model to my Taranis and now on switch on I now get a "EEPROM WARNING" "Eeprom low mem " screen and "EPROM over Flow" warnings.
I'm a bit surprised in these days of Gigabyts for memory . The first page of model set up shows 0 bytes free.
I have used Mikes (Rcsoar) F3F set-up for 15 models which uses 1400 bytes per model
another 14 simple models ( planks and RE gliders ) use 400 bytes per model plus 5 or 6 test models about 500 bytes.
I was hoping to use some duplicate model setups to try out different configurations .
One reason I switched from my old JR 9X2 was that I had used up most of its 30 memories.
So now I’ve come up against the same limitation.
I know I can copy models to / from the SD card , but I just know I'm going to over write something vital eventually doing that.
So is it possible to upgrade the eeprom memory?

P.S I've still got to add my Opus VDS

Geoff

[MikeB]

For whatever reason, FrSky only fitted a 32K EEPROM, after providing early prototypes with 64K. I always thought this was a bit limited, having got used to the SKY board that has 512K.
So, even with the compression used, you are only getting 29 useable model memories. Clearly 60 (which came from the SKY board version) is a bit optimistic for complex models.

Mike.

[nicholgd]

I take it that the eeprom is not socketed and has lots of tiny legs ?

[MikeB]

No and 8 (legs).
The firmware, as standard, only knows about 32K though.

Mike.

[nicholgd]

Would it take much for it to see 64k? .Eight legs might be do able.

[Kilrah]

Not much, but it's 8 very tiny legs i.e. 0.5mm pitch.

The most surprising here is 15 full house gliders!

[tilmanb]

It's a bit of a anachronism in the firmware. It does not (yet) use the SD cars for storage of models.
I suppose sooner or later that will have to be changed. File a issue in github for a feature request I would say. Should be done eventually anyway

[Kilrah]

Storage of "active" models on SD may never be implemented for the simple reason that in case of an issue causing an unexpected reboot in flight the SD card is not mounted, and thus the model data could not be reloaded causing a control loss.

Improvement of how model copy to/from SD is handled could be possible though.

[MikeB]

Not totally convinced to using the SD card. I wouldn't like to arrive at the flying field, then discover I couldn't fly because the SD card wasn't working due to the SD card connector failing, which might happen due to mechanical vibration etc.

Mike.

[jhsa]

you don't have to store the active model
Do like ersky9x. backup the models to the card and then restore to an empty slot when necessary.. it's a wonderful feature.. Sharing the model between 2 radios via bluetooth would be the icing on the cake Sorry the last bit was off topic

João

[nicholgd]

If I start backing up and restoring models I can guarantee that the model I overwrite will be the one I trimmed to perfection during the last flying session and forgot to back up.
Perhaps a option or reminder when you delete a model "Do you wish to backup the model before deleting it?" Would help.

[mpjf01]

Why not just get another Taranis?

[nicholgd]

Guess who would take the wrong transmitter up the hill. Most of the slopes here are a 15 -20 minute steep walk. Taranis has over 60 model memories but only if they are simple 4 channel models. Not all my models require the full f3f template but it makes things easier if they are all programmed the same way.

[Kilrah]

Note that on 2.0 you can backup and restore the entire EEPROM with one button press and without PC. You could have 2 model sets on the card and load the one you need.

Taranis has over 60 model memories but only if they are simple 4 channel models.

A typical 7 channel model I have (airplane with flaps, retracts and camera with head tracking in my case) with dual rates, sticky throttle cut, model image, 2 flight modes, a few custom switches and SFs for warnings and voice announcements, telemetry configured with a custom screen takes 502 bytes. I.e. 60 of those would fit.
I have 23 models on the radio of all types mixed, the biggest is 716 bytes, and with 10kB used in total the average per model is around 400.

F3F models are a particular case, 15 of them even more so, and the template has pretty much all you could think of i.e. most models will not use everything that's in there at the same time.

[kalle123]

I posted that information in a German forum.

Nice idea, and sorry for the German text, but the pictures are there ...

Far better then soldering that tiny EEPROM

http://fpv-community.de/showthread.php? ... r-SD-Karte

[nicholgd]

Think I will look into a F3F LITE template. Not all my models need the full f3f facilities but I do like to have all the full house models programed the same way. The more I'm becoming familiar with the in-flight adjustments the more I'm using them.
Backing up the EEPROM sounds interesting,I was putting off moving to 2.0 I was not looking forward to checking out all the models. Possibly have to reconsider.
I've done some housekeeping and now have 4000 bytes free.