 |
|
 |
|
|
Technical Support FAQ
|
|
NotePager 32 & NotePager Pro
Technical Support
|
What is an init string ?
Different modems can't necessarily talk to each other
using their default settings. Modems use many different
settings and protocols. In order for two modems to communicate,
they must agree on many things such as speed, error correction,
compression algorithms, etc... By sending a modem init
string, you can control some of these parameters.
What do I need to put in my init string?
In general, the modems used by paging carriers run at
a speed from 300 to 2400 baud (1200 being the most common).
They don't typically use any form of error correction
or data compression protocols. In many cases,
if your modem tries to use either these protocols, your
modem will be unable to communicate with the paging
terminal's modem. In your init string you should
include settings to lock your modem's baud rate to that
of your carrier's modem, disable error correction protocols,
and disable data compression protocols. In addition
NotePage, Inc.'s software would like your modem to issue
English response codes (rather than numeric response
codes), and issue complete connection information.
Do all modems use the same init string?
No, many different modem manufacturers use their own
set of init strings. Init strings may even be different
between models by the same manufacturer.
My init string works with one carrier but not the
other.
You may need a different init string to connect to each
carrier. In general your init strings will be the same,
but not always.
What do I use for an initialization string ?
There is no easy answer to that question. Some modems
may need initialization strings to connect to some paging
carriers. If the modem keeps dialing and connecting,
but does not send the message, chances are a modem initialization
string is needed. Some common initialization strings
are below. If you have a less well known brand modem,
you may need to use the documentation with your modem
to create an init string.
| AT&FQ0V1X4&D2 |
Minimal settings. Works with most
1200 or 2400 baud modems |
| AT&FQ0V1X4&D2N0S37=5 |
Works with many 14.4 and 28.8 modems.
Additional codes forces a 1200 baud connection.
Use S37=6 for a 2400 baud connection |
| AT&FQ0V1X4&D2N0S37=5\N0%C0 |
Works with many 14.4 and 28.8 modems.
Additional codes turns off error correction and
data compression. |
| AT&F0Q0V1X4&D2&B1&K0&M0&N2 |
Works with USR 33.6 and 56 K modems.
Turns off error correction and data compression.
Forces a 1200 baud connection. Use &N3 for a
2400 baud connection. |
| AT&FQ0V1X4&D2N0+MS=B103 |
Works with some of the
newer winmodems. Set the baud rate to 300 when using
this string. |
Please note all '0' are zeros not "ohs"
|
I have a US Robotics
(3 Com) modem. I have tried the init string but still
get inconsistent results.
Some model US Robotics
modems have difficulty communicating with the computer
at low baud rates (i.e. under 9600 baud). Try setting
the baud rate on the carrier setup screen to 19200 and
using the init string given to lock the baud rate between
the modems to a lower rate.
The modem keeps
redialing and doesn't send the messages, with the detailed
log option turned on the log reads:
No ID=Received
or
Automatic TAP mode
not accepted
or
No '[p' received
This could be one of
two things. First, the phone number the program is dialing
does not connect to a paging terminal that accepts the
TAP protocol (in some countries TAP is not the standard
paging protocol). Second, your modem is not communicating
with the paging terminal's modem correctly. An modem initialization
string will usually solve this problem. See the above
discussion on initialization strings.
My modem does not
hang up after sending a message.
You may need to use
an init string (or a different one) with your modem.
How do I set up
NotePager 32?
The setup of NotePager
is pretty straight forward. After the file is downloaded,
copy it to a temporary directory (it's files will be
expanded here). Run the program... the file will decompress.
Next run the program that now exists called setup.exe.
It will walk you through the install. You will also
find a readme.doc file in this directory that explains
the initial settings needed to connect with your paging
carrier.
My pager
keeps receiving garbled messages, why?
Garbled messages
are caused by a low battery, poor reception, or a defective
paging unit.
NotePager
32 says the message was sent, but it is never received
on the pager, why?
If NotePager
is communicating that the message has been sent, it
means that the paging terminal has successfully confirmed
receipt of the message. If the message is not received,
you may be out of your paging coverage area (or in a
fringe area), your account may be incorrectly set up
by the carrier, or you may have an incorrect pin or
id number.
|
|
|
 |
|
|
