I suppose you could use a dual channel scope but you'd have to take apart the transmitter to get to the pot for the steering, throttle, etc. Then you could hook up the second channel to the receiver output and take some measurements to find out how long it takes for TX input to become RX output.

A FlySky rep. told me it's less than 3 ms. I also have a Sanwa MT-44 which is suppose to have 2.6 ms but I have not yet had the chance to test the Noble on the track.

Saw a video where someone was doing actual latency measurements, and as you describe, seemed pretty elaborate. Downloading, opening, decoding and comparing some packet things that radios and receivers send back and forth to each other.

The high speed video thing, seems much more simple. Even though it will not satisfy the need to have a actual measurement in milliseconds.

I'm looking forward to hear your opinion.
I was looking at MT-44 too but went with NB4 because of receiver price $35 vs $25. Saving a bit here and there helps a lot for me.

Trust me, I would love for it to be less than 3ms. But if it was, why would they market it as 3ms in "Sport Mode"?

I'm not trying to be a Negative Nancy here, but I do find the marketing/info thing to be a bit off. Probably the language barrier.

hi i seen there was some discussion about the 1 or 2 way RF setup, is 1 way actually faster?
i tried to bind in 1 way but it never completes binding?

Transmitter case idea
 

https://cimg2.ibsrv.net/gimg/www.rct...626ae9f189.png

Line lunchbox with foam mat from Harbor Freight
https://cimg2.ibsrv.net/gimg/www.rct...cfa5919585.jpg

Made transmitter case out of a lunch box
https://cimg1.ibsrv.net/gimg/www.rct...95a13bff1f.jpg

Received my Noble in anticipation of the Mini Z Evo RX release. I have close to 5 hours of messing with this thing and no luck... It will not connect to either of the included fgr4s Rx's no matter what I try. My guess is that the Rx's need updating before they will bind but it's just not happening. Every youtube tutorial and forum post that I figured would help out has been a bust. Flysky did answer an email with what I hoped would work but still no luck. I followed their quickstart guide to a T. I updated the TX firmware, did the "RF Update", jumped the RX to force it into mandatory bind mode. I went through every process no fewer than a couple dozen times. I can't imagine what I'm missing and need a hail mary before I throw in the towel. Anyone?!

Here's everything I tried... https://github.com/open-flysky/FLYSK...ransmitter/NB4

Hello, what firmware versions have you tried? I may have an older version saved on my computer. Are the receiver LEDs flashing to indicate they're in bind mode?

Did you update the receiver? If you update the trans. firmware you must update then rebind each receiver.

Really sounds to me like you need to update the receivers. And just to make sure, here's a quick run down on how to do so.

First, make sure your receiver has a binding plug plugged in the update way (not sure what they call this). Its plugged in perpendicular to what you would normally do, and on the bind end. See the pic here:
https://cimg8.ibsrv.net/gimg/www.rct...cda3beeb23.jpg

After plugging the binding plug in this way, power the receiver on.

Then turn on your Noble, and go to "RX SET", shown here in the bottom left.
https://cimg1.ibsrv.net/gimg/www.rct...e1400ebbd4.jpg

Then scroll all the way down and select "Update Receiver"
https://cimg5.ibsrv.net/gimg/www.rct...1aa4845698.jpg

Then select what receiver you are using. And click "Update"
https://cimg2.ibsrv.net/gimg/www.rct...c2f2018af2.jpg

This should be it. You'll then see a progress bar and the radio will notify you when its done.

After that, turn off the receiver, rotate the binding plug to the "normal" way, in the bind port, and bind the radio.

I can make a more detailed explanation of that as well if needed. But its pretty much the same thing, binding plug in, power on receiver, "RX SET", "Bind With A Receiver", done.

Yeah, that's nuts. I have updated receivers several times, never had a problem. So if your doing the exact same thing, and can't get it to work, even after firmware update, I would guess you have some kind of hardware issue.

Sucks.

I wish you luck.