Assumptions. Post a link with evidence/data to back up your claims. Your feelings aren't proof of anything nor evidence.


FlySky uses AFHDS, oh yea, it's "Frequency Hopping" so it's identical.

technically speaking, FHSS is NOT an "international standard". If it was, then ALL receivers using FHSS would be compatible with ALL transmitters issue FHSS...and, as we all know, each Tx/Rx manufacturer implements their own proprietary version, which, in-turn, makes their hardware incompatible with other manufacturer's hardware. As for "frequency hopping", in general, and as already pointed out by someone else, FlySky DOES use frequency hopping technology in their transmitters & receivers. Which takes things back to the 'brown out' could have easily been that individual's own problem/fault, which could have been caused by any number of reasons having no connection to the FlySky radio you're 'blaming'.

Dynamic Frequency Hopping, IEEE Standard 802.22
It is a requirement that you follow these protocols in your specific implementation of Frequency Hopping, regardless of what you call it, and how you do it, so that all devices can share the same airspace. Inter Device Compatibility is not required, but following specifically laid out international guidelines so they can all work in the same space together...IS.

You guys are getting way to butthurt over someone saying your radio has an issue with a specific receiver.
At no point did anyone appoint blame to FlySky, dont put words in anyones mouth.
What was said is that if it is the cause, that is a problem that should be addressed, because it is a bigger issue than just "muh radio dun werk"

Go clutch your pearls elsewhere.

"More peace, love, laughter, and kindness would make the world a MUCH better place"

Ironic AF.

Seeing as how someone will want to argue instead of learn...

https://en.wikipedia.org/wiki/Freque...pread_spectrum

Note what this article is titled. FHSS is a standard, and is not a proprietary trademark of Futaba.


https://en.wikipedia.org/wiki/Dynamic_frequency_hopping

Your link actually proves their point, maybe when you quickly googled the subject in hopes of "winning" you overlooked this.

"Frequency-hopping spread spectrum (FHSS) is a method of transmitting radio signals by rapidly changing the carrier frequency among many distinct frequencies occupying a large spectral band."


I don't recall hearing anyone speak via the mouth here but didn't you write:
No? Ooooookay.


I don't recall anyone making that argument, except for the "standard" part. However, Futaba DOES IN FACT market their RX as FHSS so in that case the protocol is proprietary to the their brand. It's really not a mind bender.

Sooo...your quoting the part that proves my point? That FHSS exists, and is covered under the IEEE 802 standard???

How exactly is pointing out what FHSS is, a "gotcha"?



I dont recall anyone asking for your opinion either, but here we are.


Seeing as how you LOOOOOVE to be so pedantic...i said that in response to YOU saying...

THEIR problem, as in the other peoples radios browning out is their gear being faulty. Far from it. If one persons radio is causing others to brown out around it and glitch, then it is the fault of the radio causing the glitching, that clearly isnt following proper FHSS standards, and walking over the other radios.

You also said...

If his FlySky is breaking IEEE standards, and causing other radios that are FOLLOWING THE LAW to brown out...its not Futaba or Sanwa's fault...its FlySkys, and they need to fix it. Thankfully, it seems like it is an issue with that specific receiver unit, with telemetry, that is preventing the FHSS from happening fast enough to hop away from radios in the same band.



It is a standard, and an IEEE standard at that. And if it wasnt a standard, and FHSS rules were not followed, then everything would be browning out everything else, and nothing would work in 2.4Ghrz at all, because of how flooded that entire spectrum is.

Its not a mind bender to realize what i am saying either, but you insist on failing basic reading comprehension, and insist on arguing. Maybe you should change your username to "Pedantic Twit" instead of Werty Yui?

Lamo!! Ooooooooh snap! "Pandatic Twit"! Oh no's! You really that butthurt? This is the only part worth quoting from the gibberish you wrote which I'll admit, I mostly didn't bother reading as it's mostly back peddling and almost guaranteed nonsensical.

Bottom line is, your original and subsequent posts are 95% wrong and you're hurt over that. For some reason you're pissed off at Flysky and how they allegedly broke "standards" yet we are all still waiting for your links backing your claims. The dunce of the week award has your name all over it, nice work!

Yeah, why would you do that, you might learn something?

Huh, thats weird, i havent seen you post anything to refute the actual FHSS standards i have posted. If they are so wrtong, surely you would provide some kind of engineering article or IEEE white paper to disprove it. But you wont...because you cant, because nothing i have said is incorrect.

Hardly. I have no problem with their products at all. I responded to someone elses issue, and said that if that is a problem, FlySky need to address it, because that isnt OK. They shouldnt be going outside of the FHSS standard that everyone else is abiding by. Very simple statement, and technically correct. Only a fanboi would be so personally offended by such a statement.

If anything, it seems that you are the one who is upset that someone dare besmirch your beloved FlySky for having a technical problem that brownouts other radios.
Maybe you should send your Resume to FlySky and see if you can become their new PR Person. Youre doing a bang up job representing their products and shilling for them.
Or maybe you should just go outside and touch grass?

Looks like I need to ban a few for at least 9 months move on please

Anyone else having this issue?

I haven't. Have you checked with Jason, Casey, etc? Since almost everyone from the 'Underground' group uses the NB4, that could be your best bet.

i havent had this trouble either??

Yes, I’ve experienced this issue several times. It hasn’t caused me any major inconvenience, but it’s always concerning when it happens. Cycling power has always led to the screen powering on though.

same.. reboot fixes it. Must be some software driver issue

Technically, this doesn't have to do with the NB4...but, I just thought I'd mention it, due to the similarity. Not sure how many in here know what an EDL (electronic driver's log) is...but, they are found on commercial vehicles for companies that have been approved by the DOT to switch from paper logs. Anyway, the company I drove for uses units from Saucon. While the newer units appear to work without any problems, the older units tend to have this exact same "black screen" problem...and, the 'solution' is also the same ("reboot", and the problem doesn't happen again for at least a couple weeks). As the same software updates are pushed out to the old and new units, alike, that would lead me to believe that the problem is not software related...it would have to either be a hardware problem, or a BIOS problem.

For those having the "black screen" problem with the NB4, are yours one of the more-recently-manufactured units, or one of the older-manufactured units? If this problem is affecting only the older units, it could be similar to the Saucon problem, Which would lead me to believe that, at some point, FlySky either switched certain components to more updated components and/or the BIOS (or equivalent of BIOS) is different than the BIOS in newer units. This is just a theory...but, it could be an 'accurate' one.