rusEFI Virtual simulator
You'll be able to test out the rusEFI controller on your computer
rusEFI virtual firmware simulator is a way to play with the rusEFI without any hardware! This simulator allows you to see how the firmware reacts to different commands and configuration adjustments via Tuner Studio. The main thing one would be looking at would be the 'Engine Sniffer'.
All you need is a Windows computer. This virtual simulator is built from the same source code as rusEFI controllers firmware.
The rusEFI console runs on Java, so if you don't have that installed on your PC you'll need to download it.
If you don't have the rusEFI console you can download it here.
You'll have to unzip the file and go into the console folder.
And then open the rusefi_console.jar file.
After this, you'll start the virtual simulator.
Connecting the simulator to Tunerstudio
There are two ways to connect rusEFI virtual simulator to Tunerstudio, it all depends on whether you have the lite or commercial version.
To start off you'll need to open one of your existing projects or just create a new one.
If you don't know how to create a Tunerstudio project go here
With the paid version all you need to do is to go into the communication settings inside a created project
choose the USB and wireless driver and the WiFi driver connection type, write the Port as 29002 and the IP address as 127.0.0.1
However, if you only have the lite version of Tunerstudio the process will be different.
Emulating a serial port to connect to Tunerstudio lite
If you prefer using the free version of Tunerstudio - Tunerstudio lite - you'll need to install a serial port emulator from here. You'll need to emulate a port on your PC. The only thing that you'll need to do is to choose a port name, COM100 for example, and to change the port address to 29002.
Now you can create your virtual port.
So now if you open the communication settings in Tunerstudio,
you'll be able to connect to your emulator.
Now if your virtual simulator is connected to Tunerstudio you'll see a green zero in your rusEFI virtual simulator.
In case something does not work with the TCP<>Serial driver, first thing is to make sure that rusefi_simulator.exe is in the list of Processes in Task Manager
Next step is executing
telnet localhost 29001
to make sure that dev console protocol is alive
telnet localhost 29002
to make sure that TS protocol is alive.
Expected behavior is that connection would be established. If it does not, you might need to look in firewall settings.