Getting Started With The NWK100

Introduction

The OnLogic NWK100 is based on the PCI Express Mini Card standard with a USB 2.0 interface and utilizes UBLOX TOBY-L200 Cellular Module.

Antenna RF Interfaces (Ant 1/Ant 2)

NWK100 is based on UBLOX TOBY-L200 module and provides two RF interfaces for connecting the external antennas:

The ANT1 represents the primary RF input/output for transmission and reception of LTE/3G/2G RF signals. The ANT1 pin of NWK100 has a nominal characteristic impedance of 50 Ω and must be connected to the primary Tx / Rx antenna through a 50 Ω transmission line to allow proper RF transmission and reception.

The ANT2 represents the secondary RF input for the reception of the LTE RF signals for the Down-Link MIMO 2 x 2 radio technology supported by NWK100 as required feature for LTE category 4 UEs, and for the reception of 3G RF signals for the Down-Link Rx diversity radio technology supported by NWK100 as additional feature for 3G DC-HSDPA category 24 UEs. The ANT2 pin of NWK100 has a nominal characteristic impedance of 50 Ω and must be connected to the secondary Rx antenna through a 50 Ω transmission line to allow proper RF reception.

Initial Set Up

The following instructions will vary by your OS. Find your OS below and follow the instructions listed.

AT&T

Windows 10

The NWK100 modem requires AT commands to configure it for use.

  1. First, you will need to determine which COM port is assigned to the NWK100. You can find this in the Device Manager. To do this:
    1. Open the Windows Device Manager from the Start menu.
    2. Open the Modems section.
    3. Right click the u-blox Modem device.
    4. Right-click Properties.
    5. On the Modem tab, the COM number is listed at the top.
  2. To address the modem, you will need an AT terminal program such as PuTTY. You can download this free and light-weight program here: https://the.earth.li/~sgtatham/putty/latest/w64/putty-64bit-0.71-installer.msi
  3. Open PuTTy and select Session, then Serial on the right side. Type “COMX” where X is the COM number you saw in the Device Manager. Set the Baud Rate to 115200, then click the Terminal setting on the left. Set both Local Echo and Local Line Edititing to Force On, then click Open. You will be presented with a terminal window. You can now enter AT commands from this window.
  4. We will now be configuring the modem and activating the Packet Data Protocol (PDP) context with the AT&T APN: *Note that the “broadband” configuration is the AT&T APN
    • AT+UBMCONF=1
    • AT+CFUN=4
    • AT+CGDCONT=1,”IP”,”broadband”
    • AT+UCGDFLT=1,”IP”,”broadband”
  5. Now set the modem back to full functionality:
    • AT+CFUN=1
    • AT+CGACT=1,1
  6. You can check the signal strength with:
    • AT+COPS?
  7. You should see 7 as one of the returned numbers. This indicates that it has an LTE data connection. You can now close the terminal window and proceed with setting up the connection within Windows.
  8. You can configure the connection in Windows Network manager. Open “Network and Sharing Center” and click on Local Area Connection (associated to RNDIS interface) for the NWK100 modem.
  9. Click on Properties.
  10. Search for “Internet Protocol Version 4 (TCP/IPv4)” and click on Properties.
  11. Check the Obtain an IP address automatically and Obtain DNS server address automatically option.

Windows 7

The NWK100 modem requires AT commands to configure it for use.

  1. First, you will need to determine which COM port is assigned to the NWK100. You can find this in the Device Manager. To do this:Open the Windows Device Manager from the Start menu.
    1. Open the Modems section.
    2. Right click the u-blox Modem device.
    3. Right-click Properties.
    4. On the Modem tab, the COM number is listed at the top.
  2. To address the modem, you will need an AT terminal program such as PuTTY. You can download this free and light-weight program here: https://the.earth.li/~sgtatham/putty/latest/w64/putty-64bit-0.71-installer.msi
  3. Open PuTTy and select Session, then Serial on the right side. Type “COMX” where X is the COM number you saw in the Device Manager. Set the Baud Rate to 115200, then click the Terminal setting on the left. Set both Local Echo and Local Line Edititing to Force On, then click Open. You will be presented with a terminal window. You can now enter AT commands from this window.
  4. You should see 7 as one of the returned numbers. This indicates that it has an LTE data connection.
  5. You can now close the terminal window and proceed with setting up the connection within Windows.
  6. You can configure the connection in Windows Network manager. Open “Network and Sharing Center” and click on Local Area Connection (associated to RNDIS interface) for the NWK100 modem.
  7. Click on Properties.
  8. Search for “Internet Protocol Version 4 (TCP/IPv4)” and click on Properties.
  9. Check the Obtain an IP address automatically and Obtain DNS server address automatically option.

Ubuntu 16.04

  1. Open the Ubuntu terminal (Control+Alt+T at the desktop).
  2. Confirm that the modem manager is NOT installed – run “sudo apt-get remove modemmanager” to uninstall it.
  3. Open the AT terminal by running “minicom -s”. If minicom is not installed you may install it using “sudo apt-get install minicom”.
  4. Select “serial port setup” from the menu and configure it with:
    • Serial Device: /dev/ttyACM0
    • Bps/Par/Bits: 38400 8N1
    • Hardware Flow Control: No
    • Software Flow Control: No
  5. Press enter to exit the configuration menu, then select Exit to enter the terminal.
  6. In the terminal window, type ATE1 and press Enter. This configures the modem to “echo” back what is sent, so you can see what you’re typing in the window.
  7. You can now configure the modem for maximum throughput using the follow command: *Note: If the modem isn’t showing up in Ubuntu, the the connection may be blacklisted and will need to be removed. OnLogic blacklists the 4G driver to prevent updates from being ran over 4G during the Out Of Box Experience.
    • at+udconf=67,0
  8. Follow these steps to remove the blacklist:
    1. From a terminal, remove the blackist.local.conf file
      • sudo rm /etc/modprobe.d/blacklist.local.conf

Other Useful Resources

For more questions contact Technical Support at: (802)-861-2300 ext 2.

Updated on February 12, 2020

Was this article helpful?

Need Additional Support?
Can’t find the answer you’re looking for? Don’t worry, we’re here to help!
Contact Support