@bradnz So you want to tell, if the voltage of the LiPo battery is above 2.5 V. That should be done using the ADC, for various reasons. a) The value at which a digital input switches from HIGH to LOW is not well defined and not stable. It is somewhere between 0.75 * Vdd and 0.25 * Vdd b) You have to check the value of the variable charger anyhow, so instead of doing that you could also read an ADC value. If you want to have that done in an interrupt fashion, you can set-up a timer interrup which reads the ADC,

@jcaron It worked! My bad. Didn't even think about that. I erased flash memory and uploaded most recent firmware. Thank you @robert-hh as well. For the future, are there any best practices for connecting/disconnecting, from both a hardware and software standpoint. e.g. my boot.py file: import os from machine import UART uart = UART(0, 115200) os.dupterm(uart) Should I include anything else?

@robert-hh oooh ok this was silly. i didn't see the pinout, but only the spec on the shop. thanks!

Good pickup, I will try and use P10 and P11 unless you recommend anything else? Edit, it works now thanks for the help

Nice challange! Got some new hardware incoming to see what we can do :-)

Hi everyone. I want to tell you that I have already solved the problem. There is a conflict with the line in which I declare a Pin as output and the moment in which it is transmitted: Pin('P5', mode=Pin.OUT, value=1) What I did was change the pin to P13, this ended the problem and I was able to transmit without any inconvenience and see the data in the Sigfox Backend.: Pin('P13', mode=Pin.OUT, value=1)

@dommei I have always been in an area near the Sigfox network and don't know of a way to get data into the Sigfox back end any other way. If you just want to get the data for testing you can just save it to an SD card if you have the PySense or Pytrack or wifi. Or are you trying to export the data from the Sigfox back end into a database? If this is the case you are trying to get some test data into the Sigfox backend. I have no idea how to do this Sorry. https://resources.sigfox.com/document/callbacks-documentation might help?

It works ! Thank you !

@bigboy20769 I see at least two options: call the respective init methods in a try block call os.uname and check the type of module

@jmarcelino Thank you for sharing this. To add to this question, are there code example of we can persist an array of structs to the file system? I have a clear idea of how I want to implement a simple persistent database but I cant find micropython examples of doing so. The btree library would have been great but I realised I couldnt use it in this version of the port.

I finally got it to work, had to position the helical antenna upright, lying flat it wasnt able to send the message out.

I got this to work on a different pc with windows 10, 32 bit installer of the the visual studio code (even though windows 10 install is a 64 bit install). 64 bit install of the visual studio code didnt work with the pymakr plugin for me.

@iotmaker You can tell both I2C and onewire which Pin to use. For I2c, you do it by i2c.init(), for the onewire driver, it is given in the constructor of the class.

@littlebat It said max current 40 mA in the maximum ratings sections, but I myself did not trust that anyhow. Even if, the output levels then are somewhat off GND/Vcc. So 12 mA sounds much more convenient.

I looks like a re-flashing of the firmware fixed the issue.

That worked like a charm! Thanks!

@Lokefar said in Crash on boot: The device is powered by a 3.3V power supply. OK but make sure the the supply can deliver 500mA @ 3.3V. While the board doesn't use this much in normal use, the boot up is particularly demanding and the voltage can dip below what's necessary - for example during WiFi calibration. Most boot crashes are due to inadequate supply.