XBee Pro Digimesh 2.4: response time to RSSI and possibilty of mesh network while all clients within reach

I’m thinking of using the XBee Pro Digimesh 2.4 chipsets in a project.
However, the sensors I am deploying may move relatively fast in and out of the reach of other sensors. It’s important for me to have the ability to build a mesh as well as read RSSI values.

For a proof of concept, I am planning to trilaterate the position using 3 other chipsets (resembling antennas). First in a static scenario, then heading over to a dynamic scenario with moving sensors.
Connecting to the client and sending a small data packet should succeed, then reading the RSSI of this last packet from the antennas’ chipsets.
I have some experince in bluetooth hardware, and it takes quite sometime to build a connection using BT…
So as the sensors can & will move relatively quickly:
How fast can I connect to a client using your chipsets?

My second question: Is there a possibility to force a mesh network for testing purposes while all clients are within reach? Is there a way to specify a route?

They are a peer to peer product by nature. So as long as you are not sleeping, they only need to be in range for communications to be possible.

Thank you for your input. I presume you mean that if a chipset is in range a p2p-connection is used, so a mesh network becomes obsolete. I do know that, but I was hoping that I could build up a mesh nevertheless by specifying a route by hand, just to test the connectivity.

Also, my first question remains:
How long does it take to establish a p2p-connection to a chipset in order to get a quick RSSI?

No, regardless if you are doing a Mesh network or a peer peer, or point to point, it is the same. You only need to be in range in order to send data.

The same answer apples.

Let me answer it this way, if the 64 bit address of who you want to send the data to is within the network and your Roaming nodes are within range of any other node within the network, I can send the data. No association required. It just simply needs to be in range of a node within the network.