Ultimate LRS 1.06 updater

This page is about the open source version of the project (ULRS 1.06). It has very limited functionnalities and most users are using the ULRS 2.X version.


2014-09-02 07_01_16-Program Manager


Ultimate LRS is a free firmware for the HobbyKing OrangeRX modules and several others, including DIY modules. You’ll find more information on the project itself here.

Ultimate LRS updater is the PC software that allows to select and program the firmware on the devices.

Step-by-step instructions

  • Download the software and unzip it in any folder
  • Run ULRS_config.exe
  • Select the board type, RX or TX, and Version
  • If an internet connection is available, and all parameters are selected, the button will no longer be grayed
  • Click on “Upgrade firmware”
  • Remark : the firmware is released under GPL, source code is available here.


  • Mac users : you can run this software with ‘Parallels’
  • Windows 8 users : you may be blocked by SmartScreen, which will prevent execution of this software. This is a new feature in Windows 8 and I’ll check how to avoid it in the future (maybe by distributing the software via Windows store). In the meanwhile you can disable SmartScreen.
  • For now, all versions can be flashed on a 1W TC, but only the 1.04 RX beta will work with a 100mW RX. I’ll update the application to only show the working options.

Report a bug or request a feature

If you encounter any issue or would like to suggest a new feature, feel free to contact me.


  1. ggwarrier says:

    I am very new to these but decided to get my feet wet by changing firmware on OrangeRx (1w) to ULRS ver 1.06 using Transmit mode. I find the buzzer on continuous. Please help me resolve this or did something go wrong.

    • admin says:

      There’s a difference between version 1.X and versions 2.X : in version 1.X the TX buzzer will beep whenever the RX isn’t turned on. While with the 2.X the TX buzzer will beep but only after an initial connection with the RX, so it doesn’t beep just after programming for example.

  2. Ivan says:

    Do use your firmware is possible with modules rfm23bp 686 MHz? Thanks in advance for your reply

  3. dinoN17 says:

    Hi, thank you for your amazing works

    Since HK not sell orange openlrs anymore. any chance I can use your firmware for my DTFUHF deluxe TX and 1W hawkeye RX?


    • admin says:

      Hi Dino, unfortunately the DTFUHF / Hawkeye modules will not be supported. But there are several alternatives presented here :

  4. Orio says:

    When I fly often sounding the alarm moduleTX from the mean. “Beep..Beep” at intervals.
    But I can control it.

  5. Michail says:

    Hello I am using this software and works really well,
    I just want to ask if there is a way to set the frequency or if you know what is the default
    frequency used by the program because i want to make a custom antenna.

    • admin says:

      Hello, the 1.06 version runs on 435 mhz and two other very close channels.

      The beta version can select exactly the channels you want.

      • Michail says:

        Thank you for your helpfull reply.
        If i use the default 435 mhz its ok,
        but if i use beta version where do i set the frequency?

  6. Alex says:

    averdude.exe: ser_open(): can’t open device “\\.\COM12”
    What can be wrong?

    • admin says:

      Check that the port is not used by another software like mission planner, or reboot to be sure to close all ports.

    • Stevehr55 says:

      Hi Alex,

      Did you sort out the problem? I had it before too but then I reinstalled my ftdi drivers and made a few changes in the device manager. Now it all works.


  7. eot2 says:

    I just tested your software and the telemetry link worked really nicely. Thank you for this great work. Unfortunately the PPM signal is not working in my setup. I checked it with the scope and and the waveform dos not look correct as the ppm bursts are not simmilar. Are there any known issues?
    I used the firmware in your updater program. Is this the latest software? Have you any suggestion what’s wrong?
    Best regards

    • admin says:

      A new version is almost ready, however the current version was released 1,5 year ago and no user complained about PPM issues ? Can you send (benoit@joassart.com) me a picture of the PPM signal from your transmitter and the one from the ULRS ? Also confirm your TX brand and number of PPM channels ? Thank you !

      • Stevehr55 says:

        The issue could the brand of transmitter that you are using. I have a jr pcm9x and the output sequence is throttle->aeleron->pitch->yaw. If I am not mistaken, apm requires Pitch->Aeleron->throttle->yaw which is default futaba. You can remap the channels on mission planner, but failsafe in apm uses channel 3 which is normally the throttle channel but in this case it’s the pitch channel. So due to this, the apm will not arm the esc (from what I have tried but… esc calibration works…)….still trying to find a way around this because I got it to work on my cc3d like a charm. Will keep you posted..

      • eot2 says:

        Sorry, that I haven’t responded for such a long time. As suggested the problem was the number of the PPM channels I’ve used. I’m using a 7 CH transmitter and the code was written for 8 channels only. Unfortunately, I’m using a clone of the Flytron 1W TX 100mW RX link so I could not use the new software as well. Due to this I have built a workaround with a 7 to 8 channel PPM adapter. I’ve implemented it on an Arduino Nano and it works pretty good.
        Thank you for your help,
        Best regards

  8. Ricardo says:

    Keep having the “avrdude.exe cant open device. COM24…” tryed the right drivers with an FTDI, arduino as FTDI and arduino as USBASB none works. i was able to get them communicating 6 months ago but now i wanted to update them and i cant. i also cant use it on Pixhawk because it doesnt connect to the mission planner. they seem blocked, but if both arent connected to power the other beeps

    • admin says:

      Sorry I can’t help much with FTDI & drivers issues. Try to get it working first simply with Arduino, and try to find your FTDI original drivers ?

Leave a Reply

Your email address will not be published. Required fields are marked *