Communication module inop

I have the same issue (no lights on the SOS button and no more status information to entune). The last update from the car to entune was Apr 28. Scheduled an appt to the dealer to check it out on Wednesday.

 

hmmmmm. I will have to check my lights.. I am wondering if this is the same issue as the one I am having, just representing in a different way: Entune stopped connecting to the car | PriusChat

Seeing badasset comment above that the last update was 4/28, same as mine, is what leads me to this conclusion.

 

From what so far the comments have shown, it looks like an east coast problem, maybe the cell service that entune sos uses is down, here in the midwest it seems to be working ok

 

That makes sense. Too bad after 45 minutes with Entune and Toyota they did not have a clue. I was told no reported issues similar to mine.

 

Yes jburke313,
I also get the same error message on the entune app as you when checking the status of the charge or to turn on remote climate (worked up to April 28). If your safety connect light is not on, try pressing the SOS button - I get back a voice message saying "Communication Module not active".

 

I just checked and have the same issues. Light flashes on for a second and then gone. So this is likely an issue larger than each of us, and perhaps isolated to the east coast based on cellular network or otherwise. What a shame we all have to bring our cars in. Of well, I have been meaning to have them fix my faulty USB port on the console anyway. Thanks, all.

 

I also just checked mine and I also get the same issue. Green light on for a second then off and message saying "module not active, call. . . ". My last notification was 12:38 PM April 28th. This is definitely an issue on their side. I don't think all our cars failed at once on the same day. I will be calling them too.

 

When this is resolved let us know what the issue was. April 28th seems to be a bad at.

 

I believe safety connect uses Verizon. Maybe Toyota didn't pay its wireless bill.

Posted via the PriusChat mobile app.

 

I got my car back from the dealer - no solution to the safety connect issue. My dealer eventually had to contacted the Toyota's TechLine out in CA. The Toyota TechLine group walked the dealer through checking the antenna, the communication module and SOS button - everything looked okay. Next, they had my dealer reset all computers (no changes in the problem) in the car and then run some computer diagnostics. The results were sent back to theToyota TechLine group so they could analyze and research the problem. The Toyota TechLine is to contact the dealer sometime tomorrow to determine the next step (dealer is at a lost since there is no service bulletin on the issue as of yet). Have to just wait and see.

At least I got the dealer to change the backup beeping to just beep one time

 

Did you share with the dealership that this seems to be happening to many Prime owners on the East Coast and all on April 28th?

 

I did share with the dealership about this happening to several other people, starting after April 28, but since there is no service bulletin on the issue, the dealership need to wait for the TechLine to decide what the next step is. They said my car was the first one logged to the Toyota TechLine group on this issue. I guess more people with this issue need to contact their dealer's service desk so it will get logged to the Toyota TechLine group.

I also have a Toyota Prius Plug-in (2012) with the same safety connect service (with entune mapping, climate, status, emails, etc.), and it does not have any problems, so cell service in my area is working. I just guessing, but it is like several new Primes were recently disconnected/dropped from the cell service provider - I would hope Toyota would be able to check this out.

 

It does appear to be a mystery. Least the dealership can do is get you a cage full of carrier pigeons in case you are in an emergency and need to send for help. If that would fit in the hatch area.

 

Then you could use this network protocol. RFC 2549 - IP over Avian Carriers with Quality of Service

 

Did a little searching and found on a toyotaproblems website and found an entry with a similar problem on the 2014 Highlander.

Date Reported: May 14, 2014
NHTSA Reference: #10056054
TSB Reference: #PSD-TC-019
Description: TOYOTA: SEE DOCUMENT SEARCH BUTTON FOR OWNER LETTER. DUE TO AN UNPLANNED EXPIRATION OF MOBILE IDENTIFICATION NUMBER/MOBILE DIRECTORY NUMBER, IN SOME VEHICLES, THE SAFETY CONNECT SYSTEM HAS BECOME DISABLED AND NEEDS REPROGRAMMING.

If it happened once before ...

 

I found some additional information on the safety connect problem I posted previously with the 2014 Highlander and what was done to resolve it. I provided this information to my dealer's service manager to see if it could assist. They will get back to me later.

Subject: Limited Service Campaign (LSC) E0K
Certain 2014 Model Year Avalon, Highlander and Sienna Vehicles.

This is not a Recall, it is a Warranty Enhancement.
Background
The subject vehicles are equipped with Safety Connect, which allows drivers to contact the Toyota 24/7
response center at the touch of a button. Toyota has identified that the Safety Connect System in the subject vehicles has become disabled due to an unplanned expiration of the Mobile Identification Number/Mobile Directory Number.
Limited Service Campaign (LSC) Remedy
Toyota dealers are requested to initialize and verify proper operation of the Safety Connect System by
reprogramming the Data Communication Module (DCM) with the valid Mobile Identification Number/Mobile Directory Number at NO CHARGE to the vehicle owner. This LSC will remain available until May 31, 2017.
The following vital information is provided to inform you and your staff of the owner notification timing and your degree of involvement.

Owner Notification
The owner notification will commence in late May, 2014, approximately one week after the dealer notification. In addition to owner mailings, Toyota’s Customer Experience Center will contact customers whose vehicles are involved in this LSC.