hgw

Last week my diacom went up in a cloud of red smoke after 10 years of good service.
So I start searching for some new and hopefully better software.
I tried ECM852, Efilive 4.0, Tunerpro and finally Scannerpro.
They all had problem connecting or gave a lot off errors, but the most promising where Scannerpro. After a lot of research and head scratching I finally was able to get it to work.
But I have some questions.

1. I can’t get it to connect error free in Output mod but its ok in Dash mode!!! Am I just stupid or?

2. I have to connect, disconnect and connect to get it working could this have to do with the 400ms MAX timeout for the listen command?

(Its seems to that the CCM ALDL device presence check “heartbeat” is only
performed 1time every second).

3. Is there any way to export or convert the .XDL format to a more common format dbf xls…..?


Thanks a lot to the people that’s develop this software it seems to have a great potential

Sorry for my bad English but it’s not my native languish

-=Jeff=-

If you have it working, could you send me, vettxtc@gmail.com, or attach here your ADX file? I was having trouble with it for my 91 ECM Vette.. this way I can see how you set it up..

THANKS
-=Jeff=-

hgw

HI

Sorry for the delay but I have been away racing the whole weekend.

Since my last posting I did some more testing
I found some small issues and some of the trouble I had,
Have gone away, after some editing.
” I just added some comments and after that I don’t have to connect, disconnect connect to get it to work”
I really have no clue way

1. I can’t get it to connect error free in Output mode, Monitor mode and sometimes it’s difficult in Histogram mode or when the Editing window is open.
2. This seems to work now 19 of 20 times.
3. Is there any way to export or convert the .XDL format to a more common format dbf xls…. Or copy and past the Histogram?
4. When I try to open the editor for the first time whit my new file loaded it takes a really long………. time.

It would be great if you could test it on your -91 to see if it works.
I don’t see any big changes in data stream between the years just some some small differences in the CCM data stream.
You have to consider the file as an ALFA not even a beta file
Please post back whit your results.

Thanks
Gunnar

Mangus

Hello -

If it won't connect reliably while viewing the output tab, then it suggests that the connection scheme is very timing dependent. It takes time to output and display the text in the output tab (and calculate the histograms when viewing them, etc), and that time may affect the connection macro.

A couple things I notice with your def:

1) You mention that the heartbeat is sent out once per second, yet the timeout for the listen command is 400ms. If it is truly sent once per second, I'd recommend setting the timeout to more like 1100 or 1200 ms.

2) You might try setting the connection macro repeat count to 2, or even the silence CCM entry count to, say, 5. The latter will serve to blast the CCM silence command in case the first transmission doesn't get in due to timing issues. The 2nd attempt at the connection macro is just for good measure, so you don't have to repeat the connection process manually.

3) The ECM might require a brief timeout between the silence command detection and the CCM silence request. You might try anywhere from 1 to 30 ms.

Once you get it working reliably, and we have proof that it works for other people, I'd like to clean up and release this definition!

Thanks,

Mark

hgw

Hi

1) You mention that the heartbeat is sent out once per second, yet the timeout for the listen command is 400ms. If it is truly sent once per second, I'd recommend setting the timeout to more like 1100 or 1200 ms.

I tried that. but when I save and reload the file it’s back to 400ms.

Thanks
Gunnar

Mangus

Ah, you're right. Please inform me directly when you run into bugs like this, so I can fix them.

I'll fix this and upload a new build shortly.

Mangus

OK, I've uploaded a fixed build to the Scannerpro site. Please download it and try. You should be able to change the timeout now.

hgw

Perfect

Thank you and I will notify you directly in the future.
I think/hope that that’s the issue why it doesn’t always connect.
And your comments about output tab make sense

Gunnar

hgw

It works every time now i set the timout to 1200ms

-=Jeff=-

COOL!!! I will have to try it on my 89 vette (91 electronics) 90-91 should be the same..

Then IF mark releases your Scheme as good, I will make one for my new toy.. 90 ZR-1

hgw

Hi

So there is no confusion it won’t!!! Connect error free in output or monitor mode
Dash, Item & Histogram is OK now

Please post back whit your findings

Gunnar

Mangus

It sounds like Gunnar has it working well with the latest build (avaliable at Scannerpro.net now).

Definitely download the lateset build and give it a try, Jeff. Let us know...

hgw

Total success!!!!!!

I have been out in the car all morning to try it out.

Your fix for open files in the editor works great.

The only change was to set the timeout for listen to chatter to 1200ms


I have now connected it for at least 100 times and it works every time
I finally got tired of doing it
I tried to connect only whit ignition on and whit the engine running and it works.
I tried to restart the computer and car it still works
I tried it in every mode and so far it’s reliable in Dash, Item and histogram mod
I suppose the two other modes are to processor intense
My laptop is only a P3 750 MHZ 128 M memory running XP SP2



Some findings:
In dash mode it connects at 10.3 HZ Error free
In Item mode it connects at 10.3 HZ Error free
In Histogram mode it connects at 9.7 HZ Error free

In monitor it’s not reliably sometimes it show 13-15HZ but don’t give any useful data
Sometimes it slows down to 8 or 4-5HZ and give useful data
Sometimes it gives a lot of error.

