7,309
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: + + + Line 10:
Line 13: + + + + + Line 18:
Line 26: + + + Line 27:
Line 38: + + + Line 55:
Line 69: + + + Line 71:
Line 88: + + + Line 95:
Line 115: + + +
Updating to match new version of source page
===1. Uninstall existing Software (Windows only)===
===1. Uninstall existing Software (Windows only)===
Uninstall any existing BEASTXUpdater/Microsettings installation prior to install the BEASTXSoftware bundle.
Uninstall any existing BEASTXUpdater/Microsettings installation prior to install the BEASTXSoftware bundle.
Uninstall any existing BEASTXUpdater/Microsettings installation prior to install the BEASTXSoftware bundle.
===2. Download Update Software and Install===
===2. Download Update Software and Install===
Windows (XP, Vista, 7, 8, 8.1)
Windows (XP, Vista, 7, 8, 8.1)
MacOS 10.6.x and later
MacOS 10.6.x and later
===3. Driver installation===
===3. Driver installation===
Windows:
The driver installation will not be launched automatically during setup.
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.
Windows:
Windows:
The driver installation will not be launched automatically during setup.
The driver installation will not be launched automatically during setup.
MacOS:
MacOS:
The driver is inside the Disk-Image and must be installed manually.
The driver is inside the Disk-Image and must be installed manually.
===4. Validate driver installation (Windows only)===
===4. Validate driver installation (Windows only)===
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:
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:
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:
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.
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.
===5. Start BEASTXUpdater===
===5. Start BEASTXUpdater===
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!).
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!).
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_4.jpg|500px]]
[[File:Step 5_4.jpg|500px]]
===6. Detect connected BEASTX device===
===6. Detect connected BEASTX device===
After you selected a COM-Port the BEASTXUpdater will automatically try to identify the unit connected to it.
After you selected a COM-Port the BEASTXUpdater will automatically try to identify the unit connected to it.
After you selected a COM-Port the BEASTXUpdater will automatically try to identify the unit connected to it.
Data-Version is the format of the settings, stored on the MICROBEAST.
Data-Version is the format of the settings, stored on the MICROBEAST.
Serial-Number is a unique identifier for each MICROBEAST.
Serial-Number is a unique identifier for each MICROBEAST.
===7. Select Update-File===
===7. Select Update-File===
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 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 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]]).
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.
===8. Perform Update===
===8. Perform Update===
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:
If a valid COM-Port is selected an a valid Update-File was loaded, the "Start Update…" button will be enabled: