Motolink, my fuel mapper project for motorcycles

[mobyfab]

I'm working on this for some time now... had not touched it for almost 2 years, but I finally finished(ish) it!

Motolink is a fuel mapper, which is a device that will read values from various sensors (rpm, tps, afr) to create 2D maps containing measurements.

Why would I need this? Is it like power commander 5 autotune / Bazzaz?
There are various racing ecu kits sold by manufacturers (Honda, Yamaha, Triumph, etc...) that allow you to modify different values, like fueling and ignition advance.
These do not have any kind of real time tuning capabilities, so that's where my devices gets interesting.
In short it's pretty close to what power commander offers with their ($500+) autotune.

You basically go for a spin on the dyno / at the track, come back, and there's your map.
You can now modify the fueling in your software and start over until you are happy with the results.

Now the technical details: (current revision B)
- STM32F303 QFP64
- Qt GUI for control (Cross-platform, fast and lightweight)
- ADC1 for slow analog, ADC3 for fast analog
- Knock sensor DSP processing (Hann window/FFT)
- Timers for frequency capture (RPM/Speed)
- No ASICs, all done in MCU
- Serial interface to innovate wideband controllers (MTS protocol)
- Bootloader for firmware updates
- USB connection
- Debug console via USB CDC
- Maps and settings saved in external SPI EEPROM
- OBD emulator over CAN BUS (for external datalog ie racechrono)
- Sensors input: Direct, OBD (Can Bus)

Project url:
https://github.com/fpoussin/MotoLink



Demo:
https://www.youtube.com/watch?v=rAnS-8KSQrY

What's left to do:
- Test on a racetrack
- Map smoothing? (affect more than one cell at a time)
- ?
- Profit

For rev C:
- Replace microfit connector with a J1962 (OBD) connector/enclosure set like ELM327 adapters (these are hell to de-pin, and are a little too small for my application)
- Integrate discrete LSU 4.9 wideband controller, get rid of RS232 IC and MTS stuff (or use 14point7 module?)
- Add LSU 4.9 connector at the other end
- Add ESP32 module for wireless connection over wifi/BT SSP?
- Emulate ELM327 over BT instead of OBD over CAN?

I do plan to integrate some of these features into rusefi at some point.
Let me know if you have any questions.

[kb1gtt]

I don't have eagle right now, at work. Is the knock a generic PGA then DSP? If so that's cool. It would really simplify the design and allow for allot of flexibility. However it would also require DSP programming, which can have it's own draw backs.

[mobyfab]

Yes it's simply connected to a buffer opamp with a dc blocking cap and biasing at 1/2 VDDA.
I have a dedicated ADC for this.

There's a graph on my app that shows the FFT result.
ARM provides a DSP library, it's not too complicated to use.

[Flying]

rev. C sounds very exciting for the project itself and rusEFI, are you planning on CJ125 integration?

[mobyfab]

I won't use any ASICs in this project, so no, it will be 100% discrete and directly measured by the MCU just like knock.

[AndreyB]

Are you using ChibiOS in this project? One day I hope to grab some of your code. Maybe we can extract it to make reuse both ways easier - not sure if you would be interested to reuse anything rusEfi

[mobyfab]

Yes, using vanilla 16.1.x and contrib repo.

I'm doing everything in C so I probably won't re-use any rusefi code.