# Can't Communicate with SL5011

**URL:** <https://forum.sierrawireless.com/t/cant-communicate-with-sl5011/6216>\
**Category:** Legacy AirPrime modules\
**Created:** [March 20, 2013, 3:19pm UTC](https://forum.sierrawireless.com/t/cant-communicate-with-sl5011/6216 "2013-03-20T15:19:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![APBeck3](https://avatars.discourse-cdn.com/v4/letter/a/f14d63/32.png) [@APBeck3](https://forum.sierrawireless.com/u/APBeck3)\
**Post date:** [March 20, 2013, 3:19pm UTC](https://forum.sierrawireless.com/t/cant-communicate-with-sl5011/6216/1 "2013-03-20T15:19:20Z")

</div>

I’m having a problems communicating with my SL50101 Rev. 1.0, firmware p3110503. I can connect to it using Watcher (R7.26.3.0 - device Driver USB MUX R2.1.13.0). However, I cannot communicate via terminal emulator either through the USB interface or UART under Windows XP.

Under device manager I can see the following devices:

- Modems
  - Sierra Wireless Modem

- Ports (COM & LPT)
  - Sierra Wireless CnS Port (COM15)
  - Sierra Wireless DM Port (COM14)
  - Sierra Wireless NMEA Port (COM16)

Using a USB monitoring program I can see ‘AT’ data on the “Sierra Wireless Modem” port when I use Watcher to make a data connection.

Using a terminal emulator I can send AT commands to the SL5011 on the CnS and DM ports but I do not receive anything back from the module. I can verify that the data is being sent using the USB monitor.

I’ve also tried connecting to the UART pins and get no response on that port either.

Is this a driver issue, or do I need to do something with the SL5011 to enable communications?

---

<div class="post-metadata">

**Author:** ![Rex\_alex](https://avatars.discourse-cdn.com/v4/letter/r/73ab20/32.png) [@Rex\_alex](https://forum.sierrawireless.com/u/Rex_alex)\
**Post date:** [March 21, 2013, 11:46am UTC](https://forum.sierrawireless.com/t/cant-communicate-with-sl5011/6216/2 "2013-03-21T11:46:57Z")

</div>

Hi,

There is no AT port??

Thanks.

---

<div class="post-metadata">

**Author:** ![APBeck3](https://avatars.discourse-cdn.com/v4/letter/a/f14d63/32.png) [@APBeck3](https://forum.sierrawireless.com/u/APBeck3)\
**Post date:** [March 21, 2013, 12:11pm UTC](https://forum.sierrawireless.com/t/cant-communicate-with-sl5011/6216/3 "2013-03-21T12:11:44Z")

</div>

SOLVED IT  
There’s a listing for it under Modems, but my communications program didn’t list it as a COM port. Got it working now.

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [March 22, 2013, 10:01am UTC](https://forum.sierrawireless.com/t/cant-communicate-with-sl5011/6216/4 "2013-03-22T10:01:06Z")

</div>

> [@APBeck3](#):
>
> There’s a listing for it under Modems, but my communications program didn’t list it as a COM port.

How to identify the COM port for a “Modem”:

[blog.antronics.co.uk/2011/09/15/ … indows-xp/](http://blog.antronics.co.uk/2011/09/15/identifying-a-modems-com-port-in-windows-xp/)

(the same applies in Win-7)