Advanced Search

Search by Keyword Keywords:

Search Options

Find Posts from

Sort Results by

Search at a specific date

Jump to Result Number

Search in Categories Also search in sub-categories

Search Results (Searched for: ppmin)

PhracturedBlue

16 Dec 2013 14:12

Replied by PhracturedBlue on topic Documentation Discussion

Documentation Discussion

Category: Development

'PPM In' is a new feature that probably requires more than just a couple sentences.
It has 2 uses:
1) It can be used for additional inputs. For instance, it was primarily requested by the FPV folks, who wanted to be able to control their camera motors from their headset (as you look around, the camera looks around) or at least that is my undersatnding of their use.

2) It is used to enable the transmitter to act as a Master in a buddy-box setup. Here the student configures his student for PPMOut, and the Instructor for PPMIn with a control switch. When the instructor has the switch set, the channels from the student replace those on the Tx. When the switch is cleared, the Instructor(Master) Tx resumes control

The settings hidden behind the button enable Deviation to be compatible with any other slave radio, enabling full control of the PPM speed and structure

kreidler

18 Nov 2013 21:01 - 18 Nov 2013 21:36

Replied by kreidler on topic Release 3.1.0 Screen Shots

Release 3.1.0 Screen Shots

Category: Development

kreidler wrote: 2. I already did the shots and will add them with next post.
3. Misunderstanding NOT protocol I meant PPMin Teacher mode. I will do the shots and add them to ModelSetup.

D10ModelSetup attached with 6 new screens. The Reset screen is not a real screen but in my opinion necessary to understand how to reset a model.

EDIT:

kreidler wrote: 1. Accessing like written before from rbe. I also never use this but through the main page config menu 1 to 4 you can open most or even all of them. New D10Menu.zip attached. I will go through the menus to see what is still missing. Name proposal D10ModelMenuStandard.zip

Now attached.

kreidler

18 Nov 2013 20:37

Replied by kreidler on topic Release 3.1.0 Screen Shots

Release 3.1.0 Screen Shots

Category: Development

WheresWaldo wrote:

I have never used Standard GUI so I will need to figure out two things, first how to enable it and then what screens are changed.

If there is a screen for it, we will need it. I tried to go through most of the GUI but obviously I have missed a few screens.

Some protocols do not have sub menus.

We can always add data where it explains a setting, but I wanted to get all the screenshots first and only used the default settings. The default on this screen is no data.

Yes.

1. Accessing like written before from rbe. I also never use this but through the main page config menu 1 to 4 you can open most or even all of them. New D10Menu.zip attached. I will go through the menus to see what is still missing. Name proposal D10ModelMenuStandard.zip
2. I already did the shots and will add them with next post.
3. Misunderstanding NOT protocol I meant PPMin Teacher mode. I will do the shots and add them to ModelSetup.
4. Understood. Please reconsider if one line might be helpful for all explanations.
5. Your turn

WheresWaldo

18 Nov 2013 13:11 - 18 Nov 2013 13:19

Replied by WheresWaldo on topic Release 3.1.0 Screen Shots

Release 3.1.0 Screen Shots

Category: Development

rbe2012 wrote: I will try this. I can take the picture from my Linux pc:

Thanks, is the mouse pointer really there on the Devo8 or should I remove it from the screenshot.

kreidler wrote: I do not have my Devo or the emu on hand yet. So, may be a bit confusing:

1. Even if I do not use the 'Standard GUI' there are no screenshots from this interface with the different sub screens included. So, ModelMenu.png should be renamed to ModelMenuAdvanced.png.

2. Adding ModelSetupCopy, ModelSetupReset and ModelSetupTemplate with a screenshot of the templates would be fine.

3. I am not sure, but some screens from PPMin like a sub screen with stick mode I cannot find.

4. On the TelemetryConfig at least one line with some input data would be helpful.

5. Do plan to show the channel monitor and telemetry monitor?

Waldo, if you want, I can add all during the next days?

I have never used Standard GUI so I will need to figure out two things, first how to enable it and then what screens are changed.
If there is a screen for it, we will need it. I tried to go through most of the GUI but obviously I have missed a few screens.
Some protocols do not have sub menus.
We can always add data where it explains a setting, but I wanted to get all the screenshots first and only used the default settings. The default on this screen is no data.
Yes.

