Flypt Mover
Last updated
Last updated
Start by downloading and installing the latest version of Flypt Mover from . Launch the software to begin setup.
Source Module: Select the appropriate source for your game or application, such as Assetto Corsa or iRacing, to capture motion data.
Pose Module: Configure this to process and filter the data, ensuring smooth motion output for your platform. Check the Github for example Poses files
Rig Module: Set up based on your motion platform's specifications, like the number of axes (e.g., 6DOF for a full motion rig). NOTE: Select Rig output to 24 bits for Axis
Add a new output module and choose "Serial" as the type.
Set the serial port to the correct COM port connected to your motion4sim controller.
Configure the serial settings: baud rate to 250,000, 8 data bits, no parity, and 1 stop bit.
Define the output string to match the motion4sim controller's format, typically starting with two 255 bytes, followed by axis values as 24-bit integers, and ending with 10 and 13 (LF and CR). For example, for 6DOF: <255><255><Axis1a><Axis2a><Axis3a><Axis4a><Axis5a><Axis6a>000000<10><13>
The motion4sim controller supports Direct Mode () for immediate movement commands or Position Mode () for position setpoints. Choose based on your rig's configuration and needs, with Direct Mode often used for simpler setups.
Ensure modules are connected so data flows from source to pose, rig, and finally to the output module.
Test the setup by starting the simulation and verifying the motion platform moves as expected. Adjust the output string or settings if necessary.
Note that motion4sim also supports UDP, and Flypt Mover can output over UDP using the same output strings as serial, providing an alternative if serial communication is unreliable.
This comprehensive guide outlines the process of setting up Flypt Mover for serial data output, specifically tailored for use with a motion4sim controller, such as the AASD15A-Servo-Controller. The guide is informed by official documentation, community resources, and example configurations, ensuring a thorough understanding for users setting up motion simulation rigs.
Background and Context
Flypt Mover is a motion control software commonly used in simulation environments like racing or flight simulators. It captures data from games or applications and translates it into movements for a motion platform, often via serial or UDP communication. The motion4sim controller, particularly the AASD15A model, is designed for such setups, supporting both direct and position motion modes. The serial output setup is critical for ensuring accurate and safe motion, with specific settings like a 250,000 baud rate and 8n1 configuration mandated by the user.
Installation and Launch
Modular Configuration
Flypt Mover operates through a series of interconnected modules, each serving a specific function:
Pose Module: This processes and filters the data to generate smooth motion outputs. It may include low-pass or high-pass filters to enhance motion quality, depending on the rig's requirements.
Rig Module: Defines the motion platform's characteristics, such as the number of degrees of freedom (e.g., 6DOF for a full motion rig) and specific parameters like actuator limits. This must align with the motion4sim controller's capabilities.
Output Module: Configures the communication method, in this case, serial output to the motion4sim controller. This is where the serial settings and output string are defined.
Serial Output Configuration for motion4sim
To set up serial output, follow these steps:
Add Output Module: In Flypt Mover, add a new output module and select "Serial" as the type.
Serial Port Settings:
Select the correct COM port corresponding to the motion4sim controller, identifiable in the Windows Device Manager.
Set the baud rate to 250,000, as specified by the user, with 8 data bits, no parity, and 1 stop bit (8n1).
Define Output String: The output string must match the motion4sim controller's expected format. Based on community examples and typical motion controller protocols, it generally includes:
Two header bytes, each 255 (0xFF), to signal the start of a command.
Axis values for each degree of freedom, typically as 24-bit signed integers in little-endian format.
End-of-message delimiters, often 10 (LF) and 13 (CR).
For a 6DOF rig, an example output string might be: 255,255,<Axis1a>,<Axis2a>,<Axis3a>,<Axis4a>,<Axis5a>,<Axis6a>,10,13. Each <AxisNa> placeholder should be replaced by the axis value as a two-byte integer, ensuring the byte order matches the controller's expectations (likely little-endian).
Data Type and Format: Ensure the axis values are sent as 16-bit signed integers, as community reports suggest this is necessary for compatibility with controllers like the AASD15A. Adjust the placeholder format in Flypt Mover if needed to output binary data correctly.
Choosing Direct or Position Mode
The motion4sim controller supports two primary modes, each with different implications for Flypt Mover's output:
Users should choose the mode based on their rig's setup and the motion4sim documentation, with Direct Mode often preferred for simpler, real-time control.
Connecting Modules and Testing
After configuration, connect the modules in Flypt Mover to ensure data flows from the source module through the pose and rig modules to the output module. Start the simulation to test the setup, monitoring the motion platform's response. Adjust the output string or module settings if the platform does not move as expected, ensuring safety by keeping the area clear during testing.
Additional Flexibility: UDP Output
An unexpected detail is that motion4sim also supports UDP communication, and Flypt Mover can output over UDP using the same output strings as for serial. This provides flexibility if serial communication is unreliable or if network-based setups are preferred. To use UDP, configure the output module accordingly, maintaining the same string format for consistency.
Troubleshooting and Support
The analysis draws from the official Flypt Mover website , community discussions on , and example configurations from the GitHub repository . Given the "Work in Progress" status of some documentation, community insights were crucial for filling gaps.
Begin by downloading and installing the latest version of Flypt Mover from . Launch the software to access its modular interface, which is essential for configuring the motion output.
Source Module: This module captures motion data from the game or application. Users must select the appropriate source, such as Assetto Corsa, iRacing, or other supported titles, as listed in community FAQs .
Direct Mode: Refer to for details. This mode sends immediate movement commands, suitable for setups where the controller directly interprets velocity or position changes. The output string should reflect raw movement data without additional processing.
Position Mode: Detailed in , this mode involves sending position setpoints, which the controller then uses to calculate movements. The output string should include position values for each axis, ensuring alignment with the rig's configuration.
If issues arise, verify the COM port selection, baud rate, and output string format. Consult the motion4sim documentation or reach out to the community on for assistance.