rusEFI as ignition control unit for soviet boxer

Your chance to introduce yourself and your vehicle
Post Reply
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

Hi all.
Decided to use rusEFI as ignition ECU on soviet boxer motorcycle (currently for Dniepr MT, but will also fit Ural, K750, M72 and old BMW boxers).
Implementing two spark plugs per cylinder. Already installed ATV CV carbs, single disc clutch, hydraulic disk brake, rebuilt engine and fixed some factory problems with oil system (addded oil filter, sealed crankshaft bed), custom frame, fork, shock absorbers.

Sensors set: manifold air pressure, intake air temp sensor, engine temp sensor, cam position sensor, crank position sensor.
Two wasted-spark coils.

Now I have a question. As engine has two separate intakes, which of them should I use for IAT and MAP? When ECU takes measurements?

Pic of my dinosaur:
photo_2024-01-04_01-51-43.jpg
photo_2024-01-04_01-51-43.jpg (264.73 KiB) Viewed 63236 times
User avatar
AndreyB
Site Admin
Posts: 14334
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: rusEFI as ignition control unit for soviet boxer

Post by AndreyB »

I would not worry about IAT that probably goes to the bottom of the priority list?

Hopefully you already plan to have two widebands?

You would have to adjust MAP averaging window to get MAP to jump less. Then you use existing trim functionality to get AFR to match, and an IR thermometer to confirm matching exhaust temperature?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

Not quite shure why I need wbo? Carbs are already adjusted and synchronised with pressure gauges.
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

New trouble.
Using .bin & .ini from latest mre f4 bundle. Board is from my other old rusEFI project (32F407VGT6 verified working 3 years ago).
First got this issue while trying to disable SPI interfaces. Also cannot flash any other pin to vBAT with same error. Most of other settings are applied correctly.
What I am doing wrong?
Where should I look for logs?
Attachments
изображение.png
изображение.png (100.66 KiB) Viewed 63002 times
User avatar
AndreyB
Site Admin
Posts: 14334
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: rusEFI as ignition control unit for soviet boxer

Post by AndreyB »

Fantomiaso wrote:
Sat Jan 06, 2024 11:10 pm
Using .bin & .ini from latest mre f4 bundle. Board is from my other old rusEFI project (32F407VGT6 verified working 3 years ago).
mre f4 bundle is for mre f4 boards right?
please use mre f4 board if you want an mre f4 bundle
please use not mre f4 bundle if you have not mre f4 board?

See also https://github.com/rusefi/rusefi/wiki/Custom-Firmware
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

Just to understand logic under this. Lets take abstract 32f407 with no any peripherals. Using .bin and .ini from different board projects will give different settings availble? So, they are board dependant? Im I right? As I remember from old projects, all that affected was default pinout loaded on board first start.
User avatar
AndreyB
Site Admin
Posts: 14334
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: rusEFI as ignition control unit for soviet boxer

Post by AndreyB »

Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

To be honest. As I'm not software developer, it is rather hard to understand what, where and why I shall look for, modify and setup(
User avatar
AndreyB
Site Admin
Posts: 14334
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: rusEFI as ignition control unit for soviet boxer

Post by AndreyB »

Fantomiaso wrote:
Sun Jan 07, 2024 12:25 am
To be honest. As I'm not software developer, it is rather hard to understand what, where and why I shall look for, modify and setup(
please use f407-discovery community bundle.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

New stupid questions section.
Cannot achieve ign pulse on output pin both with ECU stimulator and bench test. Testing on stm32f4 discovery with appropriate firmware.
Log from console (bench test spark after reboot):

Code: Select all

