CKREF PID For LS1B in v7.5

[mk13]

Hi,

When I log the CKREF PID (Time Between Crank reference Pulses) on my V2 using BBL, I can see the data fine on the V2, but when I load the file into v7.5 Scan tool, I am unable to view that PID by selecting it as a parameter on the dashboard, presumably due to in the PID list it lists it as unitless, clearly it has units of time (mS) though.

How / what config file, do I change to enable using this PID in the Scan tool?

Thanks,
Marcus

[joecar]

Hey Marcus,

Can you post your log file here.

[mk13]

13457

OK, I think I have attached a log from today.

Not much to show except that you can't see the data for the CKREF PID in the scan tool v7.5.

Out of interest, I am trying to diagnose an intermitent glitch with my car ('03 SS Commodore, manual) that has gradually gotten worse over the last month or so.
The symptom is a short sudden hesitation in drive, sometimes even quite jerky through the drivetrain. I was hoping to get some indication as to what the issue was. My current theory points to perhaps a crank angle sensor on the way out.
I know they were a typical issue for the old V6s we had in Aus for years, but have no indication if it is a common problem, or a problem at all for LS1s.

In the log file there is some apparent disruptions to spark, and most times Injector pulse width, at random times through the log.
A good example of what is happening is in the sequence from frames 23700 to 23800. The disruption to fuel is also noticable in the WBO2 data.

I wonder if the nice oscilations on the RPM (when viewed on a scale of 2000-2500) is a good indication of the impulse response of a filter on the crank angle sensor input, to generate a smoothed rpm value.

Anyway, I'd just really like to be able to view the crank angle data, which was providing real time values in mSecs on the live display on my V2 unit while driving.

Any help would be much appreciated.

Thanks, Marcus

[mk13]

Hi All,

Was really hoping someone might be able to shed some light on why I am unable to select the CKREF parameter and view it on a dashboard plot in the V7.5 Scantool.
And forgot to mention that I am using the latest versions of everything (Builds 211/203).

It's a bit useless being able to log the data for a parameter if there is no way to view it.

Is this forum section often visited by the EFILive developers, or do I need to post it somewhere else?
I also posted a question for support on the knowledgebase page, but have received no reply.

Cheers, Marcus

[joecar]

Hi Marcus,

Can you see that pid logging on the V2 LCD...?

[joecar]

I don't see that pid in your log file either... I pm'd Tech Support.

[mk13]

Yes I can see the values while logging on the V2. For example at idle i think it was reading somewhere in the 15 - 20 mSecs and at highway cruise about 8 mSec (values are approximate, can't exactly remember.)
With the file in the scan tool, the PID shows as selected in the PID list tab, but doesn't appear in the data tab, or selectable in a dashboard page.

In the PID list, it indicates that there are no units for that PID.

[Blacky]

Sorry, its a bug in the PID definition for V7 for CKREF. The units specified for the PID (ms) are not defined for the scaling for that PID.
It will be fixed in the next release.

Meanwhile, if you want to "fix" it temporarily until the new release is out, you can modify the scaling for that PID and add in the ms units like this:
Edit the file called \Program Files\EFILive\V7.5\Configuration\sae_generic.txt (use notepad).
Find this data:

*UNM-16-41
s 0.0 65535.0 .0 * 1.0 0.0
km 0.0 65535.0 .0 * 1.0 0.0
mile 0.0 40722.0 .0 / 1.60934 0.0
s 0.0 65535.0 .0 * 1.0 0.0
min 0.0 65535.0 .0 * 1.0 0.0
step 0.0 310.0 .0 * 1.0 0.0
count 0.0 65535.0 .0 * 1.0 0.0

and change the second "s" units to "ms" like this:


*UNM-16-41
s 0.0 65535.0 .0 * 1.0 0.0
km 0.0 65535.0 .0 * 1.0 0.0
mile 0.0 40722.0 .0 / 1.60934 0.0
ms 0.0 65535.0 .0 * 1.0 0.0
min 0.0 65535.0 .0 * 1.0 0.0
step 0.0 310.0 .0 * 1.0 0.0
count 0.0 65535.0 .0 * 1.0 0.0


Regards
Paul

[mk13]

Hi Paul,

This has exactly fixed the issue. I can now see the data no probs.

Thanks very much,
Marcus