Detailed EcuBus-Pro Development Environment Setup Guide
This guide provides detailed instructions for setting up the EcuBus development environment. Before we begin, please prepare the following:
- Node.js - Download the latest version from the official website
- EcuBus source code - Download the latest version from GitHub
With these prerequisites ready, we can proceed with the installation.
Step 1: Install Node.js
Follow these steps to install Node.js:
Click "Next":
Click "Next":
Click "Next":
Click "Next":
Make sure to check the box highlighted in the image above. This will automatically install Python and VS2019 required for Node.js. We recommend checking this box even if you already have these programs installed.
Click "Install":
Installation in progress...
Click "Finish". The following screen will appear; press any key to continue:
Press any key to continue:
The next screen will check if your computer has Python and VS already installed. If not, it will install them. The first-time installation may take some time:
Since my computer already had Python 3.13.3 and VS2019 installed, these were skipped:
Python 3.13.3 and VS2019 development environments are now installed. You can exit this screen.
Step 2: Install NPM Packages
We've completed the Node.js installation. Now let's install the NPM packages.
Navigate to the EcuBus project directory (E:\EcuBus\EcuBus_install\EcuBus-Pro-master in this example):
Run the npm install command:
Step 3: Compile Native Modules
After the installation completes, navigate to the src/main/docan directory:
Run the following command to compile: npx node-gyp rebuild
As shown, there are 104 errors. This problem confused me for a long time. Initially, I thought it was an environment issue, but it was actually due to the encoding format of the .h files.
Opening the toomoss folder with Notepad, we find that offline_type.h is encoded in UTF-8:
Change the format to UTF-8 with BOM and recompile:
Now the errors are reduced to 75, with issues in the tsfn.cxx file:
Change the tsfn.cxx file encoding to BOM format:
After this change, run the compilation command again:
Compilation now succeeds:
Problem solved!
Step 4: Compile the Dolin Module
Next, navigate to the dolin folder and run the compilation command:
We encounter errors again, likely due to file encoding issues:
First, we modify the tsfn.cxx file encoding format:
Compilation still fails with the same errors. To identify which file has format problems, open the project in VS2019 or VS2022:
When compiling in VS2019, we get the following error:
We discover that the usb2lin_ex.h file has encoding issues. After modifying it and recompiling:
Error resolved!
Step 5: Launch the Application
Return to the main directory and run npm run dev:
After a few moments, the EcuBus software interface will appear, indicating that the environment setup is complete.
Summary
File encoding formats significantly impacted the compilation process. This was my first encounter with such an issue, possibly due to cross-platform compilation requirements for specific file encoding formats.
I hope this guide helps if you encounter similar problems. Thank you!