Dave 2.4ghz or 1.3ghz vtx are supposed to have long ranges, you could also use a tracking system with the receiver using helical antennas to try get to your 30 km but there is a lot to learn and implement properly. There is always onboard video recording an autonomous flight that goes 30 km.

Dave maybesomething bigger?

Dave itsfor larger tx than jumper t, you can buy nano elrs modules, or there are adaptors

Dave iteventually worked but you won't get full power. also, you have to update firmware on the taranis so you can use-enable 'one bit' as the old taranis doesn't have enough processing power? Anyway its working great, just can't get the max 1W power .

Dave itsa fpv camera

Dave noyou need a smaller slim version which slides on, this one needs a JR module bay like in a boxer or tx16,or taranis xd90 which you push it into.

Dave itsbuilt in. doesn't have sd card

Dave yesthey all fit 25.5x25.5 mm

Dave Firmware:betaflight_4.3.0 JHEF411. if you go to the product page and scroll down a little there is Specifications. click on it and More Details you will get everything including the firmware type of your ESCs and a diagram picture

Dave youwould probably do ok wearing contact lenses

Dave it says so in the description and it looks like it on the photos. i have a fatshark though

Dave iam running happy model EP1 and EP2 receivers and a matek diversity receiver as well as Namimno receivers with my Namimno TX. I also have a happy model nano slim TX which works with the same receivers. They have the same firmware update and binding phrase when flashing their specific firmwares.

Dave yes,i am using it on a frsky xlite which has same sized port

Dave allmotors go can go CW or CCW. their direction can be changed through swapping around two of the three wires that come from the motor.

Dave lookingat the diagram on the product page it shows the vtx(video transmitter) rx going to a pad (unnamed)on the far right, top of the flight controller, which i would say is tx1 as there is only a rx1 shown on the fc. You use the sbus which is uart2 or the tx2 and rx2 for your receiver depending which receiver you choose. Once you have connected all the wires from the vtx to the flight controller you enable the smart audio or Tramp irc (some are a tramp vtx and some are a smart audio vtx you will have to check the specs but they both enable same thing we all call smart audio just slighty different protocols) in the ports tab in betaflight configurator in peripherals column on the uart1 row. You will also have to download, depending on your vtx type, the smart audio 1 (older vtx) or 2 or the tramp files into the video transmitter tab in betaflight. you can search up smart audio files to get the correct file. more recent smart audio type transmitters have the smart audio 2 version protocol. i think there is only one tramp type file. Once you have that done than you can use smart audio to change the settings using stick movements and the goggles:)

Dave yes,just protect it from hard contact and water, don't feed it anymore than the 2.5-5.5 Volts and try have some air flow around it even though it is only 25mW power.

Dave theyellow wire is your video in from the camera, goes into the VI pad(video in)on your flight controller. the white wire is video out and goes to the VO pad(video out) on your flight controller. the green wire is smart audio and that goes to a spare uart tx pad and you enable it in betaflight ports tab allowing you to change settings through your goggles and radio transmitters sticks. red wire(positive) goes to a 5 volt (5V)pad on the flight controller and the black wire(ground) goes to a G(ground)pad on the flight controller. they all will have to be soldered to the pads. you will notice the yellow and white wires are connected with the small yellow wire, that allows the video in to connect with the video out if you want to use the AIO cam without connecting it to a flight controller for OSD.

Dave youneed a video transmitter for each camera and a video receiver(fpv goggles have a video receiver module)

Dave edge tx 2.6 supposedly enabled the touch screen