[Lonny Knudson]

Hi Robbie,
APN setting is not likely to cause a registration issue. Check AT+CPIN? (should return ‘READY’). Make sure both antennas are installed. If this doesn’t help I recommend opening a support ticket.

[Lonny Knudson]

Hi Robbie,
I would recommend using one of these:
AT+CGDCONT=1,”IP″,”NXTGENPHONE”
AT+CGDCONT=1,”IPV4V6″,”NXTGENPHONE”

[Lonny Knudson]

Hi Chuck,
Here is a simple example assuming that the Ethernet interface is already configured (via DHCP).
AT#UDPSERV=<IP address of server>
AT#UDPPORT=<UDP port to send data to>
The above values are stored to non-volatile memory on execution.

To change to data mode and send data to server
AT#OUDP
MTSEM-IP will respond with CONNECT and data on the serial port will be sent to the server.
The ETX character (0x03) will end the session and return to command mode.

Here is a link to the AT command manual:
https://www.multitech.com/documents/publications/manuals/s000457.pdf

[Lonny Knudson]

Hi Damon,
For most Verizon data plans the APN is configured over the air when the SIM is first activated. If your plan requires you to set it manually, here are 2 methods:

1. In the UI navigate to ‘Administration’ –> ‘Debug Options’, expand the radio terminal then enter the following command:
AT+CGDCONT=3,”IPV4V6″,”[your apn]”

2. Navigate to ‘Cewllular’ –> ‘Cellular Configuration’. In the ‘Modem Configuration’ section enter the following command in one of the Init String feilds:
AT+CGDCONT=3,”IPV4V6″,”[your apn]”
Click on ‘Submit’ then perform ‘Save and Restart’

[Lonny Knudson]

Hi Agathe,
The extended ERROR information doesn’t appear to be of much help. I can’t think of an explanation for the ERROR response, command syntax looks correct. You may want to open a support ticket at http://support.multitech.com

[Lonny Knudson]

