# EM7590 without AT interface

**URL:** <https://forum.sierrawireless.com/t/em7590-without-at-interface/31258>\
**Category:** MC/EM Series\
**Created:** [December 13, 2023, 10:07am UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258 "2023-12-13T10:07:25Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomerg](https://avatars.discourse-cdn.com/v4/letter/t/e9bcb4/32.png) [@tomerg](https://forum.sierrawireless.com/u/tomerg)\
**Post date:** [December 13, 2023, 10:07am UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258/1 "2023-12-13T10:07:25Z")

</div>

I have an EM7590 module connected to a linux system. I fiddled with the interface configuration a bit using AT!USBCOMP and now I only have the mbim interface on /dev/cdc-wdm0 and the wwan0 interface. Is there a way to reset the interface settings, or did I permanently lock my self out of using the AT interface?

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [December 13, 2023, 11:29am UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258/2 "2023-12-13T11:29:02Z")

</div>

how about using Windows?  
I saw the driver together with the configuration.ini which will set the USBCOMP value

---

<div class="post-metadata">

**Author:** ![tomerg](https://avatars.discourse-cdn.com/v4/letter/t/e9bcb4/32.png) [@tomerg](https://forum.sierrawireless.com/u/tomerg)\
**Post date:** [December 13, 2023, 1:19pm UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258/3 "2023-12-13T13:19:49Z")

</div>

@jyijyi I managed to get AT interface with Windows, but I couldn’t restore it from there to the Linux machine. I tried `AT!RMARESET=1` but no luck. No /dev/ttyUSB\* devices at all. Do you know what more can I do to restore the AT interface?

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [December 13, 2023, 1:23pm UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258/4 "2023-12-13T13:23:01Z")

</div>

is that your AT interface is over MBIM in Windows?

---

<div class="post-metadata">

**Author:** ![tomerg](https://avatars.discourse-cdn.com/v4/letter/t/e9bcb4/32.png) [@tomerg](https://forum.sierrawireless.com/u/tomerg)\
**Post date:** [December 13, 2023, 1:48pm UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258/5 "2023-12-13T13:48:24Z")

</div>

I’m not sure, wasn’t aware AT over MBIM is even a possibility.  
In device manager I get  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/sierrawireless/original/2X/c/c0b1fe8e80c8309bbd0067020abdcfa8e16bb57e.png)  
However TeraTerm identifies another com port, COM16, without a name, which gives me an AT interface and responds how EM7590 should.

```auto
ATI
Manufacturer: Sierra Wireless
Model: EM7590
Revision: SWIX12C_01.01.07.00 2022/11/14 16:14:31
SVN: 02
IMEI: 357999720005505
FSN: 01225200088A20
+GCAP: +CGSM

OK

```

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [December 13, 2023, 2:26pm UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258/6 "2023-12-13T14:26:54Z")

</div>

then what is AT!USBCOMP?  
If AT port already enabled in AT!USBCOMP, then this is not module problem.

---

<div class="post-metadata">

**Author:** ![hfoster](https://avatars.discourse-cdn.com/v4/letter/h/7ab992/32.png) [@hfoster](https://forum.sierrawireless.com/u/hfoster)\
**Post date:** [May 10, 2024, 4:44pm UTC](https://forum.sierrawireless.com/t/em7590-without-at-interface/31258/7 "2024-05-10T16:44:43Z")

</div>

I had to do the following on my device to get this to work:

As root:

```auto
modprobe option
echo "1199 c081" > /sys/bus/usb-serial/drivers/option1/new_id
```