Data streaming between SimpleClient and Arena

[Plume]

Hello,

I have a problem when trying to stream data from Arena.
I followed Natnet SDK user guide instructions and I can't get the streaming working.

Indeed, I launch Arena (with a rigid body loaded) and then go to the stream pad, then I write my IP address (both client and server are running on the same computer).
Right Hand Coord, 3D marker Positions and Rigid Body Data are checked.

Then I launch SimpleClient from Natnet Samples.
This is what I get :
Connecting to server at LocalMachine
Connecting from LocalMachine...
NatNet Sample Client (NatNet ver. 2.2.0.0)

[Client] Initializing using ethernet address: 192.168.21.92

[Client] Initializing command listener.

[Client] Initializing data listener.

[Client] Received command from 192.168.21.92: Command=1, nDataBytes=264

[Client] Connected. (HostApp:Arena HostVer: 1.8.1.0 HostIP: 192.168.21.92 ()
[SampleClient] Server application info:
Application: Arena (ver. 1.8.1.0)
NatNet Version: 2.3.0.0
Client IP:192.168.21.92
Server IP:192.168.21.92
Server Name:Yeosu.ipb.fr

Client initialized and ready.
[SampleClient] Sending Test Request

[Client] Requesting: TestRequest

[Client] Received command from 192.168.21.92: Command=100, nDataBytes=264

[Client] Server returned NAT_UNRECOGNIZED_REQUEST.


[SampleClient] Requesting Data Descriptions...
[Client] Received command from 192.168.21.92: Command=5, nDataBytes=107
[SampleClient] Received 2 Data Descriptions:
Data Description # 0 (type=0)
MarkerSet Name : All
Rigid_Body:root1
Rigid_Body:root2
Rigid_Body:root3
Data Description # 1 (type=1)
RigidBody Name : Rigid Body_root
RigidBody ID : 65537
RigidBody Parent ID : 0
Parent Offset : 0.00,0.00,0.00

Client is connected to server and listening for data...


So the client is able to connect to Arena, bet when I start streaming data (by clicking the button in Arena), I keep getting this :

[Client] Received command from 192.168.21.92: Command=7, nDataBytes=120
And finally, all I get in the output file, is the rigid body description.

So what am I doing wrong?

Thank you for your responses.

[morgan]

The most common reason for commands to operate but not data over multicast is a firewall.

So first I would try disabling your windows firewall

If it still does not work, try putting a breakpoint in the datahandler callback and see if frameofmocap data packets are being received. If they are not, then you might try changing from multicast to unicast (on both server and client) to isolate out the chance that multicast packets are somehow getting filtered or the multicast group ip no longer matches.

hope this helps,

Morgan

[Plume]

Thank you for your quick response.

Thanks to what you said, I managed to get it working :
In fact I was multicasting on the loopback address (127.0.0.1), I put the same multicasting address SimpleServer is using and now the datas are streaming.

So problem solved !

[fhuelsma]

Hi,

I have a similar problem using Arena 1.7.3 and the sample client from NatNet 2.2:
The connection is established, I receive the RigidBody data description, but no further data is received.

Both, arena and the client are running on the same machine.
In the Arena Software, I entered my local IP address, but I also tried using 127.0.0.1.

The same problem appears when using a self compiled version of the sample code using unicast.

Any help would be greatly appreciated.

[morgan]

Here is our most common troubleshooting steps:

If streaming locally:
- Run with the *default* settings in Motive/Arena/TrackingTools and Winforms sample, with both client and server IP addresses set to local loopback (127.0.0.1) on the client, and 127.0.0.1 set in Motive.
- Disable Windows firewall

If streaming remotely
- Disable Windows firewall on client and server
- Check server and client ip settings.
- If either machine has mulitple network cards/interfaces, make sure you are connecting to a network card that can talk to the other network card.
- Remove network switches/hubs between client and server
- Switch to Unicast (on both client and server) to isolate whether multicast filtering is in effect on your network.

Let us know if this helps,

Morgan