Except sorry to hear you're having to work the holidays.....

 

Busy, Busy, Busy...
Work has me wrapped till after Christmas. Traced more outputs but still don't have them all. Still need to post up the relocatable "stock" source and the one with Z's adders in it.
Still have the XDF to organize too.
One of these nights I'll just not sleep and do it
Think the bugs have been worked out of the stock one.
Will do one more reasembly and compare to be sure.
Maybe Eric or someone can do a quick run on it to confirm no errors before it goes to the board.

Anybody know what the pin # was for the A/C clutch output on a 730/749 ?

AUJP doesn't use it but the code and output is there to run it (3FFC, b2). Don't see where that output goes to. Hoping to trace the output back to the processor PWM or QDM.

 

A/C Request signal B15 -goes to the A/C control switch
A/C Clutch Control Relay A13 -hooked into a power relay
A/C Status C17 hooked into the 'C' side of the A/C compressor clutch

Hope this helps.... -from a 730 Vette diagram.

 

The Corvette's never ran a '730 ECM. They used an underhood '727 ECM. Thus these pinouts don't match the '730 ECM, they are different between the two ECMs.

Go over to diy-efi and get the 90 Corvette wiring sheets. Then head over to Ludis's site and get the QuadPlugEcm sheet. That lists the cross reference between the '727 and the '730/'749 ECMs. Thank you.

RBob.

 

Yea sorry was tired last night....

 

Did that last night, got me closer but still can't decifer what the addressed bit is to operate that output.
Edit: (3FFC, b2 operates "F3" pin directly by state change)
Found a few more controls at 002F and 0033 that "seem" to run the outputs on the ignition U13 (IIRC). Fuel pump addy&bit is still elusive though.
Full control over this sucker will happen!
I'm in the process of building a "quasi-bench" to test them out.
Simulation of the code only takes you so far, the communication between chips has to be tested with separate code.
Using a std bin won't really work well because of the initialization and control that is already there will limit the amount of testing that can be done.

Edit: Figured you were tired because the "703" reference had me searching insanly for what that was

 

Reverse lock out for T56's came up in another thread.
Is it on to unlock or lock?
CARS light output pin would be used.

 

This is a question for the guys that have messed with ECM hardware. How hard would it be to expand the I/O's of the 730 with maybe a card that connected to the edge connector inside the ECM. The reason I ask is if the $8D code is getting worked on the source level it would be a great time to add extra I/O features. I know there are some unused inputs and drivers on the ECM but it seems like a lot more would be needed to make a universal code to work with many features mentioned in this post.

 

I'm not sure how to add more but there are several options that I've been looking into for using the existing Outputs.
Inputs do not seem to be a problem, there are several available.
Without removing any emmisions functionality theses are available:
Outputs:
"F8" Fan 2
"F3" A/C clutch
"F5" (has two quads in parrallel)
"E8" Fan 1 (If you don't run fans)
"A2" Relay 2 output
That is 4 for sure, 5 if you don't use the fan output.

If Emmissions are removed the following become available:
"F7" Can purge sol
"F4" Air Divert
"F2" Air Port sol
"E9" EGR Sol

And if you run a manual ""F6" TCC sol is there as well.
Lots of fun options to play with.

I'm close to getting control over these by locating the bits that operate the PWM and digital registers and will be posting what I have found so others can go farther with what I've started.
Once we know how to run each of them on thier own anything can be done with them.

 

Input side of things:

Analogs possible
"A3" TPS 2
"B3" MAT 2
"B7" Diagnostic 2 ??
"E10" MAT 3
"E11" (Inverting ??)
"F11"
"F12"
"F14" MAP 2
Still need to test if they exist onboard and how to make the proper hardware connections but these are open.

Digitals:
"A7"
"C3"
"C4" Fan Request (If not using fans)
"C9" A/C Request (If not using A/C)
"D2"
"D3"
"D4"
"D10" Brake Input
"D11"
"D12" Fan 2 Request
"D13" Power Steering cramp switch
"D15"

I haven't figured out how to make them respond to input power or if they are ground to indicate types but that will come later with help from knowledgable (sp?) electrical people.
Should be plenty to play with
right now my goal is to identify how to read and switch all ofthe I/O in code, then try to connect them.

 

I am just trying to hit as many birds as I can with one stone. I was just figuring the more I/O the more applications this code could be used on. The more applications the more people interested and the more people working on this project to make it a reality. Also if a I/O expansion card was used all the stock emissions and other things I/O could be retained without picking and choosing what to use and not to use which would increase the number of applications the code could be used on.

The fan1 and fan2 output really shouldn't be used for other purpose because many people run one or two electric fans. So that takes the available outputs to 3.

 

Just using F3, F5, A2 to control a relay board would get you at least 7 on/off outputs. Just set any combination of output pins on to control ch x on the board. Do you need more than 7?
what are you going to do with them?
Would need to know so some combinations could be setup by default. Part of the reason the aftermarket ecms are so easy is the user interface does a lot of stuff for you. JP or I would have to preset all the code so each pin has x & x qualifiers. Code would get long if you start checking all sorts of arbitrary quals for each pin.

Need to go dig up the Megasquirt relay board info
and work something up unless some electronic types step up.

 

I like that idea

 

Wouldn't this setup only allow one of the 7 relays to be active at once?

 

Yes unless you come up with a scheme for a PIC to read at x scan rate. JP & I don't have smog equip so we have plenty of I/O.

That's why I said list what you want. Just a few generic comments leads to....

Could throw in F1 and maybe some sort of off delay for certain outputs on the relay board. Make up a truth table and see what you can come up with. I'm not the electronics wiz. I just listed what's available.

 

No smog here either. But I do want the fan control...

 

I would like to keep pthe fan control as well. Seems like it would be best to keep the smog control in the basic code as well. just to have more "standard" and broader application. I'm considering removing my AIR stuff, but it owuld be nice to have the optIon either way. Any chance this can be a switchable thing with a flag to set if no smog?

 

Never considered taking out the fan control.
I don't have electric but will in the future.
Emmisions haven't gone anywhere, it's pretty well wrapped into alot of the things so just disabling by parameters is the best choice for now. I just removed all of mine last month.
The code is bouncing back and forth as we speak and has gotten a little off the "stock" setup but its for the better
I was trying to keep a full stock version but it gets more difficult to maintain different files. Hopefully I can re-sync the stock file with all of the commenting that has changed. Its just time.
Scott bumped me tonight and I am still sitting here sorting addresses like a fool Wanted to finish some changes I found before I go onto porting my second head tomorrow.

 

So that's what you've been doing.
I figured 1M worth of zip files would keep you busy with the diff software......

I've made a lot of the mods bit selectable so that you can use stock or the mod.

Darn it, just remembered one I forgot to do.

Hopefully someone will enlighten me on my CCR/ IAC post.

Even though I have one of those old fashioned fans.
I never thought about loosing the ecm control of it.
I don't really like using Fan2 either.

The light bulb went on for some dry n2o stuff today though.

 

My theme for the XDF using the categories and levels.

Categories (Already done for the most part)
1 SETUP std changes to a new bin, inj const, cyl etc
2 FUEL VE, etc
3 SPARK SA and parameters
4 EMMISSIONS EGR, CCP, AIR stuff
5 C.L. BLM / o2 All parameters for closed loop controls
6 ERROR CODES All error codes selections and parameters
7 P.E. Power enrichment items
8 OPTIONAL MODES Highway mode, Low Octane, Stall saver etc
9 SHIFT LIGHT / TCC Adjustments for these
10 KNOCK Items for knock only (also in Spark)
11 MAP / BARO Pressure functions
12 AUX FUNCTION Fans, A/C, oil pressure, etc
13 STARTUP Items concerning cold starts etc
14 IDLE Items used for idle control
15 D.E. / D.F.C.O. Parameters for Decell
16 WIDEBAND Selection/setup for WB
17 IAC All parameters for controls
18 A.E. Accel Enrichment Items
19 OPEN LOOP OL Adjustments
20 PARAMETER Sub-Catergory for filtering out adjustments (not showing selection items)
The "Show up to" can then be used to remove items from the screen (like setup stuff)
Just set to "show only up to" level 9. Works neato !

I have to do the "Levels", the rest is already been categorized.
Need to do a little more checking on how to make the items show properly in TP.
The double selection is nice but can make things confusing if instruction is not provided with the file.
I'll write something up in the header to do that.
Jp

 

JP you beat me to it. So far I have done some catagories but have not incorporated all of your hac. I do want to include some of the tranny stuff you found but I don't know if it is being used. So far my Catagories are something like this:

Complete
Spark
IAC/Idle
DFCO
BLM
Acceleration Enrichment
Power Enrichment
Emissions
Highway Mode
WBO2
Transmission
Fuel

I keep forgetting to use any of it though. I guess I am too familiar with the XDF so I just go to where I want to. I didn't think about the levels so my order is messed up. I don't think there is a need to get real fancy here as the filtering leaves enough out to easily get to what you want. I was also looking into the sub catagories but it may be overkill again. It would be nice if you could name the Levels so you know what it is. I also have your ADS file modified to look more like Marks OTB setup that I am still modifing as I go. Mansur asked if he could modify what I sent and post it so it should be out there with my XDF. I told him to give you the credit. Now that you can do the catagorization I guess I need to look into merging all the additional stuff from your hac.

 

Biggest headache I have right now between the XDF and the ADS is knowing what WASN'T right.
A few changes have been made by people who got it previously but havn't really gotten any feedback what to correct.

I wanted to get a post up of all the files with a common version and then get feedback to correct things. As more feature creep gets added, the worse the base file gets (mine anyway).
One thing I need to reconfirm is that the reassembly of the relocatable code has not shifted anything
I don't believe it has but it is better to check.

I still have my original "Full" XDF file but haven't included the S_AUJP stuff that you had in the shortened one.
Some things were changed/fixed but I have no way of doing a direct compare on them.
Might be easier for you to start with my XDF file again and add?
Don't have a clue right now.
Need to look at what SL sent me.

I guess I'm in a giving mood this Christmas

 

John what I did was take your def file and remove everything that I had defined already based on the location. I have a shortened version of yours that I don't have in Super_8d. The latest includes the Z69 ext VE table and the WBO2 stuff. I will send you both copies so we can go from there. I sent Mansur a copy of what I have currently. It is easier for me to take what I know have then add yours as opposed to the other way around. The idea was to

 

Categorizing the XDF and all the other stuff you guys are talking about sounds REALLY GREAT!!!

I can hardly wait.... but I will! lOL

 

Saw a note about disabling Fan outputs above a set speed.
Shouldn't be too difficult to do.
Add to the list.

Got knock light stuff on the run, just needs tested to be sure the output works as it is supposed to.

XDF went on hold until I can do some serious testing and determine what works and doesn't. Comparing the files is too time consuming without a running car to verify readings are reletively working.

Going back over the segment table and looking for ways to make a "bypass emmisions" flag for those who don't run the equipment.
That's not looking easy at the moment, but still worth a try.
Once they are all bypassed, the hardware can be used for other "selectable" things.

 

Now that "we" have te WB and shift light stuff working, when should I expect to test the KL?

One other "wish list item": Some way to have the shift light NOT come on when you're already is your top gear (whatever it is). Maybe have a constant to set the max speed the shift light can come on? Maybe something tied into the NV ratio?

 

Sent it over to Z' last night, I don't have the fixed code for the MT version to put it into.
Also have Ryan.H doing a quick test in a stock auto bin to confirm it works tomorrow.
Shouldn't be long now on that.

 

Been looking at some of the newer bins and I have a suggestion for a improvement. There are 2 tables for Open Loop. They are for Map and temp. They act like the PE tables combined when in PE mode if memory serves me right. The newer bins combine these tables into one table to be a Map Vs. Temp. This gives a simple lookup value for the code and allows better control for Open Loop AFR ratios. It is most noticable if you look at any of the newer bins the AFR's become extreme at the ends of the MAP spectrum that the 2 individual tables cannot account for. What you end up with is compromising the tables to get a good AFR fit for most of the spectrum instead of just changing a value. This would be a huge improvement for users that want to run open loop all the time. I am not there yet but I am thinking of running Open Loop after I get my tune where I want it to be.

 

I was thinking that the opposite would be true but I guess not.
How to get the "right" value for temp to correllate to the "right" value for MAP?
The middle would seem to be incorrect unless you fudge on the temp or map values. Seems like most here use one or the other for most of the tuning and then tweak the other.
Anyone care to take a stab at the table size and the values?

 

That's easy. Just take the 2 tables and make one lookup table. Typically 20-100kPa in 5kPa increments and the standard coolant temp -40 to 152C in 12 degree increments. Should help for tuning especially when cold and be a good improvement for those running or planning to run open loop. I figured this would be a easy mod. Put in the table and look up the cell -but what do I know about programming.

 

There are two OL map tables and one OL temp table.
For map you have Hiway mode and OL afr vs map.
Not sure if Hiway uses the temp table too.

 

The LT1 bins do not have that of course but they do have something else 2 similiar tables AFR Vs. Temp at WOT and AFR Vs. RPM at WOT. I guess that means it uses those tables separately in PE mode. It would be interesting to check and see the code. I thought that there was one commanded Highway Mode constant and it did not go into the mode unless it was CL anyway. Actually having both tables would be beneficial if running OL all the time. I am going to entertain that after I get my tune in line.

 

8D PE has 2 seperate tables- not the OL ones
8D OL has a map table and a Temp table.
8D Hiway mode has a map table and I've yet to verifiy it uses the OL temp table. Lots of Branches in that area of code and I was too tired last night to follow it.

That's 5 different tables.

 

Yea sorry I jumped the gun. The AFR vs ... @ WOT is of course PE which is the same. I did just assumed that the Open Loop tables acted just like the PE tables for calculation of the final AFR. Only difference is the Open Loop uses a single lookup table -again more control in Open loop and easier to tune. Plug in the value at the proper location.

 

I think it would be really nice to be able to datalog a WB O2 sensor on each bank of the exhaust. That and the knock sensor light would be great. Should hold us over until the auto tune software becomes available anyway LOL