Thanks for the call out.
Also, now that I look into V2 deeper I see that most of the improvements you made center around the sensing circuit and code for the RPM signal. That isn't an issue in CAN as all of that is happening on the ECU side and we are just displaying pure data. So most of the settings are already handled ( setting activation zones, zone colors etc) I'll just need to add the ability to change the number of pixels and animation direction via the menu and not in the code. Should be a simple add. I'll update once I get that done.
I still need to do some testing but here is the new V2 version of my version.
Talk about a fast turn-around! Nice work!! thanks for posting this in the forums too, I know some people will appreciate this. How's the response time?
Assuming you mean response time of the CAN bus/ecu to the RPM request, It fast! faster than I could really display. I may put some delay in the read request as I'm constantly polling but as far as I can tell it doesn't really matter.
In messing around last night I switched it over to read my intake vacuum and made it into a boast gauge. :) I could thing of a bunch of uses for this. Thanks for the motivation I may just have to kickstarter my second board having the full arduino footprint will be super cool.
We should chat. :-) Shoot me an email, firstname.lastname@example.org I have some things in the works that could greatly benefit your goals. We may have an opportunity for something really great here!
Jon @ Chippernut