GPy with Hologram.io SIM

tlanier

@tealbrains said in GPy with Hologram.io SIM:

Thanks for the input.

I think the trick to get the code to be properly formatted is to surround it with with three back-ticks (key to left of the "1" key). See a better description at (https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) under the section titled "Code and Syntax Highlighting".

Looking at your code I'm not sure what I should use for the send_at_cmd_pretty('AT!="addscanfreq band=28 dl-earfcn=9410"') command. That looks like a region specific setting.

tlanier

@jmarcelino

One interesting piece of information is that the AT+CFUN=0 or AT_CFUN=1 commands do not return an "OK" response from the modem. The commands configure the control of the LED according to the manual.

jmarcelino

@nathanh said in GPy with Hologram.io SIM:

For what it is worth and not trying to take this off the current topic/carrier. But from my attempts at trying to use my FiPy on Telstra where I am under full coverage, I also get the 2,4 result from CEREG but it will also sometimes connect (for a time before it crashes).

For Telstra/Australia you need to set the correct EARFCN (with 'AT!="addscanfreq band=28 dl-earfcn=9410"'). For the US the modem knows the Verizon network already so you don't need to.

@tlanier said in GPy with Hologram.io SIM:

One interesting piece of information is that the AT+CFUN=0 or AT_CFUN=1 commands do not return an "OK" response from the modem. The commands configure the control of the LED according to the manual.

I'm not sure which manual you're following but on the one we provide CFUN is definitely used to enable/disable the radio: see "2.4 Set Phone Functionality: +CFUN:".

nathanh

@jmarcelino said in GPy with Hologram.io SIM:

For Telstra/Australia you need to set the correct EARFCN (with 'AT!="addscanfreq band=28 dl-earfcn=9410"'). For the US the modem knows the Verizon network already so you don't need to.

