AT#PING PING Command with MTSMC Cell Phone

[Chuck Sabol]

I want to verify my communications link from the MTSMC-EV3-IP Model Cell Phone and my remote server. I was hoping that the PING AT command would help me do this. I am not too sure what parameters to set.
I get a response like the following:

No answer from ‘xxx.xxx.xxx.xxx”

This happens even when I use a known IP (like the one for google.com).

Has anybody had any success with the PING AT command?

Regards,
Chuck Sabol

[Mike Fiore]

Hi Chuck,

It sounds like you have a SocketModem iCell.

http://www.multitech.com/brands/socketmodem-icell

Is that correct?

How are you interfacing to that device? Are you sure the PPP link is up before you try to ping?

Cheers,

Mike

[Chuck Sabol]

Hi Mike,
Thanks for responding to my post so quickly. I am interfacing to the MultiTech Development board with the iCell phone via a USB to Serial (COM6) device.
I am home now, but I will review the PPP (Point to Point) setup when I get to work on Monday. There seems to be some differences between using TCP and UDP.

I spent some time establishing the values for TCP (Server and Port) and also tried working with UDP (setting up the persistent socket parameters, etc.). The AT#VPING seems to have its own ideas about parameters. I am sure the AT#PING command will work on my development setup. I appreciate your help.

Regards,
Chuck

[Chuck Sabol]

Is there a sample application (written in VB, C or C#) to PING a remote server?

I am using a Serial-to-MTSMC-EV3-IP-N3 cell phone daughter board attached to the MTSMI-UDK Universal Development Kit.
A USB to Serial cable provides COM6 for communications with the MTSMI-UDK development board.

I am following the S000541, Version H Socket Modem/MTSMC-EV3 / Device Guide from MultiTech. The cell phone has been configured for use with Verizon (MTSMC-EV3-IP-N3).
I have been using the QueryDevice project in Visual Studion 2013.
I use the AT commands from S000457L (Universal IP AT Commands Reference Guide).

Regards,
Chuck

[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

[Chuck Sabol]

Hi Lonny,

Running the ping utility in a ‘DOS’ window is successful.
Running the command sequence you suggested in Tera Term results in the following:
No answer from “173.162.xxx.209

Running the sequence of commands from within the QueryDevice sample program provided by Multi-Tech results in the following (from the log file):
[10:52:02] OPEN DEVICE [ActiveComport Build 3.1.8.1203],
Device=[COM6], Baudrate=[9600],
settings=[D,D,D], HWFlowCtrl=[default],
SWFlowCtrl=[default],
result=[Error #0: Success]
[10:52:11] WRITE STRING: [ATE1]
[10:52:11] READ STRING : [ATE1]
[10:52:11] READ STRING : [0]
[10:52:35] WRITE STRING: [AT#CONNECTIONSTART]
[10:52:35] READ STRING : [AT#CONNECTIONSTART]
[10:52:39] READ STRING : [75.213.xxx.101]
[10:52:39] READ STRING : [3086]
[10:52:39] READ STRING : [PERSISTENT SOCKET START]
[10:52:40] READ STRING : [1028]
[10:54:16] WRITE STRING: [AT#PINGREMOTE=”173.162.xxx.209”]
[10:54:38] WRITE STRING: [AT#PING]
[10:55:23] CLOSE DEVICE

Perhaps it is time to open a support ticket?

Regards,
Chuck

[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.

[Chuck Sabol]

Hi Lonny,

After issuing the AT#DELFLASH
any other AT command results in a response consisting of a
series of ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ characters.

It seems that my Communication parameters (baud, bit, parity, stop) have been lost. I am unable to communicate with the MTSMI-UDK Universal Development Kit. Looks like I need to provision the MTSMC-EV3-IP cell phone again.

Regards,
Chuck

[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.

[Chuck Sabol]

Hi Lonny,

Thank you for your help.
I am now using 115,200 for Baud
Here are my results from the log for QueryDevice.
Actual value was changed to xxx was changed for public viewing.

[14:13:03] WRITE STRING: [AT#CONNECTIONSTART]
[14:13:03] READ STRING : [AT#CONNECTIONSTART]
[14:13:07] READ STRING : [75.213.230.30]
[14:13:07] READ STRING : [Ok_Info_GprsActivation]
[14:14:53] WRITE STRING: [AT#PINGREMOTE=”173.162.xxx.209″]
[14:14:53] READ STRING : [AT#PINGREMOTE=”173.162.xxx.209″]
[14:14:54] READ STRING : [OK]
[14:15:17] WRITE STRING: [AT#PING]
[14:15:17] READ STRING : [AT#PING]
[14:15:18] READ STRING : [No answer from “173.162.xxx.209”]
[14:15:18] READ STRING : [“173.162.xxx.209” is alive : time = 1175 ms]
[14:15:18] READ STRING : [“173.162.xxx.209” is alive : time = 164 ms]
[14:15:19] READ STRING : [“173.162.xxx.209” is alive : time = 188 ms]
[14:15:20] READ STRING : [“173.162.xxx.209” is alive : time = 111 ms]
[14:15:21] READ STRING : [OK]

Again, I thank you for your assistance.

Regards,
Chuck

[Author]

Posts