Output mode always gives errors

I tried to connect whit WordPad running “to stress the computer”
In dash mode it connects at 10.3 HZ Error free
In Item mode it connects but sometimes gives errors
In Histogram mode it connects at 9.7 HZ Error free
In monitor it’s not reliably
Output mode always gives errors

I can’t tanks Mangus enough for his excellent support
Gunnar

hgw

Hi
Mangus feel free to do what ever you want whit the file
I acutely would be thankful if you cleaned up the file


Thank's
Gunnar

Mangus

Hi Gunnar -

Thanks! As soon as Jeff confirms that it works for him, I'll go ahead and clean up the file and post it on the ScannerPro site. I will, of course, keep your name associated with it. Thank YOU for creating the definition! You just solved a very big problem for me and one of the reasons I created ScannerPro - to support those pesky 90/91 Vettes! =)

Thanks again,

M

-=Jeff=-

I am pretty swamped this week, I have the cbale to try out, I will find time in the next couple of days..

hgw

WOW

I just noticed that you made it possible to copy and past from the histogram
I’m so used to right click on everything “Dam windows”,
that I didn’t notice that Ctrl C Works.
Scannerpro now becomes REALLY useful.

Thanks
Gunnar

-=Jeff=-

I will try it out tomorrow monring on my vette.. then I will post results

-=Jeff=-

Tried out Gunnar's ADX this AM..

Car: 89 vette, with 1991 ECM and CCM

Computer:
MacBookPro Core 2 Duo 2.33GHz 2 gig ram

Interface: USB to OBD 1

First I was running OSX and had Windows running in Parallels Desktop. I found that no matter what I tried it was dropping with errors constantly,

Then I remembered reading on Mac forum that with Parallels the USB is set in PAckets and thought it might be an issue.

I rebooted into Windows XP , (thanks to Bootcamp)

Tried it againa nd got a couple errors.. the 1200ms is good, but I bumped mine to 1250 and I got no errors. I think the 1200 will be a good baseline and you can adjust that delay.. I would say this is good to go.. this should support BOTH 1990-1991 Corvettes..

Now I will start working on an ADX for the 1990 ZR-1 ..

Mangus

Excellent, although I didn't realize you were using a Mac (your results can't be trusted, I say! =) (just kidding).

1250 shuoldn't make much of a difference, and I'm surprised to hear that it did. I'll change it in Gunnar's definition when I put in the work to clean it up and publish it.

You're selling your Vette, right Jeff?

Thanks to both of you!

-=Jeff=-

Yes, I am selling my vette.. I am moving into a 1990 ZR-1 instead

But I will make an ADX fo rhe ZR-1 based off of Gunnar's ADX

kevosiroc

a little bit off subject... but what is the chatter/heartbeat you are communicating with the CCM about?

Obviously you have figured out how to tell the CCM to shut up so that you can data log..... but can this be used to tell the CCM to shut up or nevermind that the OE ECM is no longer present.

I am thinking about a stand-alone device that simply wires into the serial data line of the CCM to trick the CCM into thinking the OE ECM is in place and properly operating with no DTC's. Then the CCM would not do the annoying things that are discussed in this post : http://forums.corvetteforum.com/show...post1562475757

That way I could remove the OE ECM and place anything else in its place.... be it an LT1 computer, MegaSquirt, Accel, or any other standalone system. I am sure -=Jeff=- would be interested in this, as well as many other 90-91 Corvette owners that would like to ditch the stock ECM but are restricted by doing so b/c of the FU@KING CCM crap.
----------
One more mroe thought, since the CCM gets a signal from the ECM regarding engine speed, maybe this "black box" idea i described above could pass the vehicle speed data on to the CCM as well.

BTW I am 1992B4C over at corvette forum.

-=Jeff=-

CCM gets its speed from the VSS directly, not the ECM..

kevosiroc

Oh, the electrical diagrams show it going from the ECM to DDM, but those have been wrong many times before.

-=Jeff=-

Interesting.. I thought the CCM was DIRECT FED.. now I cannot remember what it was other then the ECM..

So again I have to ask why swap it out.. other then to 'clean' the engine compartment...

Heck my 89 with 91 electronics runs great, it still needs some work on the WOT tune which I have not really touched yet.. but the car is for sale now anyway..

anesthes

iTrader: (12)

Back from the dead.

If i'm using a '730 ECM how should the VSS wiring be? Should I run the 4000PPM sender direct into the '730 ECM, then use the '730 filtered 2000PPM output to the CCM?

I'm runing $58 code (from a '749, but in my '730), NOT $8D so the CCM and ECM won't share the ALDL screen. My plan is to use the CCM to just run the stupid LCD in the cluster.

I'm pretty sure I'll be using a '92 CCM anyhow.

This is from an '87 to '90 dash swap. This CCM stuff is kicking my butt.

-- Joe

JP86SS

iTrader: (1)

"B11" should be 4000 PPM output, could try that one.
Diagram indicates the signal comes from the ECM so it "should" work.
B12 & C1 are 2000 PPM outputs.
Should be the same pins as the 730, I don't show a different pinout for them between the 749/730.