I confirm problem solved by use of the DHCP instead of static parameters in wlan.ifconfig. If you need a static address it seems that the sequence : wlan.ifconfig(static parameters) (by example in boot.py) wlan.ifconfig(dhcp) wlan.ifconfig(static parameters) correctly initialize the name resolver (the DNS server must be the same for the static and dhcp config). tested with 1.0.0b2

Thanks @Ralph. On WIpy 1 there is however a little inconvenience in that the keyboard interrupt is not flagged immediately, but only after another character is typed. This behavior exists since ever, I reported it but it was never fixed. Best regards, Robert

@gertjanvanhethof We are experiencing LOS of up to 20km using the standard (20cm) antenna on devices.

Hi bmarkus, That's a good point. You are right, math is part of firmware and should work as expected. That's a bug, we'll make sure that we'll include the math module in our next docs release.

Hi bmarkus, If by list built-in modules you mean behaviour like Python's modules function while using the REPL the answer is no. Micropython does not offer this functionality. But the modules (and what's there so far) are listed in the docs The only thing that is available currently is sys.modules which shows you all the external modules that are available: >>> sys.modules {'simple': <module 'simple' from '/flash/lib/simple.py'>, 'pymate_library': <module 'pymate_library' from '/flash/lib/pymate_library.py'>}

Same for me, upgraded firmware to 1.0.0.b1 on my LoPy, re-enabled IPv6 on router, happy puppy sinds then. Thank you for quickly fixing Pycom team!

@bmarkus Works for me from Debian on a laptop and Manjaro on a Pi, both using screen out of habit.

Sure but I always obtain the max values, which means that it is not working. I tested with a voltage supplier and checked that the voltage is correct. Or maybe I have to try with another Lopys who knows

@thickglass , Assuming you are referring to using the LoRa radio: even in (impossibly) perfect conditions, it can only do 512Kbps. The codec hardware you linked to says to expect rates between 6000 to 8000Kbps, an order of magnitude more than what LoRa can do. It's better to think of LoRa as a means of transporting telemetry (periodic, small data transmissions). Media transport, by comparison, is sustained indefinitely over time and has a large amount of data. WiFi is better for this purpose, but it's still not really all that good. Hopefully that helps.

@daniel thanks for the info. In that case I'll need to test from another location. I tried with OTAA, but the Lopy didn't join.

@Ralph As far as needs to help guide... I need to scrape information from sensors' BLE advertisements and forward them over LoRaWAN to be parsed by the Things Network. Students have been using bluepy on an RasPi3 for the scraping portion, so a similar API would be nice (a whole fourish days away).

@ekpegleg said in Timer objects: Which friday? Im still waiting for the ticks_us() function. Can everyone show a hack to get the hc-sr04 to get working? This Friday I believe.

@rskoniec Exactly! :) Thank's!

@yahia said in LoPy socket.getaddrinfo strange return: I had the same problem. I was trying to connect to an ntp server and it always returns a random ip. If you however use the ip directly instead of the domain name it works and stays consistent. Try 216.58.214.164 (This is google.com) and you will see what I mean. I will report a bug. It is a different case. Probably you have used a domain name for a pool of ntp servers instead of a server. In such case you get different server address from the pool.

@gertjanvanhethof All are integers. #working code for TC74 i2c temp. sensor from machine import I2C i2c = I2C(0, I2C.MASTER, baudrate=400000) t = i2c.readfrom_mem(72, 0, 1) print('temperature room: ', t[0])

look here and use safe boot mode: https://docs.pycom.io/pycom_esp32/pycom_esp32/general.html Boot modes and safe boot after that you can connect to it by ftp and remove files created by pymate

Thank you for that link. It's nice to see what's being worked on and what's already there. "Coming soon" is a bit hard to base a time estimate on though :) I'd like to be able to use my LoPy nodes for an upcoming experiment, but I'll have to choose some other platform if the RTC support isn't coming real soon - like within the next four weeks. I'm not expecting you to start developing it just because I need it of course, I'm just after a statement like "it's the next thing we'll work on, expect it just after Christmas", or perhaps "we've got a lot of more important stuff to implement first, don't expect the RTC to be supported within the next couple of months.". That would help me immensely :-) Keep up the good work. Best regards, Mads

@Rens said in LoPy Using machine.main(filename): Well just tested again with machine.main('test.py') and now its working as i would expect. Thanks again for the support. Rens Super! I'm glad that you finally did it! :o)