 Hello, everyone. My name is Tim. I go by FOMA guy. This is the circuit python weekly meeting for April the 17th, 2023. This weekly meeting occurs on the Adafruit discord channel. During this meeting, we will talk about all things circuit python. Feel free to add hug reports and status updates in the notes document. During the meeting, we will go through them as a round robin sorted by username. As they appear in that document, you can't make the meeting, but you would still like to participate. Go ahead and just add your notes to the document with missing meeting or text only or something like that, and we'll read those off for you. Let's see here. Let me catch up to the script and stop trying to wing it as much. For folks that might be new, this meeting is about circuit python. Circuit python is a version of python that is designed to run on tiny computers called microcontrollers. Circuit python development is primarily sponsored by Adafruit. If you would like to support Adafruit, you can do that by purchasing hardware from their website adafruit.com. Those of us who they do sponsor to work on the project, definitely really appreciate all of the folks that purchase hardware there. This meeting is hosted on the Adafruit discord server. I have just noticed that the timestamper did not actually run, so I'll try to do timestamps manual. I got invisible over here. Sorry about that. It does occur on the Adafruit discord. We'll hold the meeting in the circuit python dev channel, as well as the circuit python text channel. The meeting typically occurs on Mondays at 2 p.m. Eastern or 11 a.m. Pacific time, except when that coincides with a U.S. holiday. In the note stock, there is a link to a calendar that you can view online or add to your favorite calendar app. We also do send notifications about the upcoming meetings in the discord. If you'd like to receive those notifications, just ask to be added to that circuit python Easter's discord role. There is a notes document that accompanies the meeting and the recording. The final notes document includes timestamps to go along with the video so that you can use the doc to skip around and view the parts of the video that interest you most. The meeting tends to run about 30 to 60 minutes. After each meeting, we will post a link for the next meeting's notes document in the circuit python dev channel on the Adafruit discord. Check the pinned messages there. You can always find the latest notes document pinned in that circuit python dev channel, and you can add your notes for the following meeting at any point throughout the week. If you wish to participate but you can't attend, you can leave your hard reports and status updates in that document for us to read off for you during the meeting. The meeting is held in five parts. The first part is community news. This is a look at all things circuit python and python on hardware in the community. It's a preview of the python on microcontrollers newsletter. The second part is the state of circuit python, the libraries and blinka. That one is a quantitative overview of the entire project. It's a chance to look at the project by the numbers separate from our status updates. The third part and the first of our two round robins is the hard reports section. Hard reports is an opportunity to highlight the good things that folks are doing. Take the time to recognize folks in our community and beyond for the awesome stuff that they've been up to. The fourth part and the second of our two round robins is the status updates section. Status updates is an opportunity to report on what you've been up to. Take a couple of minutes to talk about what you've been doing in the last week since the last meeting and what you will be up to over the next week until the next meeting. The fifth and final section of the meeting is in the weeds. That's an opportunity for more long form discussion. Those discussions can come out of status updates or they can be identified ahead of time as something that is going to be too long or involved for status updates. If you do know of any in the weeds topics, please go ahead and drop those down at the bottom of the notes document just as soon as you come up with them. That way, we don't have to wait around too long at the end of the meeting for those to pop up. With that, we will get into some community news. Let me get down there and take the first timestamp. The first item in community news this week is the Sony has backed the Raspberry Pi with funding and access to AI chips. Sony Semiconductor Solutions has announced an investment in Raspberry Pi Limited, the for-profit arm of the Raspberry Pi Empire. Telegraphing hopes that it will be able to make its, I don't know the correct pronunciation, so I'll go with the letters, A-I-T-R-I-O-S, EDGE Artificial Intelligence or EDGE AI Platform, the go-to way to boost the single board computer's capabilities for low-power on-device machine learning. The firm raised the cash at the same $500 million valuation it was worth in a 2021 funding round. The company has become a more active player in the enterprise in a typical year, roughly 70% of its sales now come from commercial customers embedding its products into factories and consumer devices. There are links here to more information about that on CNBC as well as Hackster IO. Next up we have Picon US is coming up this week. Picon US 2023 is coming up in Salt Lake City, Utah. That is going to be April the 21st through the 23rd with development sprints occurring on the 24th through the 27th. Aderford Circuit Python team members are going to be there hosting events. Kat Nyrenbor as well as Jeff Epler will be present along with a few other well-known community members. So if anybody is interested or going to be out at Picon, please let us know in the Discord and be great to meet up with the folks who are there. Next up we have, let's see here, Python Software Foundation is worried about looming EU cybersecurity rules. The Python Software Foundation, PSF, that is the entity that funds and develops Python for those that don't know, they are concerned that a proposed EU cybersecurity law will leave open source organizations and individuals unfairly liable for distributing incorrect code. The quote that's here says, if the proposed law is enforced as currently written, the authors of open source components might bear legal and financial responsibilities for the way their components are applied in someone else's commercial project, product, I should say. The PSF said in a statement shared by Executive Director Deb Nicholson is the one who made this quote for us. So look into that if you are interested there. I know all of us are keenly interested in open source. So I suspect many of us will have an interest in that as it develops. And then rounding out the news items for the week, we have got the project of the week, which is the PyPRCA, Circuit Python Calculator and Computer. PyPRCA is a Python Programmable Calculator and Circuit Python Computer. It has a dedicated numerical key block for better native input of numbers. It also has a QWERTY key set for writing programs functions, functions like sine and cosine are typed out rather than using shift buttons. This device is based on the Raspberry Pi Pico. It's a bit shorter and wider than a NumWorks calculator. And there are links here to the Twitter thread as well as Hackaday IO project page for that device. So those are all of the items for the newsletter. That's where all of these things came from. So let me tell you a bit about that. The Circuit Python Weekly newsletter is a Circuit Python community-run newsletter that's emailed every Tuesday. The complete archives are available on AdafruitDaily.com. It highlights the latest Python on hardware-related news from around the web, including Circuit Python, Python, and MicroPython developments. To contribute your own news or projects, edit next week's draft on GitHub. You can submit a pull request with changes to that draft. You can also tag a tweet with hashtag CircuitPython on Twitter or email to cpnews at Adafruit.com. So that is it for our newsletter segment. So next up we will get into the state of Circuit Python, the libraries, and Blinka. Let me take this timestamp for that one. This report, let me catch up over here actually. This is a quantitative overview of the entire project. It gives us a chance to look at the health of the project separate from our status updates. We'll talk about the project overall and then separately discuss the core libraries and Blinka. So first up I will tell you about the overall stats for the week. This week across the entire project we had 24 pull requests merged. Let's see here. From those 24 pull requests there were 17 authors. I did not highlight names ahead of time, but a couple of the names in here that do look new to me. So thank you to these folks who might be newer or less frequent contributors. M-M-O-N-T-O-L, X-S-T-O-O-K, Flam 84, Andy Bing, Stone Hippo, let's see Steven Gilbert Toski, Anthony W., Apple Cuckoo. Yeah, I think those are the names that jump out to me as either newer or less frequent contributors. So thank you to all of those folks as well as many of our more usual suspects that do appear in the list. We had 10 reviewers this week, so thank you to all of our reviewers. Those do look like the usual list of names. So thank you to all the folks who are working week in and week out reviewing PRs across the circuit python projects. There were 23 closed issues by 10 people and 16 issues opened up by 14 people. So that's it for overall, and I will pass it over to Scott to tell us more about the core. Awesome, thank you Tim. Okay, for the core we had seven pull requests merged from six different authors. I have a couple new folks there as well, so thank you to them. We have four reviewers, as always thank you to our reviewers. We had 24 open pull requests. A number of those are drafts, and a number of those are new, so we're not in too bad a shape. I think we're underneath that like first single page of pull request metric that I like to follow. Issues wise, we had 15 closed issues by six people and six opened by six people, so we're down nine, which is awesome. For a total of 625 open issues, we have eight active milestones, and I'm going to go through these numbers because Dan and I triaged issues last week. So we use milestones as a course prioritization for Adafruit funded folks on circuit python. That is to say, if something's marked long term and you're interested in working on it, please feel free to do that, and we'd be happy to guide you doing that. Okay, so from kind of highest priority to lowest priority, we have zero open issues for 8.0x. We have 10 open issues for 8.1, that's the next stable release we expect to do. 8xx has 28 open issues. This is quite a lot, but a lot of it needs to be retested as well. This is the kind of primary bucket that we went through and got things out of. I think it was 60 or so last week. So these issues are kind of like things we'd like to fix, but not sure exactly when we're going to do them, and they're bugs more than features. Then we have 9.0. 9.0 is our next major stable release, and we have 25 open issues for that, so we move some stuff there, particularly IMX stability stuff got moved to 9.0. And then we have a few libraries, long term support and third party that are kind of things that are either not on our radar, so long term or things that are not necessarily actually issues, but they're the things that we want to track anyway. So that's the state of the Circuit Python core pull request and issues. All right, thank you Scott. Next up, I will pass it over to Katny if you're available to tell us about the libraries. Yep. All right, so this section applies to all of our Circuit Python libraries. That includes everything in the Circuit Python community bundle, as well as the Adafruit library bundle, which is everything that starts with Adafruit underscore Circuit Python underscore and a couple of extras such as our cookie cutter. We had 11 pull requests merged with eight different authors, a number of which were listed earlier as new folks and seven reviewers. I do want to call out one person, Jay Edgar Park. That's John Park and he doesn't typically do reviews, so that's excellent to see his name pop up. Overmerged pull requests. Four of them were two weeks or older. I'm really glad to see that we're still getting through the backlog as we go. Leaving 48 open pull requests. We had six issues closed by five people and nine opened by eight people leaving 611 open issues. And we have 73 of those labeled good first issue. If you're interested in contributing to Circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more including the list of open pull requests and a list of all the open issues as well. If you're interested in contributing by reviewing, check out the open pull requests. If you have the hardware for anything, test it. If you don't, check out the code. Take a look at it for syntax, et cetera. And if you have anything, any changes to suggest, leave a comment or leave a comment and let us know that you took a look and everything looks good. This is always helpful. And once you are comfortable with that, we can talk about leveling you up to the review team. If you're interested in contributing to Python code or documentation, you can check out the list of open issues. You can search by label. If you're new to everything, good first issue is a great place to start. We have a guide on contributing to Circuit Python using Git and GitHub, which is good for both new folks and seasoned folks just to know how we do our workflow and while it's available on Discord to help you. So don't let any part of intimidate you and we want to make sure that you can contribute in a way that works for you. In terms of library, PyPI weekly download stats, our total statistics for all of the libraries, 310 of them that are on PyPI, was 102,476 downloads, which is back up to where it was typically the last few weeks have been lower for some unknown reason. And the top 10 libraries are listed in the Nodes document if you are interested in seeing those. In terms of library updates in the last seven days, we had one new library from Jose David called Circuit Python Simple Dial and a number of updated libraries that I will not read off. And that's where we are with the libraries. All right. Thank you, Catney. Next up, I will send it over to maker Melissa if you're available to tell us about Blinka. I am. So Blinka is our Circuit Python compatibility layer for MicroPython Raspberry Pi and other single board computers. And this week, we had scrolled on me. We had six pull requests merged by four authors and five reviewers. There are currently five open pull requests amongst the repositories. There were two closed issues by two people, one open by one person, leaving a net of 93 open issues. There were 12,437 PyPI downloads in the last week and 16,928 PiWheels downloads in the last month. And we are currently at 101 supported boards. And overall, there was a lot more activity with more pull requests being submitted this past week. And so it's kind of good to see the activity picking up on there. And that's it. Alrighty. Thank you, Melissa. Next up, we will transition into the hug reports section. So hug reports is a chance to highlight folks in the Circuit Python community and beyond for doing awesome things. I'll start and then we'll go down the list alphabetically or however they appear in the note stock. Give everyone a chance to participate. You are text only or missing the meeting. Just leave a note by your name in that document and I'll read your hug reports off for you when it is your turn. So I will get us started on hug reports after I take the first timestamp. Hug reports for me this week. Thank you to Nerodoc who shared a tip about an MIT licensed project called Tabler, specifically Tabler icons Nerodoc shared when I was looking for some icons over the weekend. This project is actually really cool. Not only are there thousands of icons that are free to use, there's also a full kind of front end web template with many great looking example pages that you can build your own websites from. So that's actually really cool. I may be looking into that to do some other stuff with it as well. So cool stuff there. Thanks to Nerodoc for that. Hug report to Jeff for working on Synth.io as well as Todd Bot and JP for testing out the early versions of that. I'm excited to play with that. Thank you to Scott for working on support for the DVI output as well as Mark Gambler for testing that out and then a group hug to everybody. Next up is C Grover who's not attending. So I'll read. C Grover has a group hug for the team and community and a hug report for Paul Cutler for the reawakened Circuit Python podcast. Next up is Dan H. Okay, thanks. So these are all pull requests from Circuit Python. Thanks to Flyme84 who is doing some work with GCC 13 and fix some things in advance of that. We are still way back, but we will be moving forward at some point. I'm glad to know that it mostly works. Thanks to Apple Cuckoo for a documentation fix. Thanks to Iscabaden for adding a Web Workflow name setting in settings.toml. Thanks to Retired Wizard for various fixes and testing of all kinds. And thanks to the folks at SyLabs who ported Circuit Python to a new chip family and contributed quite a substantial pull request and Scott has more about their thing in hug reports also. Okay. All right. Thank you, Dan. Next up is hug reports from David Glauda who's not present. So I will read. David has hug report for John Park for promoting the WeChuck community library and the UDRAW, probably MicroDRAW I'm guessing is how that would be pronounced, tablet in the Circuit Python parsec video. Another hug report for Jeff as well as Todd Baugh and John Park for work on Synth.io and the envelope. David says he's still learning MIDI and Synth, but I felt the interest, probably felt the interest in this even if it does require a Biffy MCU, Buffy I'm assuming they're like a larger MCU. Hug reports also for near doc for network stack stuff that he's working on, universal API as well as WebSocket. I know this will be useful to all. And then rounding out David's section, there's a hug report for Paul Cutler for new episodes of the Circuit Python podcast. Next up is DJ Devin 3. Oh, there we go. Okay. I have a hug report for Katnie for documentation and leadership in the Discord Helpers channel that's behind the scenes stuff, but she's continually updating and revising things to help others help you to help yourself kind of thing. So thank you for all that. She knows what she's done. So thank you. A hug for NaraDoc for guiding me through using display shapes with display I.O. I completely misunderstood the way that group of pens worked and now have a much better grasp on hiding or showing UI elements and I'm really excited about getting into GUI design because of him. So thank you. Hug to Anikdata and Hopkapi for a late night help session and troubleshooting a problem with the Feather S3 onboard battery monitor throwing an OS error during read failures. They give excellent advice for using try accept and power modes to filter the issue and improve performance. The failures of it happen about every 12 hours or so, so it's not like a fast iteration cycle to track. So it's going to take a while to solve that. All of your advice put me on the right track. Thank you very much. And a big hug to all the CircuitPython developers for fixing the Wi-Fi related hard fault bug on the S3. My Feather weather station is now back up and running thanks to all the S3 updates after the 8.0 launch. It wasn't working before 8.0 and now after I loaded 8.0.5 it's now just magically working. So thank you to all the developers that work on the backend every day. Thank you. Thank you. That's it. All righty. Thank you, DJ Devon. Next up is Katney. Hello again. So first and foremost, I want to thank Phil Lamour for coordinating signing two 8.0.0 lunch boxes for me so I can put together two kits to donate to the Pie Ladies auction at PyCon 2023. Pie Ladies is a Python group that is open to all but puts a lot of effort into ensuring that women are represented. They take donations and so on to help fund a number of things including people who may not be able to afford to travel to conferences. They help with the help covering travel and so on and so forth. And every year at PyCon they do an auction where people donate stuff and then it's a whole dinner and it's a whole event and it's amazing. And the kit I did last year went over pretty well and this year the two that I'm donating are signed by Lamour. So a super secret addition to that situation so I'm hoping that works out. To everyone who's been helping me with PyCon preparation, it's too much to list specifics but you know who you are. To Jeff, I'm looking forward to seeing you later this week. To Tektrick, the same thing. Hug report to Foamy Guy for writing fantastic badge code for me. I'm super excited. It's that it's received a lot of updates since the last chance that I got to take a look at it so I'll be popping that onto my Pie badge later today. And it's exactly everything that I hoped it would be so I'm looking forward to that. And to Sea Grover for slimming down the improved thermal camera software so I can put that on my badge as well. It'll have a normal badge going on. There will be a game of snake and also a thermal camera. So I tossed a feather wing on the back of the badge. To Naradok for helping me sort out button debounce without using keypad in a way that doesn't max out the circuit playground express. I have done it a number of times but not anytime recently and was completely gone out of my brain how to go about that without either introducing another library or a lot of extraneous code. And Naradok's suggestions were far better than what I want to come up with. So sorry to those I missed. It's been nonstop for the last week and a group hug to everyone. All righty thank you Ketny. Next up is maker Melissa. Hello Melissa. I wanted to give a start by giving out to I'm not sure how to pronounce this Creechy for all your contributions to the Circuit Python code editor. I hug to Alex Corvix, Corvus 84 for testing out the possible some possible I2S Mike script fixes and several different configurations on the Raspberry Pi. I hug to Dan for leading the effort and making the Blinka documentation better. And Ketny and Jepler and anyone else attending PyCon this year and a group hugged anyone else. Awesome thank you maker Melissa. Next up is Mark Gambler who I will read. Mark has a hug report for Scott for Preliminary work on DVI support that Mark experimented with over the weekend. After that is Michael Pocusa. Let me get the timestamp in there. Michael has a hug report for DNH, Anecdata, Naradok, and Deshipu for discussion about Adafruit HTTP server and security concerns related to accessing parent directories. Next up is Paul Cutler. Thanks Tim. A hug report for Jepler, Todd Bot and JP for their work on SynthIO. It's been really fun following along which inspired me over the weekend to learn more about Synth and MIDI and a hug report for Liz for her MIDI for Makers guide. I learned a ton this weekend. Thanks. All right. Thank you Paul. Next up is Todd Bot who I will read. Here Todd Bot has a hug report for Jepler for SynthIO work even during vacation. It's so fun and works on RP2040. And then a hug report also from Todd Bot. This is to Tektrick, Naradok, and Scott for teaching Todd Bot about the const function. And then next up I will pass it over to Scott. Thank you Tim. First a hug to TS for the web workflow testing and improvements. They've done a couple really awesome improvements for web workflow. It's great to see people using that and improving it. Also for Maker Melissa and I'm going to say Crikey. I think it's part of their name. For code editor improvements I'm really happy to see people starting to use code.circuitpathen.org and getting to the point where they're actually making it better too. A hug to PsyLabsBilla5 and PsyLabs Chat and Win for the PsyLabs XG24 port PR that Dan referred to as well. I'm very very exciting to see folks from a microcontroller like semiconductor company bringing CircuitPython to their devices so that's really really awesome. A hug report to Todd Bot and JP as a couple folks just mentioned about for testing just SynthIO envelope improvements. I'm very excited to see that and I think it's going to I hope it will dovetail nicely with this DVI stuff. And then last up a hug report to Katni and Jeff for representing the Adafruit CircuitPython folks at PyCon. All right thank you Scott. Rounding out the hug reports section is Tektrick who's missing the meeting. So I'll read. Tektrick has hug reports for Niradak for helping me understand how imports work with regards to RAM. A hug report for Todd Bot for raising an interesting conversation that helped me better understand how const works and a group hug for everybody. So thank you to Tektrick as well as everyone else who participated in hug reports this week. Next up will be the status updates section. Status updates is our time to let's see here let's see lost my spot there. Our time take a couple of minutes to talk about what you have been doing since the last meeting and what you will be doing until the next meeting. It's also an opportunity to provide tips and tricks relevant to what people are working on. If a discussion does become too long for status updates we can always move that down to in the weeds. So I will get us started on status updates. For me in the past week or so I've been working on enhancements for the Pi Badger conference badge app as well as the snake game that it launches. To kind of go along with that one of the things that was added was a menu to be able to launch other programs like the snake game and the camera that Katni mentioned. This menu is drawn with a library called list select which I had actually made a while ago but it turned out never actually formally released. So as part of the process I got that actually released and up on GitHub and in the community bundle this week. The other thing that I started working on over the past weekend has been a weather station or IoT server that runs on a Raspberry Pi. So this is a Django project. It basically runs a server on the Pi. It can collect data from local sensors either connected to the Pi via i2c or spy or however and it could also collect data from remote sensors that is passed over the network back over to that device. Once the data has been collected I'd like to make some pretty dashboards that show charts and you know highs and lows and things like that with the information that it has collected. I don't have the dashboards working quite yet but that's kind of the my goal for this whole project. I'm intentionally trying to make it a little bit more generic than just my specific use case so I'm interested in temperature and humidity but I'm trying to keep it kind of general enough that it could be used for other things as well if somebody else wants to repurpose it or even just learn from it to make something. While working on that I teased out an issue that cropped up with a SI7021 sensor on the Raspberry Pi. Turns out this sensor was not working at least with the currently released library so I'm tinkering around with that and I think I have actually got a fix that can work for that but I need to submit a PR later on for that. So those are the things that I have been up to. Next up is Cgrover who I will read. Cgrover says the precision VCO project is working nicely now after experiencing some weird DAC behavior when using both the itsy bitsy M4 DACs those are A0 and A1. When A0 wasn't instantiated the output voltage would slowly drift from 0 to 3.3 volts and then hold at 3.3 volts until the value was set in code. If A1 was subsequently initialized A0 would again slowly drift from its newly set value to saturate at 3.3 volts. The workaround is to set A0's value in code just after instantiating A1. It's not ideal since A1 creates a pop when it suddenly changes values. Cgrover has filed an issue documenting disinformation. In the process of testing the M4 DACs and looking for other more available MCU options. Cgrover noticed that the ESP32S2TFTs A0 DAC truncates and reverses values below the midpoint. The A1 DAC works as expected. They'll do some additional testing before filing an issue. The photo which is in the document here if you'd like to take a look at it this photo simulates, excuse me this is a photo of simultaneous sweep of A0 which is in on the top in yellow and A1 which is on the bottom in blue from 0 to 65535. All right and next up for status updates is Dan. Okay thanks. Okay last week I mentioned I was testing the Bosch BNO 055 which doesn't work very well on the I.MX board the Metro M7 and a couple other things like the ESP32S3 and I tested the BNO 085 and it's similarly a problem. This is really more a problem with these chips which violate the I2C protocol sometimes. So I added some learning guide alert boxes and a fact entry there and maybe eventually we'll make the drivers be more robust to these errors but the problem is really in the center chips themselves. As Melissa mentioned I was thinking kind of inspired by something Neridoc mentioned in Discord that we could improve the explanatory material in the Blinka-based guides or the Blinka intro guides and so I'm going to work on that and Carter will and Melissa will review it. And as we mentioned we got mentioned in the status we triaged the 810 and 8XX issues we assigned some of those issues to ourselves and to Jeff and we moved a bunch of issues to 9.00 or long term because they don't really need to be fixed for 8XX. And I'd like to now get back to reviewing Greg Neverev's Asyncio proposed changes now that hopefully we're seeing the light at the end of the tunnel for 810. Okay. Alrighty thank you Dan. Next up is David Galato who's not present so I'll read. It says not much so far for this week and a new acquisition of a device not yet supported in Circle Python is the Feather DVI, the Feather USB host and Intelli-key adaptive keyboard. So a couple new devices that David got a hold of this week. Next up is DJ Devin 3. Thank you. This week I submitted a PR example for sequential chaining of the four 13x9 matrix backpacks and submitted a request to add tuple ITUC address support to the IS-31FL3741 library which is the matrix backpacks. I'd like to get all four working together as one horizontal RGB matrix kind of like chaining seven segment backpacks but my hands are tied right now for further progress without the tuple address support and I'm hoping there is current limiting code in there where you can drop it down drop one down all the way and I'm hoping that might be enough in order to get at least two or three working if not all four simultaneously. I designed a 3D printed part of a hinge redboard wire storage box my first 45 degree print the rest of it should be finished printing by tomorrow each part is a 30 hour print started exploring a mini RC robotics project combining an RC toy tank and camera system and I'm hoping to use it as a cheap and fun way to inspect inside of the plumbing drains under my house which are encased in a slab of concrete I designed a 3D printed no I just designed a workbench lamp that housing that combines a fume extractor lamp and webcam mount into one piece I'm still working on the electronics and I hope to control all of it with circuit python I have yet to print or combine the electron oh if anybody wants to take a shot at doing that first the STL files are already available on printables it's just too big for my bed so I have to like print that on a 45 degree angle which is probably going to be a three-day print for me and I want to say thanks to the 8.0 updates I was able to renew my feather weather station tft project on the s3 without it crashing every couple of minutes and I added a high pressure and a low pressure system pop-up using display oh that serves as a rudimentary storm warning system uh that's all I got all righty thank you DJ Devin uh next up is fed a 2 whose text only fed a 2 says they've been working on coding a music instrument pedal that uses AI to unmix any song into its component instruments and then uses blinker and seesaw rotary encoders to let you mix it however you'd like perfect for practicing a song or just to have fun and replace your favorite guitar drum or bass player or singer waiting for qtsd card and some m7 boards as they take some time to make their way to Costa Rica to develop another version with cheaper hardware the current version uses a pi 4 and there are links here to a video as well as a github repo if anybody is interested in that as I certainly and that sounds like a lot of fun the other item that fed a 2 has is trying to port blinker to a mango pie which is a round 20 risk v64 board but I'm still having trouble getting i2c working in all available Linux distros all right so that wraps up fed a 2 next up is catney hello so the rfm 69 guide went live uh with uh without the circuit python essentials pages those have since been completed and uh the final touch that it needed was a basic radio demo because that's what most folks want to do with this board is receive and uh send data so I have added a page that includes an example where you press the the button on one feather and it changes the neopixel on the other feather so that should be um that should be good to go it's in moderation right now so it's not live yet but it will be very soon and then uh it sounds like um someone else who's working on arduino stuff for these boards is going to add the arduino radio examples so that they're available in both languages so today I'll be starting the rfm 95 guide it definitely isn't going to go live until well after pycon so um you know be excited about that but don't get too excited um for what it's worth uh the the code for the rfm 69 and the rfm 95 is different there are two different libraries but almost everything else about these feathers is identical so if you're interested in you know anything that isn't related to the radios uh code wise check out the rfm 69 guide it'll tell you a lot about your 95 as well um so uh today is going to be the rest of the day will be pycon prep i am off beginning tomorrow and i leave for pycon early on wednesday i return to work on may 1st um while i'm at pycon i'm giving a talk at the education summit before the conference that's at 11 am on thursday uh april 20th i'm attempting to record it no promises uh but fingers crossed um i have all of a massive av set up to do this but it'll be the first time i really use this particular setup so i'm not holding my breath but a lot of people expressed interest in seeing my talk who couldn't make it so i'm doing my best i'll be hope hosting open spaces every day during the conference proper which is the 21st through the 23rd and then i'll be hosting sprints on the first three days of the sprints which will be the 24th through the 26th there is a final fourth day of sprints that i will not be um hosting that day um if you'll be there come and find us it'll be jaffa and i uh tech trick alex will be there um kthie will be there it turns out um and so uh yeah we'll be around um for sure you'll be able to find us at the open spaces if you check the board and figure out when they're scheduled um but i'm sure that if you message me on uh discord uh or something like that um we can eventually set up uh a time to meet up um outside of that and that's what i've got all right thank you catney uh next up i will send it over to maker melissa oh um so i was out sick last week so i missed the meeting because of that um but i finished my chat gpt bear guide and showed it off on shone tail i also helped and with uh an animated gifts project i fixed the st 7789 display script or the um the pi tft script and uh because it was it was not compiling so i fixed it by not compiling and when it's not necessary and uh currently working on a project that i'm collaborating on with erin st blaine and after that i may try and fix some more of the raspberry vice scripts and i will be out next week because i'm moving and that's it all right thank you melissa next up is mark gambler uh who says uh i tried out the dvi support to some success i'm willing to do more testing if required uh and also mentions dvi support and general memory usage had me thinking about on-disk gift palette support uh so on my radar when the time permits next up is paul cutler thanks tim uh last week i recorded two podcast episodes with dan h and ben shockley who created the minifig board so you can look for those uh in may as i mentioned earlier i spent the research the weekend researching synths and midi um which just kind of blew my mind and then um trying to figure out how i might be able to run the podcast on 100 percent open source software which might be a challenge i accept um and this week i finally ordered all the parts to build the pico step sequencer by todd bot and hope to build it this weekend thanks nice thank you paul uh next up is scott hello um i've been polishing up the dvi support um folks are excited i'm excited so i'm working on getting that uh fully in uh and having some trouble re-initting the display code so like it starts up automatically but i want to be able to like de-init it and re-initialize it maybe in a different mode say switching from color to grayscale and back and forth and that sort of thing uh generally this stuff introduces a lot of complexity around the second core running code separately and there's a risk that if it runs code from flash while the first core that's running circuit python is trying to do flash stuff it could be really bad um generally everything needs to be put in ram so that it generally just doesn't do flash code um turns out the rp2040 is awesome in that it has an mpu which is an memory protection unit um this allows me and i'm going to do this today i can set it up so that after core one starts up it just won't be able to access the flash it'll just crash instead and hopefully that'll improve uh the reliability of the flash functions that is something that mark ran into and thanks again to mark for doing an early test on this also triage bugs at dan i have a couple smaller tasks to do after the dvi pr is out for review and i also need to pr the imxrt changes that i was working on a week or two ago as well so uh plenty plenty for me to do all right thank you scott uh next up and rounding out the status updates is tectric uh who i'll read uh last week tectric says took care of some pr reviews for a few different libraries uh also resumed work on the library ram consumption ci checks uh for this week tectric notes uh out for patriot stay slash boston marathon monday today uh heading to pycon on wednesday excited to see everyone else who's attending and will try to present the aforementioned ci checks after the checks after getting uh i think after getting to pycon or maybe after getting back from pycon perhaps uh since i plan to help out with the sprints during the next meeting time but i'm really excited for the current plan which would allow for future checks to be integrated easily um all right and that was the last of our status updates uh so our final section of the meeting is in the weeds section uh as a reminder in the weeds is an opportunity for long form discussions that either come out of status updates or are identified ahead of time as in in the weeds topic um we currently don't have any in the weeds topics down there so i think we are good to go on that for this week which means we can get into the wrap up instead so uh this has been the circuit python weekly meeting for april 17th 2023 thank you to everyone who participated if you want to help support aida fruit and circuit python and those of us that work on circuit python please consider purchasing hardware from the aida fruit shop at aida fruit dot com the video of this meeting is going to be released on youtube at youtube.com slash aida fruit and the podcast will be made available on major podcast services uh it will also be featured in the python for microcontrollers newsletter which you can visit aidafruitdaily.com in order to subscribe to that uh the next meeting i believe will be held at its normal time on monday at 2 p.m eastern uh next week which would be the 24th of april uh but somebody can let me know in the chat if i am wrong on the date there um the meeting is held on the aida fruit discord which you can join at uh adafru.it slash discord uh yeah thank you for the confirmation there um if you do want to participate or get pings about those upcoming meetings again a reminder you can ask to be added to the circuit pythonistas roll over on discord so that's it for today we hope to see you all next week and thank you everybody