2024-01-07_23_31_07_259: EngineState: Rebooting in 3 seconds...
2024-01-07_23_31_07_260: EngineState: confirmation_reboot:6
2024-01-07_23_31_11_090: EngineState: Power cycle count: 8
2024-01-07_23_31_11_090: EngineState: initHardware()
2024-01-07_23_31_11_091: EngineState: pin_markUsed: led: CRITICAL status on PD14
2024-01-07_23_31_11_091: EngineState: initRtc()
2024-01-07_23_31_11_093: EngineState: Current RTC time: 01 Jan 1980 00:00:00
2024-01-07_23_31_11_093: EngineState: pin_markUsed: USB DM on PA11
2024-01-07_23_31_11_094: EngineState: pin_markUsed: USB DP on PA12
2024-01-07_23_31_11_095: EngineState: *** rusEFI LLC (c) 2012-2023. All rights reserved.
2024-01-07_23_31_11_096: EngineState: *** rusEFI v20231005@65034
2024-01-07_23_31_11_097: EngineState: *** Chibios Kernel:       6.1.4
2024-01-07_23_31_11_098: EngineState: *** Compiled:     Oct  7 2023 - 18:29:28
2024-01-07_23_31_11_099: EngineState: *** COMPILER=12.2.1 20221205
2024-01-07_23_31_11_100: EngineState: *** detected HSE clock 0.00 MHz PLLM = 8
2024-01-07_23_31_11_100: EngineState: hellenBoardId=0
2024-01-07_23_31_11_102: EngineState: UID=360030 30365118 32323734
2024-01-07_23_31_11_103: EngineState: can read 0x20000010 1
2024-01-07_23_31_11_104: EngineState: can read 0x20020010 0
2024-01-07_23_31_11_105: EngineState: can read 0x20070010 0
2024-01-07_23_31_11_106: EngineState: isStm32F42x No
2024-01-07_23_31_11_106: EngineState: MCU rev=413 flashSize=1024
2024-01-07_23_31_11_107: EngineState: CORTEX_MAX_KERNEL_PRIORITY=2
2024-01-07_23_31_11_107: EngineState: STM32_ADCCLK=21000000
2024-01-07_23_31_11_108: EngineState: STM32_TIMCLK1=84000000
2024-01-07_23_31_11_110: EngineState: STM32_TIMCLK2=168000000
2024-01-07_23_31_11_110: EngineState: STM32_PCLK1=42000000
2024-01-07_23_31_11_111: EngineState: STM32_PCLK2=84000000
2024-01-07_23_31_11_112: EngineState: PORT_IDLE_THREAD_STACK_SIZE=32
2024-01-07_23_31_11_114: EngineState: CH_DBG_ENABLE_ASSERTS=1
2024-01-07_23_31_11_115: EngineState: CH_DBG_SYSTEM_STATE_CHECK=1
2024-01-07_23_31_11_116: EngineState: CH_DBG_ENABLE_STACK_CHECK=1
2024-01-07_23_31_11_117: EngineState: EFI_LOGIC_ANALYZER=1
2024-01-07_23_31_11_118: EngineState: EFI_TUNER_STUDIO=1
2024-01-07_23_31_11_118: EngineState: EFI_SIGNAL_EXECUTOR_SLEEP=0
2024-01-07_23_31_11_119: EngineState: EFI_SIGNAL_EXECUTOR_HW_TIMER=0
2024-01-07_23_31_11_119: EngineState: EFI_SHAFT_POSITION_INPUT=1
2024-01-07_23_31_11_121: EngineState: EFI_INTERNAL_ADC=1
2024-01-07_23_31_11_122: EngineState: readFromFlash 80E0000
2024-01-07_23_31_11_123: EngineState: applyNonPersistentConfiguration()
2024-01-07_23_31_11_124: EngineState: initializeTriggerWaveform(TT_NARROW_SINGLE_TOOTH/11)
2024-01-07_23_31_11_124: EngineState: Read valid configuration from flash!
2024-01-07_23_31_11_125: EngineState: pin_markUsed: Secondary UART RX on PC11
2024-01-07_23_31_11_125: EngineState: pin_markUsed: Secondary UART TX on PC10
2024-01-07_23_31_11_126: EngineState: pin_markUsed: led: comm status on PD15
2024-01-07_23_31_11_127: EngineState: pin_markUsed: led: warning status on PD13
2024-01-07_23_31_11_127: EngineState: pin_markUsed: led: running status on PD12
2024-01-07_23_31_11_128: EngineState: engine sniffer: No
2024-01-07_23_31_11_128: EngineState: engine sniffer size=300
2024-01-07_23_31_11_128: EngineState: initAdcInputs()
2024-01-07_23_31_11_129: EngineState: pin_markUsed: Coil 1 on PC0
2024-01-07_23_31_11_129: EngineState: initHardware() OK!
2024-01-07_23_31_11_130: EngineState: Emulating MINIMAL_PINS
2024-01-07_23_31_11_130: EngineState: WARNING: CAN not enabled
2024-01-07_23_31_11_131: EngineState: pin_markUsed: Tps1Primary on PA3
2024-01-07_23_31_11_161: EngineState: pin_markUsed: Clt on PA1
2024-01-07_23_31_11_162: EngineState: pin_markUsed: Iat on PA2
2024-01-07_23_31_11_162: EngineState: setTpsAccelLen: Length should be positive [0]
2024-01-07_23_31_11_162: EngineState: setTpsAccelLen: Length should be positive [0]
2024-01-07_23_31_11_163: EngineState: Running main loop
2024-01-07_23_31_11_163: EngineState: LUA loading script length: 572...
2024-01-07_23_31_11_164: EngineState: LUA script loaded successfully!
2024-01-07_23_31_11_164: EngineState: Lua memory heap usage: 14329 / 25000 bytes = 57.3%
2024-01-07_23_31_11_164: EngineState: USB: got Query command
2024-01-07_23_31_11_167: EngineState: got S/H (queryCommand) mode=1
2024-01-07_23_31_11_171: EngineState: Primary UART RX PC11
2024-01-07_23_31_11_172: EngineState: Primary UART TX PC10
2024-01-07_23_31_11_173: EngineState: TunerStudio size=804 / total=3 / errors=0 / H=1 / O=0 / P=0 / B=0
2024-01-07_23_31_11_176: EngineState: TunerStudio W=0 / C=0 / P=0
2024-01-07_23_31_11_194: EngineState: confirmation_set date 2024-01-07T23:31:11.0759788:36
2024-01-07_23_31_17_860: EngineState: Incorrect argument count 5, expected 4
2024-01-07_23_31_17_861: EngineState: failed to handle command [sparkbench2 1000 1 5 333 3]
Warnings:
fuel cut: setting disabled
Ign cut: ign off

