Uploaded August 2024 | Updated November 2026, 3 hours ago
This is one last test of the HEQ gimbal after I tried their new firmware. I ended up using their firmware to just help me go back to locking the yaw mechanically like I was before. It was the most reliable way for me to go about it without ever having to worry about random jitter. If this was just an on-road car then I would just outright use all 3 axes and set the holding torque higher.
I also wanted to test how it would look driving around with a piece of thin polycarbonate sheet. It didn't work out so well because of the voltmeter reflection so I later put an angled cover over them to block that. I figured I would try to use a simple cover like that just to protect the gimbal from getting caught on things in the woods.
The new HEQ firmware comes with more features but it also allows you to adjust the motor holding torque from standard 10000 value up to 30000. I tested the gimbal out again with the torque all the way up and noticed most of the jitter went away and it was pretty smooth. It was almost perfect until I started going over rocks and sticks etc. I got tired of messing with it and just went back to locking the yaw and using my own servo. I figured since they now allow me to reduce the torque on the yaw then I can worry less about locking it.
I later realized there's probably a fix I have yet to try or maybe won't even try cause I don't care anymore. The gimbal is weighted such that the camera makes it front heavy. I think this is why it was struggling with the yaw a lot for me because it would easily sort of slingshot one way or the other. If the higher holding torque almost fixed it then maybe it just needs to be better balanced. I think I stacked a couple pennies or dimes on the back of it and thought it had about balanced out but I never tested that theory.
This is one last test of the HEQ gimbal after I tried their new firmware. I ended up using their firmware to just help me go back to locking the yaw mechanically like I was before. It was the most reliable way for me to go about it without ever having to worry about random jitter. If this was just an on-road car then I would just outright use all 3 axes and set the holding torque higher.
I also wanted to test how it would look driving around with a piece of thin polycarbonate sheet. It didn't work out so well because of the voltmeter reflection so I later put an angled cover over them to block that. I figured I would try to use a simple cover like that just to protect the gimbal from getting caught on things in the woods.
The new HEQ firmware comes with more features but it also allows you to adjust the motor holding torque from standard 10000 value up to 30000. I tested the gimbal out again with the torque all the way up and noticed most of the jitter went away and it was pretty smooth. It was almost perfect until I started going over rocks and sticks etc. I got tired of messing with it and just went back to locking the yaw and using my own servo. I figured since they now allow me to reduce the torque on the yaw then I can worry less about locking it.
I later realized there's probably a fix I have yet to try or maybe won't even try cause I don't care anymore. The gimbal is weighted such that the camera makes it front heavy. I think this is why it was struggling with the yaw a lot for me because it would easily sort of slingshot one way or the other. If the higher holding torque almost fixed it then maybe it just needs to be better balanced. I think I stacked a couple pennies or dimes on the back of it and thought it had about balanced out but I never tested that theory.









![RC Ground FPV How-To (Analog + DJI O3)
I might have covered some of this in less detail in other videos but here is a long compilation of how Im doing FPV with these various cars. Control protocols are a whole different video so Im not really concerned with that since Im using PPM and TBS Crossfire. Whatever protocol you use you just need to make sure that your controller is compatible with the receiver youre using on the car. Since youre mixing different frequencies on the same car for both video and control, you want to make sure none of these frequencies are stepping on each other (harmonics of a lower freq which can interfere with the tx of a higher freq). This is what my notch filters are for since I use 915Mhz control combined with transmitters on 1280Mhz.
[VTX/VRX Popular Frequency Options]
- 1.2Ghz - If this does not work decently for you using the cheapest 800mW options I would not invest in it further. You may have the most luck using 433Mhz control but if 2.4Ghz or 1.2Ghz control and proper filters do not provide decent results it might not be something to pursue any further for various possible reasons.
- 2.4Ghz - I havent tried this but theoretically it should be better than 5.8Ghz. 1.2Ghz and 2.4Ghz would always be the route I would try first.. but if those do not work out then 5.8Ghz might just do it for you. Video options for 2.4Ghz are probably going to be few.
- 5.8Ghz - This is typically going to give decent results for a lot of people since 5.8Ghz is so widely supported and offers so many high power transmitters and good receivers.
[Popular Control Frequencies]
- 433Mhz - Never tried it but I would guess its one of the best options. Not a lot out there anymore I know of aside from MFDLink.
- 915Mhz - This is what I use with Crossfire and seems to work very well. Not the cause of my 1.2Ghz video issues.
- 2.4Ghz - Maybe most common and probably fine for most people. A good 2.4Ghz controller can go hundreds of meters easily. I would only try to improve this if I can tell my control range is dying before my video range. You dont want to be in a position where youre looking at a clear image of your far away car you cant control anymore, but you also dont need a mile of theoretical control range if youre just hitting parking lots or fields.
There are tons of other things that can be done with ground stuff including the use of various telemetry but I would recommend keeping it as simple as possible for a first build. Is there one best solution for all? Not really. Analog can have extremely low latency with the right equipment which makes it very useful if you want to FPV drones. This is typically why you may not see a lot of people using both DJI and analog rigs with goggles. DJI doesnt want to play well with anything but proprietary stuff, and analog goggles can be expensive. Some people prefer to just get good goggles for both HD and analog and go with a different platform aside from the DJI Air Units.
See Chad Rains for a good video on long range tips - https://www.youtube.com/watch?v=mKvI3Gj3E9s RC Ground FPV How-To (Analog + DJI O3)](https://i.ytimg.com/vi/hL6XY024JPo/mqdefault.jpg)
