GPy with Hologram.io SIM
-
-
@tlanier
Which antenna is that? Do you have a link?
Is it suitable for 746-787Mhz (Band 13) operation? -
I've moved the unit to a front office where I'm now getting +CSQ: 15,99 signal strength.
You may have discovered my problem about the antenna.
My hardware guy is not here at this moment, but this is the part number I got off our last order which is what we use for our 4G LTE modems connecting to T-Mobile.
Would the fact that I'm now getting a signal strength of 15 not indicate that the antenna is sufficient?
-
After moving the unit to a different office, I'm now getting:
+CEREG: 2,4
+CSQ: 99,99@jmarcelino has indicated that I have the wrong type of antenna.
-
@tlanier
RSSI (from CSQ) is only one measurement. Are you still not seeing CEREG returning 2,5 ?Ideally you'd use an antenna supporting 700Mhz bands, of course your antenna works on that frequency but doesn't appear designed for it so you may be losing some signal.
Can you increase the delay on your attach loop to 5s
time.sleep(5)and addat('AT+CEER')at each iteration to see if there's any error reported? -
I'm available to allow you to remote into our system anytime.
I'll order a new antenna today if you want to wait until I have the correct antenna.
-
Here's what I'm getting now after increasing the delay to 5 secs in loop with the AT+CEER command. I updated the image to show the correct time counter.

-
@tlanier
Thanks. Unfortunately it's not very helpful in this situation but keep the CEER in the code if you do get a valid CSQ again it may show a reject cause.It might be the case that the modem is connecting but being rejected by the network for some reason and then we'll know why...
-
Hologram tech support suggested plugging the SIM into an unlocked cell phone for testing.
When we plug the SIM into an unlocked Samsung S5 phone, "TMobile-Hologram" shows up in the Available Network Operators.
When we try to go to a web page (google.com), we get an off line error page.
We were able to send a text message to the Samsung S5 from the Hologram Dashboard.
I'm not sure what this really proves since we're trying to use the SIM to attach to Verizon's CAT-M1 network.
-
@tlanier said in GPy with Hologram.io SIM:
When we try to go to a web page (google.com), we get an off line error page.
Umm that should work, you should be able to load Google.com. Do you have data left?
-
The Hologram dashboard shows I have used 104 bytes of a 1MB - Developer Plan. I assume the usage is due to the SMS message that was sent successfully.
Interesting discovery (not sure what it means):
In the Logs section of the dashboard under "Message sent from GPy"
DATA: Socket error: timed out
RAW VIEW:
{"success":true,"data":{"id":5792718,"logged":"2018-04-17 19:33:13.876522","orgid":2262,"deviceid":164756,"record_id":"2b868012-4276-11e8-a470-0242ac120002","device_metadata":"{}","data":"{"received": "2018-04-17T19:33:13.798433", "authtype": "deviceid", "tags": ["DEVICE_164756", "API_RESP"], "device_name": "GPy (30674)", "source": 164756, "messageid": "2cb19d53-4ff4-415a-b3b2-7606267d8325", "record_id": "2b868012-4276-11e8-a470-0242ac120002", "data": "U29ja2V0IGVycm9yOiB0aW1lZCBvdXQ=", "device_id": 164756}","matched_rules":[],"tags":["API_RESP","DEVICE_164756"]}}DATA: Socket error: [Errno 111] Connection refused
RAW VIEW:
{"success":true,"data":{"id":5804366,"logged":"2018-04-18 18:41:10.684172","orgid":2262,"deviceid":164756,"record_id":"10604cb0-4338-11e8-bb29-0242ac120002","device_metadata":"{}","data":"{"received": "2018-04-18T18:41:10.361416", "authtype": "deviceid", "tags": ["DEVICE_164756", "API_RESP"], "device_name": "GPy (30674)", "source": 164756, "messageid": "b72e25a1-8c12-4235-b463-71f03544bf74", "record_id": "10604cb0-4338-11e8-bb29-0242ac120002", "data": "U29ja2V0IGVycm9yOiBbRXJybm8gMTExXSBDb25uZWN0aW9uIHJlZnVzZWQ=", "device_id": 164756}","matched_rules":[],"tags":["API_RESP","DEVICE_164756"]}} -
My hardware guy got the antenna vendor (San Jose Technology, Inc.) to send us a spec for the Penta Band PCB Antenna Model: EPH-502 that we are using.
The spec shows:
Frequency: 704~960; 1710~2690MHz
-
@tlanier
Ok that's fine then - and different from what was listed on the website. -
@tlanier If you're seeing these messages on the dashboard it means your phone (assuming that was the phone) is able to authenticate on our network. I think it might be another red herring though, unless you want to debug why they phone isn't connecting as well.
-
We really don't care about the phone. We were just trying to prove the SIM was functional.
The code in the GPy tried one time to run the detach function at the beginning of the program and failed. It turns out the detach function is misspelled.
Manual entry @ 6.2.26 LTE
lte.dettach()
Detach should only have one "t".
Why the lte.isattached() function returned True one time is unknown. It occurred after the laptop had gone to sleep and was reawakened.
-
I think I've just proved that there may be a bug in the lte.send_at_cmd() command. Internally the function must time out if it does not receive an "OK" response from the modem after a period of time. Your timeout may be too short.
See the response to the "ATI" command shown below. The program error'ed out because it was expecting a different response from the AT+CEREG? command. Instead it got the trailing remains of the previous ATI command.
I believe you should clear the input buffer before sending any AT command to the modem to help prevent such a problem.

