MTSMC-EV3-N3 (verizon)

[Lucas Li]

Hi

I have a MTSMC-EV3-N3 modem that has been registered under Sprint.
The modem dials and comes online under linux with the following commands:
AT&S1
AT$QCMIPEP=1
AT$QCMIPRT=1,1
AT$QCMIPP=0
AT+WOPEN=5
ATD#777
However the same commands did not work for Windows using the ev3/ev2 modem drivers.
Does the N3 only work for Verizon?

Thanks
Lucas

[Lonny Knudson]

Hi Lucas,
MTSMC-EV3-N3 only works on Verizon
MTSMC-EV3-N2 only works on Sprint

The following commands are not required to establish a data link and I would recommend removing them from the dialer for both Linux and Windows systems:
AT$QCMIPEP=1
AT$QCMIPRT=1,1
AT$QCMIPP=0
AT+WOPEN=5

If the above information doesn’t help to resolve the issue, I recommend opening a support ticket here:
http://support.multitech.com

[Darrell Jefferson]

Hi — I work with Lucas on this modem development, and I have some more information to add to the puzzle.

The most confusing part is that we have two different environments attempting to use this same N3 modem on a Sprint account — 1) Ubuntu 12.04 with our application calling pppd, and 2) Embedded XP using Multitech-provided drivers and making the calls through RAS. What confuses me is that the Ubuntu environment successfully goes online with the modem *every* time — and the XPe environment fails *every* time!
I have verified that all AT commands issued to the modem are identical between the two environments (up to the point where the dial string is handed off to pppd or RAS) … but the result of the Dial operation are just different between the two. I have logs to show that the sequence “appears” to be the same up until the dial operation.
I can’t understand how the modem would respond differently to the type of system on the other side of the serial connection. We are using the exact same hardware in both cases (I just swap out the compact flash card to load one operating system or the other).

Under XPe I have tried using the Multitech-provided MTSMC-EV2 and the MTSMC-EV3 drivers, but that didn’t make any difference. The Ubuntu environment issues the following sequence just before dialing …
AT+WOPEN=1
AT+WOPEN=5
ATD#777
And if I try that same sequence under XPe, the result is…
ERROR_AUTHENTICATION_FAILURE

Should we just give up because you say N3 doesn’t work with a Sprint account, and chalk the different behavior of the two operating systems to some post-dial activity (we don’t directly control either pppd or RAS once the hand-off has occurred)

[Lonny Knudson]

Hi Darrell,
If it works with Linux/pppd it should work with Windows/RAS/DUN…
Maybe there is some confusion about which model is in use? Both the -EV2 and -EV3 models have been referenced in this thread, and this could make a difference, specifically with regard to the use of the +WOPEN command. There is also some apparently conflicting information in regard to -N2 vs. -N3. I recommend opening a support ticket ( http://support.multitech.com ), include the serial number of the modem you are working with, and maybe a link to this forum thread to provide a little more background for support staff. The MTSMC series modems should work in both environments mentioned in your post.

• This reply was modified 8 years, 6 months ago by Lonny Knudson.

[Darrell Jefferson]

Thank you, Lonny. I recognize the confusion you speak of. All of the recent experiments have used the EV3 modem. But we have switched back and forth between the drivers for MTSMC-EV2 and MTSMC-EV3 in our attempts to get this thing working. Previously — just to be sure our application was written correctly, we briefly switched to the EV2 modem and verified that we were able to go online using either environment. (we were)

I have opened a ticket with support, as you suggested. Thank you for your help.

[Author]

Posts