Changes between Version 17 and Version 18 of wireless/modem/AMITMDG

Timestamp:

09/20/2022 11:01:52 PM (2 years ago)

Author:

Ryan Erbstoesser

Comment:

update script for modem

wireless/modem/AMITMDG

@@ -1 @@
-= Amit MDG100 and MGD200
+[[PageOutline]]
+
+= Amit MDG100 and MGD200 Cellular Modem
 
 MDG100 and MGD200 are designed as a socket modem using a mini-PCIe form factor via USB 2.0 interface, perfect for use with Gateworks SBC's. This product has cellular capability with WCDMA and LTE Cat4 and also support GNSS receiver for location information. The device offers an OS-ready NIC interface (Option1 driver in Linux) and a friendly web-based GUI for parameter setting and status checking.  Best of all it's PTCRB certified as an end device so no additional testing is required by ATT/Verizon! 
+
+MDG200 is a Cat-4 LTE (150Mbps DL, 50Mbps UL) modem.
 
 Please consult sales for specific certifications and part SKUs. The MDG100 and MDG200 are the same systems with the following differences:
@@ -60 +64 @@
 The Gateworks board is incapable of displaying when used in a headless configuration.  The Amit modem requires some configuration using it's webUI, in order to do this from the board port forwarding is required.  
 
-== Gain Access to the Amit webUI
+= Software
+== AT Commands and Script
+
+Gateworks has put together a script that allows to easily reconfigure the MDG200 modem to be configurable with modem manager in AT mode. The only dependency for this script is that you have curl installed on your system (first command run here). 
+
+The base OS for this is the Ubuntu 20.04 system that we ship as the default image on our product. This script also assumes the modem is in the factory reset state. You can simply reset a MDG200 to the factory reset by depressing the button on the modem for >6 seconds while powered on, we have found we needed to wait 30 seconds or so after doing this for the factory defaults to be set correctly.
+
+The script logs into the web ui on the device, sets the password if needed (required on first login), set the mode to "modem" mode, sets the sim selection to the external sim (on the GW board), and set AT_NMEA mode then reboots the device.
+
+Here are the commands run in order (assuming attached script is on the board at /root/init_mdg200.sh):
+
+{{{
+apt-get install -y curl
+modprobe option
+echo 0x5c6 0x90b3 > /sys/bus/usb-serial/drivers/option1/new_id
+ifconfig usb0 up
+dhclient usb0
+/root/init_mdg200.sh
+}}}
+
+After the command runs, the modem reboots and re-initializes into modem modem with the AT interface exposed that modemmanager can then latch on to. This takes 30-45 seconds to complete to the point modem manager can then communicate with it. From there, I was simply able to do the following to gain internet activity.
+
+{{{
+mmcli -L (to get the modem number)
+mmcli -m <insert modem number> --simple-connect="apn=hologram"
+ifconfig usb0 up
+dhclient usb0
+ping 8.8.8.8
+}}}
+
+
+The modprobe of the option module and the "echo" command will need to be done on init every boot, but the init_mdg200.sh should only need to be done once during provisioning.
+
+[http://trac.gateworks.com/attachment/wiki/wireless/modem/AMITMDG/MDG100%20work%20on%20Linux.pdf This] document explains how to use the AMIT modem with AT commands if you prefer to avoid the WebUI. 
+
+== Amit webUI
 
 Install nftables:
@@ -93 +132 @@
 }}}
 
-== Configure the modem using the WebUI
+=== Configure the modem using the WebUI
 
 Acquire the ip address of eth0 (not the modem).  Using a workstation on the same subnet, open a browser then enter the ip address of eth0 on the Gateworks SBC. Login using username "admin", password "admin".
@@ -173 +212 @@
 }}}
 
-= AT Commands
-
-[http://trac.gateworks.com/attachment/wiki/wireless/modem/AMITMDG/MDG100%20work%20on%20Linux.pdf This] document explains how to use the AMIT modem with AT commands if you prefer to avoid the WebUI. 
+