Home Page Forums Raspberry Pi Shields QMI Interface with 3G-4G/LTE Base Shield v2

This topic contains 4 replies, has 2 voices, and was last updated by  Saeed 8 months, 1 week ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #36959

    jcook23
    Participant

    I’m following this tutorial: QMI Base Shield v2

    It seems the modem can obtain an IP but running quectel-CM displays “Too few arguments” and then stops. Below are the steps I’ve taken. Any help is appreciated. See step 10 for “Too few arguments”

    1. sudo apt-get update
    2. sudo apt-get install raspberrypi-kernel-headers
    raspberrypi-kernel-headers is already the newest version (1.20190215-1).
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    3. ls /usr/src
    linux-headers-4.14.98+ linux-headers-4.14.98-v7+ sense-hat
    4. https://github.com/Hexxeh/rpi-firmware/commits
    kernel: Bump to 4.14.98
    hash: a08ece3d48c3c40bf1b501772af9933249c11c5b
    5. sudo rpi-update a08ece3d48c3c40bf1b501772af9933249c11c5b
    Your firmware is already up to date
    6. wget https://raw.githubusercontent.com/sixfab/Sixfab_RPi_3G-4G-LTE_Base_Shield/master/tutorials/QMI_tutorial/qmi_install.sh
    ‘qmi_install.sh’ saved [1199/1199]
    7. sudo chmod +x qmi_install.sh
    8. sudo ./qmi_install.sh
    rebooted
    9. cd ./files/quectel-CM
    10. sudo ./quectel-CM -s vzwinternet
    [03-10_09:21:48:050] WCDMA&LTE_QConnectManager_Linux&Android_V1.1.45
    [03-10_09:21:48:051] ./quectel-CM profile[1] = vzwinternet///0, pincode = (null)
    [03-10_09:21:48:052] Find /sys/bus/usb/devices/1-1.2 idVendor=2c7c idProduct=0125
    [03-10_09:21:48:053] Find /sys/bus/usb/devices/1-1.2:1.4/net/wwan0
    [03-10_09:21:48:053] Find usbnet_adapter = wwan0
    [03-10_09:21:48:053] Find /sys/bus/usb/devices/1-1.2:1.4/usbmisc/cdc-wdm0
    [03-10_09:21:48:054] Find qmichannel = /dev/cdc-wdm0
    [03-10_09:21:48:083] cdc_wdm_fd = 7
    [03-10_09:21:48:737] Get clientWDS = 19
    [03-10_09:21:48:769] Get clientDMS = 1
    [03-10_09:21:48:801] Get clientNAS = 3
    [03-10_09:21:48:833] Get clientUIM = 2
    [03-10_09:21:48:865] Get clientWDA = 1
    [03-10_09:21:48:897] requestBaseBandVersion EC25VFAR02A11M4G
    [03-10_09:21:49:025] requestGetSIMStatus SIMStatus: SIM_READY
    [03-10_09:21:49:025] requestSetProfile[1] vzwinternet///0
    [03-10_09:21:49:089] requestGetProfile[1] vzwinternet///0
    [03-10_09:21:49:122] requestRegistrationState2 MCC: 311, MNC: 480, PS: Attached, DataCap: LTE
    [03-10_09:21:49:153] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
    [03-10_09:21:49:217] requestRegistrationState2 MCC: 311, MNC: 480, PS: Attached, DataCap: LTE
    [03-10_09:21:49:248] requestSetupDataCall WdsConnectionIPv4Handle: 0x870f4060
    [03-10_09:21:49:312] requestQueryDataCall IPv4ConnectionStatus: CONNECTED
    [03-10_09:21:49:345] ifconfig wwan0 up
    [03-10_09:21:49:354] busybox udhcpc -f -n -q -t 5 -i wwan0
    [03-10_09:21:49:362] udhcpc (v1.22.1) started
    Too few arguments.
    [03-10_09:21:49:584] Sending discover…
    [03-10_09:21:49:674] Sending select for 100.76.159.201…
    [03-10_09:21:49:764] Lease of 100.76.159.201 obtained, lease time 7200
    Too few arguments.
    11. ping https://www.sixfab.com
    https://www.sixfab.com ping statistics —
    9 packets transmitted, 0 received, 100% packet loss, time 8355ms
    12. ifconfig wwan0
    wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1428
    inet 100.76.159.201 netmask 255.255.255.252 broadcast 100.76.159.203
    inet6 fe80::514b:6004:f048:bcc6 prefixlen 64 scopeid 0x20<link>
    ether 52:9e:0a:05:46:0b txqueuelen 1000 (Ethernet)
    RX packets 45 bytes 6878 (6.7 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 265 bytes 44532 (43.4 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    13. route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default 100.76.159.202 0.0.0.0 UG 204 0 0 wwan0
    100.76.159.200 0.0.0.0 255.255.255.252 U 204 0 0 wwan0
    14. sudo route del default THEN sudo route add default wwan0
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    default 0.0.0.0 0.0.0.0 U 0 0 0 wwan0
    100.76.159.200 0.0.0.0 255.255.255.252 U 204 0 0 wwan0
    15. ping https://www.sixfab.com
    https://www.sixfab.com ping statistics —
    9 packets transmitted, 0 received, 100% packet loss, time 8325ms

    #36960

    jcook23
    Participant

    Update after opening issue with data provider Link: RevX

    They are reporting the modem isn’t in Verizon’s certified device registry. I’ve verified the IMEI matches what is on the modem.

    Response from RevX:
    After closer inspection of this activation request, the Verizon network is reporting this device has not been uploaded into the certified device registry.

    861107034716184 – REQUEST_FAILED.Device is not listed with the Verizon Wireless network.

    Can you verify the IMEI is correct and try activating it again? If that fails, you may need to contact the manufacturer about the issue. Verizon will not allow equipment to be activated which is not listed in their device management database.

    • This reply was modified 8 months, 2 weeks ago by  jcook23.
    #36977

    Saeed
    Moderator

    If Verizon says “IMEI does not exist in Verizon system”, it does not mean those IMEIs were not registered as module but it does mean those IMEIs were not registered again as device yet.

    This is Verizon specific procedure to prevent from accessing uncertified device to VzW network, even if pre-certified module is used on the customer device.

    Once module is approved, customer is responsible to register IMEIs on customer’s OD portal (as device), to activate the devices on VzW network.

    #37003

    jcook23
    Participant

    Thank you for the response. Currently working with Quectel. I will update any findings here.

    #37036

    Saeed
    Moderator

    Thank you for your feedback

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.