EEC-V Diag/Test Bin

[DWS]

I'm slowly working out pinouts and the bare min code to document things on my end better and some projects I have in mind. Ultimately I think I'll end up with a bin that's just for testing/diag work. Would there be interest in something like this and what kind of features would be desirable? This would all be around testing the actual computer/chips inside, but in theory it could give manual control for testing external items too. My orig idea was to use the crank sensor input since effectively all gas engine computers have that input and should be pretty standard for how it's wired internally. Like a simple 5v pulse (button press) to activate the outputs in a pre-programmed order.

I have a QH coming, of my understanding, it's "live tuning" feature effectively allows for reading ram addresses, if that's the case it should be possible to give access via ram to control any input/output and change any modes/setups to match the physical hardware in the computer. I haven't really fleshed out the idea yet, just starting off with an extremely simple HSO test which on the computer I'm testing on is injector #1.

Either case, I'll end up with something and it will be a great learning tool for myself, but I could see it being useful for others.

As for release style, I'm not sure if I want to go open source or closed source, but if I do sell it, I plan to make it cheap as long as the support for it isn't too much extra burden. It's a fairly high technical thing, simple but if you don't know what to expect, it can be hard to understand. Like the HSO mentioned before, channel 0 goes to a UPOD chip out channel 5 which shorts the injector #1 pin to ground when activated, in a different computer that might be for injector #5 which is part of the data I'm working on collecting and documenting.

General chip pinouts like UPOD, CPU, AICE, etc I'm planning to release openly since that's info we should flat out have access to already from the mfg in my opinion (repair-ability, maybe replacement chips can be identified, etc).

Talking about open info, is there a place where eec-v info is even shared in a end user friendly accessible way like a wiki? If not I might have to host one with my host provider, I'm sure there's some people that would love to support keeping documentation accurate. I'm not the greatest with data presentation, but I tend to go nuts on collecting it lol.

Just to be clear, right now my focus is EEC-V computers that are 4 bank (224kb also called 216kb). 2 bank, 1 bank and EEC-IV should be similar code but outside my primary focus at the time. Also there's some computers with 512kb flash chips, I'm not aware of a way to read/write them even via J3 so of course those are a future idea/plan to toy with.




If things go well, there might be new features that can be added to strategies to support new inputs/outputs that already exist in the computers. Some of them can be depopulated hardware wise (resistors and transistors mostly), but some are directly wired for output. Of my understanding, most/all pins have a designed feature tied to them and are somewhat standard across several hwid's that are related. Of my understanding, no one has really documented the hardware in these computers, at least not in a location that can be access.

Anyway, back to having fun with assembly code and playing with my oscilloscope lol.