CS-3G Digital Transceiver Kits (including the COM111 modem)
40
Connect to the logger with the Device configurator program (Devconfig).
Select the terminal tab, then press the enter key several times until the logger
terminal prompt is return, e.g. CR1000>. At this point type “W” and press
enter to enter the “sniffing” mode. Select the option by number from the
menu for the “IPTrace”. Then enter a valid trace code to see the level of
information needed, entering “2” will give the basic information needed to
diagnose a fault with the initial PPP negotiation.
Click on Start export and enter a filename (end it in .txt). Connect for some
minutes or long enough to capture enough data to cover the problematic
event. When done click on end export.
You can exit the IPTrace sniffer mode by pressing ESC.
This process will capture the IPtrace log in the file specified. You can open
the file in a text editor and review the information there. The information in
that file can be interpreted by many familiar with PPP connections and
sometimes errors are obvious, e.g. mistyped dial strings. For expert
diagnosis the file can be emailed to your support contact at Campbell
Scientific who should be able to work out what is the problem and the
solution for it.
11.5 GPRS fault finding
– when using the modem TCP/IP
stack
The following steps are some basic steps to check why a connection does not
work.
Following guidance above to check the modem is connected to the
network and has reasonable signal strength. You can do this by
using the Mobile Data Assistant program and run the Diagnostics
option. This will show the signal strength, network connection and
whether an IP address has been allocated to the modem. If the
address has not been allocated please try setting up the modem
again making sure the APN, username and password are entered
correctly.
If an IP address has been allocated you can check a system setup for
call-back operation by running Loggernet and use the Logtool to
check the modem is opening the incoming socket as expected. If
not, check Loggernet, any firewall software and any routers are
configured correctly to allow the incoming connections on the
expected socket. This can be verified using a PC on the public
internet to Telnet into the IP and socket you are going trying to use.
You should see this causes a connection attempt to be registered by
Loggernet which you can see by watching the Logtool screens.
Fault finding a non-working modem with a fixed IP address is
slightly easier as the modem will still be in command mode whilst
waiting for a connection. You can also use a second PC and the
Telnet program to connect to the socket you have configured to
validate if the connection is open or not. If the modem has a fixed
IP address and is on the public internet OR your PC is connected to
the same private IP network as the modem you can also use the
standard Ping command to check routing to the modem.
The modem also supports two advanced methods of remote
debugging and reconfiguration. This can be done either via sending