LCD and buttons version in development

[clsegurac]

Is there development with LCD screen and buttons in development?

[jfseaman]

I'm editing a long reply.

Basically, if I can get let in to the allowed contributors, I can and will make more features.

Next up, the long reply.

[jfseaman]

Don't give up..

You are not the only one.

The "Ardu-Stim" package works but comes with limitations for lack of better verbiage.

I have been using Ardu-Stim for over 3 years. I like to "play" even though I am working towards deployment on a couple cars and lots of bikes.

I have the DIY-EFI SpeedySim and BobTron05 stimulator. Both use Nano and ardustim sketches. Download and controlled by Ardu-Stim. These stimulators are ~$50 to put together.

With the current dependence on ATMel328 based UNO or Nano, there is not a lot of room in flash or ram for more "features". The biggest reason for using the ATMel328 based boards is that they are 5V and "cheaper" than a full Mega 2650.

Like you I see a "need" (grain of salt) for change and features. The ATMel328 MCU boards are no longer "cheap", an actual "Arduino" brand being ~$26 and "open source" versions are 3 units for ~$20. To contrast a Raspberry Pi Pico is 4 units for ~$22, an Espressif ESP32 is 3 unist for ~$14. There are many many more alternatives. However, all the alternatives to the ATMel328 are 3.3V which means more parts are needed to send and receive signals that the ECU/Speeduino can understand.

Background:
The current official version 1.2.1 runs only on ATMel328 and uses ~23k flash and ~1k ram but 80+ more bites of ram come off the heap/stack at run time for an input buffer. Just not much memory left. I found out what happens if the code gets too close to the limit.

I've been working with my own version for quite a while but still based on the ATMel328. I've made it "interactive" and added features. It is still using a "serial" interface over the USB. Mine is sitting at ~27k flash and ~1.2k ram.

When Josh updated to V1.2.1 the changes were "drastic" so merging my feature set is difficult but I will get it done and not alter the way that the "sketch" interacts with Josh's UI. I want to add features to the UI and I have been trying to figure out how to build the UI but not succeeded yet.

I would like to get away from being tied to the AtMel328 chip as it has only 30k of flash and 2k of ram for variables and it is NO LONGER CHEAP!. My version is using 27k flash and 1.2k of ram because my input buffer is statically allocated.

Where I want to go with Ardu-Stim:
The first thing is that I don't want a separate "project". It is my feeling that if I do this it should be tied to the Speeduino community and not a forked or separate project that has to be "found" by people looking for an alternative to the main branch of supported code.

That means that I would have be be let in as a contributor to the project. I don't know how to do this.

Things I want:
Run time crank/cam trigger wheel upload. No more hard coded combinations. If the trigger crank/cam wheels could be uploaded then the definitions could be in a "database" and all that space in the code returned for use to make features.

That would require a user interface that knows the "database" and provides selection. Same as the current UI but with the trigger defs outside the code.

Separate controls for TPS and RPM. The current code ties RPM generated with TPS from a potentiometer. That makes it hard to see what injector pulse width and timing do at say WOT as RPM on the stimulator raises far faster than a running engine would. I have some of this coded. The BobTron05 stimulator has hardware for it but no software supports it.

[AngeloDP]

Hello,
I have made a "Teensy-stim", largely based on Ardu-stim. The main changes are in the signal generation. But all tables and serial interface were used "as is". The PC software is fully compatible.
As name suggest, it is based on Teensy 4.0. I added a 320x240 TFT and an encoder. Mode selection and RPM can be changed whithout the PC. RPM can be finely adjusted in 1, 10, 100 or 1000 RPM steps.
There are some firmware modifications I want to make, and then I will publish the schematics and code.