|
XtremeLink®
Device Programmer
Software
support
You
are welcome to link to these files,
but please do not host
them.
We make periodic improvements
to our software and firmware. Only the very latest versions should be
available to our customers.
Telemetry
Station software is now part of the XDP software installation
package. Please download the Current
XDP software installer -
Click
here to download
Click
on a link for more information on these subjects:
Hardware
Requirements
486
or later processor
running Windows 98 or later. 1.5 MB of hard drive space, and
640K
of memory.
This
product works only
with XtremeLink®
2.4GHz
devices. Not all
XtremeLink®
devices can have their firmware upgraded. Only 3 channel
receivers and Satellite receivers officially support firmware
upgrades. However, a large number of our products do have
this
ability. If your device shows as not
having a flashable CPU,
then you will not be able to upgrade it. It
is not possible
to upgrade older non-flashable units to be a flashable type.
Overview
The
XtremeLink®
Device
Programmer (XDP for short) is a USB based device that allows various
types of communications with the
XtremeLink®
product
line. The software available here will give you powerful
tools
for helping you setup your system and diagnose any potential
installation or equipment problems.
This
product is designed for PC computers running Windows 98 through Windows
Vista operating systems. Currently, there is not a Macintosh
OS
version available. The hardware is compatible with USB 1.1
and
USB 2.0 configurations. The required cable type is a Type A
to
Mini-B, which can be purchased directly from XPS.
IT IS NECESSARY TO
INSTALL THE XTREMELINK® DEVICE
PROGRAMMER SOFTWARE BEFORE CONNECTING THE XDP
HARDWARE!
Installing
the XDP software
DO NOT PLUG IN THE XDP UNIT INTO YOUR PC BEFORE
THE SOFTWARE IS INSTALLED!
To
install the XDP
software, download the software installer below and run the installer
by double-clicking on its icon. Hint:
hold the SHIFT key
while clicking the link or using the right mouse button when clicking
the link and save the file to your desktop so that it is easy to find.
Follow
the installer
instructions to install the software on your computer. Once
it
has been installed, you can delete the downloaded file.
Current
XDP software
installer -
Click here to download
Installing
the XDP hardware
To
install the XDP
hardware, simply connect the USB cable end with the smaller mini-B
connector to the Xtreme Device Programmer, and the other end to your
PC's USB port. The first time you do this, you may see a
Hardware
Installation Wizard appear. Just select NEXT and the
driver
will automatically found and setup. You MUST have the XDP plugged in
BEFORE running any XDP related software.
Once the XDP has been plugged in,
you can then double-click on any of the icons to run that program. Only
one
program can use the XDP hardware at a time, so it is necessary to quit
one program before launching another. NOTE: If you
receive
a Windows error message about a missing or non-registered DLL "MSSTDFMT.DLL",
then go to our help page by clicking
here.
Telemetry
Station
Compatibility
All
programs compatible
with the XDP hardware can also be used with the Telemetry Station.
Program
Summary
XDP.EXE
This
program will let you update firmware (if your unit is
in-field upgradeable) as well as change the settings instead of using
the push button and LED blinks. There are also special
programming features that are not available in the push button
programming mode. The receiver and transmitter modules must
be
put into a special mode in order to be used with this
program.
See the instructions below:
Putting
your
XtremeLink® receiver in programming mode
To
use the XDP.exe program,
you must first put your XtremeLink® receiver into a special
programming mode. To do this, press and hold the programming
button while turning on the power. There will be a brief
pause
and then the LED will light up orange. Release the
programming
button and receiver is then ready to connect to the XDP.exe program.
If
the LED does not light
up orange, it is likely that you have older firmware that did not have
support for the XtremeLink® Device Programmer yet.
Xtreme
Power Systems would need to upgrade the receiver's firmware to enable
this support.
Putting
your
XtremeLink® transmitter module in programming mode
To
use the XDP.exe program,
you must first put your XtremeLink® transmitter module into a
special programming mode. To do this, press and hold the PROG
button while turning on the power. Keep holding the PROG
button
and notice the state of the LED. It will turn green, followed
by
red, and then finally turn orange. Once orange, release the
PROG
button and the transmitter module is then ready to connect to the
XDP.exe program.
If
the LED does not light
up orange, it is likely that you have older firmware that did not have
support for the XtremeLink® Device Programmer yet.
Xtreme
Power Systems would need to upgrade the receiver's firmware to enable
this support.
TXDIAG.EXE
This
program
acts as a virtual receiver, letting you see the output of your
transmitter. The signal strength is also shown.
Added
ability to monitor
the PPM signal and notify you if the pulse jumps unexpectedly.
RXDIAG.EXE
This
program acts as a
virtual transmitter, letting you control your receiver.
ANALYZER.EXE
This
program is a real time 2.4GHz spectrum analyzer.
RSSI.EXE
This
program shows the RSSI transmitter stength (requires v3.x firmware and hopping
modes 2-5).
Firmware
Upgrades
These
firmware upgrades REQUIRE a flashable CPU and v3.0 or later firmware to
begin with.
Updater
v1.4
- Receiver v3.4, Satellite v1.1, Transmitter v3.4
Updater
v1.5 - Receiver
v3.5, Satellite v1.2, Transmitter v3.5
Updater
v1.6 - Receiver
v3.6, Satellite v1.3, Transmitter v3.5
Updater
v1.7
- Receiver
v3.7, Satellite v1.3, Transmitter v3.6 - NO OFFICIAL RELEASE
Updater
v1.8 - Receiver
v3.7, Satellite v1.3, Transmitter v3.7
Updater
v1.9
- Receiver
v3.7, Satellite v1.4, Transmitter v3.7
Updater
v2.0 - Receiver
v3.7, Satellite v1.4, Transmitter v3.8
Updater v2.1 - Receiver
v3.8, Satellite v1.4, Transmitter v3.8 - REMOVED
Updater v2.2 - Receiver
v3.8, Satellite v1.4, Transmitter v3.8 - REMOVED
Updater v2.3 - Receiver
v3.8, Satellite v1.4, Transmitter v3.8
Updater v2.4 - Receiver
v3.8, Nano Receiver v1.4, Satellite v1.4, Transmitter v3.8
Updater v2.5 - Receiver
v3.8, Nano Receiver v1.5, Satellite v1.4, Transmitter v3.8
Updater v2.6 - Removed
Updater v2.7 - Removed
Updater v2.8 - Receiver
v3.8, Nano Receiver v1.6, Satellite v1.4, Transmitter v3.8
Updater v2.9 - Removed
BETA
FIRMWARE *USE AT OWN RISK *
Updater v3.0 - Receiver
v3.9, Nano Receiver v1.7, Satellite v1.4, Transmitter v3.8 - EVO v3.9!
This update is for the Royal EVO transmitter
module and receivers. It adds MLink support with
telemetry capability.
For EVO firmware v3.30 or v3.41 you must do the
jumper modification as shown in the thread found
on
RCGroups:
V1.x/2.x support is also included with this new
version. However, v2.x requires either the
above mentioned
mod or pins 2 & 5 tied together on the module
port.
Receivers were updated with fix for failsafe
when PPM off and addition of PPM data stream for
Nanos
Firmware History
Standard Receivers:
;----------------------------------------------------------------------
;
; v3.1 - 11/06/08
;
; Changed boot error to show alternately red/orange flashing when
; receiver is powered up and a RF module failure has occurred.
;
; Fixed problem when using a transmitter with 12 or more channels
; saving failsafe positions.
;
;----------------------------------------------------------------------
;
; v3.2 - 11/20/08
;
; Fixed issue when using PPM24 mode with ATVs set at 150%
;
; Improved re-sync of lost packets with short frames.
;
;----------------------------------------------------------------------
;
; v3.3 - 01/01/09
;
; Removed virtual satellite receiver used for testing.
;
; Removed requirement of having a sensor plugged in to get
; signal strength and battery voltage.
;
;----------------------------------------------------------------------
;
; v3.4 - 03/26/09
;
; Fixed issue with push button programming not allowing the Failsafe
; of PPM OFF.
;
; Added 2 second delay after system connects before battery voltage is
; checked. This allows systems with huge servos that need massive
; power at startup a chance to power up without tripping the low
; voltage warning.
;
;----------------------------------------------------------------------
;
; v3.5 - 06/06/09
;
; Disabled telemetry output when in system is in a failsafe condition.
; The transmission time is better spent re-syncing the frequency
; hopping.
;
;----------------------------------------------------------------------
;
; v3.6 - 08/12/09
;
; Added support for 12 channel simultaneous outputs. This allows you
; to use a 12 channel transmitter with multiple receivers and use
; (via channel mapping) all 12 channel outputs. Failsafe works with
; new XDP program to setup failsafes for channels 11 and 12. Note
; that the servo output range is now limited, 850us to 2250us, 100us
; shorter than the previous versions. In testing, the lowest pulse
; we encountered was Multiplex EVO at 850us to 1950us. JR and Futaba
; are both 900us or more, even with 150% throws.
;
; Re-wrote frequency hopping code for receiver. Synchronization has
; been dramatically improved, giving the overall range a two fold
; increase.
;
;----------------------------------------------------------------------
;
; v3.7 - 10/21/09
;
; Cleared FIFO on startup to prevent possible firmware mismatch warning.
;
; Added support for changing the telemetry transmission ID so that
telemetry
; data can be sent back to the transmitter module directly instead of
just
; to the telemetry station. The 3rd programming mode (solid orange) is
; now used to set the "telemetry output mode". Possible options:
;
; 1 flash = Data sent to PC
; 2 flashes = Data sent to transmitter (as well as PC)
; 3 flashes = turn off telemetry output
;
; WARNING!! DO NOT send data to the transmitter if the transmitter
firmware
; is less than v3.6!
;
;----------------------------------------------------------------------
;
; v3.8 - 04/15/10
;
; Added support for failsafe packet for Graupner
telemetry radios.
;
; Added reboot notification. LED now flashes
orange if power is lost
; and restored.
;
;----------------------------------------------------------------------
;
; v3.9 - 10/17/11
;
; Fixed issue with RESET routine not resetting
channel 16 in the channel
; map.
;
; Streamlined failsafe capture code.
;
; Fixed PWM OFF failsafe. Previously, all channels
after a channel set
; for a failsafe of PWM off would be skewed by
66us.
Nano Receivers:
;----------------------------------------------------------------------
;
; v1.4 - 08/08/10
;
; Added support for binding as a slave receiver.
;
;----------------------------------------------------------------------
;
; v1.5 - 10/25/10
;
; Added patch to fix hardware difference for binding. Now Nano
; receivers can be bound as slaves to 8/10 channel receivers.
; *NOTE: receivers MUST be 12" or more apart when
binding!
;
;----------------------------------------------------------------------
;
; v1.6 - 04/10/11 - beta
;
; Added servo reversing and offset adjustments
using the XDP.
;
;----------------------------------------------------------------------
;
; v1.7 - 10/17/11
;
; Added ability to choose between PWM output or
PPM output for the servo
; output. PWM is the normal servo output. PPM
output supports devices
; that need a PPM data stream such as mikrocopters,
3-axis gyros, flight
; simulator inputs, etc. While in PPM output mode,
channels 1/3/5 output
; a positive going PPM pulse, and channels 2/4/6
output a negative going
; PPM pulse. Selection for the output mode is done
as the last step in
; the binding. Once the LED turns off, placing the
jumper back on the
; binding port will turn on the LED, also
selecting the PPM output mode.
; Otherwise, no jumper means the LED is off and
normal PWM mode (servo
; output) is used. If while in PPM output mode a
failsafe is set to
; "OFF" (no signal), a 680us short pulse is used.
This should trigger
; failsafe monitors as a standard servo pulse is
900us to 2100us.
;
; Fixed issue with RESET routine not resetting
channel 16 in the channel
; map.
;
; Changed slave binding to automatically change
the channel map of any
; slave receiver to be channels 7-12 on outputs
1-6.
;
; Streamlined failsafe capture code.
;
; Fixed PWM OFF failsafe. Previously, all channels
after a channel set
; for a failsafe of PWM off would be skewed by
66us.
Satellite
receiver:
;----------------------------------------------------------------------
;
; v1.0 - 09/16/07
;
; Initial test version for 16 channel receiver.
;
;----------------------------------------------------------------------
;
; v1.0b - 11/01/08
;
; Changed hardware to LDO regulator version.
; Changed LED and telemetry port input and output pins.
;
;----------------------------------------------------------------------
;
; v1.1 - 04/29/09
;
; Added failsafe routine for satellite receiver so that no data is
; passed to the main receiver when there is a complete loss of data.
;
;----------------------------------------------------------------------
;
; v1.2 - 05/22/09
;
; Fixed bug with learning multiple satellite receivers.
;
; Improved hopping re-synchronization after long loss of signal.
;
;----------------------------------------------------------------------
;
; v1.3 - 08/12/09
;
; Re-wrote frequency hopping code for receiver. Synchronization has
; been dramatically improved, giving the overall range a two fold
; increase.
;
;----------------------------------------------------------------------
;
; v1.4 - 11/28/09
;
; Removed LED blinking debug mode.
Transmitter
modules:
;----------------------------------------------------------------------
;
; v3.1 - 11/06/08
;
; Changed frame data to include hop mode type to make telemetry
; support easier.
;
; Defined new transmitter IDs for Graupner MX-16 and XD-6 radios
;
;----------------------------------------------------------------------
;
; v3.2 - 12/06/08
;
; Added 10ms delay between INIT and REQINFO commands to
; compensate for receivers that used the old (slower) data rates.
;
;----------------------------------------------------------------------
;
; v3.3 - 04/10/09
;
; Added support for new flashing setup.
;
;----------------------------------------------------------------------
;
; v3.4 - 04/13/09
;
; Fixed startup delay for PROFI and other transmitters requiring this
support
;
;----------------------------------------------------------------------
;
; v3.5 - 06/13/09
;
; Made lock command ignore all other 802.15.4 devices on startup.
;
; Fixed issue with LED not returning to normal state after attenuating
; the power when no receiver is connected (hopping modes 2-5).
;
; Changed frame rate calculation to filter PCM. This is the first step
; in supporting PCM intput.
;
;----------------------------------------------------------------------
;
; v3.6 - 10/26/09
;
; Complete re-write of the PPM pulse capturing code. It was possible
that
; if a transmitter had a spurious PPM pulse that the frequency hopping
; could become out of sync, resulting in an immediate failsafe. Invalid
; pulses are ignored, frame discarded, and last know good data is used
; instead. This keeps the hopping fully synchronized.
;
; Cleared FIFO on startup to prevent possible firmware mismatch warning.
;
; Added preliminary telemetry support using internal port connector.
This
; provides the Rx voltage and RSSI information.
;
;----------------------------------------------------------------------
;
; v3.7 - 11/16/09
;
; Fixed bug with beta release of transmitter output code when using 9
; or more channels.
;
;----------------------------------------------------------------------
;
; v3.8 - 01/04/10
;
; Added storage of PANID during binding to allow resetting of XBEE
module
; with immediate reconnection. This will eliminate bad resets due to low
; power (dead transmitter batteries or loose module pins).
;
; Removed XBEE reset routine as it is no longer necessary.
;
;----------------------------------------------------------------------
;
; v3.9 - 06/24/11 - EVO ONLY!
;
; Added support MLink emulation. This requires the extra wire
; from our module's telemetry interface.
XDP/Scanner
History
08/03/08 - v1.5.0
Fixed problem with config not saving language types other than English.
Updated installer program to fix installer error. Depending the version
of
Windows, the installer would not create the Languages folder and end up
copying the language file to the Data folder.
Renamed "Language" folder to "Languages" in preparation for other
apps getting locale support.
--------------------------------------------------------------------
08/09/08 - v1.6.0
Fixed problem when sensor command 0x82 has no data returned
with
the
class, output type, and output format bytes.
Capped telemetry packets to 80 bytes.
Added support for MCxx and MX-24 radios.
--------------------------------------------------------------------
08/16/08 - v1.6.1
Added support for GPS sensors.
Added more output types to handle more sensor types.
Added icon for telemetry window.
Added ability to show all sensors, whether connected or not
and
report
the sensor is not responding for any sensors that are not
attached.
Added support for Turbine EDT sensor.
--------------------------------------------------------------------
03/22/09 - v1.8.0
Fixed problem with some units not reporting as FLASHABLE
Added support for newer hardware revs.
--------------------------------------------------------------------
03/23/09 - v1.9.0
Fixed problem with Value and Class output for telemetry
display.
--------------------------------------------------------------------
04/07/09 - v2.0
Fixed problem with requiring a 10 channel end pin receiver
graphic
file. Removed firmware update capabilities.
--------------------------------------------------------------------
??/??/?? - v2.1
Changes not documented.
--------------------------------------------------------------------
06/04/09 - v2.2
Disallowed telemetry sub-menu to be selected when XDP is
used.
This
allows the selection only if using the Telemetry Station.
--------------------------------------------------------------------
08/12/09 - v2.3
Enable failsafe display for all channels so that failsafe map
can be changed for channels not available as receiver outputs.
Added all Nano and Pico receiver device support.
--------------------------------------------------------------------
10/21/09 - v2.4
Fixed problem with windows not showing up in the task bar.
--------------------------------------------------------------------
11/09/09 - v2.5
Added support for Nano-T, Nano-E, and Pico receivers.
--------------------------------------------------------------------
11/13/09 - v2.6
Added support selecting a telemetry output (PC only or TX/PC).
Re-enabled basic telemetry support using just the XDP so that
telemetry sensors could be developed and telemetry settings
could
be made. You still need the Telemetry Station to receive
telemetry
data on a PC.
'--------------------------------------------------------------------
11/25/09 - v2.7
Added Finnish language support. Thanks to Sami Koivisto for
the
translation (Samtron-Translations / samipupu.com)
--------------------------------------------------------------------
01/04/10 - v2.8
Fixed floating point bug with
displaying version numbers above
v3.7.
Changed copyright to include 2010.
-------------------------------------------------------------------
03/04/10 - v2.9
Fixed another floating point bug with displaying
version numbers above
v3.7 (on title bars)
|
