Difference between revisions of "BEASTX Updater Classic"

From BEASTX Wiki
Jump to navigation Jump to search
 
(57 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
===1. Uninstall existing Software (Windows only)===
+
<translate>
−
Uninstall any existing BEASTXUpdater/Microsettings installation prior to install the BEASTXSoftware bundle.
+
<!--T:1-->
 +
The tool "BEASTX Updater Classic" can be used if you encounter problems with the StudioX application and want to check if your device can be recognized at all. Also you can use it to do a firmware update with a provided update file from the BEASTX service team if necessary. You can find the BEASTX Updater Classic here:<br />
 +
<br />
 +
[http://studiox.beastx.com/download/misc/BXUpdaterClassic.zip Updater Classic for Windows]<br />
 +
<br />
 +
[http://studiox.beastx.com/download/misc/BXUpdaterClassic.pkg Updater Classic for macOS]<br />
 +
<br />
  
−
===2. Download Update Software and Install===
+
<!--T:47-->
 +
'''On Windows computers make sure that the driver files for your USB2SYS interface have been installed or install the files if necessary.''' For further information see this page: [[USB2SYS/SPMA3030 driver installation]].<br />
 +
<br />
  
−
Supported operating systems are:
+
<!--T:11-->
 +
'''1. Connecting to the BEASTX device'''
  
−
    Windows (XP, Vista, 7, 8, 8.1)
+
<!--T:49-->
−
    MacOS 10.6.x and later
+
The BEASTX device will not be powered from the USB2SYS-Interface! So the unit must be supplied with power from a different source
 +
before(!) you connect it to the PC, e.g. simply switch on tx and rx as you would go flying (on electric helis take care of the motor!).
  
−
===3. Driver installation===
+
<!--T:12-->
−
Windows:
+
The cable from the interface goes into the '''[SYS]''' port of the device. Watch out for correct polarity on both devices.<br />
−
The driver installation will not be launched automatically during setup.
+
<br />
−
The installer will be copied and a link to it is added to the BEASTX group in Start-Menu. Do not connect the USB2SYS interface to the computer unless you did not perform the driver installation. After the installation when you connect the interface to the PC, Windows will recognize the device and install it as a new device.
 
  
−
MacOS:
+
<!--T:13-->
−
The driver is inside the Disk-Image and must be installed manually.
+
If the COM-Port to which the USB2SYS-Interface has been assigned by windows is known, you can directly choose it from the list of available interfaces. On macOS/Linux usually the port is called "cu.SLAB_USBtoUART" or "tty.SLAB_USBtoUART" (you can use either of them):
  
−
===4. Validate driver installation (Windows only)===
+
<!--T:14-->
−
After successful installation of the driver, when the USB2SYS-Interface is connected to the PC, you must be able to find following entry in the Windwos Device Manager:
+
[[File:Step 5_1.png|200px|thumb|none]]
  
−
[[File:Step 4.png|500px]]
+
<!--T:15-->
 +
<br />
 +
If the COM-Port is not known you can use the "Autodetect…" function:
  
−
The name COM3 may be different on your PC. This entry must disappear when you disconnect the USB2SYS-Interface from the PC, and reappear when you connect it again.
+
<!--T:16-->
 +
[[File:Step 5_2.jpg|200px|thumb|none]]
  
−
To access the device manager under windows 7 type devmgmt.msc in the Startmenu's search bar. Alternatively you can enter the computer properties by pressing and holding the START key on the keyboard and addtionaly pressing the PAUSE key. Then click on device manager in the upper left corner of the appearing window.
+
<!--T:17-->
 +
<br />
 +
When the dialog is shown, disconnect the USB2SYS-Interface from the PC (if already connected) and reconnect it again.
 +
The Autodetect-function will only work if the driver was installed successfully.
  
−
===5. Start BEASTXUpdater===
+
<!--T:18-->
−
IMPORTANT: The MICROBEAST will not be powered from the USB2SYS-Interface, so the MICROBEAST must be supplied with power from a different source BEFORE you connect it to the PC, e.g. simply switch on tx and rx as you would go flying (on electric helis take care of the motor!).
+
[[File:Step 5_3.jpg|200px|thumb|none]]
  
−
The cable from the interface goes into the Microbeast's [SYS] port. Watch out for correct polarity on both devices.
+
<!--T:19-->
 +
<br />
 +
After a successful detection the BEASTX Updater Classic will tell you which COM-Port was detected:
  
−
If the COM-Port, to which the USB2SYS-Interface has been assigned by windows, is known you can directly choose it from the list of available interfaces:
+
<!--T:20-->
 +
[[File:Step 5_4.jpg|200px|thumb|none]]
  
−
[[File:Step 5_1.png|500px]]
 
  
−
If the COM-Port is not known you can use the "Autodetect…" function:
+
<!--T:21-->
 +
<br />
 +
'''2. Detection of the BEASTX device'''
  
−
[[File:Step 5_2.jpg|500px]]
+
<!--T:50-->
 +
After you selected a COM-Port the BEASTX Updater Classic will automatically try to identify the unit connected to it.
  
−
[[File:Step 5_3.jpg|500px]]
+
<!--T:22-->
 +
If the MICROBEAST PLUS/AR7210BX/nanoBEAST was not connected at this moment you can manually force a new detection by pressing the "Refresh" button.
  
−
When the dialog is shown, disconnect the USB2SYS-Interface from the PC (if already connected) and reconnect it again.
+
<!--T:23-->
−
The Autodetect-function will only work if the driver was installed successfully.
+
If the correct COM-Port was chosen (red), and the device is connected to the USB2SYS-Interface, some information (green) about it will be shown in the "BEASTX Device" section:
  
−
After a successful detection the BEASTXUpdater will tell you which COM-Port was detected:
 
  
−
[[File:Step 5_4.jpg|500px]]
+
<!--T:24-->
 +
[[File:Step 6.jpg|200px|thumb|none]]
  
−
===6. Detect connected BEASTX device===
 
−
After you selected a COM-Port the BEASTXUpdater will automatically try to identify the unit connected to it.
 
  
−
If the MICROBEAST/Trajectory/AR7200BX was not connected at this moment you can manually force a new detection by pressing the "Refresh" button (or "Connect" when using the MicroSettings Software).
+
<!--T:25-->
 +
* Hardware-Version 1.1 and 1.2 stand for MICROBEAST units. Hardware-Version 2.x shows that a MICROBEAST PLUS is connected. Hardware Version 8.0 identifies Spektrum AR7200BX units.
 +
* Application-Version is the actually installed firmware of the device (in this case 1.0.0).
 +
* Data-Version is the format that is used to store settings on the MICROBEAST.
 +
* Serial-Number is an unique identifier for each device.
  
−
If the correct COM-Port was chosen (red), and the MICROBEAST is connected to the USB2SYS-Interface, some information (green) of this MICROBEAST will be shown in the "BEASTX Device" section:
 
−
Klicken Sie auf die Grafik für eine größere Ansicht  Name: Step 6.jpg  Hits: 628  Größe: 48,7 KB  ID: 603
 
  
−
At this moment Hardware-Version 1.1 and 1.2 are existing.
+
<!--T:26-->
−
Application-Version is the actually installed firmware of the MICROBEAST (in this case 1.0.0)
+
'''3. Select Update-File'''
−
Data-Version is the format of the settings, stored on the MICROBEAST.
 
−
Serial-Number is a unique identifier for each MICROBEAST.
 
  
−
===7. Select Update-File===
+
<!--T:51-->
−
If the MICROBEAST was successfully identified you can go on with selecting an Update-File (if you don't have a firmware update file yet, have a look [[Update_request|here]]).
+
If the device was successfully identified you can go on with selecting an Update-File:
  
 +
<!--T:27-->
 
"Open File…" button opens a dialog where you can choose the Update-File.
 
"Open File…" button opens a dialog where you can choose the Update-File.
−
Klicken Sie auf die Grafik für eine größere Ansicht  Name: Step 7_1.png Hits: 788  Größe: 78,9 KB  ID: 606
+
 
 +
<!--T:28-->
 +
[[File:Step 7_1.png|200px|thumb|none]]
 +
 
 +
 
 +
<!--T:29-->
 
Or you can just drag'n'drop an Update-File from the Explorer to the Main window of the BEASTXUpdater.
 
Or you can just drag'n'drop an Update-File from the Explorer to the Main window of the BEASTXUpdater.
  
−
An Updates-File can only be loaded if it is free of damage, complete and has the mentioned "upd" ending.
+
<!--T:30-->
 +
An Updates-File can only be loaded if it is free of damage, complete and has the mentioned ".upd" ending.
  
 +
<!--T:31-->
 
Application-Version, Data-Version and Target-Hardware will be shown if the file was loaded successfully:
 
Application-Version, Data-Version and Target-Hardware will be shown if the file was loaded successfully:
−
Klicken Sie auf die Grafik für eine größere Ansicht  Name: Step 7_2.jpg  Hits: 700  Größe: 44,1 KB  ID: 607
 
  
−
Only a compatible "Target Hardware Version" can be installed on a MICROBEAST.
+
 
 +
<!--T:32-->
 +
[[File:Step 7_2.jpg|200px|thumb|none]]
 +
 
 +
 
 +
<!--T:33-->
 +
Only a compatible "Target Hardware Version" can be installed to your device.
 
The firmware version in the Update-File will be shown next to "Application Version" (in this case 1.0.11).
 
The firmware version in the Update-File will be shown next to "Application Version" (in this case 1.0.11).
  
−
The format of settings will be shown next to "Data Version".
+
<!--T:34-->
−
IMPORTANT: If the major version of the "Data Version" is different between the actual and new firmware, then the Basic-Setup has to be done again after the update.
+
The format of settings will be shown next to "Data Version". '''IMPORTANT''': If the major version of the "Data Version" is different between the actual and new firmware, then the Basic-Setup has to be done again after the update.
 +
 
  
−
===8. Perform Update===
+
<!--T:35-->
 +
'''4. Perform Update'''
 +
 
 +
<!--T:52-->
 
If a valid COM-Port is selected an a valid Update-File was loaded, the "Start Update…" button will be enabled:
 
If a valid COM-Port is selected an a valid Update-File was loaded, the "Start Update…" button will be enabled:
−
Klicken Sie auf die Grafik für eine größere Ansicht  Name: Step 8_1.jpg  Hits: 475  Größe: 43,4 KB  ID: 594
 
  
 +
<!--T:36-->
 +
[[File:Step 8_1.jpg|200px|thumb|none]]
 +
 +
 +
<!--T:37-->
 
After pressing the "Start Update…" button, the actual firmware version, and the new target firmware version will be shown:
 
After pressing the "Start Update…" button, the actual firmware version, and the new target firmware version will be shown:
−
Klicken Sie auf die Grafik für eine größere Ansicht  Name: Step 8_2.png Hits: 432  Größe: 70,4 KB  ID: 595
+
 
 +
<!--T:38-->
 +
[[File:Step 8_2.png|200px|thumb|none]]
 +
 
 +
 
 +
<!--T:39-->
 
Press "Yes" to start the update.
 
Press "Yes" to start the update.
  
 +
<!--T:40-->
 
After a successful update a message will be displayed:
 
After a successful update a message will be displayed:
−
Klicken Sie auf die Grafik für eine größere Ansicht  Name: Step 8_3.png  Hits: 428  Größe: 64,0 KB  ID: 596
 
  
−
After your confirmation with "Ok" BEASTXUpdater will detect the version information of the connected MICROBEAST again.
+
<!--T:41-->
−
Klicken Sie auf die Grafik für eine größere Ansicht  Name: Step 8_4.png Hits: 526  Größe: 98,9 KB  ID: 597
+
[[File:Step 8_3.png|200px|thumb|none]]
 +
 
 +
 
 +
<!--T:42-->
 +
After your confirmation with "Ok" BEASTX Updater Classic will detect the version information of the connected the device again.
 +
 
 +
<!--T:43-->
 +
[[File:Step 8_4.png|200px|thumb|none]]
 +
 
 +
 
 +
<!--T:44-->
 
You can refresh this information using the "Refresh" button.
 
You can refresh this information using the "Refresh" button.
  
−
Your MICROBEAST is now updated to the latest firmware.
+
<!--T:45-->
 +
Your device is now updated to the latest firmware.
 +
</translate>

Latest revision as of 18:42, 6 August 2018

The tool "BEASTX Updater Classic" can be used if you encounter problems with the StudioX application and want to check if your device can be recognized at all. Also you can use it to do a firmware update with a provided update file from the BEASTX service team if necessary. You can find the BEASTX Updater Classic here:

Updater Classic for Windows

Updater Classic for macOS

On Windows computers make sure that the driver files for your USB2SYS interface have been installed or install the files if necessary. For further information see this page: USB2SYS/SPMA3030 driver installation.

1. Connecting to the BEASTX device 

The BEASTX device will not be powered from the USB2SYS-Interface! So the unit must be supplied with power from a different source
before(!) you connect it to the PC, e.g. simply switch on tx and rx as you would go flying (on electric helis take care of the motor!).

The cable from the interface goes into the [SYS] port of the device. Watch out for correct polarity on both devices.

If the COM-Port to which the USB2SYS-Interface has been assigned by windows is known, you can directly choose it from the list of available interfaces. On macOS/Linux usually the port is called "cu.SLAB_USBtoUART" or "tty.SLAB_USBtoUART" (you can use either of them):

Step 5 1.png


If the COM-Port is not known you can use the "Autodetect…" function:

Step 5 2.jpg


When the dialog is shown, disconnect the USB2SYS-Interface from the PC (if already connected) and reconnect it again. The Autodetect-function will only work if the driver was installed successfully.

Step 5 3.jpg


After a successful detection the BEASTX Updater Classic will tell you which COM-Port was detected:

Step 5 4.jpg



2. Detection of the BEASTX device

After you selected a COM-Port the BEASTX Updater Classic will automatically try to identify the unit connected to it.

If the MICROBEAST PLUS/AR7210BX/nanoBEAST was not connected at this moment you can manually force a new detection by pressing the "Refresh" button.

If the correct COM-Port was chosen (red), and the device is connected to the USB2SYS-Interface, some information (green) about it will be shown in the "BEASTX Device" section:


Step 6.jpg


  • Hardware-Version 1.1 and 1.2 stand for MICROBEAST units. Hardware-Version 2.x shows that a MICROBEAST PLUS is connected. Hardware Version 8.0 identifies Spektrum AR7200BX units.
  • Application-Version is the actually installed firmware of the device (in this case 1.0.0).
  • Data-Version is the format that is used to store settings on the MICROBEAST.
  • Serial-Number is an unique identifier for each device.


3. Select Update-File

If the device was successfully identified you can go on with selecting an Update-File:

"Open File…" button opens a dialog where you can choose the Update-File.

Step 7 1.png


Or you can just drag'n'drop an Update-File from the Explorer to the Main window of the BEASTXUpdater.

An Updates-File can only be loaded if it is free of damage, complete and has the mentioned ".upd" ending.

Application-Version, Data-Version and Target-Hardware will be shown if the file was loaded successfully:


Step 7 2.jpg


Only a compatible "Target Hardware Version" can be installed to your device. The firmware version in the Update-File will be shown next to "Application Version" (in this case 1.0.11).

The format of settings will be shown next to "Data Version". IMPORTANT: If the major version of the "Data Version" is different between the actual and new firmware, then the Basic-Setup has to be done again after the update.


4. Perform Update

If a valid COM-Port is selected an a valid Update-File was loaded, the "Start Update…" button will be enabled:

Step 8 1.jpg


After pressing the "Start Update…" button, the actual firmware version, and the new target firmware version will be shown:

Step 8 2.png


Press "Yes" to start the update.

After a successful update a message will be displayed:

Step 8 3.png


After your confirmation with "Ok" BEASTX Updater Classic will detect the version information of the connected the device again.

Step 8 4.png


You can refresh this information using the "Refresh" button.

Your device is now updated to the latest firmware.

Retrieved from "https://wiki.beastx.com/index.php?title=BEASTX_Updater_Classic&oldid=16420"