Bugs & Issues

• H

  ENETDOWN for LORAWAN
  • hanselsen  

  2
  0
  Votes
  2
  Posts
  251
  Views

  J

  @hanselsen Unless you save the LoRa state, you can't send anything until you have successfully joined after a reset. When/how do you check has_joined? It can take a few seconds for the join to be successful, so you can't check right after the join call, you usually need to run a loop that checks and sleeps until joined. Beyond that, do you see the join on the network side?
• A

  Guru meditation error
  bugs • • anjusha  

  2
  0
  Votes
  2
  Posts
  335
  Views

  P

  Hello, Could you let us know what version of the firmware the effected LoPy is running so we can decode the error correctly. Any easy way to tell is to run the following: import os os.uname() thanks.
• R

  robust mqtt publish freezes randomly on Nb-IoT
  bugs • • randomrnti  

  2
  0
  Votes
  2
  Posts
  382
  Views

  R

  I've done some further troubleshooting and tried the following methods to get it to send consistently: Change QoS to 1. I found that I still encountered the same issue before where it got stuck after a random amount of time. This also delayed each additional message by about 1 - 5 seconds so I removed the time.sleep(0.2) Wait for ping message after every 10 publishes. I found that this also ended up getting stuck as well. Again I removed the sleep cause the delay was between 1-5 seconds on the ping. if (count == 10): client.ping() client.wait_msg() count = 0 count += 1 Ping message after every publish. This didn't suffer the problem of freezing during the hour that I tried. I did find however that the duration for it to get a successful ping took longer as time went on. From about 1-3 seconds average to about 7-10 seconds average after about an hour. Connect and disconnect the client after every publish. This seems to working the best, it hasn't frozen within the 30 minutes I've been testing it and each message is taking 3-5 seconds to send to the broker. If anyone has any further suggestions it would be appreciated.
• D

  lopy4 uart.write() problem
  bugs • • DanielJo  

  3
  0
  Votes
  3
  Posts
  441
  Views

  

  @johand And so the code lacks an error message. Same with machine.Pin in general, which does not stop you on defining a Input only pin as output.
• C

  py.setup_sleep() & py.go_to_sleep() don't always put PyTrack or PySense to sleep
  bugs • • combaindeft  

  3
  0
  Votes
  3
  Posts
  422
  Views

  C

  @jcaron what’s the version of the Pytrack firmware? pytrack_0.0.8.dfu
• J

  usocket issue: EBADF (or ENOTCONN) after doing a single GET request (using urequests) over LTE (NB-IoT)
  bugs • • johanbrichau  

  4
  0
  Votes
  4
  Posts
  630
  Views

  C

  @johanbrichau said in usocket issue: EBADF (or ENOTCONN) after doing a single GET request (using urequests) over LTE (NB-IoT): After making a single request using urequests, I'm getting the OSError: [Errno 9] EBADF: I've updated to 1.18.2 as @johanbrichau mentions ... but I'm still to getting these Errors ... My work-around was to wrap them in a Try-Catch ... since the data was being transmitted to the server ... @paul-thornton said in usocket issue: EBADF (or ENOTCONN) after doing a single GET request (using urequests) over LTE (NB-IoT): I know there's a ton of work going on with the LTE stack to make improvements to stability at the moment. Ill make sure this is raised as an issue and gets looked at to. Great 👍🏻 ... let us know more when you've got something to test 🙃 @johanbrichau said in usocket issue: EBADF (or ENOTCONN) after doing a single GET request (using urequests) over LTE (NB-IoT): This is fixed in 1.18.2 because you can set the dns manually: https://forum.pycom.io/topic/4361/new-stable-firmware-release-v1-18-2 This 1.18.2 may fix the following: OSError: [Errno 128] ENOTCONN when trying to do anything with sockets (e.g. usocket.getaddrinfo('cloudiotdevice.googleapis.com', 443)) Use the following to set your DNS Server to Google's DNS Servers ... usocket.dnsserver(0,'8.8.8.8') usocket.dnsserver(1,'4.4.4.4') usocket.dnsserver() ('8.8.8.8', '4.4.4.4') Then bring up your LTE Connection, and do: >>> print(usocket.getaddrinfo("www.google.com", 80)[0][-1]) ('216.58.211.4', 80)
• C

  PyMakr 1.0.5 broken in VS Code 1.31.0 update [FIX-on-its-way]
  bugs • • combaindeft  

  2
  0
  Votes
  2
  Posts
  271
  Views

  P

  Hello @combaindeft Yup. Vscode snuck out another update and broke things again. Its being worked on as I type this. Fix will hopefully be out soon.
• T

  Pymakr fresh install doesn't work
  bugs • • tboettjer  

  2
  0
  Votes
  2
  Posts
  281
  Views

  P

  For what it's worth, on a Chromebook (without Crostini), I've had good luck with Beagleterm: https://chrome.google.com/webstore/detail/beagle-term/gkdofhllgfohlddimiiildbgoggdpoea?hl=en and just using the REPL to do file read/write.
