Repository navigation
Confirm how iMotions.xml is imported and which port iMotions listens on #195
Description
Is this task related to a feature or a bug? Please include relevant issue numbers below.
This task follows up on issue #138. The README merged in PR #178 marks both points as needing verification.
Describe the solution you'd like
Two facts documented in the README:
- How the generated
iMotions.xmlis imported into iMotions. - Which port iMotions actually listens on.
Describe alternatives you've considered
Neither is recorded anywhere in this repository. 127.0.0.1:9999 appears only as placeholder text in the relay UI (relay/src/view.rs:14) and inside a validation message. Nothing confirms it is real, and the relay has no default value, so a first-time contributor has nothing to type.
Additional context
Needs access to a licensed iMotions machine.
Activity
jmacd867 commentedon Oct 15, 2026
Context from the client: her lab is currently on Prepar3D and plans to move to X-Plane later, so our pipeline isn't feeding her iMotions machine yet. Also note that no
iMotions.xmlis tracked in the repo, although this issue and the docs refer to it. Find where it lives before the client meeting, where we're asking how her lab imports it and which port iMotions listens on.jmacd867 commentedon Oct 16, 2026
From the client meeting: the port is still unconfirmed. The team sent data to a placeholder port from the code, changed it, and does not know that the new one matches iMotions. The client handles the iMotions machine and said they can test it. The relay's `127.0.0.1:9999` default was discussed and the client thought it probably isn't right.
Also learned:
Still needs: the port, the import steps, and a decision on admin rights. Notes in `docs/client_meeting_notes.md`.
Phlabry commentedon Oct 23, 2026
Half of this is answered. iMotions listens on TCP 5050 on the lab machine, read off
Global Settings>API>Event Receiving, withEnable event receptionandUse TCPboth ticked. The same panel lists our event source asId: PilotDataSync, version 1,Positional Flight Data, matching the generatediMotions.xml. Three other ports on that tab are for iMotions sending data out, not receiving, so they are not ours.It is a setting rather than a product default, so it has to be checked per machine. #248 updates the relay placeholder, the validation message and the README accordingly, and closes #239.
Keeping this open for the other half: how
iMotions.xmlactually gets imported. It was already registered on that machine and nobody on the team performed the import, so the procedure is still undocumented.