adafruit-mirror/adafruit-circuitpython-weekly-meeting
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
adafruit-circuitpython-week.../2021/2021-02-22.md
Jeff Epler a36e4305b4
Create 2021-02-22.md
2021-02-22 14:54:20 -06:00

29 KiB
Raw Permalink Blame History

CircuitPython Weekly for February 22nd, 2021

Welcome to the CircuitPython Weekly meeting notes! Feel free to add your Hug Reports and Status Updates early. During the meeting, we go through them as a round robin sorted by username. If you can’t make the meeting and would still like to participate, add your notes with a “(missing meeting)” after your username and we’ll read them off for you.

Add any longer-form discussion topics or general questions you have to the “In the weeds” section.

Thanks! We hope to see you in the meeting!

Jeff is hosting

Video is available here on YouTube.

Join here for the chat all week: http://adafru.it/discord

The CircuitPython Weekly happens normally at 2pm ET/11am PT on Mondays. Check the #circuitpython channel on Discord for notices of change in time and links to past meetings. Meeting times are also available in iCal format using the following link: https://raw.githubusercontent.com/adafruit/adafruit-circuitpython-weekly-meeting/master/meeting.ical for use with standard calendar applications or in your browser: https://open-web-calendar.herokuapp.com/calendar.html?url=https://raw.githubusercontent.com/adafruit/adafruit-circuitpython-weekly-meeting/master/meeting.ical

If you want to be able to participate in the meeting by speaking, you will need to be added to the @circuitpythonistas role on Discord. Please ask any one of the moderators or admins to add you if you’d like to join.

CircuitPython development is sponsored by Adafruit. Please support them by purchasing hardware from https://adafruit.com.

Reminders: Podcast available on most services. Let us know if we’re missing some.

3:14 Community News

On February 20th, Python turned 30 years old! - The Register and VentureBeat.

CircuitPython2021 round up

A round-up of all the CircuitPython 2021 responses received from the community - Adafruit Blog

Cat is outside reminder with CircuitPython and an Adafruit MagTag eInk display - Twitter.

Putting CircuitPython on custom SAMD21 powered "USB-C Plug" testers - Twitter.

Using CircuitPython code on the Raspberry Pi Pico to pull a prank - Twitter.

(& lots more! -- subscribe!)

The CircuitPython Weekly Newsletter is a CircuitPython community-run newsletter emailed every Tuesday. The complete archives are here. It highlights the latest Python on hardware related news from around the web including CircuitPython, Python and MicroPython developments. To contribute your own news or project, edit next week's draft on GitHub and submit a pull request with the changes. You may also tag a tweet with #CircuitPython on Twitter, or email cpnews@adafruit.com.

5:19 State of CircuitPython, Libraries and Blinka

Overall

  • 37 pull requests merged
    • 22 authors - dherrada, makermelissa, wildestpixel, jamesbowman, TG-Techie, jepler, dhalbert, jedgarpark, jposada202020, dlizotte-uwo, SAK917, caternuson, KTibow, lesamouraipourpre, jfurcean, lukschwalb, gpongelli, sandyjmacdonald, kimmellr, imgrant, OleMchls, askpatrickw
    • 9 reviewers - ladyada, FoamyGuy, brentru, makermelissa, tannewt, jepler, dhalbert, kattni, askpatrickw
  • 26 closed issues by 13 people, 18 opened by 14 people

7:15 Core

Overall: 6.2.0 is doing pretty well, will do betas until stable. Will switch gears into 7.0 following that. Please keep testing everything.

9:32 Libraries

12:42 Blinka

13:22 Hug reports

13:51 @jepler

  • Group hug
  • @tannewt for hosting me on his Deep Dive & everyone who we chatted with
  • @v923z for responding promptly to ulab items as usual
  • #pcb-design folk including @skerr for giving me compliments on a rather boring PCB design

14:56 @jerryn

  • @danh for getting the second CDC port working

