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 (264.73 KiB) Viewed 73155 times
Re: rusEFI as ignition control unit for soviet boxer
Posted: Thu Jan 04, 2024 12:23 am
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?
Re: rusEFI as ignition control unit for soviet boxer
Posted: Thu Jan 04, 2024 2:49 am
by Fantomiaso
Not quite shure why I need wbo? Carbs are already adjusted and synchronised with pressure gauges.
Re: rusEFI as ignition control unit for soviet boxer
Posted: Sat Jan 06, 2024 11:10 pm
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?
Re: rusEFI as ignition control unit for soviet boxer
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?
Re: rusEFI as ignition control unit for soviet boxer
Posted: Sat Jan 06, 2024 11:38 pm
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.
Re: rusEFI as ignition control unit for soviet boxer
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.
Re: rusEFI as ignition control unit for soviet boxer
Posted: Sun Jan 07, 2024 8:46 pm
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):
Re: rusEFI as ignition control unit for soviet boxer
Posted: Sun Jan 07, 2024 10:31 pm
by Fantomiaso
Thank you. It helped.
First start. Now using just cam position sensor with slimpe advance vs rpm plot.
Re: rusEFI as ignition control unit for soviet boxer
Posted: Mon Jan 15, 2024 7:36 am
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?
Re: rusEFI as ignition control unit for soviet boxer
Posted: Mon Jan 15, 2024 3:29 pm
by AndreyB
Yes it depends on how the firmware was compiled. Use "pins" command in console to see if and where you have UART.
Re: rusEFI as ignition control unit for soviet boxer
Posted: Sun Jan 21, 2024 2:00 pm
by Fantomiaso
Looked into one old project (based on 2019 year firmawre) to see, how BT was made years ago. There was a setting: