GPy

• K

  PIN questions
  Jun 13, 2020, 12:29 AM • kjm   Jun 14, 2020, 1:41 AM

  3
  0
  Votes
  3
  Posts
  36
  Views

  K Jun 14, 2020, 1:41 AM

  tnx Rob I'll try my luck
• K

  nvram integer limitations
  Jun 5, 2020, 1:27 AM • kjm   Jun 11, 2020, 1:47 PM

  2
  0
  Votes
  2
  Posts
  38
  Views

  G Jun 11, 2020, 1:47 PM

  @kjm said in nvram integer limitations: 1591319102); print(pycom.nvs_get('VIP')) Yes, NVRam only fits 32bit integers (signed). 2,147,483,647 is the maximum value you can fit in! Of course you can create your own workaround to use multiple keys. Gijs
• T

  GPy with AT&T SIM
  at&t gpy • Jun 5, 2018, 2:21 PM • tlanier   Jun 8, 2020, 8:52 AM

  13
  0
  Votes
  13
  Posts
  1.5k
  Views

  I Jun 8, 2020, 8:52 AM

  you have to have the correct APN. if your sim is not specific for IOT then try these APNs: broadband, phone, nxtgenphone. if your sim is specific to IOT then try the apn m2m.com.attz. you must also designate the correct earfcn for each band. for band 2, try earfcn 1000 band 5 2549 or 2450 band 4 2100 or 2300 or 2000 or 2175 band 12 5110
• I

  Connected via AT&T iot sim stopped working
  Jun 6, 2020, 7:39 AM • irfan5911   Jun 8, 2020, 8:35 AM

  2
  0
  Votes
  2
  Posts
  25
  Views

  I Jun 8, 2020, 8:35 AM

  @irfan5911 figured it out. correct band and earfcn are crucial.
• N

  GPy Modem (NB1) Firmware Update
  Jun 3, 2020, 10:47 AM • nadvorvo   Jun 5, 2020, 6:54 AM

  7
  0
  Votes
  7
  Posts
  101
  Views

  Jun 5, 2020, 6:54 AM

  @nadvorvo Good that it worked. The SD card support of these littel boards is a little bit picky. If you have a SD card that works well, keep it for that purpose. I personally have good experience with Sandisk cards. I do not believe the the fail on the first attempt was related to the SD card. The error message originates from the modem firmware.
• K

  GPy as wifi detector
  May 27, 2020, 8:02 PM • kkerem   May 27, 2020, 8:02 PM

  1
  0
  Votes
  1
  Posts
  22
  Views

  No one has replied

• 

  LTE-M Telenor
  Mar 13, 2020, 10:33 AM • Don-iot   May 27, 2020, 6:08 PM

  3
  0
  Votes
  3
  Posts
  82
  Views

  May 27, 2020, 6:08 PM

  @aen At least in Sweden we have tested both LTE-M and NB-IoT with Telia quite a lot. Telenor runs LTE-M as well, I have tested that a lot as well and Tre has the NB-IoT in place. That one I am still trying to test, for some reason the NB-IoT firmware available for GPy is not available from the firmware I am using, so I am stuck at the moment, and have been for some time now. What networks have you tested?
• K

  Syntax Error
  May 18, 2020, 2:16 PM • kjm   May 22, 2020, 10:08 AM

  9
  0
  Votes
  9
  Posts
  62
  Views

  J May 22, 2020, 10:08 AM

  @kjm have you checked this thread: https://forum.pycom.io/topic/3705/lopy4-exp-board-syntax-error-after-deepsleep Apparently there were changed in a previous version of the firmware (possibly linked to underlying ESP-IDF changes) that supposedly fixed the issue, but there seems to be a difference between FAT and LittleFS. Also you’ll find references to use of wdt_on_boot and try ... except. If none of those work you may want to try other firmware versions to see if that helps, or maybe another GPy to make sure it’s not just the one you have which is faulty.
• K

  boot.py Vs main.py
  May 22, 2020, 12:17 AM • kjm   May 22, 2020, 7:48 AM

  3
  0
  Votes
  3
  Posts
  54
  Views

  K May 22, 2020, 7:48 AM

  I've got identical copies of my non terminating software in boot.py & main.py, the idea being that if boot.py fails then main.py should run in lieu. But I'd like to get a diagnostic message when this happens so that's why I need a way of telling if the code is running as boot.py or main.py
• C

  GPy and OpenAirInterface
  gpy pycom oai openairinterfa enb • Jan 9, 2019, 1:36 AM • cmrosero   May 20, 2020, 6:08 PM

  3
  0
  Votes
  3
  Posts
  377
  Views

  N May 20, 2020, 6:08 PM

  @cmrosero I realize this is an old post but did you ever figure out how to attach Gpy to OAI network?
• A

  Anyone who has the GPY and Expansion Board 3.1 Schematic?
  schematics • May 16, 2020, 4:31 PM • aasodisen   May 17, 2020, 8:08 AM

  2
  0
  Votes
  2
  Posts
  38
  Views

  May 17, 2020, 8:08 AM

  @aasodisen No lock. Pycom refuses to publish any schematics.
• K

  Select between ota_0 and factory FW
  Apr 28, 2020, 4:35 PM • kevin   Apr 28, 2020, 4:35 PM

  1
  0
  Votes
  1
  Posts
  25
  Views

  No one has replied

• W

  This topic is deleted!
  Apr 21, 2020, 9:15 AM • wedsel2   Apr 21, 2020, 9:15 AM

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• 

  Update NB-IoT on GPY with firmware 43818
  Apr 19, 2020, 6:03 PM • Don-iot   Apr 19, 2020, 6:03 PM

  1
  0
  Votes
  1
  Posts
  48
  Views

  No one has replied

• R

  LTE NB-IoT won't connect to T-Mobile NL
  Apr 2, 2020, 2:54 PM • rfinkers   Apr 17, 2020, 12:09 AM

  8
  0
  Votes
  8
  Posts
  125
  Views

  K Apr 17, 2020, 12:09 AM

  @rfinkers We had a similar problem last week with an sma to ipx adapter cable. Inspection with a magnifying glass showed one of the bifurcated connectors in the ipx plug that mates with the centre pin of the gpy lte antenna socket was missing leading to intermittent lte reliability. Those miniature RF connectors are not well suited to the repeated plug/unplug cycles typical of development work.
• A

  Using GPy with IPv6
  Mar 10, 2020, 12:42 PM • agotsis   Apr 13, 2020, 3:39 PM

  10
  1
  Votes
  10
  Posts
  221
  Views

  N Apr 13, 2020, 3:39 PM

  Just an update of the latest changes. The API of the microATsocket has changed to be closer to the typical usocket API. Also a custom version of getaddrinfo info has been implemented, so the code now looks somehting like: import microATsocket as socket from network import LTE import binascii lte = LTE() # attach to network # ... #message as bytes data = bytearray('{data:"testmessage"}') # create socket instance providing the instance of the LTE modem sock = socket.socket(socket.AF_INET6, socket.SOCK_DGRAM) sock.setModemInstance(lte) # getaddrinfo needs to be called on the instance of socket resolvedIPs = sock.getaddrinfo("google.com", 5683) # send data to specific IP (dummy IP and port used as example) sock.sendto(data, resolvedIPs[0][-1]) # receive data from the previously used IP. # socket is still open from the 'sendto' operation (resp, address) = sock.recvfrom(1024) print("Response: from ip:" + address[0] + ", port: " + str(address[1]) + ", data: " + str(binascii.hexlify(bytearray(resp))))
• K

  802.11 LR mode
  Mar 27, 2020, 6:12 AM • kjm   Mar 27, 2020, 6:12 AM

  1
  0
  Votes
  1
  Posts
  97
  Views

  No one has replied

• F

  uping doesn´t work on LTE-M1
  Mar 19, 2020, 11:18 PM • fruiz1113   Mar 26, 2020, 5:25 PM

  4
  0
  Votes
  4
  Posts
  203
  Views

  F Mar 26, 2020, 5:25 PM

  @kjm thanks for your reply , the problem was the pppsuspend/resume ,absolutely it hangs the modem for internet. The uping file and the ping file you have sent works properly.
• M

  maxbotix ultrasonic sensor gpy
  Feb 27, 2020, 11:05 PM • marcbeltman   Mar 26, 2020, 3:25 PM

  2
  0
  Votes
  2
  Posts
  124
  Views

  J Mar 26, 2020, 3:25 PM

  This works fine for me: from machine import UART uartHeight = UART(1, baudrate=9600, pins=('G11', 'G12')) while True: Data = uartHeight.read() if Data != None: Data = Data.decode() if len(Data)==6 and Data[0] == 'R' and Data[5] == '\r': print(Data[1:5] + "\r") Johan
• T

  GPY continuously rebooting rst:0x7 (TG0WDT_SYS_RESET)...
  Mar 13, 2020, 5:03 PM • Tiit   Mar 14, 2020, 12:08 PM

  3
  0
  Votes
  3
  Posts
  170
  Views

  T Mar 14, 2020, 12:08 PM

  It really worked! Thank you so much, KJM! What I did: Connected P2 to GND, pressed reset on Exp Board v3.1. The connection P2 to ground was left on for all the deleting process time. Then I did as instructed and result is clean module; reflashed fw as usual with FAT and everything worked and I was able to update NB modem. Also, the previously disappeared wifi at power up was back. The problem is associated probably with using adhoc wifi and filezila before I tried to clean the module for another application. C:>cd Program Files (x86) C:\Program Files (x86)>cd Pycom C:\Program Files (x86)\Pycom>cd Pycom Firmware Update C:\Program Files (x86)\Pycom\Pycom Firmware Update> C:\Program Files (x86)\Pycom\Pycom Firmware Update>pycom-fwtool-cli list COM6 [USB Serial Device (COM6)] [USB VID:PID=04D8:EF98 SER=PY7C4EA8 LOCATION=1-1] COM3 [Intel(R) Active Management Technology - SOL (COM3)] [PCI\VEN_8086&DEV_A13D&SUBSYS_07D01028&REV_31\3&11583659&0&B3] C:\Program Files (x86)\Pycom\Pycom Firmware Update>pycom-fwtool-cli.exe -p COM6 erase_all Running in PIC mode Erasing the board can take up to 40 seconds. Board erased successfully in 11.61 seconds C:\Program Files (x86)\Pycom\Pycom Firmware Update>