I don't know what I did but I have not been able to undo it!
Using Windows XP and TunerPro RT when I am connected to my ecm (sd 730) and I have the page displayed with all the info. int, blm, O2, ect. on my laptop there is a huge time lag from when it happens on the engine and when it is displayed on my laptop. If I push the throttle the tps display (and everything else) might take 10 seconds to 'catch up' to what is actually happening!
Anyone else run into this? What do I need to do to correct this? It worked fine before but I don't know what I did to screw it up? Com port settings?
I am also connected to the Ostrich, I will try a chip in place of it and see if it works differently.

 

I'm running the exact same CPU and Ostrich, and mine works fine with an ALDL serial cable on my Dell Latitude D600 laptop and the Ostrich plugged into the USB port.

Did you use the latest USB drivers from Craig's site? That could be the problem if you're running the default XP drivers. He's got the directions and settings for the port as well.

 

I had it working fine just recently, but I can't figure out what happened? I disconnected the Ostrich and ran a chip and have the same problem.
My packet error counts go crazy when I hit the record button, and playback is unusable.
I have the Moates USB driver installed for the ostrich and I can upload bins fine, but the data should be on the serial port at com 1. Yes?

 

It is on mine.

Here's my COM1 port set up:
9600 baud
8 bit
no parity
1 stop bit
flow control = NONE
IRQ=04
The "Use FIFO buffers" is checked
and the Receive and Transmit bbuffers are set to the maximum on the slider

Hope this helps!

 

Checked the com port settings, they are fine. Maybe I have a problem with my cable. I tried the cable test using TunerPro and it said could not find cable.
Have you ever used this test? Could you try it next time you are data logging? It's under Tools/Pref/Aldl, let me know what it does, thanks!

 

May be a few days before I can do that - got the motor apart right now. Pulled the intake all the way down to the heads looking for the source of the extra air the left bank of the motor appeared to be getting.... and I think I've found it (or at least I found one, anyway).

 

try changing the target sample rate from 10Hz to 8Hz

 

Also set the port configuration "Latency time" to 1.
Not sure what that does but didn't see a note to that effect in other posts.

 

Both Monte and JP86SS have good suggestions. Regarding the other port settings (FIFO, baud, etc), no need to worry about those. TunerPro sets those settings programmatically as-needed.

Do set the latency timer to 1, and try a slower sample rate.

I'm not sure why hitting the record button would make the error count rise, provided you've specified an accessable file to record to first.

 

This is one of the symptoms I have experienced. Even with a lot of testing I still have not found the real culpret nor was it consistent. Uninstalling and then reinstalling the FDTI drivers and TP seemed to help along with changing the log rate to 10MHz seemed to really help with the flakeyness. I have not tried a real long log though.

 

You should never have to uninstall/reinstall TP. Doing so only replaces the binaries (and if TP runs at all, the binaries are intact). You can achieve an "initialization" of TP by simply deleting tunerprosettings.dat from the install directory.

 

I am using Windows XP and as far as setting the Latency to 1 I can't seem to find that under com port setings or usb in the hardware setup. All the other settings I found, I will try the 8 Hz setting in TP.
I have no problems with it on a 165 MAF, but even when it's working fine the cable test in TP does not reconize the cable, go figure?
As far as the record button goes I was mistaken, Actually any time I am connected and I bring up the screen with the record settings on it the packet error counts just start from zero and count rapidily upward!
The four screens used for viewing data, are basically useless, and if I try to record the playback is also useless. I can't imagine what the heck I did but it's got to be some setting parameter I changed.
Does the checksum have anything to do with this problem?

 

Heh. So you can't view data, you can't record, and you say the packet error counts are always rising. Where, then, does the statement, "even when it's working" come from?

It could very well be a cable problem, or just a settings issue. What COM port is the cable installed under?

 

I have no problems when it's connected to a 165 ecm, only the 730 (727).
I figured out the Latency setting, the Ostrich has to be connected to access that page in device manager. But, does this have anything to do with data logging if the Ostrich is NOT connected? I have problems either way.
I will try it with the new settings shortly.
When I am connected to the 165 and it's working fine if I use the cable test button it tells me cable not found, or something to that effect? Same tihing on the 730.

 

My serial cable is on com port 1 and the usb is com port 4.

 

Get the build here:

Index of /beta/Builds

That will fix the "cable not found issue".

It will not fix the 727 issue. Becuase it's a 727, I'm imagining this is a vette, probably 90 or 91, with a digital dash? If so, the CCM keeps TunerPro from connecting. That would explain the error counts. This will be fixed in Version 5 due out later this year.

 

You are correct it is a 90 vette. But it worked fine for the last year or so up until a week ago? The only problems I noticed before this was the ccm would flash 'sys' on the display, But it still worked.

 

That is strange. You might have gotten lucky in connecting (in getting a packet in at the right timing to shut the CCM up). Something you can try: when you connect and you see the error count rising, manually send a mode 8 command (it should be defined in the ADS already). Just select it in the command list and hit send a bunch of times until you see the count stop rising. That might work, although it's a pain.

 

Mode 8 command? Is this the 8 hz settig referred to earlier? I couldn't have been lucky for the past year or so only to have my luck run out now! After I just got my Ostrich working!

 

I am looking at the TP now and I see Mode 1 ALDL Dump Request in the commands quick send, with Clear trouble codes

 

No, not that. And having just looked, it isn't in the ADS that ships with TunerPro. To add it, follow these steps:

1) Open TunerPro
2) Hit F4 to bring up the ALDL setup window
3) Load the ADS (if not already loaded)
4) Click "Edit ALDL datastream definition"
5) ALDL Definition header should already be selected in the tree view
6) under commands, click "new command"
7) Set the command string to "F4, 56, 08"
8) ensure "checksum cmd" is checked, but that master and monitor are unchecked.
9) Set payload size to 0 and payload offset to 0
10) Click Save Changes and Close.

Now the Mode 8 command is in the command list in the ALDL setup window. When you see the error counts rising, send that command manually (by selecting it in the list an hitting send) quickly until you see the counts stop rising. Let's hope that works.

 

Sorry, just looked out the window and my dog is chasing the school bus down the road!
O.K. I have it setup and I am off to the garage!
So, I have been just 'lucky' for the past year? That is not usually the way it goes fo me.
Thanks for the help, I will let you know what happens.

 

O.K. sent the mode 8 command and got the dreaded "TP has encountered a problem and must shutdown ...."

Rats!

 

Rats indeed. Filthy, rotten rats! All of this will function nicely in Version 5. No need for these hacky connection schemes.

Sorry about that. Maybe your luck will return!

 

Boy some of this sounds like what I have seen. Mark I know you asked me this in the past but I am running a vette ECM with SAUJP -no ECM. I would assume that this would not affect me at all but everything I assume appears to be wrong. I have seen the error packet counts and wish I would have known about the keep hitting part to see if it would connect.

 

That is unbelieveable I was just lucky for the past year or so, must be more to it than that. But I sure can't figure it out. Oh well, I will keep watching for the updated version 5.
Thanks for your time! Keep up the good work, it is appreciated!
I believe the Moates ECM 852 program worked on the 727 at one time, will give it another try.

 

Mark could you elaborate more on what this does? I am using JP's a definition that I modified and his settings are:
F4,56,01 the payload size is 63 Bytes and offset is 4

 

Let me know if you get that to work. If you do, the current version of TunerPro still has a chance (they employ the same connection methodology).
----------
This tells the CCM to shut up and stop sending out chatter. The chatter is what makes it difficult for TunerPro to connect.

 

So I should change my command settings based on your recommendations above and not use what I have.

 

[QUOTE=Mangus]Let me know if you get that to work. If you do, the current version of TunerPro still has a chance (they employ the same connection methodology).
----------


Gave the Moates program a try and no luck.
Can you recommend another scan/log program that will work?

 

Datamaster