RACEBAND, SIMPLIFIED MENU, TX POWER IN MW

[carabidulebabat]

Add equivalent wifi chan to standard analog/hdzero raceband channel, these channel work on 40MHZ AND 20MHZ
Add tx power in MW
Improve the user experience, by simplify the menu
Only one vtx menu, avoid user error and burn pa
DISABLE OR ENABL ALINK IN VTXMENU

[henkwiedig]

• How are we going to load the diffrent files for the diffrent hardware ?
  Maybe we need to ammend the builder to copy the correct config to the correct build.

• Are you sure for the frequencies ?

R1 5658  - 5660 MHz [132] Error: 2 Mhz
R2 5695  - 5700 MHz [140] Error: 5 Mhz
R3 5732  - 5745 MHz [149] Error: 13 Mhz
R4 5769  - 5785 MHz [157] Error: 16 Mhz
R5 5806  - 5825 MHz [165] Error: 19 Mhz
R6 5843  - 5865 MHz [173] Error: 22 Mhz

• Where is R7 and R8 ?

• There is a general problem with Raceband vs Wlan Channels. They do not exactly match.
  Even when selecting close channels.

[carabidulebabat]

hello @henkwiedig , yes each file is hardware specific, to avoid user error and burning pa, I think every target gonna get specific vtx menu that its integrate in build, for example, emax wyver target will get emax vtx menu, for the race band I select band that is near race band for analog, its just a proof of concept and more a way to find channel easier.
In other hd system like dji or ws, they don't use analog channel for raceband but frequency that is near. Raceband in only for analog, I just make a equivalent with approx the same distance between each channel to avoid interference and make sure that channel is avaible for 20MHZ and 40MHZ. The first function of raceband. for R7 and R8 I can't find equivalent but If can find a way, I will add all the raceband. for frequencie is all good I tested it. See flight on telegram on channel 132 with alink and without

[henkwiedig]

I was there maybe 4 month ago as well. For OpenIPC it just does not make sense to talk in Raceband frequencies.
You now picket OpenIPC_R6 to be 5865 wich is closer to Analog_R7 as to Analog_R6.
The error margin is 22Mhz which is a half carrier for Analog.
We have the whole mess with DJI's Frequencies (frequency error and channel renameing) and OpenIPC now opens the next problem.
I think i would make more sense to inform the user that selecting Cahnnel 173@5865Mhz might interfiere with R6 and R7 and they can then arrange their channel assignment.
Simply letting the user select R6 makeing him believe he is on Analog R6 will cause problems.
Sadly our drivers do not support Mhz exact tuneing currently, wich would be preferrable.

[carabidulebabat]

Ok, I understand, yes it will be the same problem as for other digital system. so think I will implement the old system.

[carabidulebabat]

I can remove the "raceband" channel and add the old system and redo a pull request.