Hi,

You could use the TrackMen option in the Manage Devices under Camera Tracking:

You should check if the Camera Tracking module in Aximmetry is receiving any tracking data. There is a page with instructions on how to do this here: https://aximmetry.com/learn/virtual-production-workflow/tracking/how-to-set-up-tracking-systems-in-aximmetry/

If the Camera Tracking module is receiving data then the Basic Calibrator should also work. If it isn't so, which data does the Camera Tracking module receive and on which pins?

If the Camera Tracking module is not receiving data, ensure that no firewall settings are blocking the data. Additionally, are you using the UDP test tool to forward the tracking data? If you are, try connecting the Aximmetry PC directly to the tracking system or to its router instead.

Warmest regards,

Thanks, I'm just using sockettool to check the data from the port, after that, i closed the sockettool and open aximmetry.

Yes, i' m using the trackmen protocol in aximmetry camera tracking device,  as to the settings, i tried localhost,or the ip 10.129.173.80, all failed.  I will try this tomorrow.  https://aximmetry.com/learn/virtual-production-workflow/tracking/how-to-set-up-tracking-systems-in-aximmetry/    but i think it's just a good way to check the data, does not change any tracking setup.

Hi,

Have you been able to find a solution to the issue? If you require further assistance, please feel free to reach out.

Warmest regards,

Hello,Eifert

Thank you for your concern, and I apologize for the delayed response. Recently, our equipment's jib arm has been out of service, so I've been testing with another tracking gimbal, such as the Gension robot, which uses the FreeD protocol and works without issues. However, I noticed that occasionally the tracking data disconnects and, upon recovery, I need to stop and restart the project in Aximmetry to retrieve the data again. Unlike Viz, it doesn't have seamless handshake communication.

Additionally, I should be able to test the Egripment next week, and I will update you on the progress at that time.

Hi,

If there's a disconnect in your tracking data, it usually indicates an issue with your network or tracking system. This type of problem should not require a fix within Aximmetry, even though other software might obscure such issues.

We strongly recommend using a dedicated network for your tracking system. Ensure that no other devices are connected to the router aside from your tracking system and computer. Additionally, we advise against using a wireless connection. However, if you do have a strong wireless connection, it shouldn't cause disconnects.

If you continue to experience disconnects, you can check the Aximmetry logs for any error messages or warnings related to the issue. Aximmetry's log panel typically provide information that can help diagnose the problem.

You don't necessarily have to restart the entire project to reconnect either. Simply turning the INPUT off and back on should suffice:

Warmest regards,

I attempted once again to connect Egripment's tracking data to Aximmetry but was unsuccessful. I directly connected the two using an Ethernet cable, and while the UDP tool detected incoming data, Aximmetry did not recognize it. I then tried using Viz’s virtual debugging software to receive data from the same port, selecting the Trackmen protocol, and it showed that the data was connected. I suspect that the output data format may not meet Aximmetry’s requirements, but there is no indication of a format error either.

Hi,

When running Aximmetry, ensure no other programs like Viz or the UDP tool are active, as they might occupy Trackman's UDP port. Additionally, verify that the Windows firewall is not blocking Aximmetry's access to Trackman's UDP connection.

Check if Aximmetry Composer's Camera Tracking module is receiving any data, rather than the Basic Calibrator. Instructions for this process can be found here: https://aximmetry.com/learn/virtual-production-workflow/tracking/how-to-set-up-tracking-systems-in-aximmetry/
Although not yet documented on that page, it can show received raw packets (since Aximmetry version 2025.1.0):

If you suspect an issue with the data format, the Raw Packet pin should still display data, meanwhile, the Cam Transform pin should only show the zero transformation with no changes.

Warmest regards,

That would be usefull for me to check the raw packet.  i tried the camera tracking module which the cam transform is zero，but the test was running in aximmetry 2024.3.0 on my laptop.

I'm sure the Viz or the UDP tool are not active,and firewall is off also. I will try to check the data in 2025. 
Warmest regards,

Hi,Eifert

I am very pleased to tell you that the issue has been resolved. The problem was that the tracking box was previously set to store and output data in Euler format. After switching to Matrix format, Aximmetry was able to recognize it correctly.

From this, I also realized that Aximmetry represents the camera pose using a Matrix. By the way, if the data storage format is fixed as a Matrix, is there a way to convert it to Euler through a node for easier use in future applications?

Once again, I sincerely appreciate your continuous follow-up and patient explanations.

Hi,

Yes, you can easily obtain the Euler rotation from a transformation using the Transformation Decompose module in Aximmetry. Some modules work specifically with Euler rotations or perform calculations using them.
Here are some examples:

Additionally, when you peek at a transformation, both the matrix and its corresponding Euler Rotation are displayed:

Warmest regards,

Hi,

ok, got it, thanks for your knowledge, Transformation Decompose,  I'll tried this module,for the next project when dealling with eulur data

Thank you

Warmest regards!