SCT Datalogging issues PLEASE POST - Page 6

Blivit · 02-02-2010, 08:26 AM

Quote:

Originally Posted by 1turbofocus

Blivit , I have been going live with the customers PC because there telling me the PID I request are not there
I have played around with 6.1 with it hooked to PC hooked to xcal3 then to Focus and there are a few labled wrong and some not there or labled wrong and I am just missing them
One is knock retard , Its named knock retard limit but I beleive is knock retard (jfa8)

There were others engine temp I get in the 7 to 800 range , I believe its there just labled wrong

Makes it very hard to find this stuff im sure you understand

Tom

The knock retard was pointed out earlier in this thread.

Are these others pid's or DMR's?

Blivit · 02-02-2010, 08:27 AM

Quote:

Originally Posted by 1turbofocus

I have a customer that will be calling in today that we have been remote tuning that had this same issue , Nothing has been changed and we have loaded many tunes issue free , now it wont load my tunes and I was on line with him and it "just happened" out of the blue , No new programs installed just loading tunes and datalogging

Tom

Which SCT programs does this customer have installed and what operating system is on their PC?

At what point did the error start happening? Were other SCT programs open at the same time?

Also, with any of these customers, what antivirus program are they running? We recently discovered that Mcafee and AVG started flagging certain SCT files as being trojan files (which they are not.) We contacted them and they have since updated their definitions files so that this doesn't happen in the future but if the customers are running these programs and haven't updated that may be the cause.

***1turbofocus*** · 02-02-2010, 08:50 AM

He did have the LL3 open and he has W7

I am not sure of the antivirus but will ask , I am sure the tech will ask him these things when he calls in this AM

He had loaded the tunes about 8 to 10 times issue free , then yesterday it wouldnt load the tune to the xcal

I will post the rest of the info you requested when he gets back to me

Tom

***1turbofocus*** · 02-02-2010, 08:57 AM

Quote:

Originally Posted by Blivit

The knock retard was pointed out earlier in this thread.

Are these others pid's or DMR's?

It was about 10:00 last night from what I remember I could not find them in either upper or lower case labeled correctly

I got a datalog yesterday with K (small square box) N (small square box) S (small square box) all the PID in the listings had the (small square box) between each letter and it wouldnt datalog , Tech Kris got the datalog its the second time I have seen this happen and another datalog with tune I had serious issues with was sent to him

Maybe you can take a look and see whats going on with those

Tom

Tom

FordManSVT · 02-02-2010, 12:12 PM

I got the tune loaded on the SF3 at work this morning. So i am sure its something with the drivers on my laptop at home. I will recheck the drivers when i get home. I think i am using norton anitvirus, it may have run out. I dont think i changed anything before i tried to load the tune. I updated adobe reader, thats all i can think of. Ill see if livelink works tonight.

BradWhite · 02-02-2010, 12:37 PM

My issue is not being able to log my A/F ratio from my AutoMeter Ultra-Light Air/Fuel Monitor on my 08'. I did work with Blivit some months ago on this and we weren't able to figure out why.

I will post the rest of the details for version #'s etc later today, at work now.

I would like to SCT for sticking in here with us and working on these issues. You guys are great!

FordManSVT · 02-02-2010, 12:56 PM

I am using a autometer wideband A/F and can log it. Do you have a firewire cable wired to the output from the gauge? you also have to use an analog equation, which is 10+(1.5*v).

Blivit · 02-02-2010, 12:57 PM

Quote:

Originally Posted by BradWhite

My issue is not being able to log my A/F ratio from my AutoMeter Ultra-Light Air/Fuel Monitor on my 08'. I did work with Blivit some months ago on this and we weren't able to figure out why.

This should be working now. The problem is, you have to create your own datalog file then load that to the device. Once that is done, you will add the analog ON THE DEVICE (when it asks you to configure analogs.)