Im not the correct person to answer your BLE queries. but if you let me know what they are Ill get them infront of someone who can and get you answers :) Otherwise. Awesome work :D

Hello @Paul-Thornton , Glad to here that, it's very important to me to have this possibility with Pycom. All my devices should be connected to Azure. I've done some researching and found out that your MQTT libs are sending bytes that Azure doesn't understand. Short description of this is on the link: https://www.youtube.com/watch?v=pRqpKZ7mO1s

@martinnn If you build the firmware from the sources you get the most recent version. These numers are in the file pycom_version.h. At the moment it tells 1.18.2. Revision tags are not added often to the repository. So you see just a few of them.

Dear @Milan and @Martinnn, if you feel lucky, you might want to try our custom build just released on [1]. More background about this is available through [2]. Please be aware that you will have to erase your device completely before flashing in order to keep things straight. You will find respective references to this on the forum. Hint: Use pycom-fwtool-cli --port /dev/ttyUSB0 erase_all, see also [3]. With kind regards, Andreas. [1] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/WiPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz [2] https://community.hiveeyes.org/t/investigating-random-core-panics-on-pycom-esp32-devices/2480 [3] https://community.hiveeyes.org/t/installing-the-recent-pycom-firmware-1-20-1-r1-requires-erasing-the-flash-memory-completely/2688

@changeddaily said in Wipy3 Low power modes: rwble.c Sorry, I cannto find the file either. It is only referenced in the libraries.

I’ve experienced similar issues when using MySQL databases. What you’re experiencing can most likely be linked to some kind of server problem. That’s what it’s boiling down to most of the time. One of my clients was having a real bad time with his database and I identified the faulty server as being the culprit behind most of the issues. Once we switched him up to a cloud server all of the connectivity problems were gone. Also, you could try using a service like Aiven for MySQL. With that you can connect appliances to your databases with ease. I hope I could help you, and you figure out the problems.

Hey. Could you try reflashing the latest firmware. Including using the checkbox to wipe flash. And reupload and try the code again. Thanks

Update: It seems I am getting the crashes only when I have my pysense/wipy connected via USB. I have around 12-15 units running in various setups; those running standalone (battery connection only) seem to do fine, those with USB fail regularly.

Heya, Take a look at our own pybytes: http://pybytes.pycom.io/

@ingframin Did you manage to modify the firmware? I would like to have a Wi-Fi advertising per 100 milliseconds; default LoPy-4 seem to send an advertising only if requested by a station.

@wolli01 Depends on a lot of circumstances. Use WiFi and simply upload the file using FTP. LoRa will need more code and tiny files.

@noboz32 I sent you a PM

Stupid mistake, I thought I had checked the pinout... thanks! Set it to None and now it works.

@colateral I believe that the Pycom firmware uses one core for networking and the other to run the actual MicroPython code, or something similar. Not sure how easy it would be to disable one of the cores altogether. There has been discussion about changing the frequency though, there must be a thread somewhere in the forum with instructions IIRC.

And one more: File "urequests.py", line 54, in request OSError: [Errno 9] EBADF which might be #define EBADF 9 /* Bad file number */ I have a gc.collect() after the upload, but no .close on the connection. Adding this now to see how things go. -- Martin

@alexpul Indeed, but both pack to the same bytes object. PC: >>> struct.pack("f", 3.4) b'\x9a\x99Y@' >>> struct.unpack("f", b'\x9a\x99Y@') (3.4000000953674316,) >>> Pycom: >>> struct.pack("f", 3.4) b'\x9a\x99Y@'

There was a platform that first got me looking at pycom products, and that was pymate. https://forum.pycom.io/topic/14/pymate-is-here Unfortunately it seems they have moved on and no longer support it. So mobile dev is part of the discussion. Or at least was. I am still hoping they bring it back, as it was exactly what I needed when I decided to "Go pycom". It seems like the dev team has a lot of good ideas, but jump around between them so much that a lot is never finished before they change course (such as Pylife now being the new path of all effort) and move on. That makes it difficult to really plan a future around a platform that has great promise but divided focus and sometimes short attention span. And I know that sounds insulting... but I can't figure out another way to explain it. So many other products were offered as "coming soon" or "out of stock, but pre order here" that now seem to be forgotten (sensors, cases, etc) that I am not sure what to build around.

@robmarkcole After reset, just pickup the last time stamp from the SD cards' data file. That wouldn't give you a precise time but no problems with duplicates.