I've had my Troyer tunes for about 2 1/2 months now but haven't had the chance to datalog. I don't have a laptop I can easily utilize for this task.

I understand by reading the sctflash.com website that the new software for the XCal2 enables a person to datalog without a laptop--by utilizing the built-in memory in the device. However the site indicates that only the last 90 seconds of any logging will be recorded for download to a PC.

Question: is it practical to datalog this way? Does 90 seconds provide enough time to make the proper number of dyno pulls? It would not be practical to run back and forth between the dyno and my computer to download the data between pulls so I would have to store all the pull data within that 90 second window.

Does anyone know if 90 seconds is adequate for 3 (IIRC) pulls?

 

Not that I have been to a dyno but, it was my impression that the dyno readout you get when you are finished has all the info you need.Wouldn't you tell the shop that you need A/f readings posted in the readout, or tell them that you are there to check a series of tunes you have and need to datalog everything involved.Then you would scan the readout and e-mail it back to Troyer Performence to be read and see if any adj.need to be made.This is how I would think it is done.

 

You could do it that way , but you would have to download the data between runs into a computer of some sort. The dyno shop may let you use one of thiers and then move the data to a cd or usb key or something. You would have to do this even if you only used 30 seconds for each run as you would have to name the files to be usefull. maybe you could bring your home computer to the dyno shop and they would let you set it up somewhere. I hope this helped.

 

Thanks for the input, guys. Doesn't sound like a practical alternative for me.

Looks like I need a plan B (anyone have a laptop they don't need, that runs WinXP? )

 

Out of curiosity,are you using a Dyno in the Rochester area? Been trying to find someone locally that has a dyno and does trucks.

And if you did, any idea who and what they are charging?

 

I haven't got that far. I have done a search of Dynojet operators and the closest one to me seemed to be in the Buffalo area. I also did a search of Mustang dyno operators (Mike says they are not preferred but will work) and there is one in Webster. I have no idea if they do trucks:

Dynamx, Inc.
750 Basket Rd.
Webster, NY 14580
(585) 671-7047

I haven't talked with them or visited them. Try giving them a call. I believe with the Mustang dynos you need to get the tabular printouts in color and fax them in color to Troyer.

 

Hi BJB,

Yes, you can *easily* do that with the 90 seconds of on-board datalogging!

Remember, a dyno pull only takes maybe 8-20 seconds start to finish once the vehicle is up to normal operating temperature!

So what you can do is simply download the file to the dyno's PC after each run, and then have them give you those files on a floppy when you're done - they should be happy to do that for you. Of those, this is assuming you do not have a laptop handy.

Another thought - with the latest changes to Live Link, you no longer need a laptop capable of 200 ms response times, so you can use an older P3 used machine that you can pick up for a coupla hundred dollars, for example - we have a lot of customers doing that - all it needs to be capable of is running Windows XP (any version), so any laptop with say, 256 Mb RAM will do the trick. they increased that feedback response time form 200 ms, which really required a newer & more powerful laptop to accomplish (my P3 800 did it no problem), to 2 *seconds*, which any machine can do, basically.

At any rate, this should easily be doable for you.

 

Thanks for the info, Mike.

I might try the on-device route if I can work it out with the dyno operator.

 

Hi Mike;

With reference to your comment about the latest version of LiveLink (with response time issues fixed), were you referring to 2.3 (build 6) ?

Are you still recommending LiveLink v2.18 for passthrough usage?

FYI - LiveLink 3.0 (build 5) is in Beta for selected users - not many details or ETA from SCT for now, but it's supposed to address several concerns seen to date, among them the abbreviated datalogging problem some are having.

Cheers

 

Hi Vic,

2.36 enables the on-device datalogging.

We have all of the 3.0+ BETA versions of course, and were probably the first to get a couple of them, but have not even had time to put it thru it's paces, due to the moving of the shop during this past week, etc.

Version 2.38 was the first that has that change made to it regarding the response time issue that I was talking about, it going from 200 ms to 2 seconds. And that time limitation is something that affects old low-powered laptops, and a few off-brand units, basically - there is no time limitation with a "modern" laptop that has any real power and is running XP.

The bottom line is, anyone who is having a problem can simply call SCT and they will send out a later version for the user to work with.

We are still using 2.18, as it works and does what we need it to do reliably, as we don't do on-device datalogging of course, we use a high-end laptop.

So it's doable to datalog on-device with it's 90 seconds of time, you just want to dump it's file between each pull - which anyone can do by just dumping it on a PC at the dyno facility. the USB drivers are a simple download, and won't affect anything else negatively. Then they can simply give the owner a floppy with their datalog files & it's easily handled that way, too.

 

Thanks for the reply Mike.

SCT kindly provided me with v2.3.8 upon request. They declined to provide the v3 Beta, and I can understand their reasoning on that.

I will be completing the datalogging next week - just been practicing/playing with the tools and software - y'know, the 'inveterate tinkering syndrome' you are so familiar with .

I just trying to decide at this point whether or not to try capturing the LM-1 wideband analog out data on the X2, or just provide the separate log file out of Logworks in *.DIF and then dumping that into the Excel spreadsheet...

To be sure, you were absolutely right - this is fun stuff !!!
And, your docs are outstanding!

Cheers