DIYEFI.org Forum

I removed the connect button in the latest commit. After using it like this, it seems to make more sense.

I did notice a bug where it wont detect the serial monitor after you have performed a load. I'll get to it ASAP. Slowly but surely the global code is going away.

-sean

I pretend they are the same with a //TODO comment in there to factor the flow difference, before I go live with it. Right luckily the injectors are in the same family(denso 230cc vs 190cc iirc) so I should be ok with dead time being the same. Good thing you convinced me to make the xgate scheduler a...

One step closer to running with a non-piggybacked setup.

http://youtu.be/dxt9Yn3NNBM

Bench testing staged, sequential injection.

make TEST_AND_SAVE_ALL

Yeah it should make it easier, I noticed xgate failed with your example. I suspect it will "just work" with newer binutils?

c ya

Andy with the stang? Requires a decoder, not hard, but I'm busy...

What's the pattern for it?

-sean

So, do we get a full 2.5v hysteresis?

The six shooter is not the most exotic piece, but it's relaiable and often gets the job done I did'nt save it but I'll try to take another reading today. IIRC you can see it if you have the sampling set high enough to read 0.00x ms.

Fred wrote:Well, I can tell you right now, none of them are PIT and not XGATE. :-p

Fixed, thx.

Fred wrote:Upload the file and we might be able to tell you! :-p

Lol and with a fast enough scope you will also be able to tell me which leads are longer than others.

It seems I was able to move the xgate output scheduler into a more appropriate section, of the firmware. This was the result of sending the benchtest firmware the test.sequential.bin file.



Which outputs are xgate and which ones are ECT...........