DIYEFI.org Forum

... Step by step, first we need to see how good the PCBs are. fred's chinese experience is the same as mine. when they get new customers (which typically end up as one-off customers) it's cheaper to have someone do them by hand and thats where all the assembly errors are made. once they have you ho...

fixed
https://github.com/EssEss/freeems-cst/c ... a29162036a
thanks for the help

https://github.com/EssEss/freeems-cst

it's a start.
overwhelmed, but super excited at the moment.

yes, a 'tier 1' app was what I wanted to attempt first.
I'm going off to get a little project started .. got a late start tonight.

The only thing I don't agree with is the testing of commands .. I was hoping this was going to be a pure packet format verifier. The only commands I planned on using was to get capabilities and a lot of echo packets. Something that exercises commands (outside of a tuner app) seems to be something ab...

Fred, Sean[0], and I were kicking around some ideas for stress testing the comms interface of a standards compliant freeems implementation. I decided to volunteer where I could to write this app. I'm still reading and coming up with a plan, but this is some prelim direction (not in any order): - cpp...

it's more common to find in the 'cs' prefix. the 'ncv' prefix is for special tracking purposes used in the auto industry.

this is the absoultely wrong conditioner to use for missing tooth applications .. its intended for speed/abs pickups.

I'm sorry, I did realize that later.

do you have the link for that ECU ?

more of my 2c: the _t is there to avoid collision since they usually reside in a .h. The .h is only file scope, but usually gets inserted across many translation units .. thus they end up more 'global' than intended most of the time. From some real code: you're more likely to get a collision from ty...