Remote access error code 00011000
I just installed this thing in my 2011 F-350, and mine's not 100% what it should be, so I'll be watching this discussion to see what turns up.
My wife and I both use VZW with our Samsung Note 3 phones. My problem is that the Remote Access module refuses to send text alerts to my phone, but does so to hers. Very frustrating, and support is nearly non-existent.
Surely don't mean to hijack this, but did want to confirm that VZW is not the issue in your case.
I just installed this thing in my 2011 F-350, and mine's not 100% what it should be, so I'll be watching this discussion to see what turns up.
My wife and I both use VZW with our Samsung Note 3 phones. My problem is that the Remote Access module refuses to send text alerts to my phone, but does so to hers. Very frustrating, and support is nearly non-existent.
Surely don't mean to hijack this, but did want to confirm that VZW is not the issue in your case.
"Alerts" are checked in "Settings", and I can send and receive SMS all day long...except from Remote Access. Of course, I've also uninstalled/reinstalled the app numerous times, and re-entered "recipients", etc, to no avail. Also powered down the system by disconnecting the connectors on the module - nada. In addition, I've deleted the app's "data" in the phone's app mgr, in case there was corrupted data. Same thing - nada. But it gets even better. Tonight, I tried to use the app to do the usual stuff - lock/unlock doors, "find", start, etc, and NOTHING works anymore. OEM remote start from the FOB works fine, as does all the rest of the FOB functions, but Remote Access is down for the count. Nothing works.
I tried calling the support number last Friday, and got "nobody here's ever seen that". So, I'm on my own with a system that's dead, and I'm out of ideas. I uninstalled the app. Maybe I'll regenerate some new patience and try it again sometime later.
Thanks
Edit: Since calling for tech help produced nothing, I decided to attempt "re-learning" the VSS module to see if that would help. Afterward, I discovered that none of the buttons on either of my OEM key FOBs did anything. All controls inside the truck worked, but key buttons dd nothing, so I was no longer able to lock/unlock the truck or remote start it, using the key FOB. The truck's been to the dealer, and the diagnosis is that the module in the truck that the keys talk to is toast. Part is on order. Not surprisingly, I've removed the VSS and RMU modules from the truck, and learned an expensive lesson, which is that "all that glitters is not gold". I understand there are satisfied users out there; I'm not one of them.
One fascinating thing that came to light during this saga is the fact that, although Ford sells these items direct to owners from the official Ford website at http://accessories.ford.com/aerial-asy-10667.html#, and they're also available direct to customers from dealers on-line everywhere, the only tech help phone number provided for this thing is an Audiovox number, and I was told on no uncertain terms that the help (used loosely) they offer is for FOMOCO DEALER TECHs only, not for private owners. The guy actually told me he wasn't supposed to be talking to me. If true, why, then, are these things being pushed online direct to the public? I find that amazing, and a big eye-opener in terms of the Ford Motor Company's philosophy on how to run a business.
We live and learn, and life goes on.
Last edited by Racklefratz; Oct 3, 2014 at 02:18 PM. Reason: The end of the story
He started out trying unsuccessfully to connect to it, he then had me go to the truck to find the RMU which should have an amber LED light flashing on the unit. Looking at mine it was difficult to see the RMU, so I proceeded to pull it back out to get a better look at it. Once I got it pulled out, the LED would flash intermittently when I moved it around, the guy on the help line suspected that I had a bad RMU, however to me appeared to be the result of a loose connection of some sort by the way it acted when moving the wiring around, so I pulled the RMST module out also to check the wiring and connections, it was somewhere during this process that I lost contact with the help line (he either go tired of listening to me pulling the thing out and hung up on me, or I hit the wrong button on the phone and hung up on him). Anyway, wiggling the wires where the RMU plugs into the RMST module (white connector) the LED would work occasionally. I couldn't narrow it down to one specific wire, but what I did notice is when the connector was inserted part way into the RMST module, the LED would seem to work fine which made me to suspect the issue was with the connector itself.
So what I did was to slightly bend all the pins of the white connector on the RMST module itself thinking they might make a better overall connection, and then I plugged the RMU back into it and what do you know, it worked, the LED stayed on even when wiggling the wires to it, I then tested the system by using the app, to my delight the remote start and everything else worked like it's supposed to. I then reinstalled all the components and everything has been working fine ever since. So as it turns out, it wasn't the result of switching cell phone carriers that caused the problem, it just happen to be coincidental that it stopped working at the same time. I hope this helps anyone else having the same problem.








