rusefi.com

https://github.com/rusefi/rusefi/blob/master/firmware/Makefile#L62 You're using softfp in the Makefile, so it's not fully used. It has to copy register data from regular to FP registers everytime you need FP. see http://www.gurucoding.com/en/rpi_cross_compiler/diff_hardfp_softfp.php https://wiki.deb...

Maybe it's time to use LTO and switch to -Os instead of -O2

I also see that you don't use the FPU, is there a good reason?

That's how AEM does it. Except they use headers. http://www.civic-eg.com/causeforalarm/aem_twin_fire/aem_30-1000_pcb.jpg http://www.jefftsai.com/Pictures/Cars/Forums/ClubLexus/2008_02Feb/ems_2.jpg As for finished solution you have this: http://www.cinch.com/products/modular-integrated-connector-encl...

If your goal is 0.2 degree crank angle accuracy. Is that +/- 0.1 or is that +/-0.2? If you use +/- 0.1, during your tuning you will likely push until you get an issue, then you'll back off by at least 0.2 to guarantee you are safe, then you might decrease by another 0.2 just to give you some safety...

2007 CBR600RR. I run a 2014 HRC (basically Moto2) ECU for now, it's a lot better than stock but it's still years behind the current production (like 2015 R1) stuff. There's only fuel/ignition/staging offset tables, engine braking and couple things like pit limiter. The idea behind this design is to ...

LM2931. The polyfuse is only rated to 24V, the TVS is rated to 15V continuous. I actually expect the TVS to switch before it gets too high, or the transient to be short enough. Which original ECU are you talking about? This is not an ECU in my case. The OEM one is potted so... (it's a motorcycle) T...

Well if you're the only contributor there's no point indeed. At least for now.

Here's my power supply: Basically I use an input diode, a resettable fuse, a TVS diode and a pretty tough automotive LDO. In theory you only need the LDO since it's got protections everywhere. As long as your input cap is rated 60V+ and has no polarity (unlike mine). It worked perfectly for me so f...

You can manage groups of users and give those groups roles with different access rights.
ie: for pull requests you can specify who is allowed to merge.

Right now you have to specify rights for each collaborator, for each repo.

I sense sarcasm

Maybe you should turn your username (rusefi) into an organisation and create another user (russian) that's member of it.
It makes more sense and would be easier to manage code maintainers/contributors.

Thanks!

This looks like it's adequate:
http://www.vishay.com/docs/34158/icm1206.pdf

This might help: https://github.com/cmungall/gosf2github

Yes but it's a mirror, there's no way to merge pull requests and the commit history is simply broken.

Basically it's almost useless in the current state.

Maybe it's time to finally move to github and get 10x contributions and visibility
spags is 100% correct.

I would like to have a look at the code but SVN is just a big NOPE for me. I'm probably not the only one.

Indeed that was incorrect... I remember seeing this somewhere on an STM32 datasheet.
There are actually 2 versions, 0.4 and 0.5, in this case ST uses 0.5mm.
My bad

Anything below 0.8mm pitch starts to be annoying.

In fact I expect the switch to generate more ripple on SMPSes than LDOs.

On bikes most of these wires are around 24AWG. (they are much shorter than in cars)
Do you have a link or information to calculate the required RF choke?

Thanks

Keep in mind that anything larger than LQFP144 has a 0.4mm pitch.
Most SDRAM/Flash are very fine pitch or BGA as well.

An SD card would be sufficient for your use if you don't need blazing speeds.
You could even use it for firmware upgrades.

There's no RF choke, I might add one later on. I'm not using an SMPS so I don't expect a lot of current ripple. Especially that I have a big output cap that smooths things out. I had a look with a scope and voltage ripple is around a couple mV on a lab PSU IIRC. I assume the long wires and battery o...

Here's my power supply: https://s12.postimg.org/5xre8z6d5/2017_02_20_01_08_07_1_Schematic_D_src_STM32_M.png https://s3.postimg.org/5qbqge9zj/psu.jpg Basically I use an input diode, a resettable fuse, a TVS diode and a pretty tough automotive LDO. In theory you only need the LDO since it's got protec...

Seems like those are not depletion mosfets.

If you want to go cheap, go LDO. It's not like it's using a lot of power anyway right?

I'm actually surprised you guys didn't take this into account from the beginning, it was bound to happen. (no offense) Any other scenarios we might have fixed? As for internal/external flash that's technically a different subject altogether, for now our workaround is to only write flash while engin...

I'm actually surprised you guys didn't take this into account from the beginning, it was bound to happen. (no offense) I use an spi eeprom with crc and wear leveling: https://github.com/fpoussin/MotoLink/blob/master/code/app/storage.c#L271 Feel free to copy/try it. Everytime you write to the flash, ...

russian wrote:

mobyfab wrote:If you need hardware, I have an old server tower i'm not using, 2x Xeon L5420, 8Gb of ram, but it's very heavy and noisy...

Wrong continent, I am afraid to think about shipping

I'm afraid so

There's also this one: https://semaphoreci.com

If you need hardware, I have an old server tower i'm not using, 2x Xeon L5420, 8Gb of ram, but it's very heavy and noisy...

Maybe you can do the CI on travis, and still have the other tests on your server.

I can give you access to my jenkins+docker instance once I'm done migrating it.

Now again, if you were using github... https://docs.travis-ci.com (free)

RPM vs tick rate, giving the precision:

https://jsfiddle.net/X64Rb/8

It's in JS so feel free to modify calculations or add more values.

You can also export to images.

This is not the only open source ECU project. This isn't a contest ... We win Right... Contradictions? Just as a reminder, since some people seem to forget: I made a schematic for an ECU a while ago, I'm posting it here in case this helps you with hardware design kb1gtt, you get the point ;) It's al...

kb1gtt, you did a really nice explanation of the pros/cons. For the sync, you can use mutexes and sync signals to the host to work around that problem. The uart uses DMA so you can write to it while the MCU is busy and not lose any data. Russian, 0.2 because it's the same value as some commercial EC...

I never said you were an a-hole, or that you have to do as I say :| 0.2 is easily achievable with 32b timers. We have those so why not use them? IMO ignition timing should always be predictable (at least withing a hard range). So 99.9% accuracy from the software point of view. Not a problem with har...

You're right, it's not something needed in all design cases. It's just the solution I like most. If I was to design an ECU I would not allow an accuracy below 0.2 degrees at 20K rpm so it would be manadtory to use hardware timers. Since there are a limited numbers of these, especially 32b ones, usin...