OpenPort 2.0 + Chrome logging without laptop

[striker2]

I have a 93 with a 99 SL ECU and adapter harness. no CEL or ABS light when the tactrix is plugged into the OBD2 port that came with the adapter harness, either stand alone logging or via USB

[mjannusch]

I suspect that only '94 and later cars with the built-in fully populated OBD2 type port would have the ABS light problem, since the earlier cars will have a OBD2 plug with only the pins for ECU access and not the ABS diagnostic pin. Just guessing there, but it seems to make sense.

Either way, removing the setpin line from the logcfg.txt should make sure you don't see an ABS light and should work fine on any year car.

[Jimvr4]

I've been using this method for logging and one question I have is how does it know the injector scaling for the IPW and IDC% calculations?

[Chris@Rvengeperformance]

I've been using this method for logging and one question I have is how does it know the injector scaling for the IPW and IDC% calculations?

the size doesnt matter. ipw is just the number of ms the injectors are open and idc is a percentage, so the flow is not considered.

[mjannusch]

Right, the formula basically looks at how many ms the injector is open out of the number of ms available at the current crank RPM rate and results in a percentage. Note that when logging, all these values aren't "snapshotted" at the exact same time and stored for retrieval - they are updated at various times and as the logger routine makes a pass over the data it captures whatever is in those memory cells. So sometimes you may see IDC % fluctuate a bit or have values over 100% which don't make sense. Look at it more over several samples to get a general idea of where your IDCs are, not at single samples. That would likely be the case for any value that's calculated off multiple parameters.

[Jimvr4]

So what you're both saying is IPW is just the pulse width in milliseconds.

When using Evoscan on the Netbook I get 7.6ms IPW and 22% IDC for a TPS of 52% and RPM of 3343. At warm idle I get 1.5-1.8ms IPW

On the Tactrix standalone I get 33ms IPW and 92% IDC for a TPS of 54% and RPM of 3343. At warm idle I get 7ms IPW

Both use 0.256 * x for the IPW scaling so I don't see how they get different results. The only thing different I can think of is the injector scaling for Evoscan logging. I have 600 in there.

[mjannusch]

The injector scaling *shouldn't* come into play... Looking at the Evoscan formula and what's in logcfg.txt it should result in the same values, unless somehow my RPN in the logcfg.txt is incorrect. I don't see how, but it isn't like I write RPN formulas on a regular basis. I dunno! Strange. I'd certainly like to find an answer as to why the results are different.

[Greg E]

So what you're both saying is IPW is just the pulse width in milliseconds.

When using Evoscan on the Netbook I get 7.6ms IPW and 22% IDC for a TPS of 52% and RPM of 3343. At warm idle I get 1.5-1.8ms IPW

On the Tactrix standalone I get 33ms IPW and 92% IDC for a TPS of 54% and RPM of 3343. At warm idle I get 7ms IPW

Both use 0.256 * x for the IPW scaling so I don't see how they get different results. The only thing different I can think of is the injector scaling for Evoscan logging. I have 600 in there.

Double check to see if both are reading the same request. I can't remember off the top of my head which request its supposed to be.

IPW has Injector scaling factored into it because that calculation is done within the ECU.

[Jimvr4]

Both are using request 2B for the front IPW and 29 for the rear IPW

[Chris@Rvengeperformance]

Double check to see if both are reading the same request. I can't remember off the top of my head which request its supposed to be.

IPW has Injector scaling factored into it because that calculation is done within the ECU.

IPW is influenced by injector scaling, but the reporting of it should not be. Whether you have 1000cc injectors or 550s the logger should still see 2 ms or whatever the ecu is commanding and not need to scale it.