01-Nov-2020, 09:44 PM (This post was last modified: 01-Nov-2020, 10:28 PM by JohnBos.)
I have just bought a new one and I am trying to configure it. I have managed to unlock it but I have some issues, when I power it up and I am looking in the goggles, the video transmission works ok and after 5 seconds disappears, when I move the antenna the video is getting better but not as good as the begging.
In addition, the red LED blinks( I found on google that maybe the ground on the VTX is broken but I checked and it is okay.) see below my configuration:
Any suggestions? as I have spent more than 3 hours on this matter without any luck.
EDITED: After I disabled Betaflight VTX setting to none works okay.
02-Nov-2020, 01:26 AM (This post was last modified: 02-Nov-2020, 01:28 AM by hugnosed_bat.)
sounds like it was set to "pitmode" in betaflight vtx tables. smartaudio over the fc would alow you to settup a cannels bands and lower ofer the configurator or over betaflight osd. if you wont like to use that, you are fine. if you would like these options, i beleive it would be a settup issue.
(02-Nov-2020, 01:26 AM)hugnosed_bat Wrote: sounds like it was set to "pitmode" in betaflight vtx tables. smartaudio over the fc would alow you to settup a cannels bands and lower ofer the configurator or over betaflight osd. if you wont like to use that, you are fine. if you would like these options, i beleive it would be a settup issue.
what betafight version do you use?
In my betaflight configuration, I had removed the PIT mode, it looks very strange. I will need to investigate more.
02-Nov-2020, 10:35 AM (This post was last modified: 02-Nov-2020, 10:35 AM by hugnosed_bat.)
did you install the vtx table for your unify?
i had an issue a few times, it allways started in pitmode, i dont know why that was. i would power the quad, get into the osd settups with the tansmitter (short discribed at boot up); featers/vtx sa/ than check if pitmode is set to "off" or change the powerlevel manualy go to set: "yes"
have a look if you can getout of pitmode with this way
02-Nov-2020, 04:09 PM (This post was last modified: 03-Nov-2020, 01:18 PM by JohnBos.)
(02-Nov-2020, 10:35 AM)hugnosed_bat Wrote: did you install the vtx table for your unify?
i had an issue a few times, it allways started in pitmode, i dont know why that was. i would power the quad, get into the osd settups with the tansmitter (short discribed at boot up); featers/vtx sa/ than check if pitmode is set to "off" or change the powerlevel manualy go to set: "yes"
have a look if you can getout of pitmode with this way
thanks very much for your help. Sorry, how can I install the table for unify? Please find attached the picture with the settings. Please advise if I have done something wrong.
06-Nov-2020, 09:24 PM (This post was last modified: 06-Nov-2020, 09:24 PM by JohnBos.)
(06-Nov-2020, 04:59 PM)SnowLeopardFPV Wrote: Run the following block of commands in the CLI to set up your VTX tables correctly for the TBS Unify Pro32 HV...
Code:
vtxtable bands 5 vtxtable channels 8 vtxtable band 1 BOSCAM_A A FACTORY 5865 5845 5825 5805 5785 5765 5745 0 vtxtable band 2 BOSCAM_B B FACTORY 5733 5752 5771 5790 5809 5828 5847 5866 vtxtable band 3 BOSCAM_E E FACTORY 0 0 0 0 0 0 0 0 vtxtable band 3 FATSHARK F FACTORY 5740 5760 5780 5800 5820 5840 5860 0 vtxtable band 4 RACEBAND R FACTORY 0 0 5732 5769 5806 5843 0 0 vtxtable powerlevels 4 vtxtable powerlabels 25 100 400 1000 vtxtable powervalues 14 20 26 30 save
Thanks, SnowLeopardFPV it worked by changing this line vtxtable powerlabels 25 100 400 1000 to this:vtxtable powerlabels 25 100 400 1w
(06-Nov-2020, 09:24 PM)JohnBos Wrote: Thanks, SnowLeopardFPV it worked by changing this line vtxtable powerlabels 25 100 400 1000 to this:vtxtable powerlabels 25 100 400 1w
not sure why, but it works now. thanks very much.
Hesitant to bump an old thread, but I wanted to point out that the issue here is that vtxtable powerlabels are limited to three (3) characters. So '1000' is not a valid powerlabel, but '1W' is. Hopefully this helps someone out!
(06-Apr-2021, 05:18 AM)V-22 Wrote: Hesitant to bump an old thread, but I wanted to point out that the issue here is that vtxtable powerlabels are limited to three (3) characters. So '1000' is not a valid powerlabel, but '1W' is. Hopefully this helps someone out!
Yes, that is correct. I wasn't aware of the 3-character limitation at the time of writing my original reply. It would be a simple task for the Betaflight developers to increase the limit to 4 characters which would then better support some of the newer high powered VTX's such as the Rush Tank Solo which can go up to 1.6W. Unfortunately with the 3 character restriction you can't specify either 1.6W or 1600, so the best you can do is put 1W+. I guess it wouldn't be on the top of their priority list to make that change.