-
I accidentally sent a message to Chris which I meant to send to you concerning the possible bug with the lte.send_at_cmd() function. I assume you will see it; I couldn't figure out how to redirect the message to a different person.
-
One time the GPy got into a state where lte.isattached() was returning True at the start of the program. When the lte.connect() was called an exception was thrown:
OSError: the requested operation failed
After resetting the chip, things are back like they were before (unable to attach).
It's beginning to look like I may need to put try/except blocks around all calls to the LTE class. I'm not sure if this is what the designers of the LTE module intend for programmers to do.
lte.isattached() returned True but lte.connect() threw an exception
Again, this has only happened once.
-
I am now able to attach to the cell tower consistently!
response=[''+CEREG: 2,5,"AE02","02A99403",7', 'OK', '+CEREG: 5,"AE02","02A99403",7']
When the lte.connect() method is called, the program crashes with the following exception:
OSError: the requested operation failed
Notes:
-
In browsing the source code this morning I noticed Daniel posted a significant update to the modlte.c code. Do we have any idea when this update might be published for testing?
-
On the web site there is no indication of firmware versions and history. How do we know when a new update is available to download?
-
At some point the LTE documentation should be updated to indicate which method calls might throw exceptions. For instance the dettach() method can throw an mpexception_os_operation_failed exception. Maybe at the python level we should assume any LTE method call may throw an exception.
-
Problems can occur when a modem command is sent but your timeout is too short and the modem command returns before the modem has finished responding. When the next modem command is sent, the response contains the tailing fragment of the response from the previous command. Adding a delay between sending commands does keep the problem from propagating to the second command (the result received from the first command is invalid since it was aborted prematurely). Maybe the send_at_cmd() should have an optional second parameter that allows the caller to specify the timeout.
-
The dettach() method should probably be renamed detach().
-
Is there any reason to believe I should update the modem firmware at this time, or should I wait for Daniel's patches to be published?
-
-
Did something change? Or did it just start working? Or maybe i'm not following the thread? Did you end up swapping antennas or was it something in the code?
I'm still at the same point with the lte.connect() function, but Jose said the LTE team is looking at that. I found out from my co-worker that it's possible to hook into the modem UART pins, so I might try throwing some other commands via that tomorrow.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login