Hi Agathe,
Sorry about my last post, +CGDCONT is the correct command (not #SGACT). I’m not sure why you got an ERROR response. Try the following sequence and see if it helps:
AT+CMEE=2
AT+CGDCONT=3,”IP” (note: only send 2 first 2 parameters)

[Lonny Knudson]

Hi Agathe,
I believe the current firmware does not resolve correctly if an IPV6 address is obtained when activating the PDP context. Try disallowing IPV6 using the following command:
AT#SGACT=3,”IP”
Then restart the PDP context and try opening a socket using the hostname of the server.

[Lonny Knudson]

Hi Kyle,
The Verizon LTE modems use several factory programmed APNs. The APNs programmed in PDP context profiles 1 & 2 can not be overwritten. You need to use PDP context 3 for your data link (ATD*99***3# rather than ATD*99***1#). In addition I recommend removing the +CGDCONT command from your chat script. For most accounts the network will manage your APN setting and there shouldn’t be any automated process trying to overwrite the APN.

Here is an example chat script that should work for the -LVW3 modems.

ABORT “ERROR”
ABORT “NO CARRIER”
ABORT “BUSY”
“” AT+CGREG?
OK AT+CSQ
OK atd*99***3#
CONNECT “

[Lonny Knudson]

Hello,
The factory image should contain a (working) example peer file (/etc/ppp/peers/gsm). If you already edited your chat script to set the correct APN you should be able to start a ppp link by issuing the following command:
pppd call gsm

[Lonny Knudson]

Hello,
The events in the chat log show a different chat script executing than the one you posted (the one you posted is the correct chat script to use for a -H5 modem). Check your peer file and make sure the ‘connect’ option points to the same chat file that you posted here.

[Lonny Knudson]

Hi Kyle,
The serial (UART) interface on the MTQ-H5-B01 models does not connect directly to the serial port on HE910 radio module. I don’t think a ppp link would work over the serial port on the B01 builds.
For this use case I would recommend using the B02 model. On the B02 builds the UART pins connect directly to a serial port on the HE910 module.

Here is a simple H5-Linux PPP Example.

Step 1.
——-
Use a text editor to create a peer file containing the lines in the example below. (/dev/ttyACM0 may need to be something like /dev/ttyS0 for a serial build).
Save the file as /etc/ppp/peers/H5-peer.

Example peer file:

/dev/ttyACM0
connect “/usr/sbin/chat -v -f /etc/chatscripts/H5-chat”
noipdefault
usepeerdns
defaultroute
noauth

Step 2.
——-
Use a text editor to create a chat script containing the lines in the example below.
In this example [APN] should be replaced with the APN assigned by your cellular provider.
Save the file as /etc/chatscripts/H5-chat

Example chat script:

ABORT “ERROR”
ABORT “NO CARRIER”
ABORT “BUSY”
“” at+cgdcont=1,”IP”,”[APN]”
OK atd*99***1#
CONNECT “”

Step 3.
——-
Use the following command line to start pppd:

pppd debug call H5-peer

This command line enables logging of debug information and tells pppd to use the peer file referenced by the call option.
After about 20-30 seconds type ifconfig and see if a ppp interface is listed.
If not, check syslog for pppd and chat events. Normally pppd/chat logging is written to /var/log/syslog (could vary depending on syslog configuration).

The above example should be able to establish a ppp link using a -H5 product. You may need to alter the config files to optimize for your application.

[Lonny Knudson]

Hi Etienne,
The IP address for the cellular link and DNS server addresses are negotiated each time the ppp link is established. If you are seeing pppd repeatedly restarting I would suspect that it is failing to establish a link for some reason. If you haven’t changed any settings since it was working yesterday, you might want to open a support ticket to help troubleshoot.

https://support.multitech.com

[Lonny Knudson]

Hi Aurelien,
I don’t see enough information here to offer an explanation for the observations in your post. You may want to try enabling extended error indications (AT+CMEE=2) before trying to access the SIM, this may provide some useful information. If this doesn’t help, I suggest opening a support ticket ( http://support.multitech.com ). In the support ticket information please include the model number and serial number. It would also be helpful to know which physical interface you are using and a log showing your AT command sequence and responses from the modem.

[Lonny Knudson]

Hi Brian,
Regarding the items in your post:
1. Initial documentation for the MTC-LAT1 builds incorrectly describes the PROG SIGNAL LED behavior as they were defined for the MTC-H5 models.

The MTC-H5 is preloaded with an application that controlled the LEDs for signal strength.

The MTC-LAT1 does not have the capability to add an application into the MTC-LAT1 cellular modules so it cannot be programmed to match the function that exists in MTC-H5.

These LEDs can only be controlled via AT commands and are left for the customer to control, if desired.

To make use of these LEDs you can control them from the host system using the AT#GPIO command (see AT command manual for details).

The LEDs map to particular GPIO on the radio:

■ GPIO2: Controls the LED with a single bar above it
■ GPIO3: Controls the LED with two bars above it
■ GPIO4: Controls the LED with three bars above it

AT command examples:
AT#GPIO=2,0,1 – Turn LED 1 OFF
AT#GPIO=2,1,1 – Turn LED 1 ON
AT#GPIO=3,0,1 – Turn LED 2 OFF
AT#GPIO=3,1,1 – Turn LED 2 ON
AT#GPIO=4,0,1 – Turn LED 3 OFF
AT#GPIO=4,1,1 – Turn LED 3 ON

2. You may want to open a support ticket for this issue. If +IFC=0,0 (&K0) the modem should not buffer data. If you open a support ticket please remember to indicate the firmware revision on your modem (AT+CGMR). It is likely that forcing the RTS signal active will resolve the unexpected buffering behavior.

[Lonny Knudson]

Hi Jim,
Sorry, I forgot a step when I typed the procedure. Once minicom is open issue the following commands:
AT+CGDCONT=3,”IPV4V6″,”vzwinternet” (this is the step I forgot)
AT#OTAUIDM=0

[Lonny Knudson]

Hi Jim,
Could you try the following procedure and see if it corrects the issue:
1. On the ‘Cellular Configuration’ page in the GUI uncheck the ‘Enabled’ box in the ‘General Configuration’ section.
2. On the ‘Cellular Configuration’ page in the GUI make sure that the ‘APN’ field in the ‘Modem Configuration’ section is blank.
3. Click on ‘Save and Restart’ to save changes and reboot.
4. ssh to the conduit and run:
minicom -D /dev/modem_at0
5. Enter the following command:
AT#OTAUIDM=0
wait for 3 minutes
6. Enter the following command:
AT+CGDCONT?
copy and save the response and post it here if this procedure doesn’t fix the problem.
7. close minicom and ssh session then on the ‘Cellular Configuration’ page in the GUI check the ‘Enabled’ box in the ‘General Configuration’ section then save and restart.
8. A couple of minutes after Conduit reboots, check to see if the ppp link is working.

[Lonny Knudson]

If you tried to send the SMS while the ppp link was still active on /dev/ttyACM0 I would expect this type of error. The USB driver for the MTD-H5 creates 2 ports that you can use for applications (/dev/ttyACM0 and /dev/ttyACM3). If pppd is using one of these device nodes, try the other one for your SMS application.

[Lonny Knudson]

Hi Rick,
The MTR series has an API that will allow you to exchange SMS via http, here is a link to the API manual:
http://www.multitech.com/manuals/s000576_1_2_1.pdf
If you have an existing application that uses 3GPP TS 27.005 AT commands, you can enable telnet access to cellular radio and have your application interact with the radio over a TCP socket. If this method is chosen you will need to dedicate the MTR to the SMS application only.

[Lonny Knudson]

Hi Chuck,
If #CONNECTIONSTART was successful, I would expect that a TCP connection should succeed. Here are some suggestions to troubleshoot:

Try issuing the command AT#VTCP and verify that the address and port number for socket profile 1 are correct.
Test port forwarding to the SQL server from another internet endpoint (aside from the MTSMC-EV3-IP).
Try connecting to a different internet host using the socket application
example:
AT#TCPSERV-1,”time.nist.gov”
AT#TCPPORT=1,13
AT#OTCP=1

[Lonny Knudson]

Hi Chuck,
For the -IP and -GP models you should be using the UIP command set, here is a link to the manual:
http://www.multitech.com/manuals/s000457l.pdf

Here is a a quick example of the command sequence for a TCP socket using the UIP commands:

AT#TCPSERV=1,”www.xyz.com” #set address for tcp socket profile 1
AT#TCPPORT=1,3318 #set port for tcp socket profile 1
AT#CONNECTIONSTART #connect to cellular data service
AT#OTCP=1 #open tcp socket to host defined in socket profile 1

#use cntrl-c to close socket

[Lonny Knudson]

Hi Chuck,
Yes, the #DELFLASH command reset the serial port parameters back to factory default (115200, 8, N, 1). The #DELFLASH command doesn’t reset any cellular provisioning parameters so you don’t need to perform OTASP again.

[Lonny Knudson]

Hi Chuck,
It looks like the persistent socket feature is enabled, this could interfere with #ping… You may want to default the settings and try again:
AT#DELFLASH (wait for OK then power cycle and wait for modem to register)
AT#CONNECTIONSTART
AT#PINGREMOTE=”8.8.8.8″
AT#PING

If this doesn’t succeed, I recommend opening a support ticket.
If you open a support ticket, you may want to include a Tera Term log showing the above command sequence.

[Lonny Knudson]

Hi Chuck,
What happens if you issue the following command sequence using a terminal program?
AT#CONNECTIONSTART
AT#PINGREMOTE=”8.8.8.8″
AT#PING

If this sequence does not get a good response, I suggest opening a support ticket at http://support.multitech.com

[Lonny Knudson]

Hi Alex,
There are no controls built into the cellular radio that would allow an end user to modify antenna/receiver/transmitter gain. For stationary devices low signal issues are typically addressed by adjusting antenna placement, trying high gain or directional antennas, boosters/repeaters, etc…

[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, 5 months ago by Lonny Knudson.

[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

[Lonny Knudson]

Hi Lucas,
It may be normal for +CSQ to return 99,99 if the modem hasn’t registered yet. If the modem has a good SIM and antenna and cellular service is available, it should register without sending any AT commands (APN doesn’t need to be set).

Here are a couple of suggestions to resolve the ERROR response to +CREG:
The correct syntax for the +CREG query command is AT+CREG?
Issue the AT+CPIN? command to make sure the SIM is correctly installed.
If one of these suggestions don’t take care of the +CREG ERROR response, you may want to open a support ticket here:
http://support.multitech.com

[Lonny Knudson]

Hi Arjun,
If you are using more than 1 application (TCP Socket and FTP Client), I recommend disabling the persistent socket feature and managing the applications with your host system. You will need to stop the TCP listener (AT#LTCPSTOP=1) before starting a FTP session. If this dosen’t help you resolve the issue, please open a support ticket ( http://support.multitech.com ), in the support ticket it would be helpful to include a log showing the command sequence and modem responses when the problem occurs.

[Lonny Knudson]

Hi Matt,
There are 2 different registration queries, AT+CREG? and AT+CGREG?
Conventionally with 2G and 3G devices you could query +CREG? to determine that you have cell service. The LTE devices do not automatically attach at this layer like 2G and 3G modems do. However, they are configured to automatically attach to the data service which can be queried using the AT+CGREG? command. With the LTE modems it is recommended that you use AT+CGREG? as you would use AT+CREG? on 2G or 3G devices.

[Lonny Knudson]

Hi Matt,
The LTE modems don’t automatically attach at this layer when a network is found. Use AT+CGREG? to check for service instead.

[Author]

Posts