Sync edgetx to Gitea
This commit is contained in:
@@ -0,0 +1,94 @@
|
||||
# Flashing EdgeTX to Flysky PL18 or Paladin EV
|
||||
|
||||
This page lists the recommended steps to install EdgeTX onto Flysky PL18 or Paladin EV radios.
|
||||
|
||||
- [Preparatory steps](#preparatory-steps)
|
||||
- [Backing up Flysky Bootloader](#backing-up-flysky-bootloader)
|
||||
- [Flashing EdgeTX bootloader and firmware](#flashing-edgetx-bootloader-and-firmware)
|
||||
- [Preparing internal SPI flash](#preparing-internal-spi-flash)
|
||||
- [External RF module support](#external-rf-module-support)
|
||||
|
||||
***
|
||||
|
||||
[](../assets/images/hw/flysky-pl18/edgetx_pl18ev.jpg)
|
||||
|
||||
Please keep in mind that at present day, EdgeTX support for Flysky PL18 and Paladin EV radios is still in development - the upcoming v2.10 is scheduled to provide the first release. Use EdgeTX on PL18 or Paladin EV for testing purposes only at the moment. A lot of EdgeTX functionality is already successfully implemented for PL18 / Paladin EV, but not all.
|
||||
|
||||
Due to PL18 and Paladin EV radio hardware differences, when compared to other EdgeTX supported radios, full EdgeTX experience, as known from other supported color screen radios, will not be possible with PL18 and Paladin EV, at least not without some hardware modifications. Factory PL18 and Paladin EV do not have a real-time-clock, an arbitrary sound output and an expandable storage, latter due to lack of a microSD card slot. PL18 and Paladin EV come with internal 8 MB SPI flash chip, where from factory, part of Flysky PL18 or Paladin EV firmware is stored. EdgeTX uses this memory chip as a microSD card substitute. Due to limited size of 8 MB, full EdgeTX SD card contents does not although fit into the internal memory. As arbitrary sound output is not possible anyhow, you can skip copying the chunky `\SOUNDS` SD card subfolder.
|
||||
|
||||
**If you ever want to restore the original Flysky firmware to your PL18 or Paladin EV at a later date, it is crucial that you follow successfully the _Backing up Flysky Bootloader_ section.** As only, if the Flysky bootloader is restored to the radio, you can use Flysky Assistant Windows software to fully restore also the SPI flash content via Flysky online servers.
|
||||
|
||||
## Preparatory steps
|
||||
|
||||
* Remove the FRM301 RF-module for now. This module likely will never get official EdgeTX support due to proprietary API that Flysky desires to keep confidential. You can use [Flysky FJR2 JR-micro bay adapter](https://www.flysky-cn.com/b1700-specifications) to attach arbitrary JR micro bay RF-modules to the PL18 or Paladin EV instead. Alternatively, consider ExpressLRS firmware for the FRM301 (see [ExpressLRS pull-request #1811](https://github.com/ExpressLRS/ExpressLRS/pull/1811)) or see the section about supported [external RF modules](#external-rf-module-support) below.
|
||||
* Fully charge the battery of your PL18 or Paladin EV before starting with the backup or the flashing steps below.
|
||||
* Download and install the latest STM32CubeProgrammer, see for instructions: [Unbrick your radio](../troubleshooting/unbrick.md) (you need to make an account at ST to be able to download it).
|
||||
* Peel off the left rubber handle on your PL18 or Paladin EV. That should reveal two hidden buttons. The top button is the Device-Firmware-Upgrade (DFU) button, the bottom button is the ultimate master power-off button and will be required to be pressed to exit the DFU mode.
|
||||
|
||||
[](../assets/images/hw/flysky-pl18/pl18_hidden_buttons.jpg)
|
||||
|
||||
## Backing up Flysky Bootloader
|
||||
|
||||
**This step is crucial, if you ever wish to return/restore back to Flysky factory firmware on your PL18 or Paladin EV.**
|
||||
|
||||
* Make sure your PL18 / Paladin EV radio is powered off. Grab and attach a microUSB cable on the radio side only for now. Put the radio flat on the table. Next, press and hold the upper hidden button (DFU) down, while you attach the other end of the USB cable into the computer, where you previously installed the STM32CubeProgrammer software. This connects your PL18 / Paladin EV to your computer in DFU mode.
|
||||
* You should have heard the typical sound from your computer, when you attach an USB device. Start STM32CubeProgrammer software.
|
||||
* The STM32F429BIT6 microcontroller in the PL18/PL18EV should have been detected on the right side of the STM32CubeProgrammer screen under USB configuration as a USB with a number, typically USB1. Open the drop-down menu next to `Port` to check if you see USB1 listed there and then select it. Click the green `Connect` button on top right.
|
||||
|
||||
|
||||
|
||||
* You might be greeted with some seemingly random content, do not get alarmed - this is all perfectly fine and just showing some of the first bytes of memory that are currently saved on the microcontroller. Most importantly, check that the lower right corner now lists _Cortex-M4_ to the right of the field `CPU`.
|
||||
|
||||
|
||||
|
||||
* Next you will read out the STM32F4 flash memory of your radio. In Device memory tab, make sure Address is `0x08000000` (Explanation: `0x08000000` is the starting address of the flash memory on STM32F4 microcontrollers). Enter size: `0x200000` (instead of default `0x400`). (Explanation: `0x200000` is 2 MByte in hex, the size of STM32F429BIT6 internal flash). Click the blue `Read` button. It takes ca. 5 sec. to read the full flash from radio into your computer.
|
||||
|
||||
[](../assets/images/hw/flysky-pl18/stm32cb_read.png)
|
||||
|
||||
* Click the drop-down arrow on Read command and pick `Save-As`.
|
||||
|
||||
|
||||
|
||||
* Give it a name, such as `PL18_factory.bin` and save it somewhere safe. This file is your ticket back to Flysky firmware on your radio, if you ever wish to restore your operating system. Check that the file is 2 MByte in size, if not - something went wrong and do NOT continue until you are able to sort it out.
|
||||
* If you plan to continue flashing the EdgeTX bootloader and firmware next, skip all the following steps of this section, otherwise be sure to continue - as your radio will drain the battery otherwise.
|
||||
* Click the green `Disconnect` button on top right of STM32CubeProgrammer.
|
||||
* Eject the radio from your operating system, similarly as you would safely disconnect an USB stick.
|
||||
* Disconnect the USB cable from the radio.
|
||||
* Press briefly the bottom hidden button (this resets the power circuitry inside PL18 / Paladin EV and powers it down).
|
||||
|
||||
## Flashing EdgeTX bootloader and firmware
|
||||
|
||||
If your radio is already connected successfully in DFU mode to your computer, you can skip the first two steps below.
|
||||
|
||||
* Make sure your PL18 / Paladin EV is powered down, before you continue. Take a microUSB cable. Attach it on the radio side only for now. Put the radio flat on the table. Next, press and hold the upper hidden button (DFU) down while you attach the other end of the USB cable into the computer with STM32CubeProgrammer installed. This connects your radio in DFU mode to the computer.
|
||||
* You should have heard the typical sound from your computer, when you attach an USB device.
|
||||
* Open [EdgeTX Buddy](https://buddy.edgetx.org/) with a Chromium-based webbrowser.
|
||||
* Unfold `Filter` and check to list the pre-releases. Select `nigthly` as Firmware version and pick either `Flysky PL18` or `Flysky PL18EV` according to your radio.
|
||||
* Press `Flash over USB` and wait for the flashing to end. **This process takes typically ca. 2 minutes to complete.**
|
||||
* Disconnect the USB cable from the radio.
|
||||
* Press briefly the bottom hidden button (this resets the power circuitry inside the radio and powers it down).
|
||||
|
||||
## Preparing internal SPI flash
|
||||
|
||||
* Make sure your PL18 / Paladin EV is powered down. Pull both horizontal trims (TR7 and TR8) together and press both power buttons to start into EdgeTX bootloader that you can hopefully see. If nothing happens, wait at least 3 minutes.
|
||||
|
||||
[](../assets/images/hw/flysky-pl18/edgetx_bootloader_pl18.jpg)
|
||||
|
||||
* If EdgeTX bootloader started successfully, select erase internal flash (second option from the top). You navigate up/down with TR6 and select Exit/Enter with TR4.
|
||||
|
||||
[](../assets/images/hw/flysky-pl18/pl18_bootloader_keys.jpg)
|
||||
|
||||
* The flash erase can take some minutes to complete. Wait and then turn off the radio using the power buttons.
|
||||
|
||||
* Enter EdgeTX bootloader again and attach USB cable again. This time a drive should pop up on your computer. This is the 8 MB SPI flash re-purposed as a mini-storage. The first time you attach the radio to your computer, you might be prompted to format it - accept and format the SPI flash with FAT filesystem. As soon as the FAT file system has been successfully created on the SPI flash, you can start filling it, as you would normally fill EdgeTX content onto a SD card (use the [c480x320.zip](https://github.com/EdgeTX/edgetx-sdcard/releases) of the SD card repository). Remember that you only have 8 MB available, and by default you will have no audio output (without the mod), thus best you skip filling the SOUNDS.
|
||||
|
||||
* Reboot the radio. You should be greeted with EdgeTX. Run the analogs calibration - be sure to calibrate the sticks, but also the pots and side sliders. PL18 and Paladin EV are touch-screen radios - for navigation around the user interface, please use the touch screen.
|
||||
|
||||
# External RF module support
|
||||
|
||||
The following external RF-modules have been successfully tested:
|
||||
|
||||
1. External [ExpressLRS](https://www.expresslrs.org/) (ELRS) modules in micro-JR bay form factor using the [Flysky FJR2 adapter](https://www.flysky-cn.com/b1700-specifications)
|
||||
2. [External MPM in micro-JR bay form factor](https://www.multi-module.org/basics/module-hardware#external-modules) using the [Flysky FJR2 adapter](https://www.flysky-cn.com/b1700-specifications)
|
||||
3. [Flysky FRM303 RF-module](https://www.flysky-cn.com/frm303description)
|
||||
4. Do-It-Yourself (DIY) 4-in-1 Multi-Protocol-Module (MPM) in FRM301 form factor. More information about this open source module can be found under: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/tree/master/STM32%20PCB/Flysky%20PL18
|
||||
@@ -0,0 +1,17 @@
|
||||
# Instructions for Installing FlySky FRM303 External Module to TX16S
|
||||
|
||||
The modification is quite simple, similar to Access MOD but no need the inverter.
|
||||
|
||||
Just need to reconnect the AUX1 output to PPM and Heartbeat pin directly. The following image shows how this can be done, I used connection plugs so that I can easily convert back to original circuit.
|
||||
|
||||
Please note that this mod will only affect the functionality of the external module, the internal module is not affected, so that one can use the internal 4 in 1 and external FRM303 together. After the mod, the ELRS external module should still works as well, as the ELRS ext module will only use the S.Port pin, but other modules that make use of the PPM pin may not work anymore after this mod.
|
||||
|
||||
|
||||
|
||||
For FRM303 setup, you need to first select the 1.5M opensource protocol, please refer to FRM303 manual for the procedures.
|
||||
|
||||
For radio settings, you need to setup AUX1 for External Module and then select Flysky in model settings, then everything done. Enjoy.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,133 @@
|
||||
# Instructions for Installing FlySky Digital Hall Gimbals in EdgeTX Radios
|
||||
|
||||
- [Mechanical mounting](#mechanical-mounting)
|
||||
- [Electrical wiring](#electrical-wiring)
|
||||
* [RadioMaster and Eachine TX16S](#radiomaster-and-eachine-tx16s)
|
||||
* [Jumper T16 and T18](#jumper-t16-and-t18)
|
||||
* [Jumper T20](#jumper-t20)
|
||||
|
||||
***
|
||||
|
||||
FlySky [FS-HZCZ03-ADJ](https://www.flysky-cn.com/hzczspecifications) is a high quality digital hall-effect gimbal set that can be integrated into numerous EdgeTX supported radios. The gimbals feel very solid due to CNC milled aluminum parts.
|
||||
|
||||
The position sensing of the gimbal axes is based on [Melexis MLX90393](https://www.melexis.com/en/product/MLX90393/Triaxis-Micropower-Magnetometer) Triaxis magnetometer. This hall-effect sensor IC uses digital SPI interface to output 16-bit values, proportional to the magnetic flux density sensed along the X, Y, and Z axes.
|
||||
|
||||
The gimbal set employs two MLX90393 sensors, one for each stick. The SPI signals are routed to a microcontroller in the circuit board that provides a firmware that transform the 3D signal from the sensors to 4 channels output with 16-bits precision each. The transformation algorithm will combine the 3D signal with factory calibrated settings to ensure the channel outputs are linear and without temperature drifts.
|
||||
|
||||
The channel outputs are sent to the radio transmitter via UART serial communication with 921.6 kbps transfer speed to ensure minimum latency. The sticks have a resolution of ca. 4500 discretization levels per gimbal axis.
|
||||
|
||||
The code includes an automatic detection of FlySky digital hall gimbals on power-up of TX16S/T16/T18 radios and no special build-time option is required. If after initial 70 ms the FlySky gimbals are not detected, the code reverts to sampling analog sticks.
|
||||
|
||||
## Mechanical mounting
|
||||
|
||||
The original author of FlySky digital gimbal support in EdgeTX, Richard Li, developed in addition a mechanical adapter ring set to easily mount the FlySky digital hall gimbals to various radios: TX16S, T16, T18 and TX18S. He donated the design to his friend at Hawk-RC, who's business was greatly impacted COVID-19. If you are planning to integrate the gimbals into the radio, Richard kindly asks you to consider purchasing the adapter ring set from Hawk-RC:
|
||||
|
||||
[TX16/18/16S/18S M.O.D FLYSKY Hall Sensor Assembly Kit](http://www.hawk-creation.com/index.php?route=product/product&product_id=6862)
|
||||
|
||||
The adapter ring set comes with 4 plastic parts and a cable. First, the thicker set of plastic rings are mounted into the radio, using the 4 original gimbal screws:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/HawkRC_TX16S_adapter_set_step1.jpg)
|
||||
|
||||
The adapter ring set is a perfect fit for RadioMaster and Eachine TX16S. For T16/T18 and TX18S, a small plastic protrusion needs to be removed first - for further details, please see the [Hawk-RC product page](http://www.hawk-creation.com/index.php?route=product/product&product_id=6862).
|
||||
|
||||
In a second step, the thinner adapter rings are mounted on top, with two M2x6 screws each:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/HawkRC_TX16S_adapter_set_step2.jpg)
|
||||
|
||||
In a third step, the FlySky gimbals are mounted using two M2x6 screws (outside) and two M2x14 screws (inside) each onto the adapter rings. And finally, the included cable needs to be attached to the left gimbal connector on the TX16S mainboard, circled green on next image:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/TX16S_FlySky_gimbal_connection.jpg)
|
||||
|
||||
## Electrical wiring
|
||||
|
||||
### RadioMaster and Eachine TX16S
|
||||
|
||||
Two options of hooking up the FlySky digital hall gimbals to TX16S will be presented below - the first option is simpler and requires no soldering, but will cause slight ripple on the analog power rail. The second option does not use analog power rail to supply the electronics of FlySky gimbals, but will require soldering. The second option is highly recommended, as this will not inject the digital noise from the gimbals into the analog rail of the radio.
|
||||
|
||||
#### Powering gimbal from the analog power rail
|
||||
|
||||
With this option, the FlySky gimbals will be powered from the 3.3V analog rail, provided on the gimbal plug, making the wiring easy. All you need to do is to make a 4 wires cable to connect the Flysky Hall Stick to a gimbal plug and the firmware mod will works. Do note that this option, although more easy to wire, will cause some noise to your radio analogs - pots, sliders and also audio.
|
||||
|
||||
The plug required for the gimbal is a 4P [JST ZH](https://www.jst-mfg.com/product/detail_e.php?series=287) 1.5mm plug as shown in the following figure:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/GimbalPlug.png)
|
||||
|
||||
The plug required for the PCB of TX16S is a 6P [Molex Picoblade](https://www.molex.com/molex/products/part-detail/crimp_housings/0510210600) 1.25mm plug as shown in the following figure:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/TX16S-PCBPlug.png)
|
||||
|
||||
After installation the TX16S is shown in the following figure:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/TX16S-Install.jpg)
|
||||
|
||||
#### Powering the gimbals from the digital power rail
|
||||
|
||||
The preferred way of powering FlySky digital hall gimbals on TX16S is from digital +3.3V power rail. This requires either soldering a JST PH 4-pin socket onto TX16S mainboard (recommended) or soldering the gimbal hookup wires directly to the mainboard. Hookup plan:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/TX16S_better_FlySky_gimbal_hookup.jpg)
|
||||
|
||||
|
||||
The final outcome with FlySky FS-HZCZ03-ADJ on RadioMaster TX16S Max:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/TX16S-Outlook.jpg)
|
||||
|
||||
Another example, showing the usage of FlySky Paladin EV gimbals with TX16S and EdgeTX:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/FlySky_Paladin_EV_gimbals_on_RM_TX16S.jpg)
|
||||
|
||||
EdgeTX includes extended channel support for X10 family radios (this includes T16, TX16S, T18, TX18S) in the form of EX3 and EX4 inputs at right analog stick connector together with Flysky digital hall gimbals. EX3 and EX4 can be used, in addition to EX1 and EX2, to connect e.g. the Paladin EV gimbal stick end pots and stick end switches. Here the hookup of stick ends shown in detail:
|
||||
|
||||
[](../assets/images/hw/flysky-mod/FlySky_Paladin_EV_gimbals_on_RM_TX16S_hookup.jpg)
|
||||
|
||||
### Jumper T16 and T18
|
||||
|
||||
The T16/T18 gimbals use 3V for A/D conversion, and it should work as per the specifications of the gimbal.
|
||||
|
||||
### Boxer
|
||||
|
||||
The boxer mod support starts from EdgeTX 2.9.0.
|
||||
|
||||
The connector is similar to the TX16S mod, just need to swap the TX and RX.
|
||||
|
||||
|
||||
Installation of Flysky digital hall gimbals into RadioMaster Boxer, using the [Hawk-RC Adapter ring set](http://www.hawk-creation.com/index.php?route=product/product&product_id=6862):
|
||||
|
||||
Step 1: mounting the bottom rings using stock RadioMaster analog gimbal screws:
|
||||
|
||||
|
||||
Step 2: mounting top rings using 2x2 M2x6 screws:
|
||||
|
||||
|
||||
Step 3: mounting Flysky digital hall gimbals HZCZ03-ADJ (here HCZC03 from an EL18) with 2x2 M2x6 and 2x2 M2x14 screws to the adapter rings and attaching the gimbal connection cable:
|
||||
|
||||
|
||||
Do note that the RX and TX lines of the gimbal connection cable need to be swapped for Boxer, when compared with T16/TX16S/T18 cable, that comes with Hawk-RC adapter rings.
|
||||
|
||||
Here a close-up of the correct cable for Boxer - note especially the white (Gimbal RX) and yellow (Gimbal TX) data lines:
|
||||
|
||||
|
||||
Further, please do note that on Boxer, the UART4 serial connection for digital gimbals is on the right gimbal header (when radio is looked from the back, then left side, as in the above picture), whereas on T16/TX16S/T18 the digital gimbals need to be connected to the left gimbal header.
|
||||
|
||||
End-result:
|
||||
|
||||
|
||||
### Jumper T20
|
||||
|
||||
To mod Jumper T20 with Flysky gimbals, you can use the same 3D printing kit for TX16S, however you may need to cut the plastic rods in the casing, the corners of the 3D printing kit and the corners of the gimbals as well in order to fit in the T20.
|
||||
|
||||
Step 1: Remove the filtering caps, Jumper T20 uses 100nF caps for gimbal noise filtering, this will affect the serial communication for the flysky mod, so the cap need to be removed (2 caps marked as red in the following photo):
|
||||
|
||||
|
||||
Step 2: Cut the casing plastic rods and corners of 3d print kit and gimbal, only a little cut is necessary showing in the following photo:
|
||||
|
||||
|
||||
Step 3: Wiring, you need to make a wire to connect the gimbal to the main PCB using the pin outs marked in the following photo:
|
||||
|
||||
|
||||
Step 4: Put everything back together, and done!
|
||||
|
||||
|
||||
### Frsky X9D+ 2019
|
||||
|
||||
The mod for X9D+ 2019 is contributed by a user in China, he open-sourced what he did in the following link:
|
||||
https://github.com/HIT-bangbang/Flysky-Hall-Sticks-Mod-for-X9D2019
|
||||
@@ -0,0 +1,39 @@
|
||||
# Flysky NB4+ Hardware Mod for Complete EdgeTX Support
|
||||
|
||||
With some hardware modifications, it is possible to run a full featured EdgeTX firmware on Flysky NB4+ radio. Natively, these radios have the following limitations with EdgeTX:
|
||||
|
||||
1. Similar to PL18/PL18EV, NB4+ has limited internal memory that is not big enough to carry a full SD card content. It comes with a 8 MByte sized NOR flash chip, which is sufficient for EdgeTX configuration files, but not for a full EdgeTX experience.
|
||||
2. Similar to PL18/PL18EV, NB4+ cannot keep by default the date and the time. The internal printed circuit boards are prepared for real-time-clock functionality, but there are a few components are not populated by default. For this reason, RTC functionality will not work properly with EdgeTX out of the box.
|
||||
|
||||
Below you can find step-by-step tips of how to modify your NB4+ to overcome the above mentioned problems. Be aware that warranty will be most certainly lost when following the modification steps listed here.
|
||||
|
||||
### Step 1: Install RTC battery and upgrade the flash chip
|
||||
|
||||
Open up your radio and take out the MCU main PCB that is located right under the LCD display. The MCU PCB is shown here:
|
||||
|
||||
|
||||
|
||||
The BLUE SQUARE denotes the NOR flash chip. The factory chip populated is of type W25Q64JV (8MB in size) and is not big enough to fit all required files of the EdgeTX SD card content. You can replace it with MX25L25645G that has the same form factor and pinout, but is 32MB in size. Thus, desolder the W25Q64JV and replace it with MX25L25645G. Be sure to orient the IC the same way when resoldering (match pin 1 location). Besides the choice of a 32MB flash chip, the chips that uses a WSON8 packaging can fit for replacement as well. However this packaging is better soldered using a hot blower instead of a soldering iron and can be an option to those who are skillful enough. Both W25Q512JV (64MB) and W25Q01JV (128MB) NOR flash chips are supported.
|
||||
|
||||
The RED SQUARE denotes the location of the RTC battery. This can be populated with MS-621 rechargeable battery. Please note that after installation, it needs some time for it to charge up, before RTC functionality starts to work properly.
|
||||
|
||||
In order to have the RTC working properly, only adding the RTC battery is not enough. When you flip the PCB to the other side, there are some components missing for RTC to work properly:
|
||||
|
||||
|
||||
|
||||
The RED SQUARE denotes the location of the RTC clocking circuit, you need to solder a 32kHz crystal and 2 x 3.9pF capacitors in this location. The YELLOW SQUARE denotes the location of a diode that enable the charging of the RTC battery, just solder a LL4148 diode will works. The BLUE SQUARE denotes the location of 2 capacitors: 100nF and 10pF. You may refer to the following schematic for details about the RTC battery design.
|
||||
|
||||
|
||||
|
||||
### Step 2: Flash EdgeTX
|
||||
|
||||
The following link provides instructions to flash EdgeTX to PL18/PL18EV:
|
||||
[Flashing EdgeTX to Flysky PL18 or Paladin-EV](flashing-flysky-pl18.md)
|
||||
|
||||
Flashing NB4+ uses the same procedure, only differences are the location of DFU and hard power off buttons:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
I am still working a way to have usable TX modules with NB4+, stay tune and wait for my update.
|
||||
@@ -0,0 +1,54 @@
|
||||
# Flysky PL18 & PL18EV Hardware Mod for Complete EdgeTX Support
|
||||
|
||||
With some hardware modifications, it is possible to run a full featured EdgeTX firmware on Flysky PL18 and Paladin EV radios. Natively, these radios have the following limitations with EdgeTX:
|
||||
|
||||
1. PL18/PL18EV have limited internal memory that is not big enough to carry a full SD card content. PL18/PL18EV do not have an option to expand the internal memory with a microSD card. Internally, these radios carry a 8 MByte sized NOR flash chip, which is sufficient for EdgeTX configuration files, but not for a full EdgeTX experience. For example, the std. English sound pack w/o explicit script sounds, needs already ca. 26 MBytes.
|
||||
2. PL18/PL18EV cannot output arbitrary sounds. Instead they use a dedicated sound chip with factory pre-programmed sounds. And it is also not easily possible to reprogram this chip, e.g. using a software only solution.
|
||||
3. PL18/PL18EV cannot keep by default the date and the time. PL18 and PL18EV internal printed circuit boards are prepared for real-time-clock functionality, but the required battery is not populated by default. For this reason, RTC functionality will not work properly with EdgeTX out of the box.
|
||||
|
||||
Below you can find step-by-step tips of how to modify your PL18/PL18EV to overcome the above mentioned problems. Be aware that warranty will be most certainly lost when following the modification steps listed here.
|
||||
|
||||
Craig at WTF RC Cars has created a nice video, visually explaining the hardware modification steps (click on the picture below to open the video):
|
||||
|
||||
[](https://www.youtube.com/watch?v=r_UN9fZ-rDw "Edge TX PL18 hardware mods RTC battery. Sound and memory upgrade.")
|
||||
|
||||
### Step 1: Install RTC battery and upgrade the flash chip
|
||||
|
||||
Open up your radio and take out the MCU main PCB that is located right under the LCD display. The MCU PCB is shown here:
|
||||
|
||||
|
||||
|
||||
The RED CIRCLE denotes the location of the RTC battery. This can be populated with MS-621 rechargeable battery. Please note that after installation, it needs some time for it to charge up, before RTC functionality starts to work properly.
|
||||
|
||||
The BLUE SQUARE denotes the NOR flash chip. The factory chip populated is of type W25Q64JV (8MB in size) and is not big enough to fit all required files of the EdgeTX SD card content. You can replace it with MX25L25645G that has the same form factor and pinout, but is 32MB in size. Thus, desolder the W25Q64JV and replace it with MX25L25645G. Be sure to orient the IC the same way when resoldering (match pin 1 location).
|
||||
|
||||
(Updated 2023-10-07) We discovered that the chips that uses WSON8 packaging can fit for replacement as well. However this packaging is better soldered using a hot blower instead of a soldering iron and can be an option to those who are skillful enough. And the latest branch supports W25Q512JV (64MB) and W25Q01JV (128MB) NOR flash chips as well.
|
||||
|
||||
### Step 2: Mod for DAC sound output
|
||||
|
||||
This modification reroutes the sound generation directly to the main STM32F4 microcontroller, bypassing the original factory pre-programmed audio chip. This way arbitrary sounds can be output via EdgeTX firmware. The modification is carried out on the PCB in the lower part of the radio. As a first step, disconnect the output of the sound chip to the audio amplifier by de-soldering the capacitor marked with a RED CIRCLE in the following image:
|
||||
|
||||
|
||||
|
||||
As a second step, wire up the DAC output to the sound amplifier input via a capacitor as shown below:
|
||||
|
||||
|
||||
|
||||
### Step 3: Flash EdgeTX
|
||||
|
||||
The following link provides instructions to flash EdgeTX to PL18/PL18EV:
|
||||
[Flashing EdgeTX to Flysky PL18 or Paladin-EV](flashing-flysky-pl18.md)
|
||||
|
||||
### Step 4: (PL18EV Only) Reroute stick ends
|
||||
|
||||
Since we have used one of the stick ends buttons for DAC audio output, the original stick ends output need to be rerouted to the RX of UART7.
|
||||
|
||||
|
||||
|
||||
### Step 5: (Optional PL18 Only) Install an internal Multi-Protocol Module (MPM)
|
||||
|
||||
There exists an open sourced design of an internal 4-in-1 Multi-Protocol-Module (MPM) for Flysky PL18, please see for more details: https://github.com/richardclli/DIY-PL18-InternalMPM
|
||||
|
||||
|
||||
|
||||
Have Fun!!!
|
||||
Reference in New Issue
Block a user