GPy

• S

  LTE CAT M1/NB1 in Portugal
  nb-iot cat-m1 portugal • • serafimsaudade  

  7
  1
  Votes
  7
  Posts
  1556
  Views

  S

  Any news on the current LTE CAT-M1 status in Portugal? Do I need a special local simcard for this?
• D

  GPY + PYTRACK2 + VSC can't connect for normal use
  gpy vsc pytrack2 • • DEFRAINE.JM  

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied

• J

  GPy Modem unconnectable
  • Jeff Brown  

  4
  0
  Votes
  4
  Posts
  33
  Views

  G

  You can try different baudrates, as there is the possibility the modem is communicating on a different speed. Though I'll respond to your support request to figure this out in more detail!
• K

  GPY MIA
  • kjm  

  6
  0
  Votes
  6
  Posts
  37
  Views

  

  @kjm The RGB Led is connected to P2. Therefore, when connecting P2 externally, it tends to flicker. I had a board once with a defective RGB led, which I then replaced.
• A

  Directly Pass SSL certificates
  • Abdul Rehman  

  1
  0
  Votes
  1
  Posts
  13
  Views

  No one has replied

• K

  Flash problem
  • kjm  

  7
  0
  Votes
  7
  Posts
  37
  Views

  K

  @robert-hh Replaced the usb cable & all good now Rob. Why this particular gpy won't work with the replaced cable when all the others do is a bit of a mystery, the current looks the same, the voltage trace on the CRO looks the same, must be some subtlety there I can't measure that prevented it from running/uploading from the repl.
• L

  [SOLVED] GPy 1.0 extremely low RSRP of -21474836.00, no LTE connectivity
  • Laurin Schmidt  

  3
  0
  Votes
  3
  Posts
  24
  Views

  L

  I figured out what the issue was: the SIM card was advertised to the company i work at as a "IoT Sim" which apparently does not mean NB-IoT or CAT-M1, but normal non-narrowband LTE. We have logged a complaint with the card provider and ordered a new card. I hope this helps anyone else stumbling across this thread. PS: can you mark topics as solved?
• S

  What is OSError code: -202 ?
  bugs • • samith wijerathna  

  3
  0
  Votes
  3
  Posts
  20
  Views

  S

  @jcaron I update firmware of modem same as existing one then problem solved. now can communicate.
• M

  Error starting modem connection
  • Massimo Rebellato  

  4
  0
  Votes
  4
  Posts
  84
  Views

  G

  @Jeroen-Trappers Sorry for my late reply. Could you try to power cycle the modem and see if that results in any progress? If not, can you update the modem over UART using the instructions here: https://docs.pycom.io/updatefirmware/ltemodem/ Let me know!
• J

  Gpy connected to wifi but no internet access
  bugs gpy internet • • josejulianrp  

  7
  0
  Votes
  7
  Posts
  1817
  Views

  G

  In theory, it should be possible to make the GPy into a transparant bridge, between WiFi and LTE, though in practice it's not very useful, as the datarate is very limited. A more useful scenario I could think of is using the Gpy to collect data from its clients over Wifi and then forward this to a server over LTE, though there is no clear distinction to which network interface a socket is bound.
• B

  GPy Skips LTE Code on First Run
  • B Taylor  

  2
  0
  Votes
  2
  Posts
  16
  Views

  E

  @B-Taylor There are always problems with AT commands once you are connected() to LTE. To resolve this, execute the AT commands before connecting and seek "data mode" in the modem documentation on how to exit and re-enter data mode.
• Å

  Crashing after a couple of hours
  • Åke Forslund  

  2
  0
  Votes
  2
  Posts
  26
  Views

  Å

  Having it plugged to an usb-charger instead of the computer's usb has kept it stable since I sent above message so maybe it was the USB port on my computer or possibly Atom causing the issue.
• Y

  Getting GPy to connect to Google Cloud IOT?
  • Yo Yuasa  

  2
  0
  Votes
  2
  Posts
  12
  Views

  G

  Pybytes only one way from my experience. I use AWS-IoT and you can find the tutorial in the docs.pycom.io. seems like there is a micropython tutorial for esp32 https://github.com/GoogleCloudPlatform/iot-core-micropython
• G

  Modem ATI response and attachment issue
  • grpatt  

  4
  0
  Votes
  4
  Posts
  15
  Views

  K

  @grpatt I've had several GPYs where the modem has simply died, no RF output during attachment attempts. If you've got a CRO you can wrap a few turns of wire around the lte antenna & connect to the CRO on it's mV scale. If there is no carrier the device is history, if there is very low carrier then your antenna is plugged into the wrong antenna socket.
• G

  View attached bands of modem cat m-1
  • grpatt  

  1
  0
  Votes
  1
  Posts
  9
  Views

  No one has replied

• J

  AT+SQNINS not working
  • Jordan Restifo  

  4
  0
  Votes
  4
  Posts
  36
  Views

  J

  Yes I am using the latest firmware. I discovered that the issue is the documentation is lacking. lte.pppsuspend() and pppresume are not sufficient to get this data. I need to fully disconnect and actually deinit the modem in order to get this data. If I do that, it works fine.
• T

  New GPY - LED Faulty
  • tlanier  

  20
  0
  Votes
  20
  Posts
  100
  Views

  T

  @Gijs Sorry for the long delay in responding. I have rewritten our software to eliminate the use of threads and timer interrupts. My hope was this might eliminate the crashes. Instead the crashes still occur in different places and more frequently the processor locks up without printing the backtrace. Last night I was able to get a crash with backtrace. The interesting thing here is even though I do not import or use the LTE module, the program is crashing inside a LWIP (Lightweight TCP/IP Stack) routine. Apparently the TCP/IP software is being loaded and called even though I am not using it in any way. One idea is now to learn how to rebuild the Pycom OS without including the LWIP stuff. I'm not sure how big a task that would be at this time. I've also investigated a new product that might have some promise. With some effort I was able to get their product loaded on the GPy. They currently do not have support for the Sequans modem in the GPy. The Toit language is definitely harder to read than Python from my point of view and the UART driver documentation is lacking (although it does support CTS and RTS). Toit | Cloud-managed containers on the ESP32 My decision point now seems to be: Try to rebuild the Pycom OS without features that I don't need to try to eliminate the crashes. Since I don't require the TCP/IP stack (we use the Sequans modem TCP/IP stack), threading, or timer interrupts, this should make the code simpler. It is a real shame that there is no hardware reset pin to the modem from the ESP32. I hope this is fixed in some future design of the GPy. Rewrite my app using the Espressif SDK in C/C++. One hurdle I have doing this is that the hardware design already uses the pins that the JTAG debugger requires. It looks like I would have to live with debugging using print statements. I would encourage Pycom to clearly show hardware designers what pins should not be used if they hope to do JTAG debugging with their design. Pursue learning Toit and try to write a driver for the Gpy's Sequans modem. Further pursue using generic MicroPython. The initial roadblock I ran into was getting the UART talking to the modem. Pursue designing an external watchdog timer circuit that would power the GPy down/up after crashes. One challenge to this approach would be to make it field installable. Maybe the watchdog device plugs into the GPy socket and the GPy plugs into the watchdog device. A GPIO pin would be connected internally to allow triggering the device. To be generally useful to current designs, there would need to be some way to jumper/select which currently unused GPIO pin would be used for the trigger. If anyone out there can think of any better ideas, I'm open to suggestions. Which path is my best chance of success?
• K

  More lte woes
  • kjm  

  9
  0
  Votes
  9
  Posts
  83
  Views

  K

  @peterp The ticks_ms problem test program import machine, network, time, os; start=time.ticks_ms() def _t(): t=(time.ticks_ms()-start)/1000; return '%02d'%t print(os.uname()) print(_t(), 'start') epoch=1625789769; date=time.gmtime(epoch); rtc=machine.RTC(); rtc.init(date) print(_t(), 'lte'); lte=network.LTE() print(_t(), 'attach', end=' '); lte.attach() while 1: print('.', end=' '); time .sleep(1) if lte.isattached(): print(); print(_t(), 'connect'); lte.connect(); break print(_t(), 'rtc') rtc.ntp_sync('time.google.com') while 1: print('.', end=' '); time .sleep(1) if rtc.synced(): print(); break #print(_t(), 'suspend'); lte.pppsuspend() print(_t(), 'deinit'); lte.deinit() print(_t(), 'deepsleep'); machine.deepsleep(9000) and the results (sysname='GPy', nodename='GPy', release='1.20.2.r4', version='v1.11-ffb0e1c on 2021-01-12', machine='GPy with ESP32', pybytes='1.6.1') 00 start 2292128 lte 2292131 attach . . 2292138 connect 2292139 rtc . 2295011 deinit 2295018 deepsleep where the ticks_ms value is changed by rtc.init and rtc.ntp_sync
• S

  How to handle a LTE Connectivity loss
  • SciWax  

  40
  0
  Votes
  40
  Posts
  309
  Views

  S

  My minimal setup worked on my breadboard. Today, I've integrated that initially separated structure into my big prototype on my other breadboards. It is really weird. The Pull-up doesn't work always. When I use my minimal example code on my big prototype setup it works as on my minimal breadboard setup. The Pull-up works and the GPy doesn't boot up, so the GPy is powered off while the Arduino is booting. The Pull on the Gate is high enough in that case. When I use my real prototype code, where every sensor gets setup, the pull-up doesn't work anymore though. I can't explain why. I didn't change anything on my big prototype setup and I can't control a passive element like a simple pull-up setup via code. It must be related to the Voltage on my 5V-Pin on the Arduino then I guess? But why is the minimal example code on the same big prototype setup working as expected (the GPy is turned off at the beginning) ... While the Pull-up doesn't work on the big prototype setup, I can power cycle the GPy. When I pull the GPIO HIGH, which is connected to the Gate, I power the GPy off. When I set the GPIO to LOW, the GPy turns on again. I just can't explain why the Pull-Up doesn't work, while power cycling with the GPIO of the Arduino seems to be working? I've connected a 10k Ohm resistor to one of the 5V Pins of the Arduino, which is connected to the gate. I use this site as a reference: https://www.gammon.com.au/motors Would shifting the threshold by the forward voltage of the diode help, so I get consistency into my setup @robert-hh ? Kind regards, SciWax
• J

  LTE support for Telia and Telenor (Norway)
  lte nb-iot telia cat-m telenor • • Jardar  

  18
  0
  Votes
  18
  Posts
  1050
  Views

  S

  @Gijs @Yoann-Baud any luck here? I'm in Norway and using the same setup. We've had some discussions before but haven't been able to get around this either and any updates on this case you have here that you could share would be very helpful! Scott