Issue -MTCDT-LVW2-210A – Verizon serial connection terminated after second
Home › Forums › Conduit: AEP Model › Issue -MTCDT-LVW2-210A – Verizon serial connection terminated after second
Tagged: MTCDT-LVW2, ppp, verizon
- This topic has 3 replies, 2 voices, and was last updated 7 years, 10 months ago by Lonny Knudson.
-
AuthorPosts
-
January 4, 2017 at 8:02 am #16203Jim BurnsParticipant
Hi folks,
I am new to the Conduit, but love the concept.
I am trying to get the MTCDT-LVW2 connected to the Verizon network.
I have followed the MultiTech developers manual to install the SIM and enable the cellular radio but I cannot get the PPP connection up.
I SSH’d into the Conduit and checked /var/log/messages and I see the messages below.
Is there a reason that I would get the ‘Serial connection established.’ message and then one (1) second later I get the Hangup (SIGHUP), Modem hangup, and Connection Terminated in quick succession?
Thanks for any leads,
Jim BurnsJan 4 08:13:06 mtcdt local2.info chat[6013]: info: Attempting Basic Radio Communication
Jan 4 08:13:06 mtcdt local2.info chat[6013]: send (AT^M)
Jan 4 08:13:06 mtcdt local2.info chat[6013]: expect (OK)
Jan 4 08:13:06 mtcdt local2.info chat[6013]: AT^M^M
Jan 4 08:13:06 mtcdt local2.info chat[6013]: OK
Jan 4 08:13:06 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:06 mtcdt local2.info chat[6013]: info: Checking if SIM is inserted
Jan 4 08:13:06 mtcdt local2.info chat[6013]: send (AT#SIMDET?^M)
Jan 4 08:13:06 mtcdt local2.info chat[6013]: expect (#SIMDET: 2,1)
Jan 4 08:13:06 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:06 mtcdt local2.info chat[6013]: AT#SIMDET?^M^M
Jan 4 08:13:06 mtcdt local2.info chat[6013]: #SIMDET: 2,1
Jan 4 08:13:06 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:06 mtcdt local2.info chat[6013]: info: Checking if SIM is locked
Jan 4 08:13:06 mtcdt local2.info chat[6013]: send (AT+CPIN?^M)
Jan 4 08:13:06 mtcdt local2.info chat[6013]: expect (READY)
Jan 4 08:13:06 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:06 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:06 mtcdt local2.info chat[6013]: OK^M
Jan 4 08:13:06 mtcdt local2.info chat[6013]: AT+CPIN?^M^M
Jan 4 08:13:06 mtcdt local2.info chat[6013]: +CPIN: READY
Jan 4 08:13:06 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:06 mtcdt local2.info chat[6013]: info: SIM was unlocked
Jan 4 08:13:06 mtcdt local2.info chat[6013]: info: Waiting for minimum signal strength
Jan 4 08:13:06 mtcdt local2.info chat[6013]: send (AT+CSQ^M)
Jan 4 08:13:07 mtcdt local2.info chat[6013]: expect (+CSQ: )
Jan 4 08:13:07 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:07 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:07 mtcdt local2.info chat[6013]: OK^M
Jan 4 08:13:07 mtcdt local2.info chat[6013]: AT+CSQ^M^M
Jan 4 08:13:07 mtcdt local2.info chat[6013]: +CSQ:
Jan 4 08:13:07 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:07 mtcdt local2.info chat[6013]: expect (99,99)
Jan 4 08:13:07 mtcdt local2.info chat[6013]: 24,6^M
Jan 4 08:13:07 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:07 mtcdt local2.info chat[6013]: OK^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: alarm
Jan 4 08:13:08 mtcdt local2.info chat[6013]: send (AT^M)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: expect (OK)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: AT^M^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: OK
Jan 4 08:13:08 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:08 mtcdt local2.info chat[6013]: send (AT^M)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: abort on (NO CARRIER)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: abort on (BUSY)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: abort on (ERROR)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: expect (OK)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: AT^M^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: OK
Jan 4 08:13:08 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:08 mtcdt local2.info chat[6013]: send (AT+CSQ^M)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: expect (OK)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: AT+CSQ^M^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: +CSQ: 24,6^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: OK
Jan 4 08:13:08 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:08 mtcdt local2.info chat[6013]: send (AT+CGDCONT=3,\”IPV4V6\”,\”internet\”^M)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: expect (OK)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: AT+CGDCONT=3,”IPV4V6″,”internet”^M^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: OK
Jan 4 08:13:08 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:08 mtcdt local2.info chat[6013]: send (ATDT*99***3#^M)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: expect (CONNECT)
Jan 4 08:13:08 mtcdt local2.info chat[6013]: ^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: ATDT*99***3#^M^M
Jan 4 08:13:08 mtcdt local2.info chat[6013]: CONNECT
Jan 4 08:13:08 mtcdt local2.info chat[6013]: — got it
Jan 4 08:13:08 mtcdt local2.info chat[6013]: send (^M)
Jan 4 08:13:08 mtcdt daemon.info pppd[1134]: Serial connection established.
Jan 4 08:13:08 mtcdt daemon.info pppd[1134]: Using interface ppp0
Jan 4 08:13:08 mtcdt daemon.notice pppd[1134]: Connect: ppp0 <–> /dev/modem_at0
Jan 4 08:13:09 mtcdt daemon.info pppd[1134]: Hangup (SIGHUP)
Jan 4 08:13:09 mtcdt daemon.notice pppd[1134]: Modem hangup
Jan 4 08:13:09 mtcdt daemon.notice pppd[1134]: Connection terminated.January 4, 2017 at 9:53 am #16205Lonny KnudsonBlockedHi 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.January 4, 2017 at 10:59 am #16206Jim BurnsParticipantHi Lonny,
Thanks for your help.
I carried out the steps above and waited four minutes after step 8 but sadly no joy (I still have ‘PPP is down’).
As requested I am putting the output of the AT+CGDCONT command I received below.
Thank you,
Jim B.AT+CGDCONT?
+CGDCONT: 1,”IPV4V6″,”vzwims”,””,0,0
+CGDCONT: 2,”IPV4V6″,”vzwadmin”,””,0,0
+CGDCONT: 3,”IPV4V6″,”internet”,””,0,0
+CGDCONT: 4,”IPV4V6″,”vzwapp”,””,0,0
+CGDCONT: 5,”IPV4V6″,””,””,0,0OK
January 4, 2017 at 11:54 am #16207Lonny KnudsonBlockedHi 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 -
AuthorPosts
- You must be logged in to reply to this topic.