Here is where my head is on this. The images should be of the default settings, the accompanying text should explain the options. If we try to use screenshots for every permutation then we might as well make a video rather than written documentation. Or do what Mikado does with the Vbar and have the docs as a series of HTML screen and web based only. I am open to all suggestions if we need a screen to clarify a complex setting.

I am not opposed to a web only version, it could easily lend itself to an epub version that could be sort of interactive. My big problem is that I am not good at all with HTML code.

kreidler

18 Nov 2013 08:59

Replied by kreidler on topic Release 3.1.0 Screen Shots

Release 3.1.0 Screen Shots

Category: Development

I do not have my Devo or the emu on hand yet. So, may be a bit confusing:

1. Even if I do not use the 'Standard GUI' there are no screenshots from this interface with the different sub screens included. So, ModelMenu.png should be renamed to ModelMenuAdvanced.png.

2. Adding ModelSetupCopy, ModelSetupReset and ModelSetupTemplate with a screenshot of the templates would be fine.

3. I am not sure, but some screens from PPMin like a sub screen with stick mode I cannot find.

4. On the TelemetryConfig at least one line with some input data would be helpful.

5. Do plan to show the channel monitor and telemetry monitor?

Waldo, if you want, I can add all during the next days?

SadSack

12 Nov 2013 11:32

Replied by SadSack on topic Openlrs

Openlrs

Category: Feedback & Questions

You have another options to connect OpenLRS to your TX. Transmit to it using either Spektrum or Turnigy/Flysky. Could use other RX as long as it outputs single PPM. I'd go for the Flysky and use this HERE
Which would free up your PPM on your Devo for head tracker. Deviation only has one PPMin or PPMout and not at the same time.

adabman

21 Jun 2013 18:47

Replied by adabman on topic VM dedicated to compiling Deviation

VM dedicated to compiling Deviation

Category: Tutorials

Thanks for helping. Some more info. I start from scratch for you to see:

In the VM:

Warning: Spoiler! [ Click to expand ]

RBE, can you please zip and post the 2 dfu files for your built version 9a3467 and i will byte compare them with my 9a3467 build.

PhracturedBlue

12 Jun 2013 15:29

Replied by PhracturedBlue on topic Possible to control DEVO 10 using PC via USB?

Possible to control DEVO 10 using PC via USB?

Category: Development