• 

  GPy & FiPy report different voltages when being charged
  bugs • • John Baird  

  4
  0
  Votes
  4
  Posts
  510
  Views

  P

  @john-baird please do update this is the results are different and ill have the team look into it.
• C

  lambda for callbacks
  bugs • • crumble  

  5
  0
  Votes
  5
  Posts
  497
  Views

  

  @crumble said in lambda for callbacks: callback = lambda (p, p2): print('Trigger enter' + str(p2)) try: callback = lambda p, p2: print('Trigger enter' + str(p2))
• E

  ADC doesn't work when measuring a battery voltage which powers up the whole system using Lopy
  bugs • • emilija.zuk  

  3
  0
  Votes
  3
  Posts
  390
  Views

  E

  @emilija-zuk Did you take the internal pin protection diodes into account when designing the circuit?
• M

  pytrack GPS coordinate give a failure result
  bugs • • meobeou  

  2
  0
  Votes
  2
  Posts
  317
  Views

  E

  if you place your code like this no-one can see where your if statements end and thus say something usefull about it. so put your code in a code block Insert Code Here if something == true: do something some more if something is true do something no matter what something is
• C

  What is OSError code: -202 ?
  bugs • • combaindeft  

  9
  0
  Votes
  9
  Posts
  1282
  Views

  C

  @paul-thornton Thanks, makes sense.
• G

  AC Dimming with zero crossing
  bugs • • Gursehaj  

  3
  0
  Votes
  3
  Posts
  1327
  Views

  

  @hjkarssies The code above missed the line: global zeroCross, i in the function zero_cross_detect()
• A

  rtc.synced() always returns False on FiPy 1.20.0.rc0 and 1.20.0.rc1
  bugs • • akshayjames  

  13
  0
  Votes
  13
  Posts
  1284
  Views

  P

  @serafimsaudade glad to hear it :D
• R

  ImportError: no module named 'operator'
  bugs • • randomrnti  

  4
  0
  Votes
  4
  Posts
  935
  Views

  P

  @randomrnti That works :) glad you got it sorted.
• F

  Issues for connecting lora application model to lorawan nano gateway
  bugs • • fiskeminal123  

  3
  0
  Votes
  3
  Posts
  329
  Views

  P

  If you look at the TTN account the gateway is registered under at the devices gateway page. Do you see any join requests from the node. or any traffic at all? Does the output from the gateway suggest anything is happening? if you could share the code your using it would help understand what's going on :)
• I

  UART RX buffer issue after buffer overflow
  bugs • • incognico  

  15
  0
  Votes
  15
  Posts
  3780
  Views

  

  @paulm I made the test with a baud rate of 115200 and 2048 byte and 10k data. With flow control enabled, nothing is lost. Without flow control, data is lost. But that is expected without flow control. If you send more data than the input ring buffer can take, while you not fetching it, then excess data is lost. However, what I get is strange. I wait with reading until all data is sent. What I get then is 607 bytes from the first part of the message and about 100 bytes from the tail. And that is repeatable. The other thing that puzzles me was that note,. that the UART buffer was extended to 4k. Looking into the code, mods/machuart.c, line 64, it says 512 byte plus the 128 byte FIFO of the chip. But still that should be OK for 480 bytes. The Pycom code does nothing to UART besides the API. The actual data transfer is done through the esp-idf code. The only thing that could be changed is the RX buffer size.
• I

  Hardware reset ? Can't connect to board anymore
  bugs • • ioTor  

  12
  0
  Votes
  12
  Posts
  1154
  Views

  X

  @iotor Have you been able to do a successful firmware update (using the Pycom Firmware Updater tool) before you encountered this issue? If not, please first do a dfu firmware update of the Pysense without having the module plugged into it. Once you have successfully updated the firmware please try the following: Make sure all programs that could possibly block the serial port are closed. Start the firmware updater and advance to the Communication screen where you select the serial port. If you don't see the serial port for the Pysense, press and hold the reset button on the module (next to the RGB LED) while you click Rescan Ports. Next please either enable the "Erase flash file system" or "Show advanced settings" option, depending on the version of the firmware updater tool you are using. Now again please press and hold the reset button on the module while you click Continue and release it approx one second after clicking Continue. If you selected "Show advanced settings", please make sure to activate the "Erase during update" option in the File System section.
• R

  Expansion Board 3.0 bad?
  bugs • • reidfo  

  10
  0
  Votes
  10
  Posts
  909
  Views

  P

  @crumble Is your code easily shareable? I'd like to leave it running on a module overnight here and see if I can reproduce this. because its super weird. feel free to share it via email with paul@pycom.io if you'd prefer it to remain private :)