@jcaron Thanks a lot!

I think @d-alvrzx is correct here. You need some 'idle' time on the CPU for the callback to be registered. I believe its not a hardware routine that is used for the callback, but merely on top of the RTOS.

@xavier where are you running that encoder? I'm trying to do something similar with node-red.

@jjbarriga you just make a loop around whatever bit of code you want to test. If you want to measure power (which is instantaneous, measured in W), you just read the power drawn while that loop executed (you can use an infinite loop as long as you have a way to get out of it of course). If you want to measure energy (which is the integral of the power used of a time period, measured in Ws or Wh or whatever power * time unit), you read the power drawn while the loop is executed, and measure the time it takes to execute the loop, which needs to have a set number of executions. Dividing the total time by the number of iterations will give you the time per execution, multiply that by the power and you have the associated energy.

@jjbarriga The source code of the firmware is available at https://github.com/pycom/pycom-micropython-sigfox together with build instructions. So there is not need to go the extremely tedious way you sketched. Even with the source code it is some work to do.

I fixed it with: import pycom from network import WLAN pycom.wifi_mode_on_boot(WLAN.AP) Firmware version was: >>> os.uname() (sysname='LoPy4', nodename='LoPy4', release='1.20.2.r3', version='v1.11-a6eabf9fe on 2020-02-26', machine='LoPy4 with ESP32', lorawan='1.0.2', sigfox='1.0.1', pybytes='1.3.1') But it is really disappointed from Pycom, how they can deliver products with wrong default settings, there is actually a lack of quality control

@StefanoF said in STC013-015 analogic schema at 3.3 v: The Stc013 sensor has an electronic circuit on board clamp with resistor and diodes I looked up the sensor data sheet. If your sensor has printed on the case 15A/1V, then it is the voltage type sensor. And That's the one you need. But I made my tests with exactly that SCT013-015 sensor, and got up to 15Vpp, when there was a shortage in the sensed circuit. How did I test that? I had the sensor at a wire with a basic load of 1 A at 230V. And then I shortened these 230V. Boom, spark! Obviously the mains 16A fuse stepped in, but for a short moment I had a huge current, about 200A. I had an oscilloscope at the sensor output to capture the peak. Copy below. [image: 1600594794232-pic2.jpg] With the limiting circuit I showed in my last post, this overshoot was limited to about 3.5Vpp: [image: 1600594894408-with_limiting.jpg]

@jlproyectos Hi, It is the PING trigger to establish the duration of the ping for the Sensor that I used (Ultrasonic Distance Sensor - HC-SR04 (4 pins)), to convert the time into a distance.

thank you so much i would need help sending to lora, but i don't want to use cbor

@Gijs thank you for the links.

@StefanoF adc = machine.ADC() apin = adc.channel(pin='P16', attn=ADC.ATTN_11DB) def readACCurrentValue(): peakVoltage = float(0) for i in range(5): peakVoltage += apin.voltage() peakVoltage = (peakVoltage / 5) - 142 # 142 offset ACCurrtntValue = peakVoltage / 1000 return float(ACCurrtntValue) pass print(readACCurrentValue()) 0.0 at empty

@JaRay Did you manage to get this working? I have a FiPy and Chirpstack running on a Pi4 with RAK2245 same as you and I'm getting a very unreliable uplink / downlink connection similar to what you're experiencing and I suspect its due to channel configs. Someone said that you would be seeing as few as 1/5 of the packets which is about what I'm experiencing. Any luck? Here I'm sending a payload from the FiPy every 30 seconds but only getting an unconfirmed uplink every 3-5 minutes or so. So I'm actually closer to only 1 in 10 messages being delivered. [image: 1599439210870-screen-shot-2020-09-06-at-8.37.00-pm-resized.png] [image: 1599439210818-screen-shot-2020-09-06-at-8.37.39-pm-resized.png] Here is another chart to visualize how irregular my uplinks are. This reflects an attempt at 1 min intervals but shows that more often than not packets are not delivered. These spikes should be perfectly spaced 1 minute apart. This is between a FiPy and the gateway which are in the same room about 10 feet from each other, no barriers. [image: 1599496429699-screen-shot-2020-09-07-at-12.30.57-pm.png]

@kjm I repeated that test again with a LoPy4. When getting below ~3.5V, the voltage at the 3v3 pin follows the Vin voltage. In my set-up, it was ~20mV less than Vin. I connected to the LoPy4 via Telnet, which showed that WiFi worked all the time. At 3V Vin I could still send & receive LoRaWAN messages. At 2.5V Vin the ESP32 and WiFi still worked, but LoRa did not. LoRa seemed to work down to about 2.8 V. Below that it started to fail: the packet counter of transmitted messages was not increased any more, even if a counter in the Python script did.

Did you already try what the text suggests, to manually reboot the device? Next to that, you can manually put the device in safeboot, using the Safeboot button: https://docs.pycom.io/gettingstarted/programming/safeboot/

@joshhulnz a) write: Timer.Alarm(battery_voltage, s=5, periodic=True) without the brackets. Optimization: b) in the main loop, I would use a short sleep instead of the continue statement c) I you just need the average, you do not have to collect the values. Just add them up while reading, e.g. def battery_voltage(): avg = 0 for i in range(0, 35): avg += adc_b1.voltage() print(round(avg/35000, 2))

I was not aware this is the same issue, nor of any changes in the Bluetooth. Mustve been before I joined. I will take it up with the firmware team to see what we can do! Edit: It does seem like this is the most simple reproduction of the error. Not sure why changes were made..

@Gijs Hi. Yes, I have the Python plugin but I also have the Pymakr plugin installed. It seems as though when i run the code it uses the python extension by default. I found that if I say Ctrl + Shift + R (or use the run current file in the bottom toolbar), it is able to run the file just fine. But it still flags it as a problem and tells me Unable to import 'pycom' pylint(import-error) [1, 1] as well as giving me the red underline where i typed 'import pycom'

Thanks catalin , the pycom-fwtool-cli command worked for me, I thought I had bricked my lopy4

@Gijs Thank you