Error $5 (analog wideband logging)

[rumblebox]

I can't log any data after altering calc.pids to use an analog WBO2 for CALC.VET.


http://i17.photobucket.com/albums/b53/rumblebox/BB51BA1A-2014-45D3-BA9F-2F1D5C83EE00-17342-0000078A65B345B0.jpg

Also my CALC.SELBEN pid wont work, because it says i need to select CALC.PE, which i can't find.

[joecar]

What is your V8 build version...?

What is your V2 firmware version...?

Did you program the BBx config into V2...?

[joecar]

On the PIDs tab, if you click the column title heading "Caption", and then click it again, the pids are sorted alphabetically on this column, so you can then scroll down until you see the pid.

[joecar]

BTW: you can also grab a screenshot by pressing the PRTSCR button on your keyboard, then opening Paint and pasting and saving to file.

[mr.prick]

Please post your calc_pids.txt

[joecar]

BTW: CALC.PE was replaced with CALC.CL in the calc.vet tutorial/thread a while back.

[rumblebox]

BTW: you can also grab a screenshot by pressing the PRTSCR button on your keyboard, then opening Paint and pasting and saving to file.

I know, but i didnt have wifi at the time.

[rumblebox]

I'll post all this tomorrow.

[rumblebox]

i've been pretty de-motivated to do anything to the car lately. it seems like i take one step forward and three steps backward regarding software/WB, etc.


attached is my calc.pids.txt

[joecar]

Have you does this:


What is your V8 build version...?

What is your V2 firmware version...?

Did you program the BBx config into V2...?

