GPy

• K

  Fiddling firmware
  • kjm  

  2
  0
  Votes
  2
  Posts
  104
  Views

  J

  @kjm The firmware is mostly C, with a dusting of a variety of other things (C++, Assembly, Python). The initial setup is (or at least was) a little finicky, you need to have the right versions of ESP-IDF, cross-compiler, etc. Read the docs, most of it is actually well documented. Once it's all set up, it's really quite easy to make changes and recompile if it comes to just changing the behaviour of existing functions. I've never tried adding new Python functions in the firmware, though I suppose this shouldn't be too hard. The only tricky part is when the code you're interested in is in an interrupt handler, you need to take special care, you can't just do anything you want in those, so you sometimes have to defer some stuff from the interrupt handler to the "main" code. IIRC, there are already lots of facilities in the code to trace all that is exchanged with the modem, it's just a matter of enabling those, so you may not even have to write any code, if you're just interested in seeing (i.e. dumping on the console) the relevant info rather being able to process it in your own code.
• 

  How to reduce power consumption on GPy?
  power saving help helpneeded • • techykermit  

  8
  1
  Votes
  8
  Posts
  638
  Views

  

  @nwjlyons It improved drastically, from 17 hours to 2-3 days. Definitely use deepsleep!
• C

  GPy refuses to LTE attach after running for months
  • curtis.hendrix  

  22
  0
  Votes
  22
  Posts
  1372
  Views

  K

  @kjm I spoke too soon. I've got 2 x GPYs now that won't attach & all I've done is to try the lte.send_at_cmd('AT+CEREG=2;+CEREG?;+CEREG=0') cmd on them. Seems an improbable result I know but 2 out of 2 is enough for me, I'm not about to try it on a 3rd GPY just to get the hat trick & prove my point!
• K

  Delays, delays
  • kjm  

  6
  0
  Votes
  6
  Posts
  193
  Views

  J

  @kjm A few things to try: Check that the GPy actually got the time correctly sync'd. Maybe the GPy doesn't actually get its time right. Try to confirm things visually: set the GPy to change the LED colour at the right times to see what happens, and tail -f the logs on the server at the same time, and see if things match. You mentions POSTs. Are those large? Is the server timestamp at the beginning of the request (when the TCP connection is established or the POST line is sent, or when the full headers have been received) or when the full request (including all POST data) has been received? Is the received POST complete? Does this happen on GETs as well? You may want to check what tcpdump or Wireshark say (on the server) to see what actually is received (and sent) by the server. Note that some network providers do have weird stuff like (supposedly transparent) proxies between devices and the rest of the Internet. I believe it's pretty rare nowadays, but IIRC I got bit by something similar recently.
• C

  How can I check what filesystem is used on a current pycom board
  • Clemens  

  7
  0
  Votes
  7
  Posts
  316
  Views

  K

  @robert-hh In that case "try Roberts discovery arising from his masterful ability to ferret out these pearls from the great pile of info, much of it no longer current."
• H

  Sockets with LTE and W-LAN
  • htwg  

  2
  0
  Votes
  2
  Posts
  126
  Views

  H

  I used UPD sockets. Before sending the first package, you can socket.bind() the socket to the Interface IP address. That way you can select witch socket connection is using the LTE or the W-LAN interface.
• H

  This topic is deleted!
  • htwg  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• N

  Gpy bricked after adding Pybytes firmware
  • nakovi  

  2
  0
  Votes
  2
  Posts
  118
  Views

  N

  @nakovi Fixed this by using the erase all feature from: https://docs.pycom.io/advance/cli/ A little heavy handed but the board seems to be back to normal. I'm pretty afraid to touch pybytes again though. Time to look into alternative for uploading data.
• N

  GPy LTE Modem does not respond
  • nakovi  

  14
  0
  Votes
  14
  Posts
  581
  Views

  N

  @kjm Yep, LTE antenna. I finally got a connection to go through. Only thing I changed is to remove my lines specifying bands (4, 12, 13) so it may have been happier with another band. To anybody that finds this post down the road, this is what I added to the LTE example documentation code to get it to work: lte = LTE() lte.send_at_cmd('AT^RESET') lte.send_at_cmd('AT+CFUN=0') lte.send_at_cmd('AT+CEREG=2') lte.send_at_cmd('AT!="clearscanconfig"') lte.send_at_cmd('AT+CGDCONT=1,"IP","hologram"') lte.send_at_cmd('AT+CFUN=1') lte.attach()
