Speeduino is now on Github Sponsors (Rather than Patreon): https://github.com/sponsors/noisymime
Any general discussion around the firmware, what is does, how it does it etc.
By noisymime
#17667
Where does the time go? April already and March has been another big one for Speeduino. Forum users and installs are increasing all the time and it's terrific to see the project starting to be mentioned more often on forums etc as a truly viable system!

As a heads up, I plan a slightly quieter month throughout April on the firmware front. I will still be doing general maintenance, bug fixes etc, but probably not so much work on new features. The reason for this is that I want to spend a good chunk of time working through the documentation pages (https://speeduino.com/wiki/index.php) to try and:
1) Have at least something on every topic
2) Cover all of the most used pages with good detail, images etc

DIY Engine Management Systems live and die by their documentation and to date whilst Speeduino's documentation has been minimally OK, I would like to bring this up to a much more professional level. I've already begun restructuring a few things, so there are many placeholders there currently as indicators of what I will be adding.
If there is anything you find that you believe is important, but that doesn't already have even a blank page, then please drop a note in the forum and I will look at adding it.

Additionally, I am ALWAYS on the lookout for anyone who wants to help with documentation! If you have some time and knowledge to share, please do contact me and I can get you the required access!

As for the full feature list from March, here are the primary changes:
  • Addition of closed loop stepper idle control. This comes with a fairly major rewrite of the whole stepper control system, affecting open loop as well. Hopefully this should be a big improvement for those who had been asking about stepper idles
  • Add a bunch of extra info into logs (Eg boost duty, boost limiter indicator, idle load (Steps or duty cycle) etc)
  • Add an option for a number of decoders (Eg dual wheel) to only sync once. Currently these decoders will resync every time they get a cam pulse, but this can be problematic on noisy cam signals.
  • Initial Subaru 6/7 decoder. This has not yet been tested on a vehicle, so should be considered somewhat experimental
  • Thanks to user dazq, there is now an outputs test dialog in Tuner Studio. This allows you to test board functionality and outputs (Ignition and injectors) without having a stim attached. It can be enabled through the project properties dialog.
  • Some compatibility work for Teensy and stm32 (Code will now fully compile on stm32, though scheduler/timers are non-functional)
  • Calibration for the VW/Audi/Porsche 250kPa MAP sensor added
  • Fixed a bug on the On/Off idle control that could cause it to startup in the wrong state
  • Improvements to syncing on the Audi 135 decoder
Keep an eye out over the next few weeks for some more details around the hardware I've been working on over the last few months!

The firmware bundle can be downloaded from: http://speeduino.com/wiki/images/2/24/S ... _Mar17.zip
As usual, make sure to reload the latest ini into your TunerStudio project after upgrading the firmware
By noisymime
#17687
Gotboost858 wrote:
Tue Apr 04, 2017 3:29 pm
Has anyone looked into Staged fuel control for secondary injection?
I haven't yet decided on the way I want to implement this. There seems to be conflicting views as to what the most flexible way to use this is (Eg multiplying tables vs switching etc)

It likely won't happen this month, but I'll try and take a good look at it after that.
User avatar
By Bleeker
#17695
I receive the following error Message when I try to compile the firmware:

exit status 1
'IDLE_TIMER_DISABLE' was not declared in this scope

Any ideas?

Output Test sounds intresting to test my wiring :)
User avatar
By PSIG
#17696
I don't think there are differing opinions on table manipulation so much as different purposes, so different methods. Random examples: multiple or additional injector(s) or sets (for various reasons including emissions, fuel distribution, idle control, or load capacity) using same fuel added during increasing loads (staged or shared) is generally single-table math manipulation or table multiply. Different fuels at different times (track tank-ups or after-start fuel-switching, or same-fuel different tunes) is generally 2nd-table swapping or switching. Adding different fuel or oxidizer during load (injecting alky on a gas table or nitrous, etc.) is table addition, superimposition, or table blending. There are more schemes than these three for special apps or limited hardware and some can work fairly well in place of another.

Note the crossover or mash in terms commonly used. It will be important to establish Speeduino-specific terms that are accurate and clear, to avoid confusion or misapplication. The tunerz using Fast 'n Furious terms and concepts have caused enough damage and confusion to our sport thankyouverymuch. Speeduino is gaining a position to help lead them into the light, and I think we should use that opportunity.
;)
David
By noisymime
#17707
Bleeker wrote:
Wed Apr 05, 2017 6:30 pm
I receive the following error Message when I try to compile the firmware:

exit status 1
'IDLE_TIMER_DISABLE' was not declared in this scope

Any ideas?

Output Test sounds intresting to test my wiring :)
What board do you have selected in the Arduino Tools menu?
User avatar
By Bleeker
#17730
noisymime wrote:
Thu Apr 06, 2017 3:57 am
Bleeker wrote:
Wed Apr 05, 2017 6:30 pm
I receive the following error Message when I try to compile the firmware:

exit status 1
'IDLE_TIMER_DISABLE' was not declared in this scope

Any ideas?

Output Test sounds intresting to test my wiring :)
What board do you have selected in the Arduino Tools menu?
Oh, I still had the Uno selected, as I upoaded Ardustim last time.
Everything fine now, thanks for the update :D
By michelko
#18001
Hi,
trying to update to march 17 Firmware getting this message:

"'initialiseADC' was not declared in this scope"
Any suggestions?

Thanks Michael

1J and 1Q appear to be jumped at all times (with i[…]

Speeduino ECU compatibility

Speeduino works with any engine. You just need to[…]

Please read the wiki. It seems you don't understa[…]

VVT angle going backwards?

Pretty sure other than MX-5 trigger VVT is still W[…]

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