more info: Setting-up-a-FSV2-from-scratch (http://forum.efilive.com/showthread.php?20699-Setting-up-a-FSV2-from-scratch)


Yes, use that calc_pids.txt, and follow the Calc.VET thread (is this your intent...?).


Don't be discouraged... it simply is a matter of the learning curve.

[rumblebox]

Have you does this:



more info: Setting-up-a-FSV2-from-scratch (http://forum.efilive.com/showthread.php?20699-Setting-up-a-FSV2-from-scratch)


Yes, use that calc_pids.txt, and follow the Calc.VET thread (is this your intent...?).


Don't be discouraged... it simply is a matter of the learning curve.

Version: 8.2.1 Build 203

firmware is 2.07.35

yes but with analog, since i never got my serial to work.

[joecar]

Which analog wideband...?

in that calc_pids.txt you will have to modify (using Notepad) CLC-00-110 to read as follows (using LC-1 as example):



*CLC-00-110
factor 0.5 1.5 .4 "{GM.EQIVRATIO}*{CALC.AFR_LC11}/14.7"

[rumblebox]

i did that and it still wont record.

http://i17.photobucket.com/albums/b53/rumblebox/screen1_zpsa589659d.jpg

http://i17.photobucket.com/albums/b53/rumblebox/error1_zps54aaa988.png

http://i17.photobucket.com/albums/b53/rumblebox/screen2_zps3e4c3c15.jpg

[joecar]

Those screens indicate that dditionally you need to select the mentioned pids in the More Info boxes (CALC.PE in screen 1, CALC.DAT in screen 3).

Temporarily, disconnect the wideband's analog cable from V2 and see if the error in screen 2 goes away.


Also, mention of CALC.PE tells me you have the older calc_pids.txt file (since the newer file changed this to CALC.CL).

[joecar]

Which wideband do you have...?

Were you not able to get it connecting with serial comms...?

[Blacky]

I can't log any data after altering calc.pids to use an analog WBO2 for CALC.VET.

Please see this thread.
http://forum.efilive.com/showthread.php?20725-Scan-Tool-Error&highlight=loopback

Because you are using the analog/external PIDs and deselecting them is not an option, you will need to create a loopback link for AD1 to force the A/D counts for AD1 to be zero.
Then you'll need to hook up the wideband to AD2, and use the AD2 PIDs for wideband logging.

It is fixed in the next update. That update was due out earlier this week but some last minute problems appeared in final testing and they are still being fixed.
It may be another week before it is ready.

Regards
Paul

[rumblebox]

Which wideband do you have...?

Were you not able to get it connecting with serial comms...?

LC-1. i never got it to work serially. and i can't get the BBX to read the analog either. i only see it on the scan tool (before it stopped working completely)

[rumblebox]

Please see this thread.
http://forum.efilive.com/showthread.php?20725-Scan-Tool-Error&highlight=loopback

Because you are using the analog/external PIDs and deselecting them is not an option, you will need to create a loopback link for AD1 to force the A/D counts for AD1 to be zero.
Then you'll need to hook up the wideband to AD2, and use the AD2 PIDs for wideband logging.

It is fixed in the next update. That update was due out earlier this week but some last minute problems appeared in final testing and they are still being fixed.
It may be another week before it is ready.

Regards
Paul

ok i'll try this.

[joecar]

Related threads:

Scan-Tool-Error (http://forum.efilive.com/showthread.php?20725-Scan-Tool-Error)
Logging-issues-with-NGK-AFX&p=184367#post184367 (http://forum.efilive.com/showthread.php?21381-Logging-issues-with-NGK-AFX&p=184367#post184367)

[joecar]

Hi rumblebox,

I took the liberty of renaming this thread.

[rumblebox]

update: i finally got motivated to hook it up again. i disconnected the LC-1(analog), and the scan tool WILL log now. i also found all my orange analog connectors so i can jump A1+ and A1- together and use A2 for the LC-1. it's been a while, so i'm figuring out how to re-configure all my PID's to use the calc.vet with analog. i wish there was a separate calc.vet tutorial strictly for V2 analog users to alleviate confusion.

[joecar]

Pre-Release 06 software/firmware fixes the analog logging problem.


The Calc.VET thread (post #1) shows you how to setup for analog wideband...

for the LC-1, in the calc_pids.txt file, edit CLC-00-110 to read "{GM.EQIVRATIO}*{CALC.AFR_LC11}/14.7".




. . .
II. ANALOG WIDEBAND AND/OR V1 USERS

There are two methods of obtaining analog lambda which are identically the same thing. The first method has the user pre-calculate two constants (i.e. the user pre-calculates this: AFR pid divided by stoich AFR); it evaluates in one step (it evaluates lambda directly in one calculation). The second method evaluates two steps (it evaluates the AFR pid first, then divides it by stoich AFR to obtain lambda).

Method 1:
. . .

Method 2:
Using LC-1 as example:
. . .

You could also reduce those two pids into a single pid:
Define CALC.WO2BEN1 (CLC-00-110) to be {GM.EQIVRATIO}*({CALC.AFR_LC11}/14.7)

. . .

[LSxPwrdZ]

Bringing this back up, I am having trouble logging the AD1-4 in the scan tool. I have verified voltage from my NGK on the V2's display to read the correct voltage however the voltage does not show in the scan tool when logging. The Voltage in the scan tool is showing 66.xx V for all 4 AD inputs.

[joecar]

Bringing this back up, I am having trouble logging the AD1-4 in the scan tool. I have verified voltage from my NGK on the V2's display to read the correct voltage however the voltage does not show in the scan tool when logging. The Voltage in the scan tool is showing 66.xx V for all 4 AD inputs.Hi James,

Which V2 firmware version do you have in your V2...?


I pm'd Paul.

[LSxPwrdZ]

I will have to check, I did check for updates and it said I had the latest version as of last night. What's weird is it was scanning and working fine a few days ago. The only thing I didn't try is restarting my computer to see if that was the issue.

[LSxPwrdZ]

I'm not getting any error while logging, its just logging 66.xx V for any of the AD1-4. I've confirmed the calibration on the V2 itself and on its display shows the correct voltage when scanning the AD1-4 PIDs.

I am running Firmware 2.07.45 and Boot Block 2.07.05

***EDIT***
Just wanted to give a little update. Seems rebooting all programs and disconnecting all cables and restarting everything solved the issue. It is now logging voltage normally.