Which is what we are using and documented in the several Telstra posts on the forum and are still waiting on you/Pycom to refer back from meeting with Telstra as @daniel indicated on this thread (https://forum.pycom.io/topic/2769/telstra-lte-cat-m-working-on-fipy-just/21)

My point was that while the report of 2,4 from CEREG typically indicates no coverage, the actual reason according to the documentation is unknown error and even if it was lack of coverage it did not make sense since I could also get connectivity randomly in the same location with the same device, and the signal strength reporting as good/excellent when it did connect. Which in my mind could potentially indicate other issues with how the modem itself communicates on different networks.

tlanier

@jmarcelino
Sorry, my mistake. I was reading the description of the AT+SQNLED=<mode> command (see below) and thought it was describing the purpose of the AT+CFUN command instead of describing how the LED behaved with the different CFUN values.

From manual:

This command configures the control of light of a connected LED. The mode
setting is persistent after reboot.
The LED is turned on only when AT+CFUN=1 or 4. It is turned off when
AT+CFUN=0.
LED is steadily turned on when the ME is registered to the network and either
awake or in power saving state. LED flashes when the ME is registered to the
network and either awake or in power saving state. In this mode, the duration
of flashing means various states, listed below:
• AT+CFUN=0 or 4. The ME is stopped or in Airplane mode. The LED is
permanently turned off.
• AT+CFUN=1. LTE PS data transfer. The LED is permanently turned on.
• AT+CFUN=1. The ME is registered to a network, No call, no data transfer
(in RRC Idle). The LED blinks (typically 1280 ms on, 3840 ms off).
• AT+CFUN=1. Limited Network Service (no SIM, no PIN, network search).
The LED blinks (typically 500 ms on, 500 ms off).
• AT+CFUN=1. The ME is in deep SLEEP (eDRX or PSM). The LED is permanently
turned off.

tlanier

@jmarcelino
Below is the code I'm going to use in the GPy plugged into my car USB port. The LED will show me the attach/connection state. This evening I plan to drive to multiple locations to see if I can make it work.

import pycom
import socket
import ssl
import sys
import time
from network import LTE

# send AT command to modem and display response
def at(cmd):
    print("modem command: {}".format(cmd))
    response = lte.send_at_cmd(cmd).split('\r\n')
    for line in response:
        print(line)

#####################################################################
print("CAT M1 Test - V0.2")

print("disable MicroPython contorl of LED")
pycom.heartbeat(False)
pycom.rgbled(0xFFFFFF)  # White

print("instantiate LTE object")
lte = LTE(carrier="verizon")
print("delay 4 secs")
time.sleep(4.0)

if lte.isattached():
    print("LTE was already attached, disconnecting...")
    lte.disconnect()
    lte.detach()
    print("resetting modem...")
    lte.reset()
    print("delay 5 secs")
    time.sleep(5.0)

# using hologram SIM
at('AT+CGDCONT=1,"IP","hologram"')

# enable network registration and location information unsolicited result code
# +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>]]
at('AT+CEREG=2')

print("full functionality level")
at('AT+CFUN=1')
time.sleep(1.0)

print("attempt to attach cell modem to base station...")
lte.attach()
i = 0
while not lte.isattached():
    i = i + 1
    print("not attached: {} secs".format(i))

    if (i % 2 == 0):
        pycom.rgbled(0xFF0000)  # Red
    else:
        pycom.rgbled(0x000000)  # Off

    # get EPS Network Registration Status:
    # 0 - not registered
    # 1 - registered, home network
    # 2 - not registered, but searching...
    # 3 - registration denied
    # 4 - unknown (out of E-UTRAN coverage)
    # 5 - registered, roaming
    at('AT+CEREG?')
    time.sleep(1)

print("connect: start a data session and obtain an IP address")
lte.connect()
i = 0
while not lte.isconnected():
    i = i + 1
    print("not connected: {}".format(i))

    if (i % 2 == 0):
        pycom.rgbled(0x00FF00)  # Green
    else:
        pycom.rgbled(0x000000)  # Off

    time.sleep(1.0)

pycom.rgbled(0x0000FF)  # Blue

s = socket.socket()
s = ssl.wrap_socket(s)
s.connect(socket.getaddrinfo('www.google.com', 443)[0][-1])
s.send(b"GET / HTTP/1.0\r\n\r\n")
print(s.recv(4096))
s.close()

lte.disconnect()
lte.dettach()

# end of test
print("end of test")
pycom.rgbled(0xFFFF00)    # Yellow

while True:
    pass

jmarcelino

@tlanier

I'm afraid the manual is written by Sequans (who make the modem) and is more of a general guide for all possible implementations.

The LED on the FiPy/GPy is only connected to the ESP32/MicroPython and not to the modem. The SQNLED command will have no effect.

The correct way to check for correctly registration is via AT commands and specifically the status check AT+CEREG? Valid registration stats are 2,1 or 2,5 (for MVNOs)

tlanier

@jmarcelino

Thanks, I've updated the code.

tlanier

@tlanier
I took the Gpy 50 miles down Interstate 85 through West Point, GA and Opelika, AL. The device never attached to a cell tower during the entire trip.

jmarcelino

@tlanier
Were you using the code you posted below? I didn't notice you had changed the code you to calling lte.attach() again. Have you been doing the other tests with this?

For setups like Hologram where you do a custom init you need to remove lte.attach() and use AT+CEREG=2 and AT+CFUN=1 manually.

As you already have those in the code you need to remove lte.attach() otherwise it will cause problems.

tlanier

@jmarcelino

Thanks for catching the misunderstanding!

Here's my revised code. The at(cmd) function has been improved to return the modem response as a list making it easier to parse. I've also added logic to break on <tac> = 1 or 5 just in case the isattached() function is not working.

I will take the GPy north towards Atlanta today and see if I can connect there.

import pycom
import socket
import ssl
import sys
import time
from network import LTE

# send AT command to modem and return response as list
def at(cmd):
    print("modem command: {}".format(cmd))
    r = lte.send_at_cmd(cmd).split('\r\n')
    r = list(filter(None, r))
    print("response={}".format(r))
    return r

#######################################################
print("CAT M1 Test - V0.3 - 4/15/18")

print("disable MicroPython control of LED")
pycom.heartbeat(False)
pycom.rgbled(0xFFFFFF)  # White

print("instantiate LTE object")
lte = LTE(carrier="verizon")
print("delay 4 secs")
time.sleep(4.0)

if lte.isattached():
    print("LTE was already attached, disconnecting...")
    lte.disconnect()
    lte.detach()
    print("resetting modem...")
    lte.reset()
    print("delay 5 secs")
    time.sleep(5.0)

# enable network registration and location information, unsolicited result code
at('AT+CEREG=2')

print("full functionality level")
at('AT+CFUN=1')
time.sleep(1.0)

# using Hologram SIM
at('AT+CGDCONT=1,"IP","hologram"')

print("attempt to attach cell modem to base station...")
# lte.attach()  # do not use attach with custom init for Hologram SIM

i = 0
while True:
    # get EPS Network Registration Status:
    # +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>]]
    # <tac> values:
    # 0 - not registered
    # 1 - registered, home network
    # 2 - not registered, but searching...
    # 3 - registration denied
    # 4 - unknown (out of E-UTRAN coverage)
    # 5 - registered, roaming
    r = at('AT+CEREG?')
    r0 = r[0]  # +CREG: 2,<tac>
    r0x = r0.split(',')     # ['+CREG: 2',<tac>]
    tac = int(r0x[1])       # 0..5
    print("tac={}".format(tac))

    if lte.isattached():
        print("Modem attached (isattached() function worked)!!!")
        break

    if (tac==1) or (tac==5):
        print("Modem attached!!!")
        break

    i = i + 1
    print("not attached: {} secs".format(i))

    if (i % 2 == 0):
        pycom.rgbled(0xFF0000)  # Red
    else:
        pycom.rgbled(0x000000)  # Off

    time.sleep(1)

print("connect: start a data session and obtain an IP address")
lte.connect()
i = 0
while not lte.isconnected():
    i = i + 1
    print("not connected: {}".format(i))

    if (i % 2 == 0):
        pycom.rgbled(0x00FF00)  # Green
    else:
        pycom.rgbled(0x000000)  # Off

    time.sleep(1.0)


pycom.rgbled(0x0000FF)  # Blue

s = socket.socket()
s = ssl.wrap_socket(s)
s.connect(socket.getaddrinfo('www.google.com', 443)[0][-1])
s.send(b"GET / HTTP/1.0\r\n\r\n")
print(s.recv(4096))
s.close()

lte.disconnect()
lte.dettach()

# end of test, Red LED
print("end of test")
pycom.rgbled(0xFFFF00)  # Yellow

while True:
    pass

tlanier

@tlanier

I drove through both Newnan, GA and Peachtree City, GA with the GPy running in my car. The device never attached to any tower even though I passed by many towers within visible sight.

jmarcelino

Thanks @tlanier

Are you able to try it with a Verizon Cat M1 SIM?

tlanier

@jmarcelino

Anybody know how to get an evaluation Cat M1 SIM that will work.

On the Verizon web page they state: "Machine to Machine Plans are available only to business customers with five or more CLEU lines that have signed a Major Account Agreement. "

Verizon Machine to Machine Plans

I talked to Kore about a month ago, and they did not offer Cat M1 SIM's at that time.

Kore

tlanier

@tlanier

We've talked to the Verizon open development team and they indicated that CAT M1 is on ALL Verizon LTE towers in the country.

There's got to be some explanation as to why we cannot connect with the GPy.

tlanier

@tlanier

The Verizon Wireless HelpDesk @ 800-525-0481 has now told us our Hologram SIM is not a valid SIM on their network. We have contacted Hologram to try to determine what could be the problem. No word yet from Hologram.

ChrisGammell

@tlanier said in GPy with Hologram.io SIM:

The Verizon Wireless HelpDesk @ 800-525-0481 has now told us our Hologram SIM is not a valid SIM on their network

Yep, still trying things here as well. As Ryan said over on our forum, it's possible that Verizon does not have direct records of our SIMs on their network and we encourage everyone to contact us directly for connectivity. We understand you're frustrated while we try to get this sussed out, we are as well. The problem with SIM cards that normally "just work"...is when they don't.

ChrisGammell

@chrisgammell

Speaking of frustrated, I'm still getting errors from lte.connect(), is there a way to get a more verbose output?

I just saw in the docs that there is a firmware update for the modem as well as as the Pycom boards themselves, going to try that now. Is it possible that that could be contributing to the problem?

ChrisGammell

I added at('at+csq') into the loop and saw that as the device eventually finds its way onto the network here locally, it goes from "99, 99" to "11, 99" or so. Does yours change if you insert that into the loop, @tlanier? Also could you post a picture of your mobile rig? I'm curious about how you have it all hooked up and powered and such.

tlanier

@chrisgammell

I did do the firmware update from:

https://pycom.io/downloads/

I have not done the modem firmware update. Thanks for the link. I will try that first thing in the morning.

Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

GPy with Hologram.io SIM

Pycom on Twitter