'rfnano' range not as good as 'UNO with an nRF24'

Hi all. For months, your answers to other's problems have come up in my searches and been indispensable. But now, I'm forced to ask my specific question.

The project is a home-made version of a BlazePod. In brief, a master unit sends commands to slave units, which then light up. The units respond with the number of ms they were lit up for before they were 'hit'.

I'm in the early stages of development: I've got as far as a master/slave pair that perform this basic functionality using an UNO, and an nRF24.

Master code.
Slave code.

That's great, so far... it all works over a range of at least 20m, which is more than far enough.

However, now I'm thinking of moving into a more suitable form-factor, I've switched to something that was sold as being similar to an rf-nano:

(it says 'TSTAR TECH') on the bottom.

With this unit, the range has dropped to roughly an arms length.

I've got some ideas for improving the range:

  • Adding #define RF_PWR_HIGH to the code. (It tried it, not sure it helped.)
  • Soldering some AWG22 to what looks like an 'antenna hole' on the rfnano.
  • Ordering a 'genuine' rfnano and seeing if that's any better.

I'm open to other suggestions - has anyone got any please?

Thanks, in advance, for whatever input or comments you may have.

So these 'new' modules have a range thats only about 1/20th of the more normal NRF24 module, using the same code ?

If the 'new' modules had been mine, I would bin them.

Thanks. It does seem to be the modules that are the fault, doesn't it? Once they're in the bin, what would you do? Would you try a different 'rfnano' from a different supplier?

Or, does the rfnano just not have as good a range as the 'seperate arduino and NRF24 module' solution?

Both devices use (or at least pretend to) the same RF device.

So whilst you might expect a 3dB or a maybe a little more difference in actual radiated signal due to differences in design of the component layout and PCB antenna, your reporting maybe 25dB difference, which just does not sound right to me.

You could wire up a Pro Mini and a LoRa module (or other) for around the same size as the 'rfnano', distance problem solved. Although with the ground based BlazePods being only a few cm off the ground you might be limited to a kilometer or so due to curvature of the Earth issues (no the Earth is not flat!) .

With any RF application such as this, its essential that you try out the distances and approximate data rates you need (slower normally means further) in an actual simulated situation.

I'm just guessing here. Is there something positioned next to the antenna that should be moved away from it?

1 Like

Like an oversized button and pieces of wire? :grin:

And - a breadboard with embedded metal strips! :roll_eyes:

1 Like

Great point. I've switched to a much smaller button and moved it to the other end of the breadboard, like this:

There was no improvement, but great suggestion.

Again, somehow I didn't think of this. :man_facepalming: So... let's get rid of the breadboard entirely:

The range did not improve by any noticeable amount.

So.... I've ordered a different model of 'rf-nano-type-thing' and I'll try again with that. Maybe these 'TSTAR TECH' ones are just rubbish?!

Thanks everyone for your input so far - I really appreciate it.

Another small update:

I've built something quite similar to the original set-up, but using Nano instead of Uno. Great range. So... If the new RFNanos (when they arrive) are just as bad as the 'TSTAR TECH' ones, I've got a fallback option.

People at modezero use them for r/c without any drama.
I think the ones they use come from Keys.

1 Like

The RFNanos arrived, but I cant get them to even run the BLINK sample code.

I've reached out for help, I'll keep you posted.

I'd love to know more about this 'modezero'. What is it? If they know about RFNano I might be able to reach out to them for help...

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.