Starting a new thread, so as not to hijack the NVRAM emulator discussion.

It was stated there that you can disable the "chatter" by changing some data in the calibration. I just can't seem to get my 91 Y-body to talk to TunerPro, and this method seemed to hold hope.

Picking up where RBob left off

There are two other message ID's shown in my calibration, other than $F4 (Which is the ALDL mode). They are message $40 and $42. (There is no 16 message minor loop table in my cal, unlike 8D, as referenced in the previous thread)

I assume $40 is the CCM or dash, based on the data sent:

MSG $40_1: NTRPMX
MSG $40_2: PROMIDA
MSG $40_3: NTPSLD
MSG $40_4: CLDEGFLT
MSG $40_5: MATDEG
MSG $40_6: CCMMW
MSG $40_7: CCMREVS
MSG $40_8: IPFUEL+$3000
MSG $40_9: IPFUEL+$3001
MSG $40_10: KDISFSC
MSG $40_11: FILTMPH
MSG $40_12: OILDEG

Anybody know for sure what $40 and $42 messages are? $40 will definitely flash the SYS inthe digital dash if it is wrong.

I can totally disable these two id's in the calibration and see if that helps TP connect.

Todd

 

One is for the digital dash, the other for the ABS module, most likely. Which is which I do not know. Disabling them both would help, however, neither module would function without the ECM interaction, so you'd want to do this temporarily.

 

Mark,
I'll try it, if only briefly, just to test it out. I've checked the commentary more closely, and $40 and $42 are both referred to as "CCM Mode" messages.

By the way, in case I haven't said it before, thanks a ton for all the work that has gone into TP. It is a tremendous piece of work, and you should be proud. I use it exclusively for bin modifying, and can't wait to enjoy the full power of Datalogging too.

I'll have to get creative to try to disable these modules. There is no scheduler table in my bin. I think I can get the ECM to ignore the requests with $4X message byte, and only respond to $F4 requests. Setting the mode id byte for those modes in the calibration section to something which the ECM will never see, should do it.

todd

 

tpep, If you could post your BIN it would be helpfu (change the extension to .jpg or .gif before posting it). The ZR1 engine doesn't use the $8D code. As you mentioned it may only be a different message header value.

RBob.

 

Wooo Hoooo! I got TunerPro to connect to my car. I didn't even have to change the bin, as discussed above. I don't know if it is this version of TP (4.13), or the new ALDU1 and cable from Moates, but she works!

Only minor thing is that the "SYS" error flashes in the dash when TunerPro is open, even when not collecting data. The SYS stops as soon as TP is closed, even with the cable still connected.

Overall, not a worry. No ECM error codes are set, and the car runs fine.

Again, big thanks to Mark for a great program. I look forward to making much use of it in the future.

Todd