Surely the release notes/installation instructions should specify the requirements?

Not always. Different manufacturers, different countries, different ways of doing things.

OK Flysky Gurus

I have two issues.

First is my first radio bricked when trying to update its firmware to get the menu option to switch the radio to 8ch mode to connect an FGr8B for my crawler. Screen is just wavey vertical lines with mostly a greyish background except for a pale blue background bar at the bottom of the screen. I'll try to post a pic of it. The radio will not connect to the software to try to read if it took the firmware but I am guessing it didnt as it froze and rebooted at 7% and went to this state. Any ideas on recovering it other than shipping back to Flysky in China?

Guess I dont have enough posts yet to put up a picture. Oh well the description is right on and once I get the rght number of posts then I'll try to put it up unless I have totally written that radio off.

Second is actually the reason the first happened. I bought a second radio in the assumption that the first wasnt recoverable other than by shipping it off to China. So I am back at the starting point again. I need to get the radio to an 8 channel mode so I can use all the ports in the FGr8B. The receiver will bind to the radio but it doesnt go past ch 4 for settings in the radio. firmware of the radio is 2.0.100std and hardware 1.2. The receiver is 1.2 and 1.2 and was updated with the radio after binding. I tried this thread and youtube and the only thing I see for firmware 2.0.100 is the general how to update by WTF RC. I did see his video for the FGr8B and firmware 2.0.93 to get to 8 channel and connect the FGr8B. Problem is in 2.0.100 does not show the channel menu option in the SYSTEM menu. What the heck am I doing wrong? Should I just send this thing back ( yay buddy bezos ) and get the Pro?

Any help is greatly appreciated.

Radio

Firmware 2.0.100 channel selection location
 

***Update***

Well I am a dummy. Found the setting for number of channels in a different part of the menu structure. So if you are looking for it in firmware 2.0.100 following WTF RCs Youtube vid of firmware 2.0.93. Dont get frustrated like I did and go to the model menu and right there below the NAME field is the CHANNEL NUMBER DEFINITION field.

So. Anybody have any ideas on the failed firmware update radio?

Thanks in advance for any help or insight to correct my dummy ways.

Radio

Fix for failed firmware update maybe?
 

***** UPDATE 2 *****

Ok. So last night after posting I decided to try to reset the radio by draining its internal battery. I had already tried the reset and stop buttons on the grip behind the rubber to no avail. So I left it on until it died just a little bit ago, thankfully in its failed state the auto power off did not function and the audible tones also were not functioning so it was a peaceful night waiting for it to run down. Tried to fire up the radio and it would run for a minute and shut down. So pretty well dead. That seems to have cleared whatever was stopping it from talking to the update software package. Hooked it up to the computer and powered it on to hear the delightful tone of the computer recognizing it as a USB device. Tried the update software and it took and rebooted normally after the update. So there is a possible fix for that symptom if you have a firmware update failure.

So now what to do with a second radio that I dont really need.

Thanks for reading and hope this helps someone else out before they go spending money on a second radio.

Radio

I'm a bit new to the noble nb4.
I'm having issues with the signal range when running boats. My transmitter currently is running firmware 2.0.100std.
Can I update to the FCC version with no issues?
I believe the FCC version should provide better range?

Simple answer: yes & yes

yes you can.. what receiver are you using and how do you have the antenna configured?

Is the NB4 worth having for racing buggies over the RC8X?

I have the RC8X already and while I'm working out some issues with the receiver disconnecting due to voltage sag issues with my SAVOX servo, I ordered one of the Glitch Protectors to fix the brownouts (it started to happened during my second battery pack on the track). While I was shopping around, I was lookin into the NB4 and I was curious if it was worth using that for racing and using the RC8X for bashing.

If you're having voltage sags, I'd be looking at your esc. I noticed you're running a 4x4 Slash? What motor and esc are you running.

While both radios are great, the NB4 would be better suited for racing. At my old track (Nor-Cal Hobbies, San Jose, CA), there were several using them. At the local Mini-Z track, almost all racers are using them. As for the RC8X, it's great for use in drag racing & speedrunning...but, beyond that, it's probably better suited for bashing. One possible (ie. don't take my word on it, as I haven't actually tried it...yet) exception might be in racing RC boats.

I've recently switched from sanwa MT44 radio to NB4 and I found a problem
In sanwa radio, there's a feature called safety link
It gives each rx some kind of ID tag to prevent two or more rx activated at the same time
So if I turn on two kits with both of the rx bind to one tx, both of them will not move at the same time
Only the kit with the assigned ID will be activated
But I couldn't find this feature in NB4
Is there a way to fix this issue?

I haven't found that to be a problem. I have around five cars set up in my NB4, and always have to change the model in the radio to what I am running.

It can be a problem if you are playing at the track
You goes to second car and forgot to turn off the first car
Especially if you put the first car on the bench, it will jump out of control
Because even if you change the model it's still connected

I'll have to check that out. I pretty much only race, so only if I race back to back would I possibly run into that situation.