[Rock-dev] using the vicon component

Martin.Azkarate at esa.int Martin.Azkarate at esa.int
Thu Jan 9 10:26:46 CET 2014


That was it! Thanks Javier for the crystal clear instructions!

regards,

Martin Azkarate
ESA - European Space Agency
Spanish Trainee, TEC-MMA - Automation and Robotics Section 
ESTEC - European Space research and TEchnology Centre
Keplerlaan 1, PO Box 299 
NL-2200 AG Noordwijk, The Netherlands 
Martin.Azkarate at esa.int | www.esa.int 
Tel +31 71 565 3480 | Mob +31 650 625 564 



From:   Javier Hidalgo Carrió <javier.hidalgo_carrio at dfki.de>
To:     rock-dev at dfki.de
Date:   08/01/2014 18:54
Subject:        Re: [Rock-dev] using the vicon component
Sent by:        rock-dev-bounces at dfki.de



On 01/08/2014 04:57 PM, Martin.Azkarate at esa.int wrote:
Hi there,

Happy new year to everybody. 


We did some investigation and the error is not in the component not 
finding the subject. The error comes from the fact that the Nexus software 
does not calculate the coordinate system for the subject/segment in Live 
mode. 

If you look at the subject_segment_definition image attached you will see 
there a coordinate system clearly defined for it. We are using a wand with 
5 markers, 3 of them are labeled and used to define the segment coordinate 
system and 2 markers are left unlabelled. 

In the live_stream_data_SDKTest image you will see a snapshot of the Nexus 
software running live (no capture process started) and another window 
showing the output of a console application that is provided as a testing 
program with the Vicon SDK v1.2. Note in this window that the Global 
Translation and the Global Rotation Quaternion vectors for the segment are 
all zero (which is an invalid quaternion value). Basically Nexus does not 
calculate (in live mode) Global values for the segment but just positions 
of markers. See position vectors for (3) labeled and (2) unlabeled markers 
are properly calculated. 

If you look at the output image of the test_vicon ruby scripts (attached 
script with slight modification to include another reader for the 
unlabeled markers port) you will see that it shows NaN for the translation 
values of whole subject rigidbodystate type (wrong quaternion screws the 
transformation matrix values) but it shows the same values we could see in 
the live_stream_data image for the unlabelled Marker #0 (or Maker #1) 
position values. 

So, we've been told by some colleagues at ESTEC that in fact we need to 
use the Vicon Tracker software to have this in live mode (the Nexus is not 
enough), however I believe that when this component was developed in first 
instance it was done using the Vicon Nexus, or that's what I was told. So 
maybe we are missing something or we need to prepare the Nexus software to 
calculate/provide this data in live mode too. Anyone using the Vicon 
component nowadays can tell us how does configure/prepare the Vicon Nexus 
and define the subject/segments? 

Hi Martin,

I remember there is a way in the Nexus software to set the real time 
kinematics calculation. It seems you are missing this step.
I don't know why but I think it is not set up by default. In order to do 
that:

1. Go to the "System" tab inside the "Resources" windows (left part of the 
e.g.: live_stream_data_SDKTest image)
2. Click in the "Local Vicon System [100Hz]"
3. Below in "Properties" sub window, in "Core Processor" field
4. In "Processing level:" set it to "kinematic fit" in the deployed list.

I hope this is the way to set it up. Otherwise, it should be in the Nexus 
documentation. It might change among different Nexus versions.

Javier.

_______________________________________________
Rock-dev mailing list
Rock-dev at dfki.de
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev


This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.dfki.de/pipermail/rock-dev/attachments/20140109/ff51f407/attachment.htm 


More information about the Rock-dev mailing list