| View previous topic :: View next topic |
| Author |
Message |
HFD_AA
Joined: 22 Mar 2019
Posts: 5
|
 Posted: Fri Mar 22, 2019 10:52 am Post subject: Dell External USB Modem Connection Issues |
 |
|
I am attempting to get a back-up laptop running in case we have issues with our main laptop. Laptop 1 connects no problems with it's internal modem and sends messages.
The following is the log file from the attempt to send a message using Laptop 2.
22/03/2019 10:58:37 AM ========================================
22/03/2019 10:58:37 AM Start connection to carrier: HES_Zetron_2100
22/03/2019 10:58:37 AM Connect using TAP protocol
22/03/2019 10:58:37 AM Setting communication parameters (300,e,7,1)
22/03/2019 10:58:38 AM Attempting to reset modem
22/03/2019 10:58:40 AM Sent:AT<CR>
22/03/2019 10:58:41 AM Received:<CR><LF>OK<CR><LF>
22/03/2019 10:58:41 AM Modem reset
22/03/2019 10:58:41 AM Attempting to send dialer init string
22/03/2019 10:58:41 AM Sent:atz<CR>
22/03/2019 10:58:42 AM Received:<CR><LF>OK<CR><LF>
22/03/2019 10:58:43 AM Dialer init string sent
22/03/2019 10:58:43 AM Attempting to send carrier init string
22/03/2019 10:58:43 AM Sent:AT&FQ0V1X4&D2+MS=V22,0<CR>
22/03/2019 10:58:43 AM Received:<CR><LF>OK<CR><LF>
22/03/2019 10:58:44 AM Carrier init string sent
22/03/2019 10:58:44 AM Dialing carrier
22/03/2019 10:58:44 AM Sent:ATDT99053044592,<CR>
22/03/2019 10:58:52 AM Waiting for connection
22/03/2019 10:59:19 AM Received:<CR><LF>CONNECT<CR><LF>
22/03/2019 10:59:19 AM Connected to carrier
22/03/2019 10:59:19 AM Waiting for protocol initialization
22/03/2019 10:59:23 AM Sent:<CR>
22/03/2019 10:59:26 AM Sent:<CR>
22/03/2019 10:59:31 AM Sent:<CR>
22/03/2019 10:59:36 AM Sent:<CR>
22/03/2019 10:59:37 AM Received:ID=
22/03/2019 10:59:37 AM TAP protocol detected
22/03/2019 10:59:37 AM Sent:<ESC>PG1<CR>
22/03/2019 10:59:48 AM Received:}<SUB><ETB><CR><LF>NO CARRIER<CR><LF>
22/03/2019 10:59:48 AM Sent:<ESC>PG1<CR>
22/03/2019 10:59:58 AM Received:<ESC>PG1<CR>
22/03/2019 10:59:58 AM Sent:<ESC>PG1<CR>
22/03/2019 11:00:08 AM Received:<ESC>PG1<CR>
22/03/2019 11:00:08 AM Attempting to hang up modem
22/03/2019 11:00:11 AM Sent:AT<CR>
22/03/2019 11:00:11 AM Received:<CR><LF>OK<CR><LF>
22/03/2019 11:00:11 AM Modem hung up
22/03/2019 11:00:11 AM Carrier retry limit reached. Marking pending messages as bad
22/03/2019 11:00:11 AM FAILED Stn:10 To:led_sign Frm:paging Msg:Testing 003
Modem is a "Conexant USB CX93010 ACF Modem".
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4387
|
| Posted: Fri Mar 22, 2019 11:01 am Post subject: |
|
|
That's odd, you have it configured for 300 baud but the init string is configured for 1200 baud. If you would, change the init string from this:
AT&FQ0V1X4&D2+MS=V22,0
to this:
AT&FQ0V1X4&D2+MS=B103
Give that a try and let us know if it goes through, please. |
|
| Back to top |
|
HFD_AA
Joined: 22 Mar 2019
Posts: 5
|
| Posted: Fri Mar 22, 2019 11:28 am Post subject: |
|
|
Thanks for the quick reply but that doesn't seem to work as I don't get the received id from the carrier.
22/03/2019 12:11:15 PM ========================================
22/03/2019 12:11:15 PM Start connection to carrier: HES_Zetron_2100
22/03/2019 12:11:15 PM Connect using TAP protocol
22/03/2019 12:11:15 PM Setting communication parameters (300,e,7,1)
22/03/2019 12:11:16 PM Attempting to reset modem
22/03/2019 12:11:18 PM Sent:AT<CR>
22/03/2019 12:11:19 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:11:19 PM Modem reset
22/03/2019 12:11:19 PM Attempting to send dialer init string
22/03/2019 12:11:19 PM Sent:atz<CR>
22/03/2019 12:11:20 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:11:20 PM Dialer init string sent
22/03/2019 12:11:20 PM Attempting to send carrier init string
22/03/2019 12:11:20 PM Sent:AT&FQ0V1X4&D2+MS=B103<CR>
22/03/2019 12:11:21 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:11:22 PM Carrier init string sent
22/03/2019 12:11:22 PM Dialing carrier
22/03/2019 12:11:22 PM Sent:ATDT99053044592,<CR>
22/03/2019 12:11:30 PM Waiting for connection
22/03/2019 12:11:39 PM Received:<CR><LF>CONNECT<CR><LF>
22/03/2019 12:11:40 PM Connected to carrier
22/03/2019 12:11:40 PM Waiting for protocol initialization
22/03/2019 12:11:44 PM Sent:<CR>
22/03/2019 12:11:47 PM Sent:<CR>
22/03/2019 12:11:52 PM Sent:<CR>
22/03/2019 12:11:57 PM Sent:<CR>
22/03/2019 12:12:03 PM Attempting to hang up modem
22/03/2019 12:12:06 PM Sent:AT<CR>
22/03/2019 12:12:07 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:12:07 PM Modem hung up
22/03/2019 12:12:07 PM Carrier retry limit reached. Marking pending messages as bad
22/03/2019 12:12:07 PM FAILED Stn:10 To:led_sign Frm:paging Msg:Testing once again
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4387
|
| Posted: Fri Mar 22, 2019 11:31 am Post subject: |
|
|
Hm... interesting, the modem is dialing and the terminal is responding but after the initial "CONNECT" response, you stop receiving any communication from the terminal. Usually, that's a communication parameters mismatch.
If you would, try resetting the baud rate to 1200 and the init string to (auto), then try to send a message and let's see if it goes through. |
|
| Back to top |
|
HFD_AA
Joined: 22 Mar 2019
Posts: 5
|
| Posted: Fri Mar 22, 2019 11:45 am Post subject: |
|
|
Tried with the <auto> and basically got the same results.
22/03/2019 12:29:23 PM ========================================
22/03/2019 12:29:23 PM Start connection to carrier: HES_Zetron_2100
22/03/2019 12:29:23 PM Connect using TAP protocol
22/03/2019 12:29:23 PM Setting communication parameters (1200,e,7,1)
22/03/2019 12:29:24 PM Attempting to reset modem
22/03/2019 12:29:26 PM Sent:AT<CR>
22/03/2019 12:29:26 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:29:27 PM Modem reset
22/03/2019 12:29:27 PM Attempting to send dialer init string
22/03/2019 12:29:27 PM Sent:atz<CR>
22/03/2019 12:29:28 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:29:28 PM Dialer init string sent
22/03/2019 12:29:28 PM Auto detecting carrier init string
22/03/2019 12:29:28 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N2<CR>
22/03/2019 12:29:32 PM Received:<CR><LF>ERROR<CR><LF>
22/03/2019 12:29:32 PM Sent:AT&FQ0V1X4&D2N0+MS=V22,0<CR>
22/03/2019 12:29:35 PM Received:<CR><LF>ERROR<CR><LF>
22/03/2019 12:29:35 PM Sent:AT&FQ0V1X4&D2N0+MS=V22<CR>
22/03/2019 12:29:38 PM Received:<CR><LF>ERROR<CR><LF>
22/03/2019 12:29:38 PM Sent:AT&FQ0V1X4&D2+MS=V22,0<CR>
22/03/2019 12:29:39 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:29:39 PM Attempting to send carrier init string
22/03/2019 12:29:39 PM Sent:AT&FQ0V1X4&D2+MS=V22,0<CR>
22/03/2019 12:29:40 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:29:40 PM Carrier init string sent
22/03/2019 12:29:40 PM Dialing carrier
22/03/2019 12:29:40 PM Sent:ATDT99053044592,<CR>
22/03/2019 12:29:48 PM Waiting for connection
22/03/2019 12:30:12 PM Received:<CR><LF>CONNECT 1200<CR><LF>
22/03/2019 12:30:12 PM Connected to carrier
22/03/2019 12:30:12 PM Waiting for protocol initialization
22/03/2019 12:30:16 PM Sent:<CR>
22/03/2019 12:30:19 PM Sent:<CR>
22/03/2019 12:30:24 PM Sent:<CR>
22/03/2019 12:30:29 PM Sent:<CR>
22/03/2019 12:30:30 PM Received:ID=
22/03/2019 12:30:30 PM TAP protocol detected
22/03/2019 12:30:30 PM Sent:<ESC>PG1<CR>
22/03/2019 12:30:41 PM Received:pI<22><CR><LF>NO CARRIER<CR><LF>
22/03/2019 12:30:41 PM Sent:<ESC>PG1<CR>
22/03/2019 12:30:51 PM Received:<ESC>PG1<CR>
22/03/2019 12:30:51 PM Sent:<ESC>PG1<CR>
22/03/2019 12:31:02 PM Received:<ESC>PG1<CR>
22/03/2019 12:31:02 PM Attempting to hang up modem
22/03/2019 12:31:04 PM Sent:AT<CR>
22/03/2019 12:31:04 PM Received:<CR><LF>OK<CR><LF>
22/03/2019 12:31:04 PM Modem hung up
22/03/2019 12:31:04 PM Carrier retry limit reached. Marking pending messages as bad
22/03/2019 12:31:04 PM FAILED Stn:10 To:led_sign Frm:paging Msg:Testing once again
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4387
|
| Posted: Fri Mar 22, 2019 11:52 am Post subject: |
|
|
Interesting, it got further in the communication sequence with the terminal this time. The program eventually did receive a response to the initiating character in the TAP sequence (<CR>, which stands for a carriage return) and the terminal responded with the appropriate ID= to initiate the communication. However, as soon as NotePager Pro passed the next command in the TAP sequence (<ESC>PG1<CR>), the terminal responded with a few non-sensical characters (pI<22>) and then terminated the connection with "NO CARRIER" response.
If you would, leave the baud rate at 1200 but let's try the 300 baud init string:
AT&FQ0V1X4&D2+MS=B103
If that doesn't work, try using this variant of the 1200 baud init string:
AT&FQ0V1X4&D2+MS=V22
If that doesn't work, try setting the baud rate to 9600 and use this init string:
AT&FQ0V1X4&D2+MS=V32 |
|
| Back to top |
|
HFD_AA
Joined: 22 Mar 2019
Posts: 5
|
| Posted: Fri Mar 22, 2019 2:25 pm Post subject: |
|
|
I tried all of your suggestions, plus some more. The closest I get is in the log files already posted. For some reason, this modem is sending the "Sent: <CR>" 3 or 4 times compared to the once of Laptop 1.
Laptop 1 gives me the following:
********************************
22/03/2019 12:22:09 PM Received:<CR><LF>CONNECT 300 NoEC<CR><LF>
22/03/2019 12:22:09 PM Connected to carrier
22/03/2019 12:22:09 PM Waiting for protocol initialization
22/03/2019 12:22:13 PM Sent:<CR>
22/03/2019 12:22:14 PM Received:ID=
22/03/2019 12:22:14 PM TAP protocol detected
22/03/2019 12:22:14 PM Sent:<ESC>PG1<CR>
22/03/2019 12:22:16 PM Received:logon granted<LF><CR><ACK><CR><CR><ESC>[p<CR><CR>
22/03/2019 12:22:16 PM Received:logon granted<LF><CR><ACK><CR><CR><ESC>[p<CR><CR>
22/03/2019 12:22:16 PM Automatic TAP mode accepted
********************************
Laptop 1 is using an internal modem (older laptop...) and Laptop 2 is using an external Dell USB modem. But you can see Laptop 1 just sends the one carriage return and then receives the ID=.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4387
|
| Posted: Mon Mar 25, 2019 11:15 am Post subject: |
|
|
It looks like the best init string so far is:
AT&FQ0V1X4&D2+MS=V22,0
close but not quite.
Give these a try and see if any work better:
AT&FQ0V1X4&D2+MS=V22
AT&FQ0V1X4&D2N0+MS=1,0
AT&FQ0V1X4&D2N0+MS=1
AT&FQ0V1X4&D2+MS=1,0
AT&FQ0V1X4&D2+MS=1
AT&FQ0V1X4&D2N0S37=5\N0%C0
AT&FQ0V1X4&D2S37=5\N0%C0
AT&FQ0V1X4&D2N0S37=5
AT&FQ0V1X4&D2S37=5
AT&FQ0V1X4&D2
AT&F0
AT&F
Some modern modems have a really hard time connecting to those old slower baud modes. It's entirely possible that the Dell modem simply isn't going to communicate reliably with the Zetron's modem.
Do you have any different brand / model modems you can try?
Set the init string back to (auto) if you switch modems. |
|
| Back to top |
|
HFD_AA
Joined: 22 Mar 2019
Posts: 5
|
| Posted: Mon Mar 25, 2019 11:24 am Post subject: |
|
|
I'll try those. I have a feeling that, like you mentioned, the new Dell doesn't like to talk with the older modems or vice versa. I have been asking around to see if I could find an older modem to try but not a lot of people are using them any more.
I'll keep you updated.
Thanks for the help.
|
|
| Back to top |
|
|
