Accessing ClientID

[Richard]

Hi,

I've been reading through the docs, but can't find a way to get to the clientID - it mentions looking in the subclasses, but I don't have any in my distribution. Could anyone point me in the right direction?

Cheers,

Richard

[Richard]

Sorry - I guess that wasn't too clear. When I configure my radio, I "setThisAddress" and pass in a 'sender ID'.

I was wondering if this was transmitted along with the payload, and if so - how I could access it?

Cheers!

[Mike McCauley]

Hello,

On Tuesday, June 04, 2013 02:51:51 AM Richard wrote:
> Sorry - I guess that wasn't too clear. When I configure my radio, I
> "setThisAddress" and pass in a 'sender ID'.
>
> I was wondering if this was transmitted along with the payload, and if so -
> how I could access it?

Its not in the payload, it is in the headers and is handled by the hardware,
and is not accessible by the interface software.

Cheers.

>
> Cheers!
>
> On Tuesday, 4 June 2013 18:39:38 UTC+9, Richard wrote:
> > Hi,
> > I've been reading through the docs, but can't find a way to get to the
> > clientID - it mentions looking in the subclasses, but I don't have any in
> > my distribution. Could anyone point me in the right direction?
> > Cheers,
> > Richard

--
Mike McCauley mi...@airspayce.com
Airspayce Pty Ltd 9 Bulbul Place Currumbin Waters QLD 4223 Australia
http://www.airspayce.com
Phone +61 7 5598-7474 Fax +61 7 5598-7070

[regis.p...@gmail.com]

Hi,

Was wondering if there was a way to know witch adress is sending? If there is 5 senders to the same receiver, did we have a way to know which one is sending or do we have to develop a protocole of our own and decode payload to get identification informations?

Regards,

[Mike McCauley]

Hi,

as far as I understand the operation of the NRF24 chip, there is no register
that tells you the origin address of a received packet.

If I am wrong, then someone pls let me know and I will be happy to add API
support for it.

So, if you need to know the originator, its over to you.

Cheers.

[Colin Cooper]

For the NRF24L01+, isn't this STATUS.RX_P_NO "Data pipe number for the payload available for reading from RX_FIFO..."

From p.76 of the spec: When a valid packet is received (matching address and correct CRC), the payload is stored in the

RX-FIFO, and the RX_DR bit in STATUS register is set high. The IRQ pin is active when RX_DR is

high. RX_P_NO in STATUS register indicates what data pipe the payload has been received in.

[Mike McCauley]

Correct, but pipe number != sender address.

Cheers.

On Monday, September 02, 2013 10:33:24 AM Colin Cooper wrote:
> For the NRF24L01+, isn't this STATUS.RX_P_NO "Data pipe number for the
> payload available for reading from RX_FIFO..."
>

> From p.76 of the spec: *When a valid packet is received (matching address
> and correct CRC), the payload is stored in the*
> *RX-FIFO, and the RX_DR bit in STATUS register is set high. The IRQ pin is
> active when RX_DR is*
> *high. RX_P_NO in STATUS register indicates what data pipe the payload has
> been received in.*

>
> On Thursday, 13 June 2013 22:23:07 UTC+1, mikem wrote:
> > Hi,
> >
> > as far as I understand the operation of the NRF24 chip, there is no
> > register
> > that tells you the origin address of a received packet.
> >
> > If I am wrong, then someone pls let me know and I will be happy to add API
> > support for it.
> >
> > So, if you need to know the originator, its over to you.
> >
> > Cheers.
> >
> > On Thursday, June 13, 2013 04:33:00 AM regis.p...@gmail.com

<javascript:>wrote:

[Colin Cooper]

True, but can't the matching sender address be reconstructed from the RX_ADDR_P* registers?  Or more likely from the values the receiver originally set the pipes to listen on.

(Maybe I'm missing something here)

  Regards,

  Colin

[Mike McCauley]

On Wednesday, September 04, 2013 05:45:29 AM Colin Cooper wrote:
> True, but can't the matching sender address be reconstructed from the
> RX_ADDR_P* registers? Or more likely from the values the receiver
> originally set the pipes to listen on.

Alas, that would be the receiver address, not the sender address.
AFAIK.

Cheers.