[info] rusEfi simulator

[AndreyB]

rusEfi firmware simulator is a way to play with the controller without any hardware! All you need is a Windows computer.

Thank you @rus084 for the screen cast!



http://rusefi.com/wiki/index.php?title=Manual:Software:Simulator

[jfive]

Have you tried the jim stim with one of the units yet?

[AndreyB]

Have you tried the jim stim with one of the units yet?

Nope - I simply do not have one

this topic is about a simulator, not a stimulator. The simulator is a piece of windows software which you use without any hardware whatsoever.

[vincenthw]

hello russian,

i have problem with setting up virtual COM/TCP port. i followed the steps given in your video but LAN status is shown error.

i don't know what i did wrong. can you please check the attached figure and help me out?

thanks and regards,

vincent

[AndreyB]

i have problem with setting up virtual COM/TCP port.

I wonder if the problem is with the TCP port, the process not running or firewall. I've added some troubleshooting hints into the wiki page

[subnet]

hello russian,

i have problem with setting up virtual COM/TCP port. i followed the steps given in your video but LAN status is shown error.

i don't know what i did wrong. can you please check the attached figure and help me out?

thanks and regards,

vincent

when i was trying to get this working i had some problems as well. it also seems that sometimes it just cuts out after doing something (requiring that you go through the process again) even when telnet is responding, and only a reboot seems to get things back to a usable stage.

so as per instructions i do as follows:

reboot computer (if you've already run it before and are getting this error)
start the simulator (note the com port that you're binding to)
create the com in serial port redirector (com port that you selected in simulator, ip address is localhost, port 29002)

[rus084]

how i can compile it for linux?

[AndreyB]

Current makefile uses win32 HAL. You would need to compile it with posix chibios HAL which would require the makefile to detect if you run win32 or Unix

[rus084]

ok , i will try compile for linux (or maybe just use wine?)

[rus084]

demo from Chibios for Posix-GCC is compiling (need to install gcc-multilib library)
why i have this errors?
i cledated "include ${CHIBIOS}/os/hal/platforms/Posix/platform.mk" in makefile , else compiler demand windows.h library (but i dont make for windows because i add this include)

Code: Select all

komp@komp-desktop:/media/komp/ACCA670ACA66CFDE/Users/админ/code/win32_functional
_tests$ make
Compiling chcore.c
In file included from ../firmware/chibios/os/kernel/include/ch.h:113:0,
                 from ../firmware/chibios/os/ports/GCC/SIMIA32/chcore.c:35:
../firmware/chibios/os/ports/GCC/SIMIA32/chcore.h:239:3: error: ‘fastcall’ attribute ignored [-Werror=attributes]
   __attribute__((fastcall)) void port_switch(Thread *ntp, Thread *otp);
   ^
../firmware/chibios/os/ports/GCC/SIMIA32/chcore.h:240:3: error: ‘fastcall’ attribute ignored [-Werror=attributes]
   __attribute__((fastcall)) void port_halt(void);
   ^
../firmware/chibios/os/ports/GCC/SIMIA32/chcore.h:242:60: error: ‘cdecl’ attribute ignored [-Werror=attributes]
                                                            void *p);
                                                            ^
../firmware/chibios/os/ports/GCC/SIMIA32/chcore.c:75:1: error: ‘fastcall’ attribute ignored [-Werror=attributes]
 void port_halt(void) {
 ^
../firmware/chibios/os/ports/GCC/SIMIA32/chcore.c:86:1: error: ‘cdecl’ attribute ignored [-Werror=attributes]
 void _port_thread_start(msg_t (*pf)(void *), void *p) {
 ^
cc1: all warnings being treated as errors
make: *** [build/obj/chcore.o] Ошибка 1

[AndreyB]

Is that a 100% original ChibiOS demo failing for you? this case you have a chance to ask on ChibiOS forum.

You say Posix which sounds unix but folder name is SIMIA32 which sounds windows, unless I am wrong. Is this all right?

As an option try editing some Makefile and say -Wno-error=attributes just to ignore this error

[rus084]

i can compile ChibiOS_2.6.7/demos/Posix-GCC and it works , demo uses SIMIA32 too .

if i use -Wno-error=attributes , attributes errors are fixed , but i get new errors
../firmware/chibios/os/ports/GCC/SIMIA32/chcore.c:48: Error: operand type mismatch for `push'

[AndreyB]

So ChibiOS demo compiles fine but rusEfi simulator does not compile on Unix?

You would need to take the unix demo Makefile and change it to compile rusEfi simulator. Then you would need to apply all the changes one by one until you find which part of the Makefile is not right. I doubt anyone would tell you something more specific than "your Makefile is wrong"

[rus084]

YEAH!!!

Code: Select all

root@dmitriy-Aspire-V5-571G:/rusefi/win32_functional_tests# ./build/rusefi_simulator
ChibiOS/RT simulator (Linux)

Full Duplex Channel SD1 listening on port 29001
Full Duplex Channel SD2 listening on port 29002
Shell service started on SD1, SD2
  - Listening for connections on SD1
  - Listening for connections on SD2
Running version:
TODO
Warning: NaN injection pulse

i use root because i compilling in chroot

what fixed:
my system is 64bit , chibios only for 32bit . need "-m32" option for compiler



why we dont use "make -j5" option when compilling ?
on my laptop its 126% faster .
34s when just "make" and 15s when "make -j5"

[AndreyB]

Thank you @ the same Makefile now works on unix! todo: rename "win32_functional_tests" to "simulator"

[rus084]

i ported rusefi simulator for arm-linux architecture and run it via chroot in android

chibios port is here https://github.com/rus084/chibios-arm-simulator

[AndreyB]

todo: rename "win32_functional_tests" to "simulator"

And this is done now.

[wstefan20]

Probably just me being dumb so apologies in advance. When I download the simulator and launch as in the video I get Not Connected. I have tried the com port emulator, as well as all other recommendations. I even created a custom rule for the ports in windows firewall and even turned off the firewall once to no avail. I can download the Proteus rusefi_bundle and launch the simulator and it shows connected and I can launch everything but there's obviously a firmware mis-match in TunerStudio so it goes offline.

Again, hopefully something easy. Thanks!

[AndreyB]

I remember that my name is Andrey. That's a significant percentage of all things I remember. I do not remember all the details of that video, but 6 years after the video was made I am sure that it's outdated in many MANY ways.

It is my recommendation to purchase a TunerStudio license in order to get TCP/IP connector and avoid virtual serial port. Serial mismatch is NOT supposed to a problem.

At some point virtual serial itself was a problem, there was some drama with package size. It could be that at the moment virtual serial route is broken again if we are again not within the limitations of the known to be problematic at least sometimes virtual serial bridge.

[wstefan20]

I remember that my name is Andrey. That's a significant percentage of all things I remember. I do not remember all the details of that video, but 6 years after the video was made I am sure that it's outdated in many MANY ways.

It is my recommendation to purchase a TunerStudio license in order to get TCP/IP connector and avoid virtual serial port. Serial mismatch is NOT supposed to a problem.

At some point virtual serial itself was a problem, there was some drama with package size. It could be that at the moment virtual serial route is broken again if we are again not within the limitations of the known to be problematic at least sometimes virtual serial bridge.

That's a shame, but I completely understand. Unfortunately I don't really want to spend that kind of cash just to get the simulator working if I don't have to. I don't think it's the serial port issue though because why would the regular console show connected for say Proteus and not for the generic one? It's also showing not connected even before the step to pair tunerstudio as well which makes me think something else might be up, but if you think it's related I'll just leave it alone I guess

[Simon@FutureProof]

I would say at this stage the best way to play with rusefi is to get a discovery board or one of the compatible nucleo boards and load the RE firmware onto that.

Full TS license is more expensive than a board and then disco/nucleo can be used for development annd testing later.