Connectivity overview & build-in commands

[E4ODnut]

Good. Glad to be of assistance. I see your additions so I'll play around with them.

I've also written up a bit of a ".hex file loading cheat sheet" for my own use, but maybe it could be incorporated into some more comprehensive instructions.

How to get and load the latest rusEFI .hex file:

1: - Go to the rusEFI.com web site

2: - Click the “Manual-Software” button. This brings up a software manual page. In the line of text “once you get the brain board you will need to program it with the rusEFI firmware binary file. More about that here”.

3: - Click “here” link. This brings you to the thread “Setting up the board with pre-compiled binaries” This thread has instructions on how to download and use the STM32 ST-Link Utility with which to load the .hex file into Discovery.

4: - In the first line in the first post of the thread, click the “build-server” link. This brings up a link to the rusEFI consol.jar and rusEFI firmware.zip.

rusEFI consol is a utility that you can use to communicate with Discovery. It can live at whatever location you download it to. A shortcut on your desktop will allow you to run it from your desktop.

rusEFI firmware.zip contains the latest firmware .hex file and configuration settings for Tuner Studio. Create a folder for rusEFI stuff and unzip it here.

5: - To load the file into Discovery connect both the power and communication USB cables to your computer. Open the STM32 ST-Link Utility. Go to “File” . “Open” and select the .hex file in your rusEFI folder. Click the “Program and Verify” button. The process takes several seconds and if successful will report so on the screen.

That’s it.

[AndreyB]

The Manual:Software link is probably gone now, but it is replaces by a better 'wiki - Soft U Manual' link in the left navigation pane of www.rusefi.com

miniUSB is both power and programming. micorUSB is only dev console communication, without the power.

[kb1gtt]

Looks like we broke his instructions. Hopefully this helps.

Load firmware is now assimilated http://rusefi.com/wiki/index.php?title=Manual:Software:User/en#Load_firmware
Dev Console is now assimilated http://rusefi.com/wiki/index.php?title=Manual:Software:User/en#Dev_Console

[AndreyB]

tss renamed to tsinfo
new command - lcdinfo

[AndreyB]

analoginfo
Brief analog inputs report. This command reports voltage taking current divider settings into account.

[AndreyB]

It is now possible to control which protocol would be activated on microUSB, and which one would be activated on the UART:
reset while not holding the blue button - dev console would be using USB and TunerStudio would be using UART
hold the blue button while resetting - TunerStudio would be activated on the USB and dev console on the UART

[acab]

By default we use USART3. TX is pin PC10 & RX is PC11

you sure?

Code: Select all

firmware / config / boards / arro_board.h

#define EFI_CONSOLE_UART_DEVICE (&SD3)
#define EFI_CONSOLE_TX_PORT GPIOC
#define EFI_CONSOLE_TX_PIN 10
#define EFI_CONSOLE_RX_PORT GPIOC
#define EFI_CONSOLE_RX_PIN 11
#define EFI_CONSOLE_AF 7 

#define TS_SERIAL_TX_PORT GPIOC
#define TS_SERIAL_TX_PIN 10
#define TS_SERIAL_RX_PORT GPIOC
#define TS_SERIAL_RX_PIN 11
#define TS_SERIAL_AF 7 

[AndreyB]

you sure?

Am I sure about what exactly? I am pretty sure - and you are quoting the right source code file, so yes. Please note that RX/TX naming is one way on discovery end and the opposite way on the USB/TTL device, because TX&RX depends on where you look from - from stm side or from usb/ttl side. It's a bit confusing.

[AndreyB]

new commands:

fuelinfo shows injection pulse width for current rpm and engine load

fuelinfo2 RPM ENGINE_LOAD (for example fuelinfo2 2000 2) shows injection pulse width for current rpm and engine load

[Tambralinga]

Good. Glad to be of assistance. I see your additions so I'll play around with them.