15:12 @jfurcean (lurking)

  • @anecdata and @Neradoc for helping debug a socket issue in the requests library.
  • @GeekMomProjects for her LED art and CircuitPython talk at Pycascades.

15:42 @Jose David M. (missing meeting)

  • @kmatch98 for reviewing and keeping the conversation open
  • @Microdev1 for implementing UART for the pico
  • @neradoc for always help in discord. It is inspiring to witness.
  • @foamyguy @tannewt thanks for the streams, it is important as a community builder tool.

16:20 @kattni

  • Everyone who has contributed to the Adafruit CircuitPython Libraries and the Community Bundle - we have passed 300 total libraries!
  • @Hugo for working on adding Pylint to the pre-commit
  • @askpatrickw for continued work on circup
  • @Kmatch98 and @foamyguy for continuing to work on CircuitPython UI elements
  • @krayola for spending multiple days in the labyrinth that is JavaScript to help me with my website, and for helping me with my new theme.

17:04 @kmatch98

  • @kattni, @jfurcean and @Hugo for guidance on Sphinx and class inheritance
  • @foamyguy for experienced feedback on the Widget and Control classes
  • @jposada202020 for the prompt bitmap_label improvement and PR for setting the textbaseline. I used it in a project the same day!
  • @jepler - I’ve reflected further on what you did in the bitmap_font library to add PCF fonts. Not only does this change save space and is faster, but you also created a website to convert files to the right format with one click(!), and added a guide page to explain it all. After using this, it’s clear to me you thought through the whole problem and solved the whole chain of issues, not just one technical piece. To me, this serves as a good example of reducing the many layers of “friction” focused on solving the full problem at hand. Hugs for sharing your broad set of skills to do this and to set a good example for all of us to strive toward.
  • @Hugo for the improvements in the progress bar and for sharing your positive attitude!

18:43 @MakerMelissa

  • @danh for your help with getting my system set up to compile circuitpython
  • @tannewt for the groundwork you laid out for displayio E-Ink displays
  • @kmatch98 for your suggestion about adding rotation to MatrixPortal
  • @jepler for reviewing my code
  • @askpatrickw for your work on the cookiecutter templates
  • @brentru for writing the datetime library
  • Group Hug

19:39 @microDev (text-only)

  • Group hug

19:47 @Neradoc (text only)

  • Group hug to the whole community for its warm welcome
  • @askpatrickw for more circup goodness
  • @danh for the second CDC channel and his insights on why mac pyserial incorrectly identifies the channels
  • Belated hug report to @kattni for welcoming me in the circuitpython helper role

20:28 @ntoll

  • Those CircuitPythonistas making thoughtful contributions to the CircuitPython-mode related discussions over in “Mu-land”. Thank you..!

21:00 @tannewt

  • @ZodiusInfuser from Pimoroni for the board support PR
  • @jepler for joining my stream
  • @jun2sak for the PR for deep sleep on the nrf52
  • @danh for knocking out a few of our oldest issues
  • JLink folks for releasing version with RP2040 support

22:27 @TG-Techie participating/un-lurking (listening-out?)

  • @danh for helping understand some nrfboard customization naming
  • Community hug

22:46 @askpatrickw (lurking)

  • @jepler and @kattni for the PR reviews for circup
  • @Microdev1 and @skieast for picking up the Update ESP-IDF to 4.3 work and running with it

23:15 @CGrover (text only)

  • @tannewt and @ladyada for the encouragement to challenge my software development limitations.
  • Group hug to the team and community.

@charlesburnaford (lurking)

23:31 @danh

  • @Neradoc for lots of helping in discord.
  • @jepler and @v923z for quick fixes to ulab to fix a bug provoked by a BLE program (but not related to BLE).

@DaveP(lurking)

24:15 @David.Glaude (lurking)

  • @tannewt for the #CircuitPython2021 round up and PWM (sound)
  • @danh for the second CDC serial
  • @jepler for the 8 neopixel thing with PIO and that book on binary hack you recommended in the stream with tannewt.
  • @deshipu for the displayio Tetris

24:56 @deshipu

  • Group hug

