MiraBot Multi-Axis Playback Setup Guide for EDI

What this guide covers

This guide focuses on the simplest local playback workflow for using EDI v1.0.1 to connect MiraBot and play basic multi-axis funscripts.

It covers USB connection, basic OSR/TCode configuration, simple Gallery file naming, and playback from the EDI Launcher.

Related resource: For the latest EDI updates and advanced usage, see the original ES forum thread: Easy Device Integration for Games. EDI  

 (EDI作者帖子连接：https://discuss.eroscripts.com/t/easy-device-integration-for-games-edi-game-selection-fix-assets-multi-channel-12-2025/108186)

Before you start

You will need:

• A Windows PC
• A MiraBot device and a USB data cable
• A matching set of multi-axis funscript files

Step 1 — Download EDI and install the required runtimes

Downloads:  EDI  |  .NET 8 Desktop Runtime (x64)  |  ASP.NET Core Runtime 8 (x64)

【EDI】https://mega.nz/folder/3JUh1RBD#5b11fFQCAdNCukbtMs28MQ

【.NET 8 Desktop Runtime (x64)】

https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-8.0.26-windows-x64-installer?cid=getdotnetcore

【ASP.NET Core Runtime 8 (x64)】

https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-8.0.26-windows-x64-installer?cid=getdotnetcore

• Install both required runtimes first if they are not already installed on your PC.
• Then extract EDI to an easy-to-access folder, such as D:\EdiDemo.

Figure 1. Example EDI folder structure.

Step 2 — Connect MiraBot and check the COM port

• Connect MiraBot to your PC using a USB data cable.
• Open Windows Device Manager.
• Expand Ports (COM & LPT), then find the USB serial device and note the COM port number. In the example below, the device is connected to COM3.

Figure 2. Example COM port shown in Windows Device Manager

Step 3 — Prepare the multi-axis funscript files

Create a separate folder for your multi-axis script set inside the EDI `Gallery` directory.

Make sure the main script and its axis files use matching filenames, as shown in the example below.

Figure 3. Example multi-axis funscript files in a dedicated Gallery folder

Step 4 — Remove the sample definitions file for basic automatic detection

If your EDI package includes sample scripts and a sample `definitions.csv` file in the `Gallery` folder, remove the `definitions.csv` file before adding your own basic test scripts.

The file `definitions.csv` is used for custom script definitions. Manually adding your own multi-axis script set to this file can be complicated, and an incorrect definition may cause EDI startup or loading issues.

For this basic guide, we recommend removing `definitions.csv` and letting EDI automatically detect all scripts in the `Gallery` folder at startup, including the included demo scripts and any multi-axis script set you add yourself. This is simpler and more stable for basic playback testing.

Figure 4. Example Gallery folder. For this basic setup, remove or rename the sample definitions.csv file

Step 5 — Configure EDI for MiraBot

EDI uses both the application configuration file and a user-level configuration file. For MiraBot multi-axis playback, make sure the OSR settings are correct in both places.

5.1 Configure EdiConfig.json

• Open  `EdiConfig.json` in the EDI folder with a text editor.
• Find the OSR configuration section. Enter the COM port you found in Device Manager and make sure multi-axis playback is enabled:

“OSR”: {   “COMPort”: “COM3”,   “EnableMultiAxis”: true,   “RangeLimits”: {     …   } }

If your device appears on a different COM port, replace COM3 with the port number shown in Device Manager.

5.2 Configure UserConfig.json

• Open `Edi.exe` and click the user configuration folder button shown below. This opens the folder that contains `UserConfig.json`.

Figure 5. Open the EDI user configuration folder from EDI Launcher

Figure 6. UserConfig.json in the EDI user configuration folder

• Open `UserConfig.json` with a text editor. In the OSR section, confirm the same COM port and make sure multi-axis playback is enabled here as well.

“OSR”: {   “COMPort”: “COM3”,   “UdpAddress”: null,   “EnableMultiAxis”: true,   “UpdateRate”: 200,   “RangeLimits”: {     …   } }

Important: For USB connection, `EdiConfig.json` and `UserConfig.json` should both use the correct COM port and both should have `EnableMultiAxis` set to `true`. If multi-axis is enabled in only one place, EDI may still behave like a single-axis setup.

Step 6 — Play the multi-axis script

Open `Edi.exe` and wait for the device to connect. EDI may need a short moment to initialize the MiraBot device. If the device does not appear, click `Reconnect` and confirm that the COM port in both configuration files is correct.

Figure 7. EDI showing the OSR port and detected MiraBot device

Your script set should appear in the EDI script list. In the example below, the script set is shown as `multi-FunScript`.

Figure 8. Example script set shown in the EDI script list

Select the script set in the playback list. If EDI shows a matching option in the device selection/variant field, select the same script set there as well. Then click the play button to start playback.

During playback, EDI will show the current playback status at the bottom of the window.

Figure 9. Selecting and playing a multi-axis script set from EDI Launcher

Quick checklist

• `EdiConfig.json` uses the correct COM port.
• `UserConfig.json` uses the correct COM port.
• `EnableMultiAxis` is set to `true` in both configuration files.
• The sample `definitions.csv` file has been removed.
• All axis files are in the same dedicated folder under the EDI `Gallery` directory.
• The main script and axis files use the same base filename.
• The script set is selected in the playback list, and the matching option is selected in the device dropdown if shown.
• EDI was restarted after editing configuration files.

Basic troubleshooting

Symptom	What to check
Device not found	Check the USB data cable, confirm the COM port in Windows Device Manager, and make sure both EdiConfig.json and UserConfig.json use the same COM port.
Only the main axis moves	Confirm `EnableMultiAxis` is set to `true` in both `EdiConfig.json` and `UserConfig.json`. Also check that the pitch, roll, and twist files use the same base filename as the main funscript file.
Script set does not appear	Make sure the script files are placed in a dedicated folder under the Gallery directory. Remove the sample `definitions.csv` file, then restart EDI.
Other axes do not move	Use the simple filename pattern first: Name.funscript, Name.pitch.funscript, Name.roll.funscript, and Name.twist.funscript. Avoid extra variant layers until basic playback works.
Playback does not start	Close EDI, check JSON formatting in both configuration files, then start EDI again.

Notes

This article covers the basic local playback workflow only. Advanced EDI features such as script segments, variants, channels, game-specific integration, and custom HTTP event workflows are outside the scope of this guide.

EDI is a third-party community tool. Interface labels and configuration details may change in future versions.

If you are using a different EDI version or a different game integration package, the exact folder structure or configuration file may vary.