RPM fuel/ignition cut are disabled, RPM is in appropriate limits. Launch control is also disabled.

If you need more info from me, please ask.
User avatar
AndreyB
Site Admin
Posts: 14334
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: rusEFI as ignition control unit for soviet boxer

Post by AndreyB »

Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

Thank you. It helped.

First start. Now using just cam position sensor with slimpe advance vs rpm plot.

Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

Hi again. I'm trying to add bluetooth HC-05 module, but not sure I'm doing it right.
Should I use calibration secondary UART channel for this? Or it is firmware dependant setting somewhere in Tuner Studio?
User avatar
AndreyB
Site Admin
Posts: 14334
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: rusEFI as ignition control unit for soviet boxer

Post by AndreyB »

Yes it depends on how the firmware was compiled. Use "pins" command in console to see if and where you have UART.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Fantomiaso
Posts: 59
Joined: Fri Jun 14, 2019 12:48 pm
Location: Belarus

Re: rusEFI as ignition control unit for soviet boxer

Post by Fantomiaso »

Looked into one old project (based on 2019 year firmawre) to see, how BT was made years ago. There was a setting:
изображение.png
изображение.png (20.66 KiB) Viewed 49585 times
Where has it moved in actual firmware?

In console messages I see:

Code: Select all

2024-01-21_17_18_14_808: EngineState: Primary UART RX PC11
2024-01-21_17_18_14_809: EngineState: Primary UART TX PC10
But using USB-UART converter to connect to theese pins results no connection (port test fails).
Post Reply