This guide enables support to validate a customer's hardware configuration by cross-referencing the systemInfo.json log with recommended bandwidth standards.
Critical Operational Notes
- Log Refresh:
- Hardware inventory is polled exclusively at application startup. To ensure the systemInfo.json reflects the current hardware state or any recent cabling changes, TrackMan Performance Studio (TPS) must be restarted before retrieving the log.
- Hardware Support:
- Currently, this reporting and validation method only supports USB Cameras (E-Con). Additional cameras such as IDS or Iphone is currently not supported.
1. Recommended Configurations
- 1 Camera per Host Controller — ✅ SUPPORTED
- The gold standard for reliability. Ensures dedicated bandwidth.
- 2 Cameras per Host Controller — ⚠️ NOT RECOMMENDED
- Can lead to bandwidth sharing, jitter, and instability.
- 3+ Cameras per Host Controller — ❌ NOT SUPPORTED
- Insufficient bandwidth. Causes system crashes and data loss.
2. Data Analysis (systemInfo.json)
Log Path: C:\ProgramData\TrackMan\TrackMan Performance Studio\Logs
Identify Available Controllers
Scroll to the "USB" section. Each unique entry represents a physical path for data.
"USB":[
{ "Name": "Renesas USB 3.0...", "DeviceId": "PCI\\VEN_1912&DEV_0015..." },
{ "Name": "Intel(R) USB 3.20...", "DeviceId": "PCI\\VEN_8086&DEV_7A60..." }
]Verify Camera Mapping
Match the "UsbControllerId" of each camera to the controllers identified above.
3. Practical Examples
EXAMPLE 1 — Overloaded Controller (Critical)
In this log, all three cameras are sharing a single Intel controller (Device 7A60).
"Cameras":[
{ "Name": "See3CAM", "UsbControllerId": "...DEV_7A60..." },
{ "Name": "See3CAM", "UsbControllerId": "...DEV_7A60..." },
{ "Name": "See3CAM", "UsbControllerId": "...DEV_7A60..." }
] EXAMPLE 2 — Distributed Load (Optimized)
Cameras are balanced across three separate controllers (Renesas and Intel).
"Cameras":[
{ "Name": "See3CAM", "UsbControllerId": "...6&2D8216F1..." },
{ "Name": "See3CAM", "UsbControllerId": "...DEV_7A60..." },
{ "Name": "See3CAM", "UsbControllerId": "...6&113DDA51..." }
]4. Troubleshooting Symptoms
- Camera Disconnections: System "drops" the camera during a session.
- Low FPS: Bandwidth throttling ruins AIMA/3DMA accuracy.
- Missing Videos: Software fails to save high-speed recordings.
- Visual Artifacts: Green lines or "ghosting" in the video feed.
5. Recommended Steps
- Physical Re-plugging: Move USB cables between front and back ports to trigger a different controller path.
- Hardware Upgrade: Install a dedicated PCIe USB expansion card if your motherboard support additional controllers.