There is PPMIn as FDR mentioned. so you could use your audio-out headphone jack to generate a PWM signal that gets read into Deviation as a signal. That is supported (though I don't know if such an audio program exists for the PC)
Currently the code works by converting the Tx pin to work as an input for the PWM signal. The reason is that on the Devo8, the Rx pin is not connected to the audio jack. I believe the Devo10 is different in this regard though.

PhracturedBlue

12 Jun 2013 14:20

Replied by PhracturedBlue on topic Possible to control DEVO 10 using PC via USB?

Possible to control DEVO 10 using PC via USB?

Category: Development

No FDR is right, I have no idea what I was thinking. Of course you can't send commands via the UART today. My mind seems to be in the cloud. Sorry for getting your hopes up.
Still, it should be possible to transmit via the HID interface I just set up by extending its definition and hooking into the ppmin code.

ymboc

11 Jun 2013 18:00 - 11 Jun 2013 18:03

Replied by ymboc on topic Build instructions

Build instructions

Category: Development

I'm running into a bit of difficulty building from sources.

On Ubuntu 12.04, I installed the following additional packages to (hopefully) setup the build environment (apt-get install'd):

gcc-arm-none-eabi (from the ppa referenced at github.com/esden/summon-arm-toolchain )
alibfltk1.3 libportaudio2
libnewlib-dev libnewlib0 newlib-source
mingw32 mingw32-binutils mingw32-runtime

I'm getting a "hubsan_a7105.c:(.text.initialize+0x1a0): undefined reference to `rand'" error in function 'initialize'.

Which leads me to believe I may a misconfigured build environment...

Can someone offer a gentle nudge in the right direction?

Complete make command line output in Spoiler below:

Warning: Spoiler! [ Click to expand ]

user@host:~/deviation/src$ make TARGET=devo7e
 + Compiling 'target/devo7e/backlight.c'
 + Compiling 'target/devo7e/channels.c'
 + Compiling 'target/devo7e/crc.c'
 + Compiling 'target/devo7e/lcd.c'
 + Compiling 'target/devo7e/tx_buttons.c'
 + Compiling 'target/common_devo/adc.c'
 + Compiling 'target/common_devo/clock.c'
 + Compiling 'target/common_devo/dump_bootloader.c'
 + Compiling 'target/common_devo/err_handler.c'
 + Compiling 'target/common_devo/errno.c'
 + Compiling 'target/common_devo/fgets.c'
 + Compiling 'target/common_devo/haptic.c'
 + Compiling 'target/common_devo/iwdg.c'
 + Compiling 'target/common_devo/petit_fat.c'
 + Compiling 'target/common_devo/petit_io.c'
 + Compiling 'target/common_devo/power.c'
 + Compiling 'target/common_devo/ppmin.c'
 + Compiling 'target/common_devo/printf.c'
 + Compiling 'target/common_devo/proto_stubs.c'
 + Compiling 'target/common_devo/sound.c'
 + Compiling 'target/common_devo/spi_flash.c'
 + Compiling 'target/common_devo/spi_proto.c'
 + Compiling 'target/common_devo/spi_touch.c'
 + Compiling 'target/common_devo/syscalls.c'
 + Compiling 'target/common_devo/tx_misc.c'
 + Compiling 'target/common_devo/uart.c'
 + Compiling 'target/common_devo/msc2/hw_config.c'
 + Compiling 'target/common_devo/msc2/mass_mal.c'
 + Compiling 'target/common_devo/msc2/memory.c'
 + Compiling 'target/common_devo/msc2/scsi_data.c'
 + Compiling 'target/common_devo/msc2/usb_bot.c'
 + Compiling 'target/common_devo/msc2/usb_desc.c'
 + Compiling 'target/common_devo/msc2/usb_devo8.c'
 + Compiling 'target/common_devo/msc2/usb_endp.c'
 + Compiling 'target/common_devo/msc2/usb_istr.c'
 + Compiling 'target/common_devo/msc2/usb_prop.c'
 + Compiling 'target/common_devo/msc2/usb_pwr.c'
 + Compiling 'target/common_devo/msc2/usb_scsi.c'
 + Compiling 'target/common_devo/msc2/lib/core_cm3.c'
 + Compiling 'target/common_devo/msc2/lib/stm32f10x_flash.c'
 + Compiling 'target/common_devo/msc2/lib/stm32f10x_gpio.c'
 + Compiling 'target/common_devo/msc2/lib/stm32f10x_misc.c'
 + Compiling 'target/common_devo/msc2/lib/stm32f10x_rcc.c'
 + Compiling 'target/common_devo/msc2/lib/usb_core.c'
 + Compiling 'target/common_devo/msc2/lib/usb_init.c'
 + Compiling 'target/common_devo/msc2/lib/usb_int.c'
 + Compiling 'target/common_devo/msc2/lib/usb_mem.c'
 + Compiling 'target/common_devo/msc2/lib/usb_regs.c'
 + Compiling 'target/common_devo/msc2/lib/usb_sil.c'
 + Compiling 'autodimmer.c'
 + Compiling 'battery.c'
 + Compiling 'buttons.c'
 + Compiling 'curves.c'
 + Compiling 'inputs.c'
 + Compiling 'main.c'
 + Compiling 'misc.c'
 + Compiling 'mixer.c'
 + Compiling 'mixer_standard.c'
 + Compiling 'music.c'
 + Compiling 'telemetry.c'
 + Compiling 'timer.c'
 + Compiling 'version.c'
 + Compiling 'screen/lcd_gfx.c'
 + Compiling 'screen/lcd_string.c'
 + Compiling 'screen/128x64x1/lcd_screen.c'
 + Compiling 'screen/128x64x1/usblogo.c'
 + Compiling 'gui/bargraph.c'
 + Compiling 'gui/button.c'
 + Compiling 'gui/dialog.c'
 + Compiling 'gui/gui.c'
 + Compiling 'gui/image.c'
 + Compiling 'gui/keyboard.c'
 + Compiling 'gui/label.c'
 + Compiling 'gui/listbox.c'
 + Compiling 'gui/rect.c'
 + Compiling 'gui/scrollable.c'
 + Compiling 'gui/scrollbar.c'
 + Compiling 'gui/textsel.c'
 + Compiling 'gui/xygraph.c'
 + Compiling 'pages/128x64x1/about_page.c'
 + Compiling 'pages/128x64x1/chantest_page.c'
 + Compiling 'pages/128x64x1/dialogs.c'
 + Compiling 'pages/128x64x1/lang_select.c'
 + Compiling 'pages/128x64x1/main_config.c'
 + Compiling 'pages/128x64x1/main_page.c'
 + Compiling 'pages/128x64x1/menus.c'
 + Compiling 'pages/128x64x1/model_config.c'
 + Compiling 'pages/128x64x1/model_loadsave.c'
 + Compiling 'pages/128x64x1/model_page.c'
 + Compiling 'pages/128x64x1/pages.c'
 + Compiling 'pages/128x64x1/reorder_list.c'
 + Compiling 'pages/128x64x1/splash_page.c'
 + Compiling 'pages/128x64x1/telemconfig_page.c'
 + Compiling 'pages/128x64x1/telemtest_page.c'
 + Compiling 'pages/128x64x1/timer_page.c'
 + Compiling 'pages/128x64x1/toggle_select.c'
 + Compiling 'pages/128x64x1/trim_page.c'
 + Compiling 'pages/128x64x1/tx_configure.c'
 + Compiling 'pages/128x64x1/usb_page.c'
 + Compiling 'config/display.c'
 + Compiling 'config/ini.c'
 + Compiling 'config/language.c'
 + Compiling 'config/model.c'
 + Compiling 'config/tx.c'
 + Compiling 'protocol/protocol.c'
 + Compiling 'pages/128x64x1/standard/common_standard.c'
 + Compiling 'pages/128x64x1/standard/curves_page.c'
 + Compiling 'pages/128x64x1/standard/drexp_page.c'
 + Compiling 'pages/128x64x1/standard/failsafe_page.c'
 + Compiling 'pages/128x64x1/standard/gyrosense_page.c'
 + Compiling 'pages/128x64x1/standard/reverse_page.c'
 + Compiling 'pages/128x64x1/standard/subtrim_page.c'
 + Compiling 'pages/128x64x1/standard/swash_page.c'
 + Compiling 'pages/128x64x1/standard/switchassign_page.c'
 + Compiling 'pages/128x64x1/standard/throhold_page.c'
 + Compiling 'pages/128x64x1/standard/traveladj_page.c'
 + Compiling 'pages/128x64x1/advanced/mixer_curves.c'
 + Compiling 'pages/128x64x1/advanced/mixer_limits.c'
 + Compiling 'pages/128x64x1/advanced/mixer_page.c'
 + Compiling 'pages/128x64x1/advanced/mixer_setup.c'
  UPDATING HEADERS
  BUILD   lib/stm32/f1
  CP      libopencm3_stm32f1.ld
  CC      rcc.o
  CC      gpio.o
  CC      usart.o
  CC      adc.o
  CC      spi.o
  CC      flash.o
  CC      rtc.o
  CC      i2c.o
  CC      dma.o
  CC      exti.o
  CC      ethernet.o
  CC      usb_f103.o
  CC      usb.o
  CC      usb_control.o
  CC      usb_standard.o
  CC      can.o
  CC      timer.o
  CC      usb_f107.o
  CC      desig.o
  CC      crc.o
  CC      dac.o
  CC      iwdg.o
  CC      pwr.o
  CC      usb_fx07_common.o
  CC      gpio_common_all.o
  CC      vector.o
  CC      systick.o
  CC      scb.o
  CC      nvic.o
  CC      assert.o
  AR      libopencm3_stm32f1.a
 + Building 'devo7e.elf'
 + Optimizing placement and re-linking
ROM: 0x08003000 - 0x0801f8e0 = 114.22kB
RAM: 0x20000000 - 0x2000279c =   9.90kB
Found 12 ranges
Found 16 ranges
Found 1 ranges
 + Copying template files for devo7e
 + Checking string list length for devo7e
 + Compiling 'protocol/devo.c'
 + Compiling 'target/common_devo/protocol/a7105.c'
 + Compiling 'target/common_devo/protocol/cc2500.c'
 + Compiling 'target/common_devo/protocol/cyrf6936.c'
 + Compiling 'target/common_devo/protocol/nrf24l01.c'
 + Compiling 'target/common_devo/protocol/pwm.c'
 + Building 'objs/devo7e/devo.bin'
Building devo module
 + Compiling 'protocol/dsm2.c'
 + Building 'objs/devo7e/dsm2.bin'
Building dsm2 module
Building dsmx module
 + Compiling 'protocol/flysky_a7105.c'
 + Building 'objs/devo7e/flysky_a7105.bin'
Building flysky module
 + Compiling 'protocol/hubsan_a7105.c'
 + Building 'objs/devo7e/hubsan_a7105.bin'
objs/devo7e/hubsan_a7105.o: In function `initialize':
hubsan_a7105.c:(.text.initialize+0x1a0): undefined reference to `rand'
make: *** [objs/devo7e/hubsan_a7105.bin] Error 1

Wene001

15 May 2013 17:31 - 15 May 2013 17:55

Replied by Wene001 on topic devo 12 wide screen...

devo 12 wide screen...

Category: Development

good work rbe

but one thing i don´t like is the gap between the two middle columns in this view
Also it would be nice to have ppmin as input for the bars in the middle of my picture

PhracturedBlue

14 May 2013 18:51

Replied by PhracturedBlue on topic USB HID Joystick & PPM-In program

USB HID Joystick & PPM-In program

Category: Development

rbe2012 wrote: Good decision, I think. Better we have a working config where some values are constant defaults (=0?) than configs who are only valid under special conditions.
PB, must we have PPMin profiles? If you think about some kind of calibration for the inputs it will be different for the different tx. And such things as channel directions and allocation can differ too (e.g. WK vs. DX). I would appreciate to save the PPMin configuration separated from the model and include them in different model configs.

That is reasonable. We could use them for PPMOut too.
I need to think about how to implement it though. Using a full block for each profile is very wasteful, so that indicates using a single ini with all profiles in it. That can be done, but I need to figure out how to use the ini parser that way.
I'm not sure I want to save the profile name in the model though. It would be easier to just use it as a template and copy the values into the relevant PPMIn parameters. The downside is you couldn't know by looking at it which profile you had selected. I'll need to think about it some more.

rbe2012

14 May 2013 17:47 - 14 May 2013 17:47

Replied by rbe2012 on topic USB HID Joystick & PPM-In program

USB HID Joystick & PPM-In program

Category: Development

Good decision, I think. Better we have a working config where some values are constant defaults (=0?) than configs who are only valid under special conditions.
PB, must we have PPMin profiles? If you think about some kind of calibration for the inputs it will be different for the different tx. And such things as channel directions and allocation can differ too (e.g. WK vs. DX). I would appreciate to save the PPMin configuration separated from the model and include them in different model configs.

PhracturedBlue

14 May 2013 16:57 - 14 May 2013 16:58

Replied by PhracturedBlue on topic USB HID Joystick & PPM-In program

USB HID Joystick & PPM-In program

Category: Development

vlad_vy wrote: With any 'PPM In' choice (Channel, Stick, Extend) I can select PPMx as input for channel. Is it correct?

After further consideration, I've decided to leave it the way it is. There would be a bunch of complexity to only allow selecting PPM when it is active. I already have a similar case for the 'Ch' values. You can select up to 'Ch12' on the mixer regardless of how many channels are actually enabled. Maybe some day I'll rework it, but I don't think it is worth it right now.

Note that these values are not actually set (just like any 'Ch' value beyond the configured # of channels) when PPMIn is not in 'Extend' mode. So you can't use Extend and Train together.

PhracturedBlue

14 May 2013 14:17

Replied by PhracturedBlue on topic USB HID Joystick & PPM-In program

USB HID Joystick & PPM-In program

Category: Development

I also see the problem with Channel7 sometimes. It depends on how I configure the slave. I thought it was because I had my devo12 configured for more than 9 PPMOut channels, but perhaps not. I'll investigate further.

If you see values <-100 or >100, then the PPM configuration is probably wrong. As I mentioned somewhere above, we need to find a way to calibrate the PPMin. Each radio has different center and offsets, and if these are set wrong in the master, you won't get the proper values.

As for using PPM in the crosses, you should never use the ppmChannels variable.
Instead use:
MIXER_GetChannel(1 + NUM_INPUTS + NUM_OUT_CHANNELS + NUM_VIRT_CHANNELS + channel, 0);

We can add a macro so you don't need to do the math.

PhracturedBlue

13 May 2013 22:00

Replied by PhracturedBlue on topic USB HID Joystick & PPM-In program

USB HID Joystick & PPM-In program

Category: Development

You do not want to have ppmin as both a primary input and as a toggle-able input/output at the same time.

The 3rd mode is absolutely capable of implementing the 1st 2 modes. However it would be tedious to program all the mixers for it. Mode 1/2 are basically like templates to make it possible to quickly setup train mode. The alternative would be to actually do just that and create a few templates to make master-trainer mode easy to set up. I think the current solution is easier to use/understand though.

I'm not sure there is much value in having both mode 1 and 2, but the amount of additional code to support both is minimal. Most likely users will just choose one or the other depending on their needs. Once I have some mechanism to transfer models between Deviation transmitters, mode-1 may be more interesting as it would mean the trainee is flying in exactly the same way they would if they were solo.

Hexperience

13 May 2013 20:36

Replied by Hexperience on topic USB HID Joystick & PPM-In program

USB HID Joystick & PPM-In program

Category: Development

PhracturedBlue wrote: I added a 2nd train mode. You can now choose whether to apply the PPMin to mapped outputs, to mapped inputs, or as new inputs.
I think that will give sufficient flexibility to everyone, while keeping the effort to configure the trainer as easy as possible.

Right now, the settings are:
Train1 : Map PPM-In to output channels
Train2 : Replace stick inputs with PPM-In
Input : Create new inputs called 'PPMIn' that can be used in the mixers

These names are terrible and need to be changed. If anyone has any ideas for concise names for these modes, let me know.

Sorry guys... I know I'm missing something here, but if you have #2 and #3 above when would you ever use #1?

My brain keeps telling me there is some overlap here, but I can't put my finger on it.

PPM-in as an input should be available all the time, much like a virtual channel. There's no need to select it on or off?? (Unless it's simply to save CPU cycles somehow, but if it's not listed as an input in one of the mixers, it would never get polled would it?)

Trainer mode input could be configured at the TX level, but applied at the model level. So in the TX pages you set that PPMin1 = ELE channel (stick replacement only) and you are able to center it there. PPMin2 = AIL etc.
Also on this page you set the switch to use for trainer mode.

Then in the model config, you simply say if this model can be a trainer or not, and if it can, then when ever the switch is pulled, those PPMin inputs take over the sticks. If the trainer option is NOT on for a model, then all the PPMin inputs are available to the mixers... This is how it's done in er9x. Basically just 2 modes. Train (replace the sticks) or NOT Train, all PPMin available to the mixer.

Again... just putting thoughts down on "paper"...

Cheers!

PhracturedBlue

13 May 2013 04:11

Replied by PhracturedBlue on topic USB HID Joystick & PPM-In program

USB HID Joystick & PPM-In program

Category: Development

I added a 2nd train mode. You can now choose whether to apply the PPMin to mapped outputs, to mapped inputs, or as new inputs.
I think that will give sufficient flexibility to everyone, while keeping the effort to configure the trainer as easy as possible.

Right now, the settings are:
Train1 : Map PPM-In to output channels
Train2 : Replace stick inputs with PPM-In
Input : Create new inputs called 'PPMIn' that can be used in the mixers

These names are terrible and need to be changed. If anyone has any ideas for concise names for these modes, let me know.

PhracturedBlue

11 May 2013 15:10

Replied by PhracturedBlue on topic devo 12 wide screen...

devo 12 wide screen...

Category: Development

The new PPMin method we were discussing in the other thread would replace the stick-input with the PPM input. If we do that, then getting the main page to show the ppm-input would just-work.

Wene001

09 May 2013 20:26

Replied by Wene001 on topic devo 12 wide screen...

devo 12 wide screen...

Category: Development

bitbucket.org/PhracturedBlue/deviation/c...9e62830c02990c8cfb1a
Above is the code that i added to your model.c
i think if you have merged with b8bd2b then you have all the changes i made

it would be nice to see action on the bars of the mainscreen if we switch to the slave in trainer mode, like we could see it on the channel page.

If i configure PPMin to the mixer, all is fine, and i can see it on the bars of the mainscreen

Displaying 21 - 40 out of 57 results.

Time to create page: 1.422 seconds

Force desktop display

All Categories
News, Announcements and Feedback
- News & Announcements
- Feedback & Questions
Development
- Development
- Protocol Development
- Builds
General
- General Discussions
- Polls
- Tutorials
- Stock Firmware Help
- Marketplace
Model Configs, Templates, Skins
- Model Configs
- - Model Requests
- Model Icons
- - Color icons for DEVO 6, 8, 12
- - BW icons for DEVO 7E, 10, 12E
- - BW icons for DEVO F12E
- Model Templates
- Custom Layouts
- Custom Skins
- Translations