RCGRS MRT Wiki - User contributions [en]

Revolution Radio Control

2026-03-15T07:49:33Z

EricTimberlake: /* Tools */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Unlike WiFi, instead of you deciding on the SSID/password credentials, the nodes being link figure all that crypto key data transparently for you. Once linked, we have a point to point data link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools to Update Firmware and Sound Files =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading Fw using Parallels Windows 11 virtual machine on an Apple M1 laptop]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking") ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

<big>The link button has '''DUAL FUNCTIONALITY'''. A '''''very short''''' press doesn't do anything. A '''''medium''''' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. As you are pressing and holding the decoder link button, watch the decoder LED. After 1/2 second of pressing the link button, it will flash quickly, KEEP pressing the link button for approximately 4-5 seconds and it shifts into FW update mode. The LED will blink much slower and upon release of the link button you should be able to see the transfer progress updating in the "PC Software v1.1" window.</big>

The USB Device Programmer red LED should still be blinking at a fast pace while the file transfer is in progress.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===
[[File:Throttle update dialog.jpeg|300px|thumb|right|Throttle FW update confirmation dialog (LONG PRESS)]][[File:Revolution throttle update status.jpeg|300px|thumb|right|Revolution throttle FW update status]]

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T07:44:18Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Unlike WiFi, instead of you deciding on the SSID/password credentials, the nodes being link figure all that crypto key data transparently for you. Once linked, we have a point to point data link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading Fw using Parallels Windows 11 virtual machine on an Apple M1 laptop]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking") ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

<big>The link button has '''DUAL FUNCTIONALITY'''. A '''''very short''''' press doesn't do anything. A '''''medium''''' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. As you are pressing and holding the decoder link button, watch the decoder LED. After 1/2 second of pressing the link button, it will flash quickly, KEEP pressing the link button for approximately 4-5 seconds and it shifts into FW update mode. The LED will blink much slower and upon release of the link button you should be able to see the transfer progress updating in the "PC Software v1.1" window.</big>

The USB Device Programmer red LED should still be blinking at a fast pace while the file transfer is in progress.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===
[[File:Throttle update dialog.jpeg|300px|thumb|right|Throttle FW update confirmation dialog (LONG PRESS)]][[File:Revolution throttle update status.jpeg|300px|thumb|right|Revolution throttle FW update status]]

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T07:25:40Z

EricTimberlake: /* Bluetooth */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Unlike WiFi, instead of you deciding on the SSID/password credentials, the nodes being link figure all that crypto key data transparently for you. Once linked, we have a point to point data link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading Fw using Parallels Windows 11 virtual machine on an Apple M1 laptop]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

<big>The link button has '''DUAL FUNCTIONALITY'''. A '''''very short''''' press doesn't do anything. A '''''medium''''' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. As you are pressing and holding the decoder link button, watch the decoder LED. After 1/2 second of pressing the link button, it will flash quickly, KEEP pressing the link button for approximately 4-5 seconds and it shifts into FW update mode. The LED will blink much slower and upon release of the link button you should be able to see the transfer progress updating in the "PC Software v1.1" window.</big>

The USB Device Programmer red LED should still be blinking at a fast pace while the file transfer is in progress.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===
[[File:Throttle update dialog.jpeg|300px|thumb|right|Throttle FW update confirmation dialog (LONG PRESS)]][[File:Revolution throttle update status.jpeg|300px|thumb|right|Revolution throttle FW update status]]

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

User talk:EricTimberlake

2026-03-15T07:09:18Z

EricTimberlake:

Should be all up to date now! -ET-

