@mthethwansm I'm having the same problem, did you ever get this resolved?

@ahmadelmasri said in Anyone have a reliable MQTT interface using PyCom?: Hi @netskink, Yes this is part of Pybytes, but you can use the MQTT without integrating with pybytes, I mean you can use the library instead of umqtt.py In your case what you should use is only: mqtt_core.py msg_handl.py the try-catch is related to libraries under the "lib" folder and in the frozen zone. so if you are using your own firmware, you can just add the above files and ignore the try-catch or remove them. if you are using pybytes firmware, you can import mqtt.py or _mqtt.py and do subscribe, publish directly. @ahmadelmasri I am trying this but it complains about missing arguments for MQTTClient, such as the mqtt_download_topic and pybytes_protocol. Do you have complete example code using the Pybytes MQTT library?

@andrew-alberty Most people use Thonny as the IDE. https://thonny.org/ P.S.: Using the ESP8266, you may better discuss your topics at the genuine MicroPython forum forum.micropython.org

@Gijs said in Update to Micropython V1.13: You (@David-Neumair ) are indeed correct in that we need to be more transparent about our future plans. Gijs Hello @Gijs , I second that! Currently we've developed a product with pycom modules inside, and we need to add ULP feature to our end product in order to count pulses (flowmeter feature). We promised to our end users (in 2019-2020) that the modules would have that feature on a few months but at the moment we are waiting ULP feature to be added in pycom firmware. The only tutorial that we found is one from @oligauc https://forum.pycom.io/topic/5337/ultra-low-power-ulp-processor-part-1 but I believe Oligauc no longer works at or with pycom. I've tested this tutorial but I don't know what to do next. It's possible to add ULP feature? or is something pycom isn't going to implement? Kind regards!

As my best knowledge NO. :( Threading in pycom threading is very limited. I am also looking for a solution for threading locks. You can check out uasyncio.

@robert-hh said in (Newbie) - filesystem: @Mark-Wills did you set ftp to passive mode? No I don't think I did. I'll check that - thank you!

@jcaron Yes I will try that. Thanks for the advice!

Thank you for your response and support.

It looks like you are using signed intergers/numbers for the reading from the light sensor. When it reaches the half way value it wraps around and goes negative. If you simply define the data as an unsigned type does it fix the issue.

@railmonitor You do not need the lamda function for setting the callback. Simply giving the name of the callback function is sufficient. Timer.Alarm(timer_sampler, s = 1, periodic = True) Obviously, the function timer_sampler has to be placed in your script before using if for the alarm callback notification, and the callback has to have a single argument, the alarm object.

@robert-hh said in Convert string to integer: binascii.hexlify("\x12") On my gpy binascii.hexlify("\x12") gives b'12' Rob. How come I get bytes but you get a hex string?

@ciccio vin is the pin to supply the WiPy. When the module is attached e.g. to the expansion board, you can of course take power at that pin for other devices. But the WiPy is not the source of that power.

@Doroana, not sure if you have figured this out yet but when you create your instance of the queue, you can give it a parameter of the size of the queue. a = queue.Queue(10), this will create a queue with max size 10. The default value is 1.

You can create a timer chrono / alarm instance using the following API: https://docs.pycom.io/firmwareapi/pycom/machine/timer/

@jcaron Dear Jcaron: Tnx for your reply. Sorry, if I couldn't make it clear. But, I now I have made it to sending a few hundreds of bytes now (upto 1KB). As soon as I am done with the final project, I will share my updates.

@melkoutch hope you still read this as this thread is quite old. I stumbled upon it having the exact same problem (LoPy4 <-> Feather M0 in raw LoRa). Adjusting the spreading factor doesn't seem to solve it for me. Would you be able to post the code fragment that you used to successfully connect the two? Thanks a lot!

@robert-hh Thank you so much for that input! I'm really new to Python in regards of MCU's, so there is still alot to learn for me. Now I'm less afraid, that something could go wrong. :)

Hi @stsiafak Just curious, were you able to send the data using non-IP mode? Also, how did you get the packet into wireshark?

Took more time than planned. Voilá, more community Pycom MicroPython firmwares, including : 24 firmwares without ulab, in combinations of 6 xxPy boards, Pybytes or not, single/double precision; 21 firmwares with ulab, in combinations of 6 xxPy boards, Pybytes or not, single/double precision. 3 LoPy/SiPy/WiPy firmwares with ulab and Pybytes combinations are not possible due to the small firmware partition size of these boards. These firmwares with ulab have 'MICROPY_PY_REVERSE_SPECIAL_METHODS' enabled to allow '1 + np.arange(10)', for example. Announce with more details in 'Pycom firmwares with single/double precision and ulab module' topic.