Request to add PINIO Support to FLYWOO GOKU F405HD AIO to control it's 9V VTX power supply output
There is currently no Firmware release for this FC to support PINIO. This 2S AIO FC is pretty unique in that it includes SDA & SCL pins for good Compass and GPS nav capability. It's a great FC for Sub250g builds but given it targets HD VTXs only, some method to avoiding VTX overheating during GPS lock seems VERY desirable
A Mode needs to be added (USER1 or USER2 or other) to enable the VTX power supply switching, - thereby avoiding over heating problems while waiting for a GPS lock.
I understand the boards 9V VTX supply was controlled by PINIO on B05 on early boards but was changed to C08 on later revisions.
VTX power switching is a highly desirable, (if not fundamental !) for ALL users of this FC since it targets HD VTXs.
Many thanks in advance if this can provided
This post explains how to get the vtx working on the later board in beta flight:
# This set of commands gets the 9V BEC working again
resource motor 8 none
resource pinio 1 c08
set pinio_box = 40, 255, 255, 255
set box_user_1_name = 9V SWITCH
# This command aligns the gyro to where it is supposed to be
set gyro_1_sensor_align = CW180FLIP
save
It agrees that the pin is c08.
Taken from here: https://intofpv.com/t-flywoo-goku-f405-hd-9v-vtx-switch-issue
It turns out I'm mistaken and I don't have this board, I have the Flywoo GOKU GN405 Nano HD FC V3.
As my board doesn't have the 2A BEC for the VTX, it seems very unlikely I'll be able to switch it without a dedicated realpit or similar vtx switch.
If anyone else is wondering, for completeness, PC8 is the correct one for the "GOKU F405 HD 1-2S 12A ELRS AIO V2" board (the white one with a vertical USB type C connector). You can actually test if it's on or off based on the bright orange LED near the 9V silkscreen (near the dji connector). I don't know where B05 comes from, but seems other boards make references to it.
The way I found this out is by flashing the appropriate arducopter firmware and playing with relay 3, it did make the orange led go on and off. Here's the appropriate section in arducopter's hwdefs.dat:
# GPIOs
PB5 PINIO1 OUTPUT GPIO(81) LOW
define RELAY2_PIN_DEFAULT 81
PC8 PINIO2 OUTPUT GPIO(82) LOW
define RELAY3_PIN_DEFAULT 82
More data points: my fc board came with the flylens75 + hdzero. After spending an infuriating amount of time trying to make it work I discovered my hdzero Whoop V2 lite vtx was not actually connected to this 9V bec, but it was hooked up directly to the battery for some reason. Also, it's not UART6 (like the dji connector), it's hooked up to UART2. You can confirm this by investigating the wiring.
I took a stab at resolving this issue and perhaps sending a PR, but I'm not having much luck.
Here's my git diff so far:
diff --git a/src/main/target/FLYWOOF405PRO/config.c b/src/main/target/FLYWOOF405PRO/config.c
index dfe6c0ce1..a8dc5fd29 100644
--- a/src/main/target/FLYWOOF405PRO/config.c
+++ b/src/main/target/FLYWOOF405PRO/config.c
@@ -31,4 +31,7 @@ void targetConfiguration(void)
timerOverridesMutable(timer2id(TIM3))->outputMode = OUTPUT_MODE_MOTORS;
timerOverridesMutable(timer2id(TIM2))->outputMode = OUTPUT_MODE_MOTORS;
+
+ pinioBoxConfigMutable()->permanentId[0] = BOX_PERMANENT_ID_USER1;
+ pinioBoxConfigMutable()->permanentId[1] = BOX_PERMANENT_ID_USER2;
}
diff --git a/src/main/target/FLYWOOF405PRO/target.h b/src/main/target/FLYWOOF405PRO/target.h
index a5a02c5fe..ef47a6f82 100644
--- a/src/main/target/FLYWOOF405PRO/target.h
+++ b/src/main/target/FLYWOOF405PRO/target.h
@@ -152,6 +152,12 @@
#define CURRENT_METER_ADC_CHANNEL ADC_CHN_2
#define RSSI_ADC_CHANNEL ADC_CHN_3
+// *************** PINIO ***************************
+#define USE_PINIO
+#define USE_PINIOBOX
+#define PINIO1_PIN PB5
+#define PINIO2_PIN PC8
+
// *************** LED2812 ************************
#define USE_LED_STRIP
#define WS2811_PIN PA9
I tried playing in the modes tab, despite my remote being configured correctly, resources command in the cli showing correctly too, it doesn't seem to make the led or 9v change.