I've also written up a bit of a ".hex file loading cheat sheet" for my own use, but maybe it could be incorporated into some more comprehensive instructions.

How to get and load the latest rusEFI .hex file:

1: - Go to the rusEFI.com web site

2: - Click the “Manual-Software” button. This brings up a software manual page. In the line of text “once you get the brain board you will need to program it with the rusEFI firmware binary file. More about that here”.

3: - Click “here” link. This brings you to the thread “Setting up the board with pre-compiled binaries” This thread has instructions on how to download and use the STM32 ST-Link Utility with which to load the .hex file into Discovery.

4: - In the first line in the first post of the thread, click the “build-server” link. This brings up a link to the rusEFI consol.jar and rusEFI firmware.zip.

rusEFI consol is a utility that you can use to communicate with Discovery. It can live at whatever location you download it to. A shortcut on your desktop will allow you to run it from your desktop.

rusEFI firmware.zip contains the latest firmware .hex file and configuration settings for Tuner Studio. Create a folder for rusEFI stuff and unzip it here.

5: - To load the file into Discovery connect both the power and communication USB cables to your computer. Open the STM32 ST-Link Utility. Go to “File” . “Open” and select the .hex file in your rusEFI folder. Click the “Program and Verify” button. The process takes several seconds and if successful will report so on the screen.

That’s it.

Hey man,
I'm newbies for the rusEFI and I follow 5: step via Discovery board.
Connect to that new serial port @ 115200 with 8/N/1 no flow control.
I got the results form microUSB. but I cannot got the result from directly from PC10,PC11.
And same problem, cannot connect to Tuning Studio. It return message connection fail!!
What am I doing wrong?

PS. rusefi.ini followed link...
http://sourceforge.net/p/rusefi/code/HEAD/tree/firmware_archive/rusefi.20140702_3817.hex

Thanks.

[AndreyB]

Connect to that new serial port @ 115200 with 8/N/1 no flow control.
I got the results form microUSB. but I cannot got the result from directly from PC10,PC11.

It's my fault - it is currently set to 38400. I guess I should get it back to 115200 one day soon, but for now it's going to be 38400.

I've created http://rusefi.com/wiki/index.php?title=Manual:Software:TunerStudio_connectivity with a summary so that you do not have to look around on the forum.

PS. rusefi.ini followed link...
http://sourceforge.net/p/rusefi/code/HEAD/tree/firmware_archive/rusefi.20140702_3817.hex

The current files are always in http://rusefi.com/build_server/rusefi_firmware.zip

[AndreyB]

http://rusefi.com/wiki/index.php?title=Development:Software:connectivity would host the general connectivity Q&A.

[AndreyB]

While using the simulator you have some special commands to control virtual sensor voltage - that's the fake voltage with the logic would decode according to the settings.

set_mock_iat_voltage X
set_mock_maf_voltage X
set_mock_afr_voltage X
set_mock_tps_voltage X
set_mock_map_voltage X

where X is a value between 0.0 and 5.0

There is also a way to apply the values using the dev console UI - double-click on a gauge and you will get a spinner which allows changing the values.

[AndreyB]

egtinfo

set_egt_spi X

for example
set_egt_spi 3 would set EGT to SPI3

set_egt_cs_pin X Y
for example
set_egt_cs_pin 0 PD10
would set EGT channel #8 chip select line to pin PD10

[AndreyB]

get_float OFFSET
get_int OFFSET
set_float OFFSET VALUE

this commands allow you to access any given part of the configuration if you know the offset, which you can probably find inside rusefi.ini

for example
get_float 524
get_int 4
set_float 524 10000

[puff]

wow! this adds flexibility!
what about set_int offset value? %-)
are these new values applied immediately? is write_config needed to save the changes?
some explanation on finding offset from the rusefi.ini would also be nice…

[AndreyB]

some explanation on finding offset from the rusefi.ini would also be nice…

It is obvious that you have not yet opened rusefi.ini in notepad