Hello,

I encountered an issue when connecting TBS Unify Pro32 HV analogue VTX and SpeedyBee F405 FC + ESC stack. I soldered exactly as instucted and in TBS Agent selected Smart Audio in Data Port setting, also uploaded LUA from TBS website that should be correct: 

FC -> VTX
=========
9V->7Vto26V
GND->GND
GND->GND
VTX->VIDEO
T1->CRSF/SMARTAUDIO

There are three wierd things that I'd like to solve. 

1) why is there Devise Ready: False message
2) why do I see a camera feed in goggles, but no OSD
3) why is there an VTX(MSP+Display port) setting that is impossible to change to VTX (TBS Smart Audio)? When I do change it (pick it from the drop down menu) and click Save and Reboot, the setting goes back to VTX(MSP+Display port) after reboot.

CLI dump here: https://we.tl/t-DLpS7kPh11

Can anyone help please? I am already couple hours into this issue and cannot see the way out. 






Thank you!

The SpeedyBee F405 V3 FC is plagued with hardware design flaws, so if you have any strange issues then it might be down to that. One particular issue is that you can't have both OSD and blackbox logging switched on at the same time due to an SPI bus conflict. If you switch on blackbox logging you will lose the OSD. Likewise, there is a DMA conflict that can cause some issues when using DSHOT for the ESC protocol.

The issue you are seeing with the SmartAudio setting might also be related to the poor hardware design of that particular FC. Try using a different UART to see if it works on that instead.

SpeedyBee claim that they have fixed all of the hardware design issues in the newer V4 version of the same FC.

(02-May-2024, 05:42 PM)SnowLeopardFPV Wrote: The SpeedyBee F405 V3 FC is plagued with hardware design flaws, so if you have any strange issues then it might be down to that. One particular issue is that you can't have both OSD and blackbox logging switched on at the same time due to an SPI bus conflict. If you switch on blackbox logging you will lose the OSD. Likewise, there is a DMA conflict that can cause some issues when using DSHOT for the ESC protocol.

The issue you are seeing with the SmartAudio setting might also be related to the poor hardware design of that particular FC. Try using a different UART to see if it works on that instead.

SpeedyBee claim that they have fixed all of the hardware design issues in the newer V4 version of the same FC.

Thank you for the reply! I managed to fix an issue with Device Ready: False message. Configuration/MSP was enabled and is not supposed to be. That fixed issue no. 3 as well. 

However i turned of black box logging in backbox tab, rebooted, but OSD did not show up. Any other ideas?

(02-May-2024, 08:12 PM)Shoto Wrote: i turned of black box logging in backbox tab, rebooted, but OSD did not show up. Any other ideas?

I just checked your CLI dump and you're using an analog viseo system but you have the Video Format set to "HD" which only works for digital video systems. In Betaflight Configurator go to the OSD tab and set the Video Format (top right) to either "PAL" or "NTSC" to match the signal type that your camera is putting out. Using "Auto" isn't recommended because sometimes the FC isn't able to correctly detect the camera signal type, so it's safer / better to explicitly set the correct format. Don't forget to click the "Save" button in the bottom right once you've done that.

(02-May-2024, 10:10 PM)SnowLeopardFPV Wrote: I just checked your CLI dump and you're using an analog viseo system but you have the Video Format set to "HD" which only works for digital video systems. In Betaflight Configurator go to the OSD tab and set the Video Format (top right) to either "PAL" or "NTSC" to match the signal type that your camera is putting out. Using "Auto" isn't recommended because sometimes the FC isn't able to correctly detect the camera signal type, so it's safer / better to explicitly set the correct format. Don't forget to click the "Save" button in the bottom right once you've done that.

Fixed! HD was one problem. However the key was to run set osd_displayport_device = MAX7456 command in CLI. Suddenly OSD appeared.

The default value of "AUTO" should work for the osd_displayport_device setting, but maybe you need to explicitly set the value of that to "MAX7456" for the SpeedyBee F405 V3 FC because of the hardware design flaws. At least it's now working which is the main thing.