25:12 @foamyguy

  • Anyone who has tuned in to my weekly Saturday morning streams. I have learned lots from it, and it’s become something I’m excitedly looking forward to each week.
  • @jposada202020 for diving into an issue with tab characters in display_text
  • @hugo for looking into and starting up a PR in cookie cutter to move the PyLint action into pre-commit. Also for writing up a very helpful page covering git commands for renaming and other tasks a few weeks back
  • @kmatch98 for testing and thoughtful discussion on many different displayio related PRs of mine and others.

27:09 @hierophect

  • @danh for answering low power questions
  • @brent for some testing help
  • Group hug

27:34 @Hugo (will miss, work meeting)

  • @kattni for being trusting enough to let me take a crack at the pylint change in Cookiecutter
  • @askpatrickw and @jepler for the input on the pylint-in-pre-commit change
  • @foamyguy and @kmatch98 for feedback and testing of the progress bar
  • @kmatch98 for spurring thought and discussion on inheritance while working with Sphinx

@jasonp(lurking)

28:09 Status Updates

28:36 @jepler

  • Last week:
    • Shift register neopixels code & (upcoming) guide
    • Various bug fixing
    • Implemented memoryview.cast() function from standard python
    • Looked at storage.erase_filesystem() problem on rp2040, kicked it over to @hatach
  • This week
    • RP2040 protomatter bug chasing
    • We will probably hold the “NeoPIO” guide until after the next beta
    • More PIO + CircuitPython guide content
  • Fun stuff:
    • It’s over freezing again! Time to go out and walk after this meeting

Mini-In The Weeds