Eric,
Some minor changes:
*“Zigbee Network” link (http://zigbeehttps//en.wikipedia.org/wiki/Zigbee) does not work.
*Can you provide more specific links to the download files for the Revolution
*What is the “correct” USB adapter? And why is it the “correct” one?
*I assume the “Goal” paragraph refers to your goal, not the readers. As you do research, you will add the results to this paragraph (or elsewhere).
*The :USB programming adapter” link caused a download of a “revoprog.zip” file, which my MAC unzipped into “RevoProg.exe” dated 4 Dec, 2016. MACs running MacOs won’t run “.exe” files - they are Windows. Is it possible to get a “.jar” version (like a Java implementation) that will run on any OS? Also, I think people will be a bit cautous about downloading executable files. And it’s confusing to me how I would insert the downloaded adpater into a USB port. (Relates back to what a “correct” USB adapter is?)
*I opened and read part of the “Windows 11” page. The first thing that hit me was:

"'''Note: Windows 11 Installation Assistant doesn’t run on Arm-based PCs; it only works for x64 processors.'''"

But I noticed that you said you were running Windows on an Arm architecture MAC. So I looked at the next link (“Parallels”) and think I see the answer. It will cost $55 to install Parallels (my MAC is Arm-based). Then I can run the Windows apps (e.g., the “RevoProg.exe”) on my MAC. I’ll have to dig into this further. But to run just one app, it’s not very cost effective. I do have a Dell, running Windows. But I hated it too, and it has been sitting - unused - on my desk for almost 2 years now. The battery is probably really dead.
*I didn’t understand the rest of the paragraph - about “… getting the USB to passthrough…”.
*I obviously have not run the “PC Software”. So I don’t know what those LEDs are. I’m guessing they are on the USB Adpater that is connected to the computer through the dongle chord.
*Next I’m guessing the “Programmer Interface” (AKA: The USB Adapter?) will make a Bluetooth or WiFi connection to the desired device. How this automatically happens is a mystery to me, as I haven’t seen any “pairing” operations or WiFi login operations yet. Nor do I see a direct wire connection from the subject device to the “Programmer Interface”. So how is this happening?
*In “Updating the throttle”: It may “break” your throttle (not “brick”)?

So, with all that said, I really appreciate you putting this together and posting it. Hopefully, folks will get a big help from it.

User talk:EricTimberlake

2026-03-15T07:08:08Z

EricTimberlake: Reverted edits by EricTimberlake (talk) to last revision by DErik

Eric,
Some minor changes:
*“Zigbee Network” link (http://zigbeehttps//en.wikipedia.org/wiki/Zigbee) does not work.
*Can you provide more specific links to the download files for the Revolution
*What is the “correct” USB adapter? And why is it the “correct” one?
*I assume the “Goal” paragraph refers to your goal, not the readers. As you do research, you will add the results to this paragraph (or elsewhere).
*The :USB programming adapter” link caused a download of a “revoprog.zip” file, which my MAC unzipped into “RevoProg.exe” dated 4 Dec, 2016. MACs running MacOs won’t run “.exe” files - they are Windows. Is it possible to get a “.jar” version (like a Java implementation) that will run on any OS? Also, I think people will be a bit cautous about downloading executable files. And it’s confusing to me how I would insert the downloaded adpater into a USB port. (Relates back to what a “correct” USB adapter is?)
*I opened and read part of the “Windows 11” page. The first thing that hit me was:

"'''Note: Windows 11 Installation Assistant doesn’t run on Arm-based PCs; it only works for x64 processors.'''"

But I noticed that you said you were running Windows on an Arm architecture MAC. So I looked at the next link (“Parallels”) and think I see the answer. It will cost $55 to install Parallels (my MAC is Arm-based). Then I can run the Windows apps (e.g., the “RevoProg.exe”) on my MAC. I’ll have to dig into this further. But to run just one app, it’s not very cost effective. I do have a Dell, running Windows. But I hated it too, and it has been sitting - unused - on my desk for almost 2 years now. The battery is probably really dead.
*I didn’t understand the rest of the paragraph - about “… getting the USB to passthrough…”.
*I obviously have not run the “PC Software”. So I don’t know what those LEDs are. I’m guessing they are on the USB Adpater that is connected to the computer through the dongle chord.
*Next I’m guessing the “Programmer Interface” (AKA: The USB Adapter?) will make a Bluetooth or WiFi connection to the desired device. How this automatically happens is a mystery to me, as I haven’t seen any “pairing” operations or WiFi login operations yet. Nor do I see a direct wire connection from the subject device to the “Programmer Interface”. So how is this happening?
*In “Updating the throttle”: It may “break” your throttle (not “brick”)?

So, with all that said, I really appreciate you putting this together and posting it. Hopefully, folks will get a big help from it.

User talk:EricTimberlake

2026-03-15T07:06:12Z

EricTimberlake: Replaced content with "Updates made! Pretty sure this is final or close to final edit.."

Updates made! Pretty sure this is final or close to final edit..

Revolution Radio Control

2026-03-15T07:03:11Z

EricTimberlake: /* Loading the Windows tool "PC Software v1.1" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading Fw using Parallels Windows 11 virtual machine on an Apple M1 laptop]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

<big>The link button has '''DUAL FUNCTIONALITY'''. A '''''very short''''' press doesn't do anything. A '''''medium''''' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. As you are pressing and holding the decoder link button, watch the decoder LED. After 1/2 second of pressing the link button, it will flash quickly, KEEP pressing the link button for approximately 4-5 seconds and it shifts into FW update mode. The LED will blink much slower and upon release of the link button you should be able to see the transfer progress updating in the "PC Software v1.1" window.</big>

The USB Device Programmer red LED should still be blinking at a fast pace while the file transfer is in progress.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===
[[File:Throttle update dialog.jpeg|300px|thumb|right|Throttle FW update confirmation dialog (LONG PRESS)]][[File:Revolution throttle update status.jpeg|300px|thumb|right|Revolution throttle FW update status]]

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T07:00:42Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

<big>The link button has '''DUAL FUNCTIONALITY'''. A '''''very short''''' press doesn't do anything. A '''''medium''''' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. As you are pressing and holding the decoder link button, watch the decoder LED. After 1/2 second of pressing the link button, it will flash quickly, KEEP pressing the link button for approximately 4-5 seconds and it shifts into FW update mode. The LED will blink much slower and upon release of the link button you should be able to see the transfer progress updating in the "PC Software v1.1" window.</big>

The USB Device Programmer red LED should still be blinking at a fast pace while the file transfer is in progress.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===
[[File:Throttle update dialog.jpeg|300px|thumb|right|Throttle FW update confirmation dialog (LONG PRESS)]][[File:Revolution throttle update status.jpeg|300px|thumb|right|Revolution throttle FW update status]]

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:53:20Z

EricTimberlake: /* Updating the throttle vs. a decoder */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===
[[File:Throttle update dialog.jpeg|300px|thumb|right|Throttle FW update confirmation dialog (LONG PRESS)]][[File:Revolution throttle update status.jpeg|300px|thumb|right|Revolution throttle FW update status]]

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:52:11Z

EricTimberlake: /* Updating the throttle vs. a decoder */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===
[[File:Throttle update dialog.jpeg|300px|thumb|right|confirmation dialog]][[File:Revolution throttle update status.jpeg|300px|thumb|right|update status]]

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:49:36Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===
[[File:Revoprogram 4.png|200px|thumb|right|Transfer Successfully Finished]]
Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:48:32Z

EricTimberlake: /* Sending the staged file from the Programming Adapter to the target */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
[[File:Revoprogram 2.png|200px|thumb|right|Step two in the upload process]]
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:47:54Z

EricTimberlake: /* Setup "PC Software v1.1" to transfer files */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|200px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:47:33Z

EricTimberlake: /* Step 1 - Pre-stage the file to the Programming Adapter */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|400px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|200px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:46:02Z

EricTimberlake: /* Step 1 - Pre-stage the file to the Programming Adapter */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|400px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|400px|thumb|left|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:45:21Z

EricTimberlake: /* Step 1 - Pre-stage the file to the Programming Adapter */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|400px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===
[[File:Revoprogram 3.png|800px|thumb|right|Step one in the upload process]]
After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:44:09Z

EricTimberlake: /* Setup "PC Software v1.1" to transfer files */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
[[File:Revoprogram 1.png|400px|thumb|right|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:42:33Z

EricTimberlake: /* Setup "PC Software v1.1" to transfer files */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|600px|thumb|left|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:42:00Z

EricTimberlake: /* Setup "PC Software v1.1" to transfer files */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|800px|thumb|left|A PC Software v1.1 screen shot BEFORE inserting the USB Device Programmer]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:38:44Z

EricTimberlake: /* Setup "PC Software v1.1" to transfer files */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1" that you downloaded from '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' after '''[https://www.revoelectronics.com/customer/account/create/ creating a Revolution site account]''' or '''[https://www.revoelectronics.com/customer/account/login/ logging in]''' if you already have one...

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|800px|thumb|left|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:33:53Z

EricTimberlake: /* Loading the Windows tool "PC Software v1.1" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|1000px|thumb|right|The Basic setup for uploading and testing]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|800px|thumb|left|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:33:18Z

EricTimberlake: /* Loading the Windows tool "PC Software v1.1" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector which are functionally identical. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|800px|thumb|right|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|800px|thumb|left|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:32:20Z

EricTimberlake: /* Loading the Windows tool "PC Software v1.1" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the link connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|800px|thumb|right|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|800px|thumb|left|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:30:43Z

EricTimberlake: /* Tools */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|800px|thumb|right|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|800px|thumb|left|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:30:18Z

EricTimberlake:

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|none|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|none|800px|thumb|right|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|none|800px|thumb|left|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|none|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|none|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|none|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|none|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|none|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|none|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|none|1000px|thumb|left|frame| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:24:51Z

EricTimberlake:

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|800px|thumb|right|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|thumb|left|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|thumb|left|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|thumb|left|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|thumb|left|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|thumb|left|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|thumb|left|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px|thumb|left| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:23:03Z

EricTimberlake:

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|800px|thumb|right|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|thumb|right|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|thumb|right|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|thumb|right|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|thumb|right|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|thumb|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|thumb|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|thumb|left|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px|thumb|left| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:19:53Z

EricTimberlake: /* Tools */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:19:09Z

EricTimberlake: /* Tools */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =

[[file:Revolution Downloads Screenshot.png|400px|thumb|right|Downloads page as of 2026]]

Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files. There's a screen grab of the files as of 2026 to the right.

There are also more files there for older and alternate (DCC) products which we won't cover here.

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T06:16:58Z

EricTimberlake: /* Tools */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

We cannot provide direct links to the files located at the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''', the files are behind a login-wall that prevents direct links. At the time of this writing you could select from six (6) diesel and four (4) steam sound files.

There are also more files there for older and alternate (DCC) products which we won't cover here.

[[file:Revolution Downloads Screenshot.png|400px|thumb|left|Downloads page as of 2026]]

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

File:Revolution Downloads Screenshot.png

2026-03-15T06:13:33Z

EricTimberlake: just a list of files pertinent to the USB Device Programmer instuctions..

== Summary ==
just a list of files pertinent to the USB Device Programmer instuctions..

Revolution Radio Control

2026-03-15T06:06:19Z

EricTimberlake: /* Loading the Windows tool "PC Software v1.1" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works ''MOST OF THE TIME'', with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

Pay attention to the link button! It is a single momentary contact push button that shorts pins 1-3 to pin 2 of the trigger connector on the decoder. The connector is a 3x Micro '''[https://en.wikipedia.org/wiki/JST_connector JST]''' or '''[https://en.wikipedia.org/wiki/Molex Molex]''' PicoBlade connector. A link button is included with every decoder purchased from Revolution.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:58:52Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

It should be noted that this special link mode is for pairing to the USB Device Programmer, which then knows to download the "staged" file. It does not erase or alter already established credentials..
a
When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. In the very first photo, I have a decoder with a motor, a speaker, input triggers, and a link button.. This is just a PARTIAL test setup - a full setup would have a number of LED's attached to the headlights and the function outputs.

To test, just power cycle, turn on your throttle, link it if it hasn't been previously linked (see manual for instructions) and turn up the speed steps and observe the motor spin. Use F1 to start the sound. Use 7,8,9 to adjust the volume.. You should see the motor turn and hear the sound file you selected.

The trigger wires will toot the horn or trigger a chuff, pins 1 or 3 shorted to pin 2 (center).

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:49:01Z

EricTimberlake: /* Bluetooth */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually '''[https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers]''' or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:48:36Z

EricTimberlake: /* Bluetooth */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:47:26Z

EricTimberlake: /* The "pairing concept" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept", an explination ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:45:38Z

EricTimberlake: /* Zigbee */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
'''[https://en.wikipedia.org/wiki/Zigbee Zigbee]''' is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a '''[https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network]''', for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:45:01Z

EricTimberlake: /* The "pairing concept" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks '''[https://en.wikipedia.org/wiki/Cryptography involves cryptography]'''. You use '''[https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data]''' every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day.

Note that ALL of these work within the '''[https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum]'''.
==== WiFi ====
'''[https://en.wikipedia.org/wiki/Wi-Fi WiFi]''' should be familiar to many. You configure the controlling device, your '''[https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router]''', with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows '''[https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol]''' traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
'''[https://en.wikipedia.org/wiki/Bluetooth Bluetooth]''' should also be familiar - You tell your Bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to '''[https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]'''. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or '''[https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones]'''.

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:42:11Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the link button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:41:17Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished" similar to the screen shot below.. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:40:19Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:39:28Z

EricTimberlake: /* Step 2 - Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The USB Device Programmer red LED should still be blinking at a fast pace.

'''<big>At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.
'''</big>
When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:34:27Z

EricTimberlake: /* Using the Tool */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Step by Step ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:33:53Z

EricTimberlake: /* Running "PC Software v1.1" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Setup "PC Software v1.1" to transfer files ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Using the Tool ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:33:11Z

EricTimberlake:

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Windows tool "PC Software v1.1" ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Running "PC Software v1.1" ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Device Programmer is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Using the Tool ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the USB Device Programmer and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "USB Device Programmer" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the USB Device Programmer to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that USB Device Programmer - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the USB Device Programmer itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:31:15Z

EricTimberlake: /* Tools */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation. In case it's not obvious, we will explain the use of the files you may download and the USB Device Programmer below.

There is exactly ZERO documentation provided for any of these USB Device Programmer tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Programmer Interface tool ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Running "PC Software v1.1" ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Programmer Interface is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Using the Tool ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the Programmer Interface and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "Programmer Interface" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the Programmer Interface to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that Programmer Interface - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the Programmer Interface itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:27:20Z

EricTimberlake:

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these Programmer Interface tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Programmer Interface tool ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Running "PC Software v1.1" ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Programmer Interface is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Using the Tool ==
=== Step 1 - Pre-stage the file to the Programming Adapter ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Adapter will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Adapter with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Adapter to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Adapter changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the Programmer Interface and start transferring the staged file embedded in the Programming Adapter. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming Adapter is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "Programmer Interface" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Adapter was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Adapter was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the Programmer Interface to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that Programmer Interface - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the Programmer Interface itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:22:44Z

EricTimberlake: /* Starting the upload (Where we will use a special mode of "linking" */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these Programmer Interface tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Programmer Interface tool ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Running "PC Software v1.1" ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Programmer Interface is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Using the Tool ==
=== Step 1 - Pre-stage the file to the Programming Interface ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Interface will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Interface with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Interface to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Interface changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Step 2 - Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the Programmer Interface and start transferring the staged file embedded in the Programming Interface. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming interface is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "Programmer Interface" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Interface was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Interface was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the Programmer Interface to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that Programmer Interface - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the Programmer Interface itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:21:50Z

EricTimberlake: /* Pre-stage the file to the Programming Interface */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these Programmer Interface tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Programmer Interface tool ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Running "PC Software v1.1" ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Programmer Interface is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Using the Tool ==
=== Step 1 - Pre-stage the file to the Programming Interface ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Interface will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Interface with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Interface to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Interface changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the Programmer Interface and start transferring the staged file embedded in the Programming Interface. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming interface is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "Programmer Interface" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Interface was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Interface was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the Programmer Interface to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that Programmer Interface - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the Programmer Interface itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]

Revolution Radio Control

2026-03-15T05:21:11Z

EricTimberlake: /* Starting the upload */

[[Category:Works In Progress]]
 Under construction/modification by [[User:EricTimberlake|Eric Timberlake]] ([[User talk:EricTimberlake|talk]]) 
{{rtoc}}

[[Category:Electronics]] 
[[Category:Revolution]] 
[[Category:Crest]] 
[[Category:Train Engineer]] 
[[Category:Remote Control]] 

= Precision RC, aka Crest 'Revolution' =
Formed as an offshoot of Aristocraft as they created their own RC control solution.

[https://www.revoelectronics.com/ '''Train Engineer''']
Precision RC
16 Chestnut St. Ste 201E
Emerson, NJ 07630 USA

== What is it? ==
Revolution is based on a 2.4GHz "[https://en.wikipedia.org/wiki/Zigbee Zigbee Network]" to create a network infrastructure similar to WiFi with the throttle at one end and various decoders at the other end. This allows the formation of a [https://en.wikipedia.org/wiki/Mesh_networking zigbee mesh network] and the support of consists with multiple locomotives, for instance.

Let's explain this a little further - what do we mean when we say "formation of a zigbee mesh"?
=== The "pairing concept" ===
All modern over the air networking and point to point networks [https://en.wikipedia.org/wiki/Cryptography involves cryptography]. You use [https://en.wikipedia.org/wiki/Cryptographic_hash_function complex cryptography encoded data] every minute of every day without even being aware of it. To use these encryption tools, you need to establish "keys". You create these keys when you "pair" or "link" a device to another node on the network.

''We will use this "pairing" concept later in the instructions to start the file transfer process..
''
Here are some examples to help illustrate the concept in ways that you likely use every day. Note that ALL of these work within the [https://en.wikipedia.org/wiki/2.4_GHz_radio_use 2.4GHz radio frequency broadcast spectrum].
==== WiFi ====
[https://en.wikipedia.org/wiki/Wi-Fi WiFi] should be familiar to many. You configure the controlling device, your [https://en.wikipedia.org/wiki/Wireless_access_point WiFi AP or wireless router], with an SSID (network name) and a password. Or a "key", if you will. To join the network, at the end node, we select the SSD and provide the "key", or password, and you become linked to that network that allows [https://en.wikipedia.org/wiki/Internet_protocol_suite TCP/IP protocol] traffic to flow over it. This is essentially what the internet is built on, TCP/IP connections. Anyway, the point here is, you "link" a node of some sort to a "controller" of some sort.

==== Bluetooth ====
[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] should also be familiar - You tell your bluetooth end node to advertise itself (like a link button!) to be open to linking. Then you initiate a search on the controlling device, your phone, for instance, to [https://en.wikipedia.org/wiki/Bluetooth#Implementation_2 initiate the link bonding and key generation]. Now we have a secure encoded point to point link between the phone (controller) and the bluetooth device, usually [https://en.wikipedia.org/wiki/Wireless_speaker#Bluetooth speakers] or [https://en.wikipedia.org/wiki/Audio_headset#Bluetooth headphones].

==== Zigbee ====
[https://en.wikipedia.org/wiki/Zigbee Zigbee] is extremely similar, but is the one most people haven't heard about, because it's more low key utilitarian in scope. If you have a smart electrical meter on your house it may be part of a [https://en.wikipedia.org/wiki/Wireless_mesh_network large Zigbee mesh network], for instance. In our case, the Revolution Throttle is a Zigbee Controller. You use the menu to select "linking", then on the decoder end, you press the "link" button for a short period. This causes the Throttle and decoder to pass cryptographic keys with each other and they are then "linked". Because Zigbee is a mesh network, you can repeat this process with addition decoders.

= Tools =
Deep within the bowels of the '''[https://www.revoelectronics.com/blog/cat/download/ Revoelectronics Downloads page]''' you can download sound files, throttle firmware and the Windows program(s) to move these files around using the '''[https://www.revoelectronics.com/product/revolution/usb-programmer.html USB Device Programmer]'''.. You need to create an account on the Revolution website to access the downloadable files and/or any documentation.

There is exactly ZERO documentation provided for any of these Programmer Interface tools that I can find. The goal is to figure out and document just how this all plays together so you don't have to go through what I did..

= Observations =
== Loading the Programmer Interface tool ==

Running the Windows SW is simple and so far, it works MOST OF THE TIME, with just a few caveats.

So, you insert the '''[https://www.revoelectronics.com/usb-programmer.html USB Programming Adapter]''' into a USB 2.0 Type A port. Then start either the cleverly named "PC Software v1.0" or "PC Software v1.1"

The photo below shows a modern Arm architecture Mac running Windows 11 within '''[https://www.parallels.com/products/desktop/ Parallels Desktop]'''. This is not required, just a proof of concept that the tools provided will run within a virtual machine as well as a dedicated Windows laptop.

Also visible in the photo is an off the shelf '''[https://www.amazon.com/s?k=usb-a+to+usb-c+adapter USB-C to USB-A adapter]''' (the little red cable) readily available at Amazon and other suppliers.

Additionally, you can clearly see the blue LED that indicates power to the USB Programming Adapter. The red "activity" LED is on the adjacent corner of the USB Programming Adapter and is clearly visible when lit.

[[File:Revo setup 1.jpeg|800px|The Basic setup]]

== Running "PC Software v1.1" ==
So, now you should have Windows (real or virtual) running, the USB Programming Adapter inserted into a USB port.. When you insert the USB Programming Adapter there are two LED's of note. A blue LED that indicates power and a red LED that indicates various states of use.

Time to light up the programing SW interface, called "PC Software v1.1".. You can ALSO use the slightly down rev "PC Software v1.0" version if you desire..

After starting up the SW, you should see a screen '''SIMILAR''' to the photo below. Note in this photo that the USB Programmer Interface is NOT visible - I took the screen shot before actually inserting the tool. The tool can and sometimes MUST BE inserted while "PC Software v1.1" is running - more on that later!

[[File:Revoprogram 1.png|800px|PC Software v1.1]]

== Using the Tool ==
=== Pre-stage the file to the Programming Interface ===

After the tool is started, the first step is get that field under the logo to say "Programmer found". Sometimes this works right off the bat if the dongle is pre-inserted, other times it needs to be "hot plugged" while "PC Software v1.1" program is actually running. When inserted the Programming Interface will light a blue LED in a steady state.

Once you get to the "Programmer found" status, the work flow runs like this:

#Select '''the device''' you want to send a file to in the upper left dialog window.
#Select '''the actual FILE''' you want to send to the device using the "File Open" button, which will bring up a normal file selection dialog.
#Select the "'''Load/Program'''" button.

This will result in a file transfer status being shown - this is ''important'', you are '''NOT''' sending the file to your device at this point, you are "''pre-loading''" the Programming Interface with the file for further processing. While this pre-load is happening, a red LED located on the opposite corner from the blue LED will light in a steady state.

[[File:Revoprogram 3.png|800px|Step one in the upload process]]

=== Sending the staged file from the Programming Interface to the target ===
Once the "Load/Program" process is completed, the dialog window will update to say, "'''Searching Target Device Signal'''". You should also note that the red LED on the Programming Interface changes from a steady state to a rapid blinking state! If you do NOT see the LED blinking, something is wrong! (See hints towards end of article..)

[[File:Revoprogram 2.png|800px|Step two in the upload process]]

=== Starting the upload (Where we will use a special mode of "linking" ===

Move to your staged device - you should have it powered up and at a minimum the "link" button attached. In the photo further up the article you will note a speaker, a motor trigger wires and the link button all attached to the decoder so all the features can be easily tested after the upload process is completed.

The link button has '''DUAL FUNCTIONALITY'''. A ''very short'' press doesn't do anything. A ''medium'' length press puts the decoder in standard linking mode. A '''''LONG PRESS''''' (what we want to do in this case) triggers a special upgrade mode and will immediately link with the Programmer Interface and start transferring the staged file embedded in the Programming Interface. You should be able to see the transfer progress updating in the "PC Software v1.1" window.

The red LED should still be blinking at a fast pace.

At this time, press and HOLD the link button. The decoder LED will first flash quickly, then after a few seconds will slow down - that's the sign you have entered the second "programming mode". Release the button and observe the "PC Software v1.1" window to monitor the transfer process.

When it is completed, it will note "Transfer Successfully Finished".. This is a good sign!

[[File:Revoprogram 4.png|800px|Transfer Successfully Finished]]

After the process is completed, simply power cycle the decoder and test to your satisfaction.. Repeat as required to get the sound you want loaded into your decoder..

=== Updating the throttle vs. a decoder ===

Updating the throttle Firmware is a similar process with just some minor variations.

#First, select "Revolution Transmitter" as the device to upgrade.
#Second, select the FW file you want to upload into the throttle. (3.03 being the most current)
#Third, after the transfer into the Programming interface is complete and the red LED starts flashing, power up the throttle, select MENU -> ASSIGN FUNCTIONS ->10. UPDATE FIRMWARE.
#Forth step, like the decoder, the "Are you sure?" dialog needs a '''LONG PRESS''' on "Yes" to trigger a transfer.

If something is wrong and you can't see any progress happening, use the MENU and ON/OFF button together to reset the decoder. DO NOT do this "mid transfer"! It may brick your throttle! Only do this if something is amiss and the process never starts at all.

[[File:Throttle update dialog.jpeg|300px|confirmation dialog]]
[[File:Revolution throttle update status.jpeg|300px|update status]]

== Errors and Caveats ==
I started this project with a used Throttle and an older decoder found "miss-listed" on Ebay, thus a real steal of a deal. I borrowed the "Programmer Interface" from Warner Swarner.

It turns out that I was fighting several issues that made figuring this out quite difficult..

#The used decoder is broken, it won't accept updates. Fortunately I was loaned a couple of new decoders that work correctly, and that helped establish what works and what doesn't work as well as proving the decoder I got off Ebay is just plain broken.
#The Programming Interface was partly faulty - the zigbee radio module was not making a firm connection to the USB dongle.. This was HUGE..

It took MANY, many tries to get things working. The intermittent Programming Interface was the largest hurdle. Ultimately what I found was this:

[[File:Revo programmer exposed 1.jpeg|400px|the offending connector that needed reseating]]

That disconnected connector you can see is pried apart so I can try seating and re-seating it a few times. This cleared up the "loads, but red LED stays solid" issue that I fought off and on for weeks while I worked my way through the puzzle of how this is SUPPOSED to work..

=== Other gotcha's ===
It is not uncommon for the Programmer Interface to just not respond to the "Load/Program" button. The only cure I can relate is to leave the "PC Software v1.1" running and unplug, then re-plugin that Programmer Interface - wait for "Programmer Found" to appear, then start at the beginning by selecting a device, file, then "Load/Program".

Sometimes, the exact opposite is true and you need to quit out of the "PC Software v1.1" and restart it. And sometimes you need to do BOTH actions to get it all happy..

If the red LED does not start blinking at the end of the "Load/Program" step, something is wrong with the Programmer Interface itself, try GENTLY unpluging the zigbee module (it will NOT come completely free due to a soldered ground connection!!) and re-plugging it back onto the USB module a few times.

= Flow Chart =
A basic flow chart of the process...

[[File:Flowchart.jpg|1000px| Flow Chart of process]]