bobterry99

"f" indicates there is a fault code stored in the system; however, the fault is not currently active. In contrast "F" indicates there is a current fault active in the system.

This would be a cause of your no-start condition. The right-bank engine management controller (system) will not engage the starter unless it is receiving a CAN message from the transmission controller that the shifter is in either park or neutral.

I would check to see that the little 2-wire CAN connector is securely plugged into the right-bank engine management controller N3/12 (picture). If it is, then I would check the resistance of the CAN port on that module at a moment when the engine will not start. To do that simply unplug the CAN connector and insert your meter probes into the port. You should measure 235-245 ohms.

What is the release date of your XENTRY? Are you using the wired "C3" multiplexer?

johndtitus

All of the codes I was able to access were small -f- so none were currently active. Of course it was 75F yesterday afternoon when I did the test.

The ME1-SFI - Motor electronics showed "!" which I took to mean communication error. This was confirmed when I tried to access the ECM directly.

Do you think it is the intermittent CAN communication or the "implausible" engine temperature? If I only had access to the ECM, I could see if the fuel injection was compensating for a strange water temperature reading (or some other temp sensor). I'm not even sure which temp sensor the transmission would be reading....

This is a C3 multiplexer clone (silver box) with Star C3 (Xentry/DAS) running on a refurbished Dell D630. I don't recall the release date of the Xentry, but it was updated only through 2014. Seller advertised that it was compatible from 1989 through 2014.

Also, it might be November before I can perform the test you suggest. I live in Phoenix and last weekend may have been the last time I see below 55F for a while....

bobterry99

It is surely referring to a lack of CAN communication. If this were a temperature sensor it would be for the engine coolant, and you would also have a fault in the engine management controller and a check engine light.

You appear to have all the right hardware and software. You might try downloading and installing another copy of XENTRY. There are free torrents around; also, with a $15 sign-up fee you can access *******.com where there are many copies available. You should probably choose XENTRY dated 9/14 or older, since later versions do not officially support the C3 multiplexer.

johndtitus

I opened up the module bay and found the N3/12 controller, however, I could not find anything that looked like a 2-pin connector CAN. The only connector appeared to be a HUGE (at least 100 pin) connector with a cam-lock coming out of the top of the module. Do I need to remove the module from the module bay to see this CAN connector?

I think I have 9/15 version of XENTRY...

bobterry99

I misled you. I assumed there was a separate CAN connector as there is with most other models. Instead, the CAN is pins 61 and 62 of the big connector (picture).

I would very definitely find another version that is 9/14 or older.

johndtitus

OK that is a huge help. I will look at the resistance across those two pins tomorrow morning. Actually, it looks like there are two of those huge connectors on that module, and two more on the module next to it.

I assume the connector that is most forward on the left side module is the one we are talking about? I did spray some contact cleaner on the forward connector (the rear connector cannot come loose without taking the cowl trim off).

Also, I just noticed that there is no pin 62 on the thumbnail diagram you attached. Would you please verify which pins are the CAN bus? Thanks

bobterry99

I don't know the location of the connector you want, but since their pin-outs are different, only one will match the picture from my prior post.

I should have typed 61 instead of 62. So, the two pins you want are 60 and 61, and the resistance measured between them with the key off should be 235-245 ohms.

johndtitus

Still trying to identify the correct pin.
My module bay looks like the one in the photograph you posted previously.




1999 SL 600 Module Bay

However, when I pull the connector that is in the location of the N3/12 connector in the photo (lower right in photo), it looks like this.







N3/12 connector?

As you can see, only some of the slots are filled and they do not correspond to the diagram you posted.

bobterry99

For no apparent reason my older browser does not display your photos, so I have posted the layout of both of the connectors to help you identify which one has pins 60 and 61 for the CAN.

johndtitus

I re-posted with compressed images. Maybe they will display for you. Anyway, the connector I pulled off (forwardmost on the N3/12 controller) looks more like Conn 2 than Conn 1. That means Conn 1, which will have pin 60 and 61 is the connector that you can't remove without disassembling the cowl trim (of course)

johndtitus

Just updating on the progress (or lack thereof). I have been stalled while I try to get Xentry to work in HHT-WIN mode. FWIW, beware of the eBay seller "Ecartool," she told me that the system would be fully compatible with a 1999 SL600, but it can only do the quick check. When it tried to go into HHT-WIN mode, it errored out with COM port in use. After hours of searching on the web, I realized that the HHT-WIN.ini file was defective and had to set the slave to D2 instead of T. That got the COM port open but it still says communication cut turn key off and on, then nothing. When I complained that this was supposed to be a 'turn key' system and I am already having to do programming, she insulted me. Working with eBay now to force her to take back the system and refund my money.

Long way of saying I still haven't resolved the issue, but I promise I will report back when I do, or if I have further issues. Thanks for your help

johndtitus

Finally closing the loop on this issue. Ultimately I had to go to my indie to to have them figure it out. They were finally able to determined that the right hand Motor Electronics unit had a temperature-dependent failure. I was convinced it was the transmission controller as were the techs at Bluelink (who rebuild these things). My shop persevered and finally convinced me otherwise. The only way they finally isolated the fault, was they noticed that when the temperature was below about 60F, the transmission controller and the left hand ME unit were still communicating through the CAN bus, but the right hand ME would go silent. Since the right hand ME conducts the handshakes with the transmission controller, the neutral start inhibitor and the rest of the systems before authorizing a start, the failure prevented the car from starting, and since the right hand ME can't diagnose itself, it never recorded any start failures... My shop and the techs at Bluelink have never, ever heard of this failure, so it was quite a challenge. All it took was a salvage yard ME unlocked by Bluelink and programmed by my indie and all is well.

BryanW203

Glad to hear you found a fix and awesome to see you updated the thread. Its always a bummer when you find your issue on a forum, then there is a huge discussion then the OP either says fixed but no description or you never hear from them again!