Troubleshooting with antilatency tracking system

 

Hi,

I was trying to setup my tracking devices but it seems impossible.

I follow Richard Frantzen tutorials but doesn't have the same result for me.

For example when i try to calibrate tracker in aximmetry, the current position stills the same ever. Doesn't matter if i move the tracker.

But the tracker works. Because i can move my camera. But no my position...

https://drive.google.com/file/d/1WDuN15B0x0KCWlnvQWiY7-qudEoe3kVB/view?usp=sharing


Thanks in advance!

   CYMATIC

 
Profile Image
Aximmetry
  -  
Hi,

In your video I can see that you use the same tracker for the camera tracking and for the billboard tracking.
In this case the billboard will be where the camera is so you will not see it.
If you want to test how to move the billboard with the tracker then you should remove the tracking device from the camera tracking.
(or you should use two different tracking device)

Best Regards

 
Profile Image
Picicsavarkulcs
  -  

Hello!

We had the same issue. Here is the solution.

You have to check if the antilatency hw and sw properly calibrated. 

1. Install the antilatency service the 2.1.0 works well with aximmetry. Maybe the newer version is good for 3.0 but, I use the 2021.2.1.

2. Connect your hw

3. If the service software see all the things, you’ve connected, choose the floor plan.

4. Install the sdk. 

5. Test the antilatency system with the Antilatency demo app. If you placed the floor or the ceiling precisely, there should be fine everything. If the tracker doesn’t move only the giro works, you have to change the floor plan in the service software, or move the floor or ceiling infra transmitters more precisely to the correct place.

6. Test again if you had to correct something.

7. If it’s fine than launch aximmetry, and everything should be work well. If you launch axi, on the manage devices tab if you move the tracker, you should see the 3 axis coordinates changing. 


That’s all. 

 
Profile Image
PromiseoVideoTeam
  -  

Going back to antilatency service the 2.1.0 helped me to solved this too :)

;