Any general discussion around the firmware, what is does, how it does it etc.
#58459
Wow, that's really bad. The sensor response to the tooth shape is likely what we are seeing (similar to some Toyotas) So, yeah, the first way is correct for the sensor, but keep in-mind I don't know which edge the decoder was written for. So either correct or reversed polarity could be the right one to use for that, and if it was written for reversed, it won't read right either way… if you see what I mean.
#58512
@PSIG : I see what you mean.

I took a look at the code for clue and the workaround is to devided the real 44-2-2 flywheel into a 4 virtual tooth trigger wheel. 360/44 equal a floating number and Speeduino deals only with real number to calculate angles. So we end up with 4 trigger tooth and an trigger angle of 90°.

Each 12 real tooth detected decoder counter reset and virtual tooth increment.

Renault_44_2_2_Flywheel_speeduino_workaroud.jpg
Renault_44_2_2_Flywheel_speeduino_workaroud.jpg (172.55 KiB) Viewed 6618 times

Only raising edge can work.

Assymetric_missing-tooth.png
Assymetric_missing-tooth.png (178.14 KiB) Viewed 6618 times

I added some debug info into the code and made a try on the stock engine with stock sensor and code seems to work properly.
But no sync and no rpm signal into TunerStudio.

- Can you confirm that speeduino use the #1 teeth as reference point (just after missing teeth) to compute ignition and injection stuff ?
- What event trigger RPM signal and sync from Speeduino to TunerStudio ?

Best regards.
#62890
The 44 tooth decoder is now part of the main code branch. This means it will be in the next firmware release. The code also supports the 66 tooth trigger wheel using the same principle but this isn't tested. The testers didn't have a cam signal so the code only works with a distributor due to their being nothing unique within 360 degrees of crank rotation. A cam signal can be added in so the distributor can be removed in due course if there is demand.
#69835
Nawakland wrote: Wed Sep 07, 2022 7:39 am @PSIG : I see what you mean.

I took a look at the code for clue and the workaround is to devided the real 44-2-2 flywheel into a 4 virtual tooth trigger wheel. 360/44 equal a floating number and Speeduino deals only with real number to calculate angles. So we end up with 4 trigger tooth and an trigger angle of 90°.

Each 12 real tooth detected decoder counter reset and virtual tooth increment.


Renault_44_2_2_Flywheel_speeduino_workaroud.jpg


Only raising edge can work.


Assymetric_missing-tooth.png


I added some debug info into the code and made a try on the stock engine with stock sensor and code seems to work properly.
But no sync and no rpm signal into TunerStudio.

- Can you confirm that speeduino use the #1 teeth as reference point (just after missing teeth) to compute ignition and injection stuff ?
- What event trigger RPM signal and sync from Speeduino to TunerStudio ?

Best regards.
I have the same problem
#70446
Evening,

I finally got it working with the last LTS update - February 2024 Fix Pack 2 (FP2) - https://github.com/speeduino/speeduino/ ... g/202402.2

Stock engine, flywheel and sensors.I only swap injectors for modern high imp.
I already made 1000 kms with this setup and full E85. Still need some fine tuning to smooth cranking phase, warmup and idle valve control.

I can provide some info about my tuner studio settings.

PS : I use renix 44-2-2 decoder. It's my daily car a Renault R21 GTS 1.7 with F3N engine. Inline 4.

Some pictures of my speeduino ECU into OEM Siemens/Renix/Fenix enclosure : https://pixelfed.social/p/electronlibre ... 0067769012

Best regards
Traction control

Hello! If you're searching for a reliable and fun […]

Is the brightness control done by adjusting the su[…]

Dropbear V2 Availability

Thanks for the response - I think I'll wait for th[…]

Please post: ECM version and any module versions […]

Still can't find what you're looking for?