31:02 @ntoll

  • We’ve had several contributions of ideas and PRs about changes and fixes to the CircuitPython mode over in the Mu editor repository (see: https://github.com/mu-editor/mu/pull/485#issuecomment-782879502 for a summary). I’d like to raise this here simply so folks have a) visibility of this discussion, and b) feel invited/empowered to take part in it. I’d feel gutted if folks felt left out. Our aim: reach consensus among folks about what, if anything, could/should change in the CircuitPython mode. That’s it..!
  • Doodle “A Mu-moot about CircuitPython-mode improvements.”: https://doodle.com/poll/uw4mrfe5kuehxqka

Status Updates Part Deux

33:37 @jerryn

  • Ran some simple tests of second CDC on several boards
    • nrf52840_sense, RP2040 pico, grandcentral_m4 -- fun stuff
  • Lots of unfocused explorations….. More of the same next week.
  • Working on getting my “birdcam” ready for deployment.
    • RPi zeroW with camera in the birdhouse - provides stream via WiFi
    • Worked well last year - 2 different nests - replacing NOIR camera with normal camera this year.
      • Did not use the IR very much - better quality pictures with normal camera.

34:53 @Jose David (missing meeting)

  • Last week:

    • Updated base alignment feature for bitmap_label
    • PR to solve label not seeing tab characters in strings
    • Spanish Weblate translations
    • Studying the I2Cperipheral.

  • Next week:

    • PR to solve the Tab issue in bitmap label
    • Update Read_the Docs for display library after all changes.

35:26 @kattni

  • Last week:
    • Passed 300 libraries!
    • Finished the Pico guide
    • Updated the MLX90393 guide for STEMMA QT rev
    • Added further documentation to the Feather CAN guide
    • Worked with Anne to start learning how to take over the newsletter - covered some of the initial steps and a bit on adding content
  • This week:
    • Add PCB files for PiRTC to GitHub
    • Work with Anne on the publishing end of the newsletter
  • Over the weekend:
    • Published a new theme for my website, super excited about it!

@kevin_thomas (lurking, text only)

41:09 @kmatch98 Last week

  • Submitted a pull request for the Widget and Control classes
  • Setup Sphinx on my local machine to create and debug library documentation
  • Added “easing” functions for more dramatic animation in widgets This week
  • Update documentation on Widget and Control classes and incorporate the good feedback received.
  • Verify SwitchRound compatibility with grid_layout
  • Document SwitchRound and submit PR
  • Brush up on Sphinx commands, explore and verify options for capturing class inheritance, including with Core classes
  • Review the latest Progress bar PR
  • Organize the bitmap rotozoom function into a bitmap_tools folder option in the core Other fun(?) stuff
  • Fixing frozen plumbing/playing whack-a-mole

43:38 @MakerMelissa

  • Last Week:
    • Finished writing the 1.54” eInk guide
    • Added fromisoformat() function to the datetime library
    • Updated a project for John Park to use the datetime library
    • Did some troubleshooting on the I2C soft reset issue with CircuitPython and ESP32-S2.
    • Wrote my first eInk driver for the SSD1681
    • Started working on getting the EPD SSD1681 driver on the Raspberry Pi to work
  • This Week:
    • Finish getting the EPD SSD1681 driver working
    • Update the 1.54” E-Ink guide with the new pythonian drivers
    • Test out a new ST7789 Raspberry Pi driver
    • If that works, update the PiTFT scripts to use that driver
    • Update the Gizmo library to test out the SSD1681 display on there
    • If time, look at adding rotation to the MagTag library

45:29 @Mark(Gamblor) (text-only may not be here)

  • Taking a look at countio on RP2040. Have a question in the weeds about how to read it in the background.

45:45 @microDev (text-only)

46:19 @tannewt

  • Need to finish audio work. Hang/or crash is happening with PIO PDM test code
  • Add stop-gap for flash size config per-RP2040 board
  • Get UART merged in
  • Implement rotaryio

49:51 @TG-Techie: Last week:

  • Got bluetooth working on the TG-Watch by dead bugging a nrf module and comparing behavior. Turns out adding a 32khz crystal revealed the miss-configured board port. This was the last known hardware related bug on the watch…
  • until found a bug in the LC709203 driver
  • Shocked by wandavision reveal Next week:
  • Having trouble erasing the metro m4 and wiping out the boot-loader
  • Unify TG-Gui into one repo
  • eposWork on the rect library (meant to last week, but school)

50:10 @askpatrickw (lurking)

  • Last week:
    • Updated Circup to:
      • use the requirements.txt released in the bundles (Thanks @Jepler)
      • added pre-commit and made the repo and dev workflow feel like other CircuitPython library repos
    • Using a FeatherS2 and BME680 to monitor my refrigerator. We think the thermostat is off because it is freezing things.
  • This week:
    • Start looking at Azure IoT library work to support Sockets

50:41 @CGrover (text only)

  • Submitted the learning guide for improving the low-speed performance of brushed DC motors by adjusting the PWM frequency parameter. Was the result of needing to attain smoother startup movement of the StringCar Racer and other DC motor-based robots. Low-speed movement is especially critical for the String Car when it’s searching for end-of-string, to prevent an acrobatically fatal collision. The guide provides a few practical CircuitPython examples derived from a custom motor testing apparatus that measured motor PWM frequency response spectrum. The MotorKit library was modified to permit adjustment of PWM frequency as well.
  • After the all-too-long distraction into DC motors, it’s time to take stock and reprioritize the stack of unloved projects, unless these two Picos manage to squirm to the top. Oh yeah, after I look into submitting a PR to add UV Index and Lux getters to the LTR-390UV sensor library.
  • Unrelated: Took on a challenge to illustrate a book of poetry for young adults. I’m not an artist, so this is definitely out of my comfort zone. Lesson learned: hide your doodles.

@charlesburnaford (lurking)

52:01 @danh

  • Fixed glitchy RP2040 PWMOut.
  • Finished second USB serial channel.
  • Debugging a BLE problem led to ulab, used by the CircuitPython program that was throwing an error. Fixed by @jepler and @v923z.
  • Looking at I2C problems on RP2040. Added a bitbang fix for short writes, but it appears bitbangio.I2C may have timing issues. Continuing to debug.
  • Continuing to knock off various bugs blocking 6.2.0 final.from usb uefi or legacy

53:47 @David.Glaude (lurking)

  • received my ESP32-C3
  • some failure with reading from more than one LYWSD03MMC
  • adapting and testing Tetris on the uGame10

54:08 @deshipu

  • Trying to improve the displayio.Group by making it use a List internally.

54:50 @foamyguy

  • Last Week
    • Merged base_alignment PRs in display_text
    • Reviewing and testing ProgressBar and Displayio_Layout PRs
    • Learned how to “install” pre-commit to make it automatically integrated with git
    • Successfully sent / received msgpack’d data over LoRa RFM Radios
  • Next Week
    • Begin working inside the learn system on a new guide covering display_text more comprehensively than existing pages.
    • Make a PR for LinearLayout the displayio_layout library
    • Get out my matrix portal for progress bar testing.
    • Test the tab issue fix PR in display_text

57:37 @hierophect

  • Last week:
    • Hacked at the I2C problems on ESP32S2 with GDB a bit, got some decent test results but no substantial progress.
    • Low power on the STM32
    • Extracted out EXTI into a new module and made sure that it didn’t break PulseIn
    • Finished PinAlarm
  • This week:
    • More low power stuff, TimeAlarm, etc
    • The extraction of the EXTI and RTC system means that the RTC and RotaryIO modules might be low hanging fruit.

59:57 @Hugo (will miss, work meeting)

  • Last week:
    • Got 98% through the progress vertical progress bar updates
    • Fixed issues and suggestions from other PB issues into the current one
    • Started working on moving Pylint to pre-commit
  • This week:
    • Wrap up progress bar refactor & vertical
    • Make sure examples still work as expected on devices (not just Blinka-on-computer ones)
    • Work on Cookiecutter to incorporate Pylint
      • Include documentation of changes for changes to apply to existing libraries
    • Add support for anchoring in ProgressBar
    • Might take a detour from the progress bar and work issues on other libraries (open to suggestions and/or requests)

@jasonp(lurking)

1:00:58 In The Weeds

31:02 @ntoll

  • We’ve had several contributions of ideas and PRs about changes and fixes to the CircuitPython mode over in the Mu editor repository (see: https://github.com/mu-editor/mu/pull/485#issuecomment-782879502 for a summary). I’d like to raise this here simply so folks have a) visibility of this discussion, and b) feel invited/empowered to take part in it. I’d feel gutted if folks felt left out. Our aim: reach consensus among folks about what, if anything, could/should change in the CircuitPython mode. That’s it..!
  • Doodle “A Mu-moot about CircuitPython-mode improvements.”: https://doodle.com/poll/uw4mrfe5kuehxqka

1:01:12 @Hugo (will miss, work meeting - if @foamyguy is around, can expand on it)

  • To keep full backward compatibility with the currently published version of adafruit_circuitpython_progressbar, @foamyguy found that we can add an import statement at the bottom of the init.py. This has the immense benefit of keeping all the examples, samples and learn guides as-is. However, we don’t know if adding that import would have any negative impact on memory usage.

1:05:44 @Jose David (missing meeting)

  • Related to a lot of discussions in discord and the work in the new progress bar, I saw that there is a function to transpose xy the tile as a bitmap. I am wondering if we can apply the same to a character (glyph) and have vertical text. Ie for the progress bar or labels. Any insight is appreciated

1:09:02 @Mark(Gamblor) I may be missing due to work if so I’ll ping someone on discord later. If I’m around it will likely be after 2pm CST.

  • Looked at countio for RP2040. The PWM counter wraps at 65536 so unless the user is actively reading it, it would be very easy to wrap and have no indication. My thought is to use a background process in the port_background to just read/update this if it is active. Just making sure that sounds correct.

1:12:33 @TG-Techie:

  • There is still an issue with the lc709203f driver where the chip occasionally doesn’t respond to queries but sends “all 0s” (which appears as crc errors). The chip does support clock stretching. Has anybody seen similar issues with I2C chips?

1:17:41 @deshipu

  • Multiple inheritance from native base classes.

1:27:26 Wrap-Up