Difference between revisions of "BEASTX Updater Classic"

From BEASTX Wiki
Jump to navigation Jump to search
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
<languages />
 
−
<br />
 
 
<translate>
 
<translate>
 
<!--T:1-->
 
<!--T:1-->
−
The StudioX software bundle includes the old MICROBEAST update tool which is now called "BEASTX Updater Classic". You can use this tool especially if you encounter problems when using the StudioX application and want to check if your device can be recognized or simply if you want to do a quick firmware update to one of your units or just because you did like to use this old tool. You can find the BEASTX Updater Classic in the BEASTX programm group in your Windows START menu.
+
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 />
−
[[File:Updater classic link.jpg|200px|thumb|none]]
 
−
 
 
−
<!--T:5-->
 
 
<br />
 
<br />
−
'''1. Driver installation'''
+
[http://studiox.beastx.com/download/misc/BXUpdaterClassic.zip Updater Classic for Windows]<br />
−
 
 
−
<!--T:47-->
 
−
If not already done make sure that the driver files for your USB2SYS interface have been installed. The driver installation will not be launched automatically during setup. Windows should install the correct drivers when the USB2SYS is plugged in the PC for the first time. Check the notifications in the right corner of your task bar:
 
−
<gallery>
 
−
File:Driver install.png
 
−
File:Driver success.png
 
−
</gallery>
 
 
<br />
 
<br />
−
 
+
[http://studiox.beastx.com/download/misc/BXUpdaterClassic.pkg Updater Classic for macOS]<br />
−
<!--T:7-->
 
−
'''2. Validate driver installation'''<br />
 
−
If the driver installation fails, you may see an error message with a red cross next to the device icon:
 
−
[[File:Driver failed.png|200px|thumb|none]]
 
−
<br />
 
−
In this case you have to install the driver files manually which will be described in the following step 3.<br />
 
 
<br />
 
<br />
  
−
<!--T:48-->
+
<!--T:47-->
−
If you did not see any message popping up at all, check you Windows device manager if the USB2SYS has been installed correctly. 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.
+
'''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 />
−
[[File:Device mgr.png|200px|thumb|none]]
 
 
<br />
 
<br />
−
You must be able to find following entry:
 
−
 
−
<!--T:8-->
 
−
[[File:Step 4.png|200px|thumb|none]]
 
−
 
−
<!--T:9-->
 
−
<br />
 
−
The name COM3 may be different on your PC. This entry must disappear when you disconnect the USB2SYS-Interface from the PC and re-appear when you connect it again.<br />
 
−
If there is only an entry marked with an yellow "!" something went wrong and you have to install the driver files manually which will be described in the following step 3.
 
−
[[File:File:Device mgr failed.png|200px|thumb|none]]
 
−
<br />
 
−
 
−
<!--T:10-->
 
−
'''4. Manual installation of USB2SYS interface driver'''
 
−
First of all make sure the USB2SYS interface is disconnected from the computer. Then start the StudioX Software and click the download link for the USB2SYS driver package:
 
−
[[File:Driver download page.png|200px|thumb|none]]
 
−
<br />
 
−
Your web browser will open and ask to save the file "CP210x_VCP_Windows.zip" or will save it automatically. Open the downloaded zip-file from the folder where it has been saved to and extract the content of the file to your harddisk (here we directly extract it to drive C:). Go to the extracted folder and start one of the included setup files (if you have a 64-bit Windows use the "CP210xVCPInstaller_x64.exe", if you have a 32-bit system use CP210xVCPInstaller_x86.exe).
 
−
<gallery>
 
−
File:Driver file.png
 
−
File:Extract driver.png
 
−
File:Extract driver2.png
 
−
File:Extract driver3.png
 
−
</gallery>
 
−
<br />
 
−
 
−
Proceed through the installer by accepting the license agreement and clicking "Next" and "Install".
 
−
<gallery>
 
−
File:SiLabs1.png
 
−
File:SiLabs2.png
 
−
File:SiLabs3.png
 
−
File:SiLabs4.png
 
−
</gallery>
 
−
<br />
 
−
 
−
When the installation was finished, connect the USB2SYS interface to the computer (again). That's it, your interface should now appear correctly in device manager (see above) and you can use the assigned COM port to connect to your MICROBEAST/Ar7xxxBX device.
 
  
 
<!--T:11-->
 
<!--T:11-->
−
'''3. Start BEASTX Updater Classic'''
+
'''1. Connecting to the BEASTX device'''
  
 
<!--T:49-->
 
<!--T:49-->
−
'''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!).
+
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!).
  
 
<!--T:12-->
 
<!--T:12-->
−
The cable from the interface goes into the MICROBEAST's '''[SYS]''' port. Watch out for correct polarity on both devices.<br />
+
The cable from the interface goes into the '''[SYS]''' port of the device. Watch out for correct polarity on both devices.<br />
 
<br />
 
<br />
  
 
<!--T:13-->
 
<!--T:13-->
−
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:
+
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):
  
 
<!--T:14-->
 
<!--T:14-->
Line 108: Line 54:
 
<!--T:21-->
 
<!--T:21-->
 
<br />
 
<br />
−
'''4. Detect connected BEASTX device'''
+
'''2. Detection of the BEASTX device'''
  
 
<!--T:50-->
 
<!--T:50-->
Line 114: Line 60:
  
 
<!--T:22-->
 
<!--T:22-->
−
If the MICROBEAST/Trajectory/AR7200BX was not connected at this moment you can manually force a new detection by pressing the "Refresh" button.
+
If the MICROBEAST PLUS/AR7210BX/nanoBEAST was not connected at this moment you can manually force a new detection by pressing the "Refresh" button.
  
 
<!--T:23-->
 
<!--T:23-->
−
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:
+
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:
  
  
Line 125: Line 71:
  
 
<!--T:25-->
 
<!--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 AR7xxxBX units.
+
* 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).
 
* 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.
 
* Data-Version is the format that is used to store settings on the MICROBEAST.
Line 132: Line 78:
  
 
<!--T:26-->
 
<!--T:26-->
−
'''5. Select Update-File'''
+
'''3. Select Update-File'''
  
 
<!--T:51-->
 
<!--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-->
 
<!--T:27-->
Line 148: Line 94:
  
 
<!--T:30-->
 
<!--T:30-->
−
An Updates-File can only be loaded if it is free of damage, complete and has the mentioned "upd" ending.
+
An Updates-File can only be loaded if it is free of damage, complete and has the mentioned ".upd" ending.
  
 
<!--T:31-->
 
<!--T:31-->
Line 159: Line 105:
  
 
<!--T:33-->
 
<!--T:33-->
−
Only a compatible "Target Hardware Version" can be installed on a MICROBEAST.
+
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).
  
 
<!--T:34-->
 
<!--T:34-->
−
The format of settings will be shown next to "Data Version".
+
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.
−
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.
 
  
  
 
<!--T:35-->
 
<!--T:35-->
−
'''6. Perform Update'''
+
'''4. Perform Update'''
  
 
<!--T:52-->
 
<!--T:52-->
Line 195: Line 140:
  
 
<!--T:42-->
 
<!--T:42-->
−
After your confirmation with "Ok" BEASTX Updater Classic will detect the version information of the connected MICROBEAST again.
+
After your confirmation with "Ok" BEASTX Updater Classic will detect the version information of the connected the device again.
  
 
<!--T:43-->
 
<!--T:43-->
Line 205: Line 150:
  
 
<!--T:45-->
 
<!--T:45-->
−
Your MICROBEAST is now updated to the latest firmware.
+
Your device is now updated to the latest firmware.
 
</translate>
 
</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"