Dear Pycom community!
We're happy to announce the release of version 1.20.2.r1
This version contains new functionalities dedicated to the Machine Learning app in Pybytes:
Machine learning model deployment feature
install this update from Pybytes
or with the Firmware Updater
find the source code in the git branch v1.20
download the firmware packages (.tar.gz) from the docs
and find the .elf files in the github release
I would like to add a constructive criticism. I really like the Pycom's products, but several times I have also felt like something is missing in the documentation. Sometimes it is the way it's organized, not so easy to browse it, other times some details are missing to quickly understand how things are working/designed or how should be configured, and sometimes it's not updated. In some way, I agree with this comment: "It sounds like you should do an audit of all your documentation". I know that I'm not the only one, I have read other people saying this kind of things.
Pycom products are great, but you have to make your documentation easier to read, add all necessary details, do not assume that your users know all the internal details that you know. You have to create documentation as great as your products.
@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.
With the limiting circuit I showed in my last post, this overshoot was limited to about 3.5Vpp:
@Alois 125 kHz tags are quite common, but I’m not sure if it’s really standard, you may need different readers depending on the exact type of tag. You should find some types of readers on SparkFun for instance.
I didn’t know about the 134.2 kHz tags, but they’re animal identification tags, right? Found some reader modules on eBay, Amazon... they seem to have pretty low-level interfaces, though.
@tlanier yes this is intentional. We're running low on storage capacity for the firmware, so we released this beta version without sqnsupgrade. We're looking into ways to get it back in, but we didn't want to delay the release of a beta version to get some idf4 feedback
@troy-salt it should definitely be something you can control, though, so you can decide to which version you want to upgrade, and which devices should be upgraded.
Many past firmware versions have broken quite a few things, so you need to be able to test any new firmware on a limited set of test devices before deploying it widely.