openrcforums

I find difficult you have been able to write an empty file in taranis drive.... (FAT is read only)

Anyway we try to overwrite taranis.bin file
so you need to have write access to the drive and to the file.

Thanks Rob, I've got the code. Where can I find the default build options for the Taranis as well as the generic build instructions, or are there any? Could this info be added to the CompilationOptions Wiki page? If there is any build instructions, I have not found them. There are however build ins...

If mass storage is visible, it means that radio is turned on... consequently DFU is not visible.... you need to connect the radio turned off to upgrade/read the firmware. I clearly written in the online manual: http://code.google.com/p/opentx/wiki/OpenTx_FrSky_EN#Basic_concepts An important thing to...

Do you have many drives (disk / cdrom / usbpens and so on ??)
The only possibility, in my opinion, is that it's loosing time in enumerating drives

May you write me the exact error you get when eeprom does not appears ?

the problem is how do you mount taranis eeprom drive.
I suppose you need gksudo also for writing

You need to be sure that TARANIS drive is mounted...
so that you have a drive with TARANIS.BIN in..
If you have such a drive, try to copy TARANIS.BIN to some dir and see if you get some error from the OS

try from a terminal
mkdir /firmware
/opt/local/bin/dfu-util -a 0 --dfuse-address 0x08000000:524288 -d 0483:df11 -U /firmware/t.bin

For assembling my own packs soldering battery in line I use a soldering tip ad this one...

Try this command line: I see missing at least: EXT=FRSKY & SDCARD=YES make PCB=TARANIS EXT=FRSKY SDCARD=YES PPM_CENTER_ADJUSTABLE=YES FLIGHT_MODES=YES AUTOSWITCH=YES PPM_LIMITS_SYMETRICAL=YES AUTOSOURCE=YES DBLKEYS=YES HELI=YES TEMPLATES=YES PPM_UNIT=PERCENT_PREC1 GVARS=YES FAI=CHOICE TRANSLATIO...

http://code.google.com/p/opentx/source/detail?r=1

Only two years old and still growing...

Fixed in SVN: next release will be ok.

Yes really a lot of fuss for nothing:
http://www.ti.com/lit/ds/symlink/cc2500.pdf

Page 2

The controller is:
"Suited for systems compliant with EN 300 328 and EN 300 440 class 2 (Europe), FCC CFR47 Part 15 (US), and ARIB STD-T66 (Japan)"

custom function left there from previous try...
the idea was to avoid "seconds" using a gvar decreased every second,,

Committed, if --print is on command line c9x will exit

you need libusb devel

the curves are saved in the temporary folder but: the name will be the same for all.
About displaying the pdf: any browser can display a pdf maybe in a IFRAME

For the images then is better in PDF mode.

Just use .pdf as extension.

I think there is something more.... if you try to do an eeprom decoder you will soon understood that there are at least 6 eeprom decoders to be implemented for each version of the eeprom, and keep them updated will be a mess. I have started implementing the print function, but it will be difficult t...

I will try to have a look...
maybe not so easy but maybe not so difficult...

fixed in SVN: next release will be there...

Thanks, next release will be ok...

fixed in svn, but please confirm that you only loose settings if editing the specific custom function
If the appear in simu they should be exported correctly.

Bill, A channel at rest stay at 0. In your original eeprom when the launch mode ended there was nothing driving the channel so it was at 0. While for a part like rudder or aileron this means: stay at rest for a ESC that normally means: RUN AT HALF SPEED . In one model I forced the channel at -100 an...

Is there any version of eepe working with taranis radio and OpenTX?
Have I missed something ?

wait how long is the pulse train ? 12ch=32.5ms as minimum

No we are experiencing issues on the fiber connection and for some reason backup server get not used...
Working on it...

maybe the problem is that you probably cannot write to the device...
either you are not member of dialout group...
so try to connect the radio:
then
sudo chmod 666 /dev/ttyACM0
try to read again, if we succeed we will find a more definitive solution

may you post the details reported in the read eeprom window ?

and also teh output (with the radio attached of

ls -asl /dev/ttyACM*