@tttadam I think it because there may be values in the read buffer, which are discarded when you init the device. You could try to call tou.read() to flush the buffer instead of re-initing the UART. if that does not work, it's no big harm. Reestablising the UART does not harm.

Great! Thanks for the explanation. It all makes sense now!

@tttadam If I understand the data sheet right, the orange should go to GND an the white to an Analog input, like P13 to P18. The uncovered one is shielding. You can put that to GND. The output range is small, 0-30mV, which means, that you will get no reasonable reading, because there is no reading at all below ~70mV. The value you read should mostly be 0. So you need to insert an amplifier. Edit: The ESP32 has an built-in amplifier. But that is not supported by the Pycom firmware and not by espressif itself.

@fsergeys same problem here :-(

@Terry666 You can derive that from math.log() math.log10(x) = math.log(x)/math.log(10) math.log2(x) = math.log(x)/math.log(2) Since math.log(10) and math.log(2) are constant, you can pre-calculate them. P.S.: Looking at the code, they are not included in the PyCom build. You can do so by building you own firmware and setting #define MICROPY_PY_MATH_SPECIAL_FUNCTIONS (1) in mpconfigport.h.

@tttadam If you have trouble with fragmentation, you have to redesign your program. Running the garbage collector will not help in all situations and small changes can get you into trouble again. You can reduce fragmentation by using precompiled scripts and allocating huge buffers at early stages. Reinitialize your buffers instead of allocating them each time.

There is also pycom.wifi_on_boot method which can be set to False. more info in the Docs

@robert-hh what I see in the docs is ujson, and I think it is very basic. But I will search for some sample code, and write what I come up with. (last year when I checked this topic, there was no support for json in micropython. Or I was lazy when did my research)

Json on the sd is come up to my mind also for config, I will give a try with that. :) I hoped, that there is an easier solution for source code protection, but it seems there isn't. Still thanks for your suggestion.

@Lucas_Vieira I'm missing the print statements form the script. So your test script is not executed at all.

@misterlisty for instance: indexs.group(0) But if you search for a fixed string, you can as well use index, e.g. try: found = response.index("2,1") except: found = -1 it returns either the position of the string or raises an error.

Actually I think I can do what I need by using mktime() : t = (2009, 2, 17, 17, 3, 38, 1, 48, 0) secs = time.mktime( t ) print("time.mktime(t) : %f" % secs)

@misterlisty Not sure of the context exactly, but I am thinking you want to extract the "2,1" from the data returned from the CREG+ AT command? I came up with this to extract the RSSI from the LTE connection and use it in a text string for example.. # Get the current LTE signal quality squallteM = lteM.send_at_cmd('AT+CSQ').strip().split() rquallteM = int(squallteM[1].split(',')[0]) # Evaluate the returned signal quality Data rssilteM = 113 - ((rquallteM) * 2) ltesqual = ("LTE RSSI: -{} dbM".format(rssilteM)) The .strip() and .split() operators should do what you want.. Hope it helps.

@PeterB I'm not using the pymakr plug-in, but form the discussion i recall, that there is an option to run safe boot before upload. Safe boot bypasses boot.py and main.py. In that case the objects defined in boot.py to not exist.

@Lonefish Do you actually have a valid IP connection between the FiPy and the server? The topic of the subject talks about LoRa, but you can't perform HTTP requests over LoRa, you need to go through a gateway for that.

Hi again, we resolved this issue and it is easy to tackle if you know what has been happening to make things go south. So, let me explain. When installing micropython-urllib.parse with upip, this obviously pulls in all package dependencies. One dependency, the package micropython-re-pcre brings in the re.py module along with ffilib.py as a utility module to be able to talk to libpcre. However, all of this is not available on the Pycom platform, but Pycom itself ships a built-in re package, which would have worked right away when not being masked by the vanilla re.py shipped through micropython-re-pcre. So, we manually remove re.py and ffilib.py from the dist-packages folder before uploading the firmware using rshell. Then, urllib will use the built-in re.py module and everything works like a charm. Sorry for the noise and happy hacking, Andreas. P.S.: If you are interested in what we are building here, you are welcome to have a look at the Hiveeyes MPY data logger firmware. We'd love to hear about any feedback and suggestions you might have.