Foxeer was kind enough to send me one of their new Predator Nano FPV cams. The Predator Nano is a low latency, feature packed, small FPV camera.
The Nano form-factor is 14mm wide and 14mm high and thus a perfect size for your larger brushless whoops - I would recommend to use the Nano form factor on 2S builds, 75mm and up - definitely not something for your super light 1S build. But it might be an alternative for your cuurrent Micro or even full sized FPV cam.
Same as with the NamelessRC flight-controller, Bob Roogie (KababFPV) also helped designing this one. This is also the reason why these boards are so similar to each other - they even have the same build target.
In this article I will show you some details about this flight-controller and maybe help you decide if this one is the right one for your next build.
After releasing their first set of AIO flight-controllers, NamelessRC now released a nano sized video transmitter, the Nano400. The form factor of this VTX is very similar to the HGLRC nano, the Eachine nano or the TBS Unify Pro Nano - smaller than the nail on your thumb.
The NamelessRC Nano400 video transmitter weighs in at 1.8g with wires, antenna and heatshrink. The PCB itself weighs in at just 0.75g and the antenna at 0.55g. The VTX dimensions are 12.4mm by 12.4mm and 3.5mm at the highest spot - the antenna connector. The VTX has a u.FL connector as they all do in this form factor and comes with a linear antenna - you can change this to a circular polarized if you prefer.
In my last article I showed how you can get RPM filtering on your AIO flight-controller with BLHELI_S. Since then I heard from couple of people that they seem to have fried the ESC’s on their NamelessRC AIO 412(T) after flashing JESC. They did everything as per tutorial - we double checked versions, magnet count and everything else we could think of.
TLDR: DO NOT USE THE RECOMMENDED HEX FOR THE NAMELESSRC NLRC AIO 412(T) when flashing JESC.
As many of you might know, BLHELI_32 has some really great features - bi-directional DShot and ESC telemetry. This enables the ESC to transmit the RPM the motor is currently spinning with, back to the flight controller, which enables such cool things as RPM filtering. And with bi-directional DShot you do not even need to attach the ESC’s telemetry wire since the back and forth communication is done via the DShot channel.
In this article I want to show you my top picks for brushless whoop LiPo battery chargers. Unfortunately there is no one, best battery charger for all whoop classes, but rather one best charger per cell count.
The optimal brushless whoop charger in my mind would be one where you can can attach 1-3S batteries, six at the same time, each one on a separate channel. The charger would have an internal power supply so it can be powered from the outlet but would also allow to be powered from a bigger LiPo battery.
And there is a reason for that: The NamelessRC board was developed in heavy cooperation with Bob Roogie, and it seems he mixed up with whom he was talking to at one moment in time. Instead of telling NamelessRC his ideas, he told them to one of the BetaFPV techs - that is the reason why the two flight-controllers are so similar. Funny enough they also credit him on their board. Bob says that NamelessRC was not to thrilled about that incident, but they understand.
They reached out to me and asked me if I would be interested to take a closer look at their product - sure, I always like to check out new gear. So they sent me one of their NLRC AIO412 and one NLRC AIO412T flight-controllers. In this article I will show you what the differences are and maybe help you to decide which one is the right one for you. The T in AIO412T supposedly stands for “Toothpick”.
Turtle mode or flip over after crash enables you to - as the name suggests - flip your quad back over after a crash. It reduces the walks of shame and the times you need to get off your couch to flip over your brushless whoop.
Flip over after crash is a mode that can be enabled in the modes tab, in order for this mode to be available you need to have your motor protocol set to at least DSHOT300. Also make sure that your ESC’s run at least BLHELI_S version 16.7.