• G

  Mqtt subscribe stops receiving
  • gt1  

  1
  0
  Votes
  1
  Posts
  90
  Views

  No one has replied

• P

  pulses_get holding buffer values?
  • pycom9  

  3
  0
  Votes
  3
  Posts
  105
  Views

  

  @pycom9 pycom.pulses_get() has no means of managing what it is doing. It uses the RMT device. So you could try to use the RMT module API, allowing to deinit and init the channel again. That may reset the internal ringbuffer of the RMT peripheral.
• K

  GC auto or not?
  • kjm  

  4
  0
  Votes
  4
  Posts
  169
  Views

  A

  Dear @kjm, @kjm said in GC auto or not?: We continue to play whack-a-mole with GPY lte connection stability. As we eliminate problems we are left with more obscure errors (eg OSError: [Errno -29312] MBEDTLS_ERR_SSL_CONN_EOF). These resources might give you some clues: https://github.com/espressif/esp-idf/issues/1009 https://github.com/espressif/esp-idf/issues/3624 https://github.com/espressif/esp-idf/issues/4127 I am really encouraging you to give the Dragonfly firmware [1] a try as it already fixes some of the problems outlined within those issues, especially the PSRAM bug. With kind regards, Andreas. [1] https://community.hiveeyes.org/t/dragonfly-firmware-for-pycom-esp32/2746
• 

  Gpy without Pymakr
  • Don-iot  

  6
  0
  Votes
  6
  Posts
  169
  Views

  

  @Don-iot As said, that seems only to be a problem when using one of the various pycom expansion boards. I'm using Fipy and Lopy boards on a homebrew expansion board without a pull-up resistor at P8. The issue seems to be caused by the PIC on Pycom's expansion board, which pulls P2 low when the device is powered by battery and the PIC is not powered. If then P8 stays low since it has an internal weak pull-down, the device does not boot.
• K

  Dumb Atom question
  • kjm  

  4
  0
  Votes
  4
  Posts
  109
  Views

  K

  tnx fellas shift-ctrl-C does the trick in Atom under Windows10
• K

  Pycom firmwares question
  • kjm  

  2
  0
  Votes
  2
  Posts
  116
  Views

  K

  Has anyone got a contact inside pycom? I really want to know why the sqns 43818 firmware in my latest gpy isn't available for download somewhere?
• K

  Identify GPY FS?
  • kjm  

  3
  1
  Votes
  3
  Posts
  77
  Views

  K

  @robert-hh said in Identify GPY FS?: pycom.bootmgr()[1] tnx Rob, bootmgr tells me the 1.20.0.r4 firmware was done with LittleFS. The updater.py looks intimidating. Isn't there something I could type on the cmd line in Atom that would erase just the userland flash now that we know it's LittleFS?
• K

  python glitch
  • kjm  

  5
  0
  Votes
  5
  Posts
  133
  Views

  K

  @robert-hh Interesting. The GPY modem gets itself into a state where it says it's connected but can't run data. Trying to disconnect it to reset it gives an OSError so I do a machine.reset(). Can you suggest any tricks to maybe restore the modem without a machine.reset()?
• K

  OSError 23
  • kjm  

  1
  0
  Votes
  1
  Posts
  87
  Views

  No one has replied

• S

  This topic is deleted!
  • Skipper90  

  1
  0
  Votes
  1
  Posts
  4
  Views

  No one has replied

• J

  GPy + Pytrack startup connection issues
  • jchernandez  

  4
  0
  Votes
  4
  Posts
  497
  Views

  P

  --- Edit --- Nevermind. The same problem occured again after a few hours. See my current thread on bridging P3 to GND for a possible solution. --- End Edit --- @jchernandez Hi, I came across the same problem just now and managed to solve it: For me, the problem first occurred after I accidentally disconnected a GPy and PyTrack from USB. The GPy would work with the PWR_EN removed, like yours. Other board and shield combinations would work, too. What resolved the problem was re-flashing the pytrack firmware from the dfu file. Now everything works again without pin modifications.