V4 beta? Scannerpro build is 0.50. You're not talking about TunerPro, are you?

 

He's talking about the S_AUJP V4, he's been testing for a while now.

I do have some $8D stuff made up for SP if you like I can shoot it off to anyone who wants it. It was connecting slow and replay was a bit slow yet too. I think it has allot to do with the massive amount of items I've created.
Seems to run faster when stripped down. Just ain't had time to do more with it lately. Now that the snow is flying, I'm knee deep in my ECM bench building. Hopefully that will speed up the process of new stuff. Its all a big learning experience and Certainly will be more fun.

 

Yep, S_AUJP v4. JP - shoot it off to me if ya can. I had to work all day today and then had our local club meeting tonight, so I haven't had a chance to try it again and get the complete error message I'm seeing. Hopefully I can do that in the morning for ya, Mark.

 

Tried using JP's $8D stuff, no change. When I start up SP, I see the message in the big white box saying it has loaded the ADX file. When I click on the double arrows to connect to my ALDL, I get the error message in the white box "0.225!!!!! SEND COMMAND FAILURE!!!!!" and the yellow connect status in the lower left corner still says it's disconnected. Checked the preferences, and it shows serial port #1. Close SP, and immediately start Datamaster using the same cable on port #1, and it reads my ALDL just fine.

So, obviously I'm not doing something right here. Any ideas?

 

I'm trying to be patient.....

 

Did the box indicate the def was loaded ok?
That is the same message I get when no cable is even connected.
(first number is a timestamp I believe and is not important)
Obviously SP is not seeing the cable or something with the port.
The command defs are ok so it must be something else.
Maybe try uninstall/reinstall SP ??
Also reboot after reinstall, I found I needed to do that when I upped to the latest version (5.0349)

 

outta curiousity did you add the checksum to the end of the byte string in the mode 1 aldl dump request ?

you can let scanner pro do it for you
import an ads file with the correct mode 1 aldl dump request byte string
you can create your own ads and only put in the byte string
you need to know what your byte string is by looking at the aldlstuff.zip or look in another ads that someone has made for your proper mask or just use someone elses ads thats for your mask

then import that ads with scannerpro
save it somewhere on your hard drive
load it up with scannerpro
and notice it has added a 4th byte thats your checksum
use that in your adx def you created

example
mode 1 aldl dump request in tunerpro
F4, 56, 01

after loading that ads into scannerpro to convert to adx
0xF4 0x56 0x01 0xB5

bold = checksum

 

Those are exactly the numbers shown under my command0

 

Vern - you're using a serial ALDL interface, correct? And you're sure it's on COM1 (sometimes serial ports are on COM2)?

 

Yep, a serial cable on COMM1. DataMaster uses COMM1 too, the same port. After I get a SP failure I can immediately start DM without changing anything laptop or cable wise and DM worked just fine. Checked the DM config, and COMM1 is selected.

FYI - my serial cable is one of the Mastech units that I out a ALDL connector on the end of. It never has been a problem data logging with TP-RT or DM although I haven't tried TP-RT lately. Will do that this evening to verify it is still working....

FWIW - I'm also using an Ostrich.

 

No ideas?

 

If you are using an Autoprom go into TP and set your interface to Max 232 -passthrough setting and make sure your vertical switch is out. I just went through about my 100th time trying to get a datalog with errors. I finally figured out that it all had to do with the FTDI drivers. If you go to the site and download the newer drivers you have to run the uninstall program. You also must do it using the version from Craigs install -2154. Don't ask my why but all of my datalogging gremlins appear to be driver related. I connected yesterday even with a virus-scan on. Also when you set the settings for the AP in TP check to make sure the cable is functional.

Now onto Scannerpro. This looks great. I took JP's definition and modified it to my liking. Anybody interested I can send a copy. Onto the SP forum.

 

I made a definition for Dimented's MAF'd 16197427 TBI PCM that I am now running on multiple TBI vehicles.

https://www.thirdgen.org/forums/atta...maf-tbi-od.zip

 

No AUtoProm, I'm using an Ostrich.....

 

Yes 7427, this means I can run scanner pro on my truck.
Thanks fast.

 

Why when I connect with the 7427 definition does it display some good data and some bad and it will only stay connected for like 10 seconds then I have to click connect agian.
I just remebered I had anti-virus software running Ill make sure thats not running next time.

 

Because my ALDL cable took a dump as soon as I made the definition. Should have put a disclaimer on it that it was nearly untested. The command line is faulty. Working on that one right now. Just don't have means to test it.

BTW,
This is for the MAF setup so some of the outputs have been changed to meet that datastream rather than the regular 427 PCM.

 

Oh ok thanks. The rpms always read in the 3,000s but the tps worked but then things like speed and mpg where off.
Will there be one for the regular 7427?

 

Wouldnt't it be grand if RBob and Magnus collaborated on this for EBL?

 

If you have the datastream info, just create a def and go.
Still has some kinks to work out with execution speed and interface additions but is neat to play with even as is. There's a couple of threads in the support forum with tips on editing the def file in text editors.
Try not to get overzelous and create lots of things. The speed is reduced with larger amounts of active items in the displays.
I'm using it pretty much exclusivly as I TRY to get my bench up and running.
Something about watching an analog needle on a gauge that just makes things much easier to relate to.

Any new info Magnus?

 

Well we have the EBL .xdf already. I was suggesting using the GUI from what Mangus has with the goodies RBob has in the EBL software. I know Bob won't take offense if I say that the ScannerPro screens are prettier.

 

I plan on a 20-30 minute datalog over to a buddies. I went back to CL and I am very interested in using histograms to get my VE tables in line -which is never ending and also getting my timing tables in line looking for any spark retard areas. Last but not least I want to see how this does in PE mode! So far it looks like everything promised and then some. I do have some enhancement requests but I am sure Magnaman (redhot) is working hard for us all!

 

I'm sitting on a build that fixes the CPU-maxing issue when starting/stopping logging. Craig and I are going to be creating a 94/95 LT1 definition over the next few days (he finally has a test mule).

Work will slowly start resuming. I've been really lax lately on the software side of things (I've been enjoying a couple of my other non-vehicle and non-software related hobbies).

Happy new year to everyone!

 

HEY.............everybody deserves a rest now and then........

Happy new year to you too!!

Still lovin TunerproRT

 

That's cool, I've just gotten used to using pause/play. As long as you don't hit stop it runs good.

Need those breaks to keep you sane.

 

I can connect for varied lengths of time, max so far is about 17 seconds, sometimes its only 1 or two, and it is due to an error during transmission. Is there a reason that SP doesn't discard the errors and continue monitoring, instead of stopping like its doing for me.

BWT, in the output window, its saying !!Send Command Failure!! as the last thing in the log.

 

It shouldn't disconnect on errors. I can turn off the bench/car and let it spit out errors all day without stopping. Not sure what's up with that.

 

That's the same error messsage I'm getting whenever I try to connect to the ALDL with SP. Except mine has never connected at all. I'm having to do all my logging with TP-RT right now....

 

Ya, mine will connect, says ALDL connected, and I get valid data for the time it is connected, then I get the send command failure message and its done, have to reconnect all over and same thing every time.

On the other hand, TP-RT works great every time.

 

I have the same issue