DIYEFI.org Forum

2) If you use "int" then the code is actually NOT portable, whereas if you use char, short, long then it IS portable because the same behaviour AND accuracy and overflow etc will be present on both platforms. In the case of this chip alone, without porting it, a compiler flag change could...

how would you handle overlapping dwell ?

In the end your original accuracy is still limited by the ecu + the latency of your device which may change from build to build unless you keep close tabs on it. To me, it's not a true offload of responsibility.

I think I kinda of get it, correct any of the following assumptions if they are wrong: 1. so your dwell start is predicted for each particular cylinder ? 2. so you need at least one whole complete rev (2 'home' pulses) to actually begin prediction ? 3. you're depending on prediction to be well enoug...

I'd be interested in hearing more about how Python changed your view of your embedded code so please elaborate. About 8 or so years ago I was getting sick of making the same mistakes over-n-over in C; It was my breaking point where I resolved to start taking control of the quality of my code. I kne...

I'm just sharing my view on this based on my experience. This is exactly why I'm here, I truly am thankful for your perspective. I really have no problem with adhereing to the rules at all. I've traditionally attacked #2 as you state by being very rigid in my choices and very aware of my platform, ...

I see a potential benefit of getting 8 cyls, but other than that, what benefits does EDIS offer? a limp mode of sorts .. if (for whatever reason) the base ecu stops providing advance info, edis defaults to a hard tooth, and if you've phased the pickup correctly it'll fire @ 10bdtc. It's a completel...

nothing stands out immediately except for: # when declaring a pointer make it (type* name) not (type *name) # Never use int, always char, short or long I disagree w/#1 because: int* pThing1, Thing2; vs: int *pThing1, Thing2, *pThing3; granted, I can't even remember that last time I did that, but I'v...

I'd just like to say that this: 00076 #else 00077 /* let us know if we are being untidy with headers */ 00078 #warning "Header file FUELANDIGNITIONCALCS_H seen before, sort it out!" 00079 /* end of the wrapper ifdef from the very top */ 00080 #endif ... is genius. I usually walk through my...

I'm quite a bit late on the discussion, but I'm using this on my board. I have a simple single sided gerber to put up if anyone wants to make it (smt) .. it only does mode a1/a2/b .. the c mode peak detect can be mimicked w/a simple cs1124 so I didn't bother trying to accomodate it. mode c is intend...