I've been going through the open loop threshold subroutines for the last day or so. One interesting tidbit I found is that if anyone wants to force full time open loop, set Periphery0 bit4 = 0. The car will be in open loop 100% of the time regardless of the values open loop load and open loop TPS tables.

 

Thank you mrfred, table updated.
That should be useful for testing stuff.

 

um, can I get a ruling on what Periphery0, bit 06 & bit 07 do?
I think my def is a bit muddeled here.

 

I haven't come across their purpose yet.

 

Great find, will you update "periphery bits" thread?

 

Is the ECU powerful (fast) enough to run open loop at high RPM? and if not, what happens? does it just shut off?

 

I think you mixed up open and closed loop.

Yep. :-)

 

is that in FAA ?

 

Yep.

 

cheers

 

Better name would be

Closed loop supported
or
Enable Closed loop bit.

I am curious about bit3 thou as this one has also flag at F3B.

Offtopic: Another thingy is @100A which looks like OBD keyword and is indexed like periphery bits and main maps.

 

Yes, in my periphery table that I have for the updated xmls that I'm working on, I call it, "Allow Closed Loop".

Not sure what you mean by a flag a F3B. I don't see anything at that location in my 88590015 ROM.

Yes, @100A appears to be a set of bits for OBD.

 

True it is not in 88590015, sorry I have not double checked with 88590015, so it seems it is not universal.

 

Ive been changing all mine to:
0 = Disable XXXXXX
As we mostly seem to be interested in switching off problem functions or fault flags.

 

Openloop without CEL?