What you've seen today is that we've completed an attack with the Danish attack squadron supported by a German JTAC and American Apaches. We utilized the effect of the Apaches before the attack in order to take out targets in depth and afterwards we initiated the attack with the tank squadron moving into positions and from here conducting a fire and maneuver.


Look at this, what a thing. Yes, day in the bay and we've got classic split-stream Volta again, I mean what more can we have for it? And it did make it in, we were a little bit nervous that it might not, but it feels closed. We've had one in before and that was Polysipala's ice cream truck. So cool. Really cool. I mean I'm excited about all the days in the bay. Look it's a split-stream, when do you get to detail a split-stream van? I don't, not split, not since the last Polysipala one that was with an ice cream. No ice cream today, but it doesn't matter. I'm rambling. So today, I mean we're going to get it washed and dried. Terry Deona is really into his car care and detailing. Like I said, there's no swirls on it. He details it regularly, takes to a lot of shows and events. He's going to be joining us for early addition at Cyworld this weekend as it's going to be on the stand. And yeah, so just kind of find out from him what he wants to get out of it and why he's come and you know what products he wants to play with. So if people don't know how to get in the bay, contact us directly. So it's dmastamentatmagwires.com. Contact us images of your show car or project build and a list of shows and events that you go to. Then if we can get it in, we will. Good job, let's crack on. So there's a lot of negativity when it comes to using a waterless product on your vehicle or the paintwork. But what we'll always say is it's perfect for a dirty clean vehicle. So something that's been cleaned, driven to somewhere and just need to spruce up. It's got like road grime and dirt on there. The reason it works so well is because it encapsulates and lubricates the road grime and dust away from the surface rather than just saturate it and push it around. So that's why I would always have by using it. Cool. And then we've got two towels, one for taking dirt off and one for making clean. Exactly about. We've got two towels when folded, make 100 towels. Yep. So we're using a nice pile on our towel, which is going to like say grab hold of the dirt, embed it into the pile and remove it away. Like I said, I do fold them, which means that every time I go into a new panel, I unfold it, it's a fresh new microfiber towel. And then your second towel is going to buff the surface and kind of bring that wax to a shine. So we'll protect it once used as well.  Then if you don't want any kind of white marks and streaks in the car, get your buffing towel and go in the opposite direction. This way you're not constantly using the same movement on the paint and you won't get any white marks. Just to give everyone a delve into the world of content creation from Aguayas, our content creator is borrowing my phone to take a picture. Your foot's in the shot. Can you believe it? I'm stood here and your foot is in the shot. Sorry, sorry. Well for some reason. Is it superior? No. It's not superior than our iPhone and I will never conceive to that. I'm maybe two feet away from the bus and I've got the whole of it in. Let's see that. Yeah, science. You mentioned that you use the ultimate paste wax and my lot on the on the van. So we're going to be using, we're going to switch it up because we know I'd always go to a paste wax and if you had Tom in here, he would favor towards the liquid side. So what we're going to do is show you how to use the liquid and how it's different from the paste. Performance wise you're going to see the same, but you can use these slightly different. So with this you can actually use it with a machine. So on a vehicle like this it's so big and vast, especially for like the big long panels, side panels just can make your life a lot easier. But you can still use it by hand around the intricate parts. So I'll show you how to use it with our DA machine and also the black finishing pad. So this is ultra soft. So you mentioned earlier about all different types of pads and products. So we have a burgundy cutting pad, which is a firm pad for swirl removal and defect removal. The yellow polishing pad for refining and then this really soft finishing pad for waxing. So on the, sorry, going back to the burgundy pad. What product would you use with that? Yeah, to take out swirl. So it'd be like an ultimate compound. Right. Something like our ultimate compound. So if you feel that. Yeah. So that's a lot firmer. It needs that back firm behind it. When it's got product in it and it's going at a heat it will get softer. The reason it's so rigid is so you can cut through those swirls and scratches. Right. A good middle ground is the yellow pad. So you can see it's softer. It's still got a bit of back to it. It's still quite firm. So it will refine the paint. Then ultra soft black pad. Yeah. So kind of revival refining protection. And sorry, products to use with that. Ultimate compound, ultimate polish, ultimate wax. Right. Okay. Yeah. So any kind of mid range refining tool, whether it's like 205 or 210 or ultimate polish would be great with that. Yeah. Or if you've already taken the hard swirls and scratches out and you want to maintain it, you can get rid of that and maybe use ultimate compound with that if it's swirl but not heavily swelled. Yeah. So it's just adapting it to the paint. Right. Okay. So normally if we're working a product like a compound or a polish, we would prime the pad. Yeah. But because we're only applying a wax, we're not working a wax. All we need to do is put a small amount of product on it. So let's get the wax nice and short go up. I use the back kind of the lid there to kind of get a nice clean line like that. So that's all you need. And you only ever top this up when you start seeing gaps in it. Right. So this should, theoretically, pretty much most outside. Really? Yeah. You should barely see it. It should be a fine, right, finer film technology that's called a wax. I've probably used half a bottle. So it's like, you know, if you put way too much lacquer on a car, it's never going to cure. It's never going to harden up. No. If you put too much wax on a car, it's never going to cure. Right. It's going to get quite muddy and when you're wiping it down, it will kind of look cloudy and stuff like that. So if you've got a fine film or wax, it's going to firm up nice and hard. You'll take it off and you've got a good layer of wax on it without doing too much work. Yeah. Stamp out the area you want to work like this. Set the speed to the slowest on the machine, which is free. Okay. And then the golden rule is the slower the machine's moving, the quicker you can go. Because we're not correcting, we're just applying. Yeah. Whereas if we were correcting, we'd be going much faster on the machine, but slower on the arm movements. Right. That makes it because we need to give it time to work it, but because we're just applying a product, it doesn't matter. Okay. So turn it on. Nice and quick. Always start and stop on the panel. That's done. Okay. That's as much wax as you need on the surface. Right. Okay. Is that a lot less than you may be used to seeing?  Yeah, yeah, yeah. Throw it on a little bit around. I would have probably gone over that three or four times. No. I'd go sideways up and down. Yeah. Sideways and then up and down. Which is cool if you're working the product. It's a good practice to have. Yeah, definitely. So if you were compounding or polishing, exactly that. Yeah. Because we're just applying the wax, we're just applying it to the surface. We're backing off from the paint. Yeah. That's it. That's all you need to do. So it makes your life ten times easier. Yeah. That's it. Done. Right. Because it's synthetic, it's going to stay nice and cool, which means it won't harden like a cannibal wax. Cannibal wax is because they're a natural material, can get quite firm. Yeah. Whereas this will stay nice and soft. So you can confidently cover the whole van knowing that you're going to be able to take it off. While he's machining, obviously there's quite some intricate areas on here. But we probably won't want to get in with the machine polish. We're not going to rattle the ease or shake any of that. So it's going to use it by hand. Per section. Talk about that. That's it. So before you do it, put some lines across it like that. Yeah. This means when you go over it, it's going to top up the pad. It means you get a nice even spread. And that'll do the whole project. Oh yeah, completely. So just to recap on what we're doing and why we're doing it. So we've got Terry using the machine polisher with the blank finishing disc and our ultimate liquid wax. It's not because it's such big panels. He says he likes to use a DA, but he just wanted to know how he could use on using a wax. So we're using the liquid wax with that to make his life easier. If this goes to a lot of shows and he likes to look at best, you can see how good the paint is. And so we don't need to do any correctional work, just a bit of enhancement of the gloss really. Then we've got Lauren over here using the same wax, but by hand. So for the smaller intricate areas, same wax, same liquid wax on a black soft foam Africa pad, which is exactly the same as our yellow soft foam Africa pads, just black as it comes with wax. And then we're just going to get the whole car covered, let it cure, then take it off for the finishing towel. This is the area we did first. You can see that it's nice and cured there. So we're going to use our finishing towel. So these are, you know, we've been using the regular myfab towel. So with detailing and removing wax, you want to go for all two nice soft, lush ones. Yeah. Oh, sweet. So you know, we've been doing up looking down, left and right, exactly the same. So take the kind of wax off there, flip the towel. Look that way. That's it. Okay. That's as easy as the wax should be to take off. Be nice and clean. You see, that really takes us about another 10 minutes to get the wax off. Oh, does it feel like it drags and stuff? Yeah, like you'll wipe it and then you'll see another bit. Streaks and stuff. Yeah. Yeah. Cause a lot of people kind of like go crazy like that. And sometimes you put too much heat through it and it kind of harms up. If you're just nice and chilled out, just nice, clean, wipe lines like that. So we used a waterless wash mic anywhere on the body. So this is the waterless wheel and tyre. So it's a heavy duty detailer and tyre dressing. So we just get it on there. Make sure you get it on the tyres as well. Then with the microfiber towel, wipe it down. So with a separate towel, I'll pinch it. With a separate towel. If you like them looking glossy, leave it. But if you like a satin sheen like me, just run the towel over it like that. So if you wanted it shiny, you wouldn't have to try shine afterwards. Exactly that. Yeah. So it's going to dress the tyres for you as well as clean the wheels. Okay. Cool. Nice one, isn't it? And it smells amazing too. So another day in the bay done. What we've done today is kind of come away from our usual processes of you know, compounding it down, reviving it, refining it, protecting it. We've come away from that and we've kind of stripped it down to a nice gloss enhancement detail. So we cleaned it down using the waterless wash mic anywhere. It didn't need clean. It was perfectly smooth. And then we showed Terry how to use our ultimate liquid wax with a machine polisher to really enhance the gloss but also use it by hand as well in some of the intricate areas. We finished off the glass and we used the waterless wheel and tyre. It really didn't mean much doing to it. You just needed a nice gloss enhancement. People always ask what's the difference between the paste and the liquid. As long as they are the same wax performance wise, you're going to get the same amount of gloss and performance protection. And it's just you can use them differently. I like a paste wax. I like that kind of hand kind of finish. You can still use the liquid by hand but you can really get the benefit from it by using with a machine and especially if you've got a bigger vehicle or times at the essence.  And yeah, good job. Good job. Thanks. Big snap. Good way. See ya.


What's up everybody? It's Jason here for jasperjasecasebrakes.com. Another $500 being given away here with this 21-22 prism choice basketball 4 box break PYT number 9 Here we go guys so Joe got last one magic and here we go another four boxers I think we just opened up the case number eight, so we just grabbed four randoms just and See we can get some nice stuff All right, it looks like no tiger stripe here, but So you get a nice couple colors or Duncan Robinson Norman Poel There's Garland and a Moises moody for the Golden State Warriors, which is going to Aaron And we got Ricky Rubio and a nice dissoon move for the Bulls number to 88 Bulls is Aaron that's number 239. Ooh, do we have a green coming up out of eight? Yep, green out of eight. We'll take that. Here we go. Scotty loose Yonatan to the Kumpo We got Deloni rights Moises brown White chocolate Jason Williams Whoo Nick Smith got the Detroit Pistons straight up and got rewarded with a Cade cunning hand. Let's go nice Danny green to 88 and it's a rookie Golden State Warriors. Oh bad Juan Toscano Anderson a little bit of a teaser there Still nice hit though for the Warriors Aaron 7 or 1 at 8 That would have been a crazy box of those like a flamingo. Nice Cade All right, two more boxes maxi Bridges Marcus Morris Ben Simmons Juan Toscano Anderson and a Rick Fox for the Lake show going to Matt and we got Cooper Fred Lannister 39 and then Greg Brown was a third to 88 ATL is going to Eric Portland is going to Aaron last box here guys two reds it looks like Tires maxi Jared Allen Isaiah Jackson And a Jeremiah Robinson Earl for the Thunder Brandon Boston Jr. There for the Clippers And a Ricky Rubio to 88 All right, we had one really solid box, which is really nice getting a Cade in that green The other ones were okay And not the best But I definitely want it better But another one's posted but again, I guess no chance to win back some money $500 though, so there you go Okay Soon move Moises moody All right, let's do it. Let's see who's gonna win some money back. Let's copy everybody's name here Let's roll Five into two lucky number seven one two three four five six and seven seven times seven five two seven seven oh Just missing on Nick. Sorry, buddy But Nick Wow There you go top two what a break for you man. You bought the pistons and the Rockets Let's go. Congrats. I don't know what you would have been the pistons There you go man. Congratulations. You just won $500 back in break credit So I'm gonna send that out to you, buddy. And like I said Do you want to use that on this break again or any other break you want on the website? Whatever you want, buddy Let me check and see the most recent email you used because it looks like you have two on file I'm just gonna give it to the most recent email you got. Okay Just that yeah, like that be all a big make or something like that. Yeah, okay I appreciate guys another one is in the store. Thank you


Welcome everybody to this panel discussion on the first global platform sponsored by the Open RAN Alliance or ORAN. My name is Drew Gupta. I'm with AT&T and I'm currently the co-chair of ORAN Alliance Working Group 2. And it's my pleasure to host this panel with my colleagues. Next slide, please. So just a bit of introduction to the ORAN Alliance and the platform. So ORAN Alliance is a consortium or global community of more than 200 members, including mobile operators, vendors, as well as research and academic institutions. And all of these members are committed to evolving the current radio access networks based on the core principles of openness and intelligence. The key mission for ORAN Alliance is to drive our industry towards a more open, multi-render, virtualized and interoperable network stage. And the ORAN Alliance accomplishes this in many ways. It publishes RAN technical specifications related to the interfaces that are defined by the ORAN community. And it also releases open software via its ORAN software community or OSC. In order to showcase the nature of the interfaces that are being defined by ORAN, including the O1, A1, E2 and front hall specification, and to highlight the multi-vendor interoperability aspect, ORAN conducted its first global podcast in December of 2019. This was attended by 30-plus operator and vendor partners. And all together they demonstrated 10 different scenarios and use cases that both highlighted and validated the interface specifications that have been published by ORAN so far. The breadth of the use cases varied from demonstrating the open front hall interface between the DU and the RU units in the ORAN architecture to also demonstrating the O1 interface and the ORAN-defined SMO and their role in enabling vendor agnostic test gaps of RAN nodes. The first version of this ORAN plug-fest occurred in North America on December 5, 2019. This happened as a mix of both online participation as well as on-site demonstrations conducted at the open wireless lab at Rutgers University in New Jersey. The demonstrations were conducted by various companies including AT&T, Comsco, Ericsson, High Street Technologies, Nokia and Wipro. The companies demonstrated four use cases related to the ORAN-O1 interface and an ONAP-based service management and orchestration platform or the SMO. And the use case is focused on demonstrating the physical network function or PNF plug-and-play, bulk performance management data collection, RAN optimization use case related to PCI and RSI optimization, and also basic test gaps of 4G LTE small cells. And just a quick nod to the large number of members from all of the different companies that were behind making this plug-fest a great success with other contributions would not have been able to demonstrate the use cases successfully. So thank you to all of them. Now I will go ahead and introduce our panel members and that will lead us through today's discussion. First, we have Zak Lava from Comsco. He's a product night manager for small cells at Comsco and is responsible for the one-cell solution including service management and orchestration. We also have Ben Ching from Nokia who's a system architect in 5G Cloud RAN and ONAP and he's been working in the wireless industry for over 23 years and focuses on ONAP RAN use cases. We also have Mikayla Bevilakwa from Ericsson, who's a researcher in RAN standard and technology organization, and she represents Ericsson at ONAP for RAN-related topics. And finally we also have Haseeb Akhtar from Ericsson who's responsible for end-to-end network evolution at Ericsson and also represents Ericsson at ORAN Alliance's Working Group 1 which covers use cases and overall architecture. So now I will hand it off to Zak to lead us through the first demo. Zak? Yeah, hi everyone. Zak Lava here. For this plug fest, what we wanted to demonstrate was that legacy 4G devices implemented using 3GPP compliant data models could be adapted to follow an 01 compliant service management model. And this is really done in recognition that open RAN really needs to consider all aspects of the network. It's more than just about radios and it requires a uniform service management orchestration interfaces with an ability to also manage legacy devices. And for this demo we deployed a fully functional end-to-end setup at the Rutgers Open Wireless Lab. We used a mix of real and simulated one-cell C-RAN based band controller devices, each communicating to an instance of our TRO1 adapter. The adapter translates the protocols and data model parameters between the device and the OWNAP functions. And so from the perspective of OWNAP or from the service management orchestration layers, the adapter is essentially the device itself. And so next slide please. And so in this plug fest we demonstrated three OWN aligned use cases using OWNAP together with the TRO1 adapter. The first use case we demonstrated was a device initiated physical network function registration. This enables a new device to become known to the service management layer, thus enabling FCAPs for it. The basic flow is that the device will send the TR69 bootstrap to the adapter, which in turn translates that into a VEDS PNF registration message, which gets sent on to DCI-E. From there it gets forwarded to DMAP, the messaging interface. And from there SDNR then receives the notification. That closes the loop and now allows the remainder of the use cases to take place. The second use case was a demonstration of TR69 fault events being sent by the device with the adapter then generating a corresponding VEDS alarm. And then the VEDS alarm follows the exact same path through DCI-E to DMAP and ultimately where an SDNR is notified of the event, which can be observed through the ODLUX user interface. Lastly we demoed focusing on configuration management aspects. So with the adapter we provided Yang definitions that included the broadband forum TR181 and TR196 data models. And these are the same data models that were used by the device itself. These Yang models were in fact presented to SDNR by the adapter during the initial bootstrap and registration procedures. Using ODLUX we were then able to go into SDNR and trigger it to request the device to get parameter values for the device as well as the ability to edit or change the values on the device itself. These three essential use cases demonstrate that legacy LTE devices can be adapted to follow the O1-based management model. Now I'll hand it over to Ben who will share with you the details of Nokia's plug-and-play with Saun demo. Ben you're on mute. Sorry I'll be talking about plug-and-play in ONAP. It happens in five stages. It's been developed since the ONAP release to the Beijing release. In the first stage design time modeling happens where basically a user of ONAP can define the services that the service provider intends to use and defines the resources that are associated with those services. In stage two the services are instances of those services are created and basically that allows ONAP to declare that it needs and is expecting certain kinds of resources to connect to it. And then finally in stage three the PNF itself is delivered on site and powers up and then eventually sends a PNF registration VES event, virtual event streaming event over O1 through to the PRH, the PNF registration handler, where in stage four ONAP becomes aware essentially of that new PNF that's come online. And the PRH then takes that message, publishes it onto the internal messaging bus, the DMET bus. And the A&EI entry for that PNF can then be updated and this allows ONAP to recognize and then operate and do things with that PNF as it's officially now registered into A&EI. And also and finally in the stage five the PNF can be configured and activated. So the demo basically showed this flow of being able to recognize and go through the paces of PRH to show that ONAP can see and recognize a PNF. That's what was demoed. Okay, next. Another long-standing use case is the self-optimizing network and physical cell identifier. Use case led largely by AT&T but in collaboration with many others. The idea of self-optimizing networks is actually been around since 4G but largely will come to fruition in 5G where there are three principal main ideas, self-optimization, self-configuration and self-heal. So building more intelligence into the network and automation of control. And PCI is just one basic example of SON. An idea here is that cells within a wireless network are assigned PCI values and there's only a limited pool of PCI values are available. And you want to avoid collisions where neighboring cells have the same PCI value and confusion where adjacent cells have this exact same PCI value. So within ONAP there's a control loop that has been developed using OF, the optimization platform component within ONAP. It can evaluate policies and make decisions and send down new values to the RAN and then over 01 it can receive information from the RAN network that's then collected through the DCAE data collection analysis to look at the values that have been assigned in the network. So basically this demo demonstrates this one of the more interesting applications of SON. Hi everyone, I'm Nicola from Ericsson. The Ericsson demo, the first RAN plug-fax focused on ONEM interface used by the 5G RAN network function to interwork with the service management orchestrator implemented by ONAP. The demo has been performed from an Ericsson lab in Ireland where an ONAP allowed to release was installed to interwork with the real Ericsson GNOTB. We demonstrated the two use cases, plug-and-play and the above PM data collection. And with the help of ONAP it has been possible to show GNOTB event notification, configuration operation and data file transfer based on RAN alliance SON specification. To provide secure connection, TLS protocol has been used over the old interfaces. Next slide please. Let's have a look to the two use cases. On the left, the GNOTB auto discovery mechanism is shown. After the service and the resource instantiation in ONAP, a netconf young connection has been established with the network function using an ONAP controller workflow. ONAP CDS component has been used to execute a customer specific workflow through the STNC. And XNF will react to the netconf application configuration, choosing the registration event requested towards ONAP. On the right, you can see the other use case, the GNOTB data file collection. Ericsson has contributed to different microservices in ONAP, the PM mapper and the data file collector that are responsible of the collection of the file and the mapping of the PM counter on the events. PM data are then available over the DMAP bus, both as file and event. Next slide. I'll see you back to you. Thanks, Mikayla. Let's see from Ericsson here. So, as you can see that our contributions to ORA and OSC and ONAP, all of these open source forum, is helping to foster innovation across 5G. And in order to handle one of the key in a topic about sustainable business model related to open source, we have been engaged with the customers and partners and trying to jointly create a business model that would be beneficial for both the customers as well as for the suppliers. This type of events like podcast helps to drive towards that goal. We are also pushing the industry towards agile and faster development by participating in open source in general and in particular this podcast. And we hope to collaborate across all ecosystem players to achieve a global scale in developing open systems. Thank you everyone. That was a great presentation and thanks for the great overview. A lot of great progress made with this Blackfest. So before we have some question and answers, I want to pose a couple of questions to each of our members. So Zach, starting from you, can you please share some of the key lessons that you learned out of this Blackfest? Yeah, absolutely. Thank you. What I'd say is, you know, the most interesting thing is that the devil is in the details. And as we went through this, there are a number of things that, you know, we discovered along the way and some of it may seem very basic. Oh, we're building an adapter and it converts one thing to another. But you get into little things like the different notions between what is a client and a server. And you end up having an adapter that needs to have two different server interfaces as opposed to just the simple protocol translation. And so it's only through real use cases and real world problems that we're able to uncover and find these sorts of issues. And what we found was that while, you know, ONAP had a reasonable level of maturity, that maturity didn't necessarily extend to every use case. And so as we're trying to build out these use cases, we're doing an environment where the standards are still being defined. A lot of the underlying technology is still being defined. The only way that you can sort it out is get all the stakeholders together and really execute these real test cases. And that I think was really exciting about this plug test. And I think the real value of the future plug test to come. Thank you. Ben, same question for you. Some of the key lessons learned from your perspective. Yeah, so I think one of the more interesting things is, you know, just watching a community of a diverse community of many companies come together to show something meaningful and useful. And ONAP has really been very interesting and amazing. I think it's one of the key lessons learned also is I think, you know, just to give us runway time to work out bugs and watching problems in the lab get resolved. You know, it does take time and always have a backup. So, you know, we had had many planning meetings and I think those have those helped the actual eventual plug fest go very smoothly. We had continued disease to for slides and demos and recording pre-recorded stuff. So I think that helped a lot. Great. And finally, Michaela, from your perspective, some of the key lessons. Yeah, when I like the engagement with people open source community will not be what is today without really the active participation of the people from the ground and skills. All of us has given feedbacks and helped one another in some really common problems. And the open discussion with the service provider and the vendor to understand the different perspectives, needs, priority are all very important. And it also provided the opportunity to explore new technology and innovate. And we see a coordinate effort across the remote standardization form and open source project, creating a sustainable environment. Thank you. So I guess, yeah, I think collaboration is the key and box and plug fest really help us to demonstrate right all the specifications and put together all the software. Now, I have one more question. Maybe, Zach, again, starting with you, can you give us any information about any future demonstrations that we can anticipate? You know, so one thing that we look to be supporting at the end of this year is a demonstration related to CBRF staff domain proxies. And that I largely be leveraging our CBRF devices for that activity. And then we're also looking at future use cases, kind of rounding out more FCABS functionality and more O1 interface capabilities. And we're really working closely with AT&T to see what we can best target for 2021 in that area. Thank you. Ben, how about from Nokia's perspective, what can we anticipate? So we're involved in, as with a lot of companies in the community, in a lot of the upcoming use cases I see are related around like end-to-end network slicing. There's a 3GPP own app and O-RAN alignment use cases like the standard defined VES notifications and A1 adapter extension policy extension use cases. So there's a lot of exciting stuff coming up. I think CMPV2, IPV6, Mdans, and Etsy, more Etsy use cases and enhanced software upgrade. So I expect to see a lot of interesting things. This is just the beginning really. And I think we'll see some interesting stuff coming down the pipe. Great. And Haseed, maybe from Eric's point of view, what can we anticipate in the near future? Yes. Thanks, Rob. I mean, as you all know that it has been a challenge to do face-to-face demonstrations due to COVID-19 implications. But having said that, you know, Ericsson has committed to participate in the virtual O-RAN Blackfest 2 at the end of this month. And we will be presenting three demos there. The first one is on A1 interface support in Genote B, leveraging a couple of Ericsson contributed OSC components, A1 adapter, and policy management service. The next demo is on PM counter management over O1 interface. And the third demo is on software upgrade also over O1 interface. And in addition to that, we are considering to participate in O-RAN sponsored Mobile World Congress North America's virtual demo at the end of October. And we're also hoping that the 2021 Mobile World Congress will have some level of face-to-face aspects and hopefully we'll be able to plan something like that. But stay tuned for it. Thank you. So great stuff to look forward to. And finally, quickly, I would call Tracy Van Braco from AP&T to give us a quick sneak peek on the second plug fest being organized by O-RAN Alliance. So the second plug fest is in multiple regions, North America, Europe, Asia, Japan and India. India is a newcomer. In North America, there will be two parts to this event or activity. Part one is it's a plug fest and workshops, as Hasid mentioned, mostly virtual on account of the COVID-19 crisis. And that's the end of this month. And I'm very pleased that both Ericsson and Nokia are bringing three scenarios each to share with the 5G LTE ecosystem. The second part of the POC plug fest in North America will coincide with the release of O-RAN Software Community Release Free. It's called the Cherry Release. And Zach, that's when we're eagerly anticipating the commscope CVRS-SAS, maybe with additional vendors contributing as well. I just want to thank everybody on the panel for collegiality, collaboration, and it's just so great to work with so many bright people who work together so well and who are so much fun. So see you at the next POC plug fest. Thanks, Tracy. And thank you to all our panel members for the great discussion and for the great overview. And now we can move on to the question and answer session. Thank you. Hello, everyone. We have now activated the phone bridge so the speakers can answer your questions live. Please enter your questions in the Q&A chat with speakers. Hi, this is Drew Gupta from AT&T. So I see a couple of questions here. So let me just quickly address those in terms of the duration of the plug fest. The first plug fest was conducted for one day in North America. Of course, the activities and the preparations for that began weeks to months ahead of time. And it was all the demo that occurred on the final day. Of course, the second plug fest is being conducted right now. And the total duration for that is actually two weeks. So it started last week and it's ongoing this week as well. And then also in terms of the reports from plug fest number two, so that's ongoing, like I said this week. So, you know, I'm sure we'll start seeing some reports and outcomes of that plug fest very soon as it wraps up later this week. So let me address some questions for speakers here. So maybe starting with Zach. Zach, could you maybe talk a little bit about how ComScope aligns across different open initiatives such as ORAN, OSB, ONAP. There are so many. Can you talk a little bit about that? Yeah, absolutely. So ComScope is fully committed to open standards and in particular open RAN. So we're active in a number of working groups there. We're also active in the small cell forum. And we're also members of of course Linux Foundation and working in ONAP. And so we have a number of contributions that we've made and will continue to make. And, you know, we really see a lot of vibrant engagement in those forums. And I think it's really great to see it. And we are, you know, committed to continuing to support ORAN, ONAP, and so on. All right. Thank you. And I'll see if Mikaela has her audio. Then maybe Mikaela, do you want to also talk about how, from Eric's perspective, how do you balance across the multiple open initiatives that you're involved in? Do you hear me? Yeah. So the Open Source Alignment is key for Eric's. We are active in ORAN, Alliance, OSCE, and ONAP. We want to avoid fragmentation between open source initiative and we try to integrate the reuse of the common components. It's always a challenge because you risk that a different open initiative want to drive. As a company, we want to stimulate the interworking and we try to use the same thing as an open source active company. We encourage to have monthly meeting between the different open source initiatives and adopt meeting with the different open source initiatives and the key stakeholders. All right. Thank you. And maybe one more question here. So maybe Haseeb if you can help us with it. Can you talk about, you know, there is some obvious challenges that people talk about about the business model for open run systems and so on. So could you give a brief perspective on some of these challenges in making these open systems real? Thanks, Rup. So I think one of the key challenges to make open systems real is the lack of contributions and investment from the key stakeholders.  Because without really serious participation and or investment, things will not move. The second one is, you know, sometimes there are too much focus on the processes. So, you know, processes are good when needed, but that could also create red tabs. So we believe that the release cycles are still too long. So something needs to be done on that. And then sometimes we are kind of, you know, very much attached to the not invented here mindset. So if I'm coming from on up and trying to do something in OSC or in or and then we try to bring our own kind of mindset to with it. So that also needs to be broadened. We need to look for the best solutions for the community. And then, as Michaela mentioned, lack of alignment across projects within the initiative itself and also with other related initiatives should be addressed. And finally, open does not necessarily mean free. So we have to also examine as an industry on that concept and must develop a viable open based business model by addressing some of these concerns. So I think that's that's how I like that. All right. Thank you. Thank you everybody. Thank you. We're at time so I'm going to go ahead and end the webcast here shortly but you can continue the discussion on the Slack channel. Stephanie, do you have the name of that Slack channel? Yes, I posted it in the chat. It is the number two AI networking edge ran channel. So thank you so much for joining us today. Thank you everybody. Have a good rest of your day. Thank you. Thank you all.


Hello everyone. This is the Circuit Python Weekly for April 1st, 2024. It's the time of week where we get together to talk about all things Circuit Python. I'm Jebler and I'm sponsored by Adafruit to work on Circuit Python, which is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is a community effort, but it's sponsored primarily by Adafruit. So if you want to support Adafruit and Circuit Python, consider purchasing hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafruit.it slash discord. There is pretty much constant talk about electronics topics in the Discord, but this meeting is held in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel, usually on Mondays at 2 p.m. US Eastern, 11 a.m. US Pacific, except when it coincides with the US holiday. In the notes document, you can find a link to a calendar. You can view online or add to your favorite calendar app, which eases checking time zones and things, especially if you're outside of the US. We also send notifications about upcoming meetings via Discord. If you'd like to receive these notifications or you'd like to participate in the voice meeting, ask us to add you to the Circuit Python East's Discord role. There is a notes document to accompany the meeting and recording. You can contribute to this document beforehand. The final notes document includes timestamps, so you can skip around to the part of the video that interests you the most if you're watching it after the fact. The meeting tends to run 30 to 60 minutes, depending how many folks have updates to share. And after each meeting, we post the link to the next meeting's notes in the Circuit Python Dev Channel of the Aideford Discord. Just hit that pinned messages button at the top to find the link so you can add your notes for the following meeting. And if you wish to participate but cannot attend, you can leave hug reports and status updates in the document for us to read during the meeting. When you do that, it's super helpful if it's, you know, something that somebody can just read cold that they don't have to make a lot of interpretation of that. But anyway, the structure of this meeting, we're going to have five parts after this introduction. We're going to take a look at the community news, which is a set of items from the Python on Microcontroller's e-newsletter. Next up after that is the state of Circuit Python, the libraries, and Blinka, a quantitative overview of the whole project, a chance to look at the numbers separate from our individual updates. And then come the participatory parts. The third part is hug reports, an opportunity to highlight the good things folks are doing, taking time to recognize the awesome folks in our community that can be on Discord, on GitHub, on the Aideford forums, or just on the internet at large. The fourth part is status updates. It's the opportunity for anyone to report on what they've been up to, moving the status of Circuit Python forward, take a couple of minutes and talk about what you've been doing in the last week or since you had a chance to catch up with us, and what you hope to get up to over the next week or in the near future. And then the final part, if we need it, is called in the weeds. If we need a more long form discussion about things, whether this emerges from status updates or something that you have identified ahead of time, this is the place for it. And that covers how the meeting will go. And so next up we will start with community news. I've picked just a couple of Python related news stories or stories from the newsletter. And number one is a little project called EcoEDA, recycling e-waste during electronics design in KeyCAD. And this is a Python-based tool that integrates with KeyCAD and is designed to provide suggestions of recycled components whenever you add a new symbol to your schematic. Next up, Python tops yet another rankings list. And this is a link to a real news article published in ABC Australia. Python snake meat could become a super protein on dinner plates in years to come, research suggests. A study published in The Nature Journal has found the meat to be highly efficient environmentally friendly source of nutrition that can be raised on waste proteins. And then back to serious stuff for a moment, the Adafruit IO in 2024 survey last chance is coming up. Inspired by Scott's blog post circuit Python 2024, the Adafruit IO developers and designers are requesting feedback from you to help guide development of Adafruit IO in 2024. It's wrapping up soon, so please respond. There's a link to the Adafruit blog, which says if you're a current Adafruit free IO user or an Adafruit plus paid user or have previously used IO in the last year, we want to hear from you. And there's a lot more in the newsletter. The Python and Microcontrollers weekly newsletter is a circuit Python community run newsletter emailed every Monday. The complete archives are at adafruitdaily.com slash category slash circuit Python. It highlights the latest Python on hardware related news from around the web, including circuit Python, Python and MicroPython developments. You are invited to contribute your own edits, whether it's news that you ran across or a project of your own. And you can do that on GitHub. There's a link in the notes document and submit a pull request with the changes. You can also email CPnews at adafruit.com or tag a post with hashtag circuit Python on mastodon, blue sky or X. And next up, we have the state of circuit Python, the libraries and Blanka. We have our lovely Adabot run a report covering seven days of contribution information and that runs in the early hours of the morning US Eastern time. So changes that occurred today are not included in this report. And I will do the overall section and then ask some other Adafruit folks to take up some individual sections below. So overall, we saw 33 pull requests merged by 18 authors and eight reviewers. So thanks to all of those people. Among the authors, there are some names that are less familiar to me. We have URE, Yuri, Kyle Moore. Anonymous Cowhead is back. Thanks for sticking with us. Fabian Chouteau is a newer name for me. SAK917 and XS5871, I also don't recognize. And issues-wise, we saw 29 closed issues by 13 people and 16 opened by 12 people. So it's really nice to see those large numbers of people involved. And it's always nice when the net number of issues edges down a little bit. And with that, I'll ask Scott to go over the numbers for the core. Sure, thanks, Jeff. Okay, for the core, we had 24 requests merged from 12 different authors, which is awesome. Seed Areas, Fabian Chouteau, URE, SAK917, Kyle Moore, Sean the IT guy, XS5871, and Bablock B are all infrequent authors. So thanks to those folks. For reviewers, we had six reviewers. BlitzCityDIY, Retired Wizard, and Anecdater are all infrequent reviewers. So thanks to them. We had 24 open poll requests. So we're just under the 25 single-page goal that I have for us. Issues-wise, we had 14 closed issues by eight people and 14 opened by 11 people. So we're net zero, which is great. And we also have nearly signal digits on both opening and closing, which is awesome. We have a total of 672 open issues. We have nine active milestones. These are used to prioritize work by Adafruit-funded folks. If you have other issues that you'd like to work on, don't be afraid if they're long-term. We're happy to help shepherd changes that people want to see. But these are the priorities for Adafruit-funded folks. So we have four open issues for 9.0.x. These are like small fixes to the latest stable release, 9.0. We have zero open issues for 8.2x, which we could probably close at this point. I think we're feeling good about 9.0 well enough to close 8.2x. We have one open issue for 9.1.0, which will be the next feature release. And then we have 29 open issues for 9.xx, which are other things that we've had to do between before 10. And we have two issues, not assigned to milestones. So we do have some triage to do, although that may have been done between when these tasks were grabbed and when I'm reading them off there. All right, thank you, Scott. Next up, I'd like to invite Tim to tell us about the libraries. All right, thanks, Jeff. This section covers the circupython libraries, all of which can be found on GitHub under names like Adafruit underscore, circupython underscore, and then the name of whatever library it is. Across all of those libraries this week, we had eight pull requests merged by six authors. The name that was there that stuck out to me as newer or less familiar was VIN 1953. The other names there are folks that I see more frequently on this list. So thanks to them as well and VIN 1953 this week. We had four reviewers, also relatively usual suspects on reviewers, thanks to Melissa, Scott, Tektrick, and Dan. All the pull requests this week were just one day old, relatively light week, all brand new ones. That leaves us after the week with 72 open pull requests. The oldest one I believe is a draft one at 592 days and the newest one is actually two days old, which is interesting. Usually that shows one day. We had over the past seven days, 13 issues that were closed by six people with two new issues opened up by two people. That leaves us with 730 open issues across all these libraries and of those, we're down to five of them that are labeled as good first issues. You can find those five as well as all the other open issues in PRs over at circuitpython.org slash contributing, which is where you should head if you are interested in getting involved in the project. If you wanna start out with reviewing, that's usually a pretty good spot. Over on that contributing page, you'll find a list of all the open PRs. You can take a look through those. If you've got hardware for any of them, you can test it out. Otherwise you can just have a look at the code and the syntax spelling, et cetera. Leave a comment letting us know that you took a look and what you found. Once you get comfortable with that, we can get you leveled up to leave official reviews over on GitHub. If you like to get more involved on the coding side of things than reviewing, you can also view a list of open issues over on that contributing page. The open issues are issues that have been created on GitHub. So if you would like to try to tackle one of those, you can identify one that you've got hardware for or a particular interest in and go try to code up whatever change is mentioned in the issue and submit a PR with that change. The page does have a dropdown near the top that allows you to filter those, which is how you can pull out those good first issues if you'd like or search by one of a few other filters that are there. We do have guides for contributing to get in GitHub. If you need help, we also have folks available on the Discord. So just let us know if you're trying to contribute and having trouble, just let us know on the Discord. We're always gonna be happy to help folks get spun up with contributing, whether it's reviewing or contributing code or whatever. We want everyone to be able to contribute in whatever ways they can. In library PyPI weekly download stats this week, we had 151,767 downloads across the 325 libraries on PyPI. The top tens list is here in the note stock if you'd like to check those out. And then for new and updated libraries in the last seven days, there is a new EHTTP server, which is a different variation of HTTP server that was added to the community bundle, which looks really interesting. And then the RSA library was updated with some new examples. That's what we've got for libraries this week. Thanks. Thank you. And to round out this section, Melissa, would you like to give us the stats on Blinka? Yes, Blinka is our circuit Python compatibility layer for MicroPython Raspberry Pi and their single port computers. And let's see, I lost my place on here. Oh, here it is. The text is like smaller than the other ones. So this week we have five pull request merge by two authors and two reviewers leaving a net of four open pull requests amongst all the repositories, which is definitely less than I normally am reading off. There were two closed issues by one person and zero open by zero people leaving a net of 84 open issues. There were 15,121 PyPI downloads in the last week, 12,031 PyWheels downloads in the last month and we are at 132 supported ports. And that is it. All right, thank you to all three of you for going through that information for us. And now we're ready to move on to hug reports. Hug reports is a chance to highlight folks in the circuit Python community and beyond for doing awesome things. I'll start, then we'll go down the notes document in the order that folks are there. If your text only are missing the meeting, I'll read your notes when I get to them in the list. So I want to start with a group hug, but then thank Melissa for her patience as I worked on a PR about absolute image links on circuitpython.org. And shortly before the meeting, Todd Bot dropped a cool demo on Mastodon. There is a video and I think that Tim or somebody is going to put the link in the channel if you want to check that out, but otherwise you can find that link in the notes document. All right, next up is Anikdata, hello. Or I can just read it out. Happy to. Anikdata has a hug for me for ongoing work on SSL and server-side stuff like SOReuseAdder. Next we have Dan and then I have notes to read from Devin. Okay, thanks to Bill88T, who was trying the main branch and noticed that the tags, there was something odd when setting up the ESPIDF environment that it got the version wrong and that turned out to be due to tagging problems with our fork of their repo. So that was noticed and easily fixed. And then thanks to Anikdata and McCall-Fukusa and DJ Jevin and Retard Wizardence and other people, there have been many who are doing a lot of testing on network issues. There's a lot of discussion in Discord and also in a few different issues on GitHub and that's really helpful for people to kind of pin down what's really going wrong. Okay. All right, next I have the notes from DJ Devin 3. Coming up after that, though, is Tim, foamy guy. So DJ Devin 3 writes a hug for StudioStuff, Anikdata, Dan H, and Jebler for working together to fix a bug that prevented the RP2040 from starting HTTP server. The fix by Jebler was rolled into 9.1.0. A hug for Justin for his continued work on connection manager and rough linting. Also a thank you for the quick PR involving connection manager with HTTP server. A hug for Snakey Makercat for starting a port for the ElectroSmith Daisy Seed. After looking into it more, they figured out it has eight megabytes of flash so it could be a pretty nice circuit python port. A hug to Kmatch for the excellent learn guide on memory saving tips. It was a nice quick reference for using Memfree to track resource usage. Hugs for Toddbot, Anikdata, Deshipoo, Alpakenon, foamy guy, Tyeth, and many others for answering questions in the Help with Circuit Python Discord channel. A hug to Sean who is a relative newcomer to our Discord. They're doing a custom ESP32 board port, parallel display project and helping others with display related questions from the experience they've gained. A hug for Michael Pocusa for starting to port HTTP server examples to connection manager. A couple of hugs to foamy guy, the first for recommending Windows task scheduler to keep circuit python stubs updated as well as for the new outlined label for display text. It works very well. And that brings us to foamy guy and then to Kenny. All right, thank you. Hug reports for me this week. Thanks to DJ Devon 3 for diving into typing in some of the libraries as well as submitting a new feature for the IS31FL, something, something, something that I don't remember library. That's a matrix LED display driver. Thanks to Dan H for sharing a PDF copy and the idea of checking on Archive Orc to find a learn guide page that got deleted when I tried to use a rollback to the earlier state functionality while I was slightly panicking, trying to figure out how to get it back. Very much appreciated. Thank you to Jeff and that maker Melissa for improvements to the way that the images are included in the RSS feed on circuitpython.org and a group hug. Thanks. All right. And after Catni is maker Melissa, but go ahead, Catni. Hello. So first my hug is for Tyath for talking girl light setups with me and for answering an ate a fruit IO question. It's been so long since I've actually used the dashboard to track data that I couldn't remember whether I needed a single feed for individual things or so on and so forth. And that got answered really quickly. To follow me guy for working on interactive software for my conference badge and a group hug to my PioHio organizers team for being an amazing group of folks. That's what I got. All right. Thanks. Melissa, you're up next. And then I got some notes to read. Okay. I have to Jeff and Dan for a quick responsiveness with the circuitpython.org updates and group hug to my notes. All right. I have notes from snaky maker cat and then we'll go to Scott. First snaky maker cat says hug to DJ Devon three for being patient while I dig through the daisy seed guts. I know he is dying to test circuitpython on the new board and a group hug. And for one, Scott, you're not rounding out the section, but you are next. Yeah. Thanks, Todd, but for rounding out just in just a minute. First, I have a hug to Dan for figuring out Bill 88 T's issue that I hadn't pushed tags to the Adafruit USB IDF. I hadn't thought about that. And then thanks to TAC for working on D&Net for tiny USB for me. I know there's a lot going on in tiny USB land and it's really helpful when he's lets me interrupt him and kind of co-opt his time for a little bit. So I really appreciate that. All right. And the notes from Todd bot say group hug. Thanks for all the circuitpython work. It's so fun to hack on. A hug specifically for me for bitmap filter. I'm starting to play with it now for non photo uses to Kreer, Tanute, Dan H et al for getting parallel bus working and enabled for ESP32. These fast displays on fast processors are super nice. And that concludes hug reports. So we will move on to status updates. It's time to tell folks what we're up to individually. I'll start and then we'll go through the notes document once again. When I call on you, take a couple of minutes to talk about what you've been doing since the last meeting and what you'll be doing until the next meeting. And this is a great time to provide a quick tip or trick but if a discussion is gonna become long then we want to move it to in the weeds. So with that general reminder, I will get started. Last week I wrote a learn guide the first that I had written in a while. I used an RP2040 with the Feather RP2040 DVI to create a DVI converter for a particular vintage computer. And I use circuit Python to do it. So that guide is live on learn.aderfruit.com and was the 3,000th guide published on learn which is an amazing number. What I'm doing other than that is working on updates to the floppy IO module and the Adafruit floppy circuit Python package. That is mostly done. There's just one problem with PIO capture of flux that I need to get back to. And I'm hoping that with the fresh eyes of taking like five days off from it to do other stuff that I will just see that and fix it, but you never know. And that's what I am gonna be up to. Next up is Dan. Then I'll have some notes to read from DJ Devon 3. Okay. So last week was three circuit Python releases, 9.01 with some fixes, 9.02, which was a single point released to make to fix a missing pin on a single board which was just being introduced and also 9.10 beta zero, which includes a bunch of development changes working toward 9.10. So there'll probably be a 9.03. And related to that, there was a problem with analog in on NRF boards. So I fixed that in the 9.0 X branch. As mentioned, I updated tags to fix a problem, a build problem when you're using the main branch. That was really simple. I'm kind of watching over some testing of wifi stuff that's going on and to see at what point I need to start doing some deeper debugging in the core of what's going wrong with some wifi stuff, but I appreciate everybody who's working on that. And otherwise I just have a long list of 9.0 X and 9.0 XX issues to work on.  And I will continue to do that when I get bored. Okay. Thanks, Dan. Next up, I have notes from DJ Devin 3. Submitted a PR for HTTP server that uses Connection Manager for the socket pool. The idea was well received and it was decided all examples with socket pool will use Connection Manager going forward. So that's a thing now we're full steam ahead with Connection Manager. I reported my multiplexed seven segment display project to 9.0 didn't run into any HT 16K33 library issues. It pulls six different API sequentially. So it's a pretty good torture test for socket reuse. It works great on an S3, but on the S2 it throws an ESP IDF memory error. I tracked the memory error as far back as 8.0 beta then handed my findings over to the devs. The mastodon API example I submitted two weeks ago is already broken as mastodon revamped their API this week and deprecated a lot of endpoints. It only required minor changes in the URL and endpoints to get it working again. Seems like they're moving towards OAuth 2.0. So it's probably just a matter of time before they completely deprecate their publicly open version one API and wrote a playground note on automating PIP and circuit Python stubs updates for Windows by creating a task scheduler bash script. So check out the eight of fruit playground for that. The next up we have foamy guy again. All right, thanks Jeff. Last week I updated some learn guide, both code in the repo and some pages that reference different bits of code but aren't checked into the repo for some of the updates to display IO in 9.0. But we decided to change the way that those warnings work and the timing of the deprecation and how that rollout will go. So those will sit as draft for now until we're ready. And then I did go back through the guide pages to change them back to how they were originally and also saved off a list of URLs this time. So when it is time to make that switch, we can actually just click through that list instead of searching through them again, which will save a fair amount of time when the time does come. I started up a Grove feather wing in a feather S3 TFT reverse with the intention, they've got some pins that are kind of backwards compared to how most normal feathers are, but I started them up that way so that they could be used back to back with the Grove plugs on one side and the display on the other side inside of a Simon type game that I would like to make inside of a cardboard box. My feather does have a dead TFT, so I've got to get a new one, but everything else did fit together how I'd imagined and the buttons work how I was imagining. So once I get the new device, I think I will be good to go on that, at least as far as what I have planned. I updated the display text learn guide to include some new sections for the two new types of labels, outline label and scrolling label. Both of those I created at some point after that guide was written and it was never updated to include them. So now they're there. I updated the pie charm page specifically that's in, I think it's in the Welcome to Circuit Python guide. There's like an advanced page and then pie charm is one of the sub pages there. I updated that to include information about the new device specific board stuff, so how you can enable that onto that page. And then lastly, I've been working on a Tic Tac Toe game that runs on the Eink display for a Badger 2040W. Most recently, the bits that I added were checking for the winners at the end of the game or really checking for the winner after every turn and then drawing a line through the winning pieces if there was a winner found. Currently it draws correctly, but it does need some help still because it refreshes the display a bunch of extra times and it also doesn't remove the line when it's time to start the next game. So it's close, but still needs some tinkering and that's what I have got. Thanks. Thank you. And next up is Catney, followed by maker Melissa. All right, so I finished up the software for my Girlite setups. There are currently three different versions because I ended up needing to mount the controller in an opposite orientation on one terrarium and there's another one running a, there's only one running a sensor, so three different versions of the software. I eventually figured out where to mount the other three, but it required rewiring the level shifter so the connector was coming out the opposite side of the Feather sandwich. The difference in the code on the other three is that one's currently running the temperature and humidity sensor out inside the terrarium. I'm only running one at the moment to compare to one that I have outside the terrarium to see if there's any point in adding it into the other setups or whether the climate inside is identical to ambient. So far it seems that LEDs increase the temperature in the terrarium during the day, but it's basically identical at night. That said, watching the humidity spike after watering and seeing how long it remains high is at least interesting. So that may be enough reason to add sensors to the others. The one with the sensor displays the date, sensor data and what the manual LED status is which is to say whether or not I turned the LEDs on or off using a button on the controller and the ones without sensors display the date and LED status only. My wife designed a 3D printed case for the controllers that mounts to the terrariums using magnets. It's a really slick design and it worked incredibly well for my needs. We're finishing up a case for the sensor to allow airflow, but avoid directly misting the sensor board when watering the plants. It looks really neat so far, but we need to test it to make sure the airflow is enough. After that, we're designing a case for the Badger 2040W with that is gonna be running the code that Tim was talking about. For me, the case, I added Neopixels to mine by soldering three wires of a STEMQT cable to it and using the quick port on the Badger to connect them. The Neopixels are about the same height as the Badger so I'm going to add them into the case along the left side of the board. And then completely unrelated, I'm not sure I shared this here, but I agreed to be conference chair for Pi Ohio 2024 which is where my hug report to my organizing team came from. It is an incredible amount of work, but I have an amazing team of people helping me. So hopefully I can get everything going in time and within budget. But it's been an incredible learning experience and I'm very excited to be doing that. So if you are in the area and or want to come out, it's July 27th and 28th, I think, in Cleveland, Ohio. Anyway, that's what I've got. Thank you. And next up is maker Melissa. Hello. So I added the new boards to circuitpython.org that were added to circuitpython 9.1 beta and fixed compiler warnings in some Arduino libraries to fix some small issues in a couple of circuitpython libraries. I updated the magic storybook guide with, or this magic storybook with chatGBT guide for Bookworm and the latest open AI API. And I'll probably update the chatGBT bear project to Bookworm next. And that's for a minute. Thank you. Next I have notes from Snakey Maker Cat who writes, I started working a few weeks ago on the circuitpython port to the Daisy Seed, a really cool STM32 board, but ran into the 128KB internal flash issue early on. Luckily, there is an eight megabyte chip external flash and 65 megabytes of RAM that makes the project totally work the effort. Unfortunately, the documentation from ElectroSmith is not great, especially since they went closed source recently, and the only available config file for the flash chip contains plenty of mistakes. So at the moment, I'm working on an STM cube IDE project and digging through data sheets to figure out the right configurations for the MCU and how to use the Q-Spy flash in XIP mode. It's easier to test all that in the ST work environment. I'm sure I will get to the actual circuitpython part soon. And this time, Scott, you do get to finish the section. So what's up? So I'm giving a podcast gates talk next weekend. It's mostly done. They actually wanted slides yesterday, which I didn't realize until Wednesday evening last week. So I was doing a lot of work on my podcast gates talk on Thursday and Friday. So thanks to DeepDivers for working through them with me and giving feedback. I do have some bugs to file for the mobile apps. I'm gonna try to do that today as well. And then after that, I'm back to the USB host featherwing work. I tried to show it on, show and tell on Wednesday and saw that there was a bug and I figured out soon after that that I had the console UART set up for circuitpython debugging and but the like input serial stream was just floating pin, which meant that like any sort of noise that I generated was causing random inputs to circuitpython, which it caused my demo to not work. So remember that if you're ever in a world where you're getting using the UART input into circuitpython, make sure that your RX pin or like the data going into circuitpython is pulled down or up whatever it should be for UART.  All right, pro tip tips from Scott. But next we have the section in the weeds. In the weeds is an opportunity for long form discussions. If you have any in the weeds topics, please make sure they get added while we're discussing other things. So we're not waiting around to see if anybody has topics and we do have a topic from Dan. So I will let you take it away. Okay, this topic came up in issue 9112 that's linked in the notes. Circuitpython issue 9112. So the question is right now, well it used to be that we would give Wi-Fi credentials in two variables in secrets.py and then we switched that to settings.toml. And then very much because of the web workflow, we decided that if two variables were used, circuitpy Wi-Fi SSID and circuitpy Wi-Fi password that we would auto connect to that access point when circuitpython started up. And if I'm correct, Scott, you can tell me yes or no. That always happens, but the web workflow isn't started unless the circuitpy web API password is set. Right, it used to be that if you had the auto connect stuff, then the MDNS server and the HTTP server for the web workflow would start. And then you would just, it would tell you that you needed to set the password but people wanted to separate that out. So we've tied the web workflow to the presence of the password now. And does the MDNS server start on auto connect or only when the password is present? I believe it's gated by the password too. Okay, all right. So the fact that auto connect occurs at all is it's not clear from the names, but they are kind of official sounding names. There was some discussion in examples of whether we wanted to give examples that use some other names to distinguish whether or not. You wanted auto connect or not, or you could add a flag and use the same names but suppress auto connect by saying set circuit pi Wi-Fi auto connect to zero or if we implemented Booleans, which we don't have yet, in settings.toml to set it to false. So I think we have some kind of varying ideas on this. And I think the question is what's clear and should we document this somewhere? Should we think about changing the names in the long run to make it more obvious that auto connect happens from the names? Like you could think of names could be circuit pi Wi-Fi password auto connect or something like that. But that's mouthful and we'll have to change a whole lot of examples. My intention was that the circuit pi prefix meant that it was something that circuit pi would do something based on. Yeah, yeah. And I understand that, but it's not, it's still you have to look up what it is or you have to know. It's like it's not manifest from the name. So it's not sort of, so- Yeah, the auto connect is. Yeah, the auto connect, the word auto connect isn't there or something. It is. You could put a comment in. It is documented. In settings.toml that says what, you know, like a tiny bit of documentation or something like that. And I was just wondering whether people have ideas about this and whether when auto connect happens, it screws them up where they like it. I mean, I don't think it makes a lot of difference. It makes it go a little faster if you haven't enabled the web blur flow. But I'm not sure what other, whether there are disadvantages for the auto connect and whether people are even aware that auto connect is happening. Also, I guess when you do a deep sleep, I don't know, does it be auto connect when you wake up from deep sleep? I don't even know if you answered that question. And that takes a while. So you don't really want to do that if you're just doing something simple. So all those things make it a little complicated about. It looks like it does. It will auto connect again for you. Right. It will not start the workflow again. Okay. So that first link I posted is into this logic. So it does, it gets the SSID, it gets the password. If it can't get those, it returns. And if it can't get those, it calls connect. If connect doesn't work, then it just disables the radio returns. And then it gets the reset reason. And, oh, I guess deep sleep alarm, reset reason doesn't equal deep sleep alarm, then return false. So I guess it will start, it will start the web workflow again after deep sleep alarm. Okay. So that means it's kind of expensive to wake up from deep sleep if these things are set. So, and then the question is like, I know this foamy guy says in the comments that he likes auto connect because it's nice not to have to actually put a Wi-Fi.radio.connect in the user code and have to look up the environment variables. And I guess the question is like, well, what should be the standard boiler plate or not? And, we could say like, okay, you can do a connect or if you do this, it will connect automatically. And it's sort of like, there are definitely two use cases and they're both kind of equally valid. So, I don't know if, so David glowed the pet, it's the password. This is not the Wi-Fi password. This is a password that you have to type into the browser when you're using the web workflow. Well, we won't connect if there's no password. Right. It's a separate issue. It's not related to this discussion. Yeah, yeah. Like, yeah. If, if circuit by what Wi-Fi password is not found. Oh, actually, no, if, if it's not set at all, then it assumes there's that it's an open network. Web API, web API password or Wi-Fi password? Wi-Fi password. So you, you, you can auto connect if you have an open number. Yeah, that makes sense. It's the web API password that I'm talking about that. It's really a different password completely. So. Well, yeah, for Wi-Fi password. So my, my response on the issue was if people want to store Wi-Fi credentials but not have circuit Python do anything with them, they should just use a different key. So I can be the question is then in the examples, like we have examples all over the Wazoo that say like, here's a sample test program to get you started with Wi-Fi and what, what should be the standard? Should the standard example use the auto connect behavior or not? I think it should because I think web workflow is good. Okay. I think by default people should have web workflow on. Okay. I have one quick observation about that. When I hung out with JP a couple of weeks ago, he had brought his Memento camera and he wanted to take it out and make a quick snapshot of something. And this, this could be down to his configuration and in this case, you'd want to change it. But anytime he wanted to turn the camera on, he had to wait out the auto connect timeout of his Wi-Fi that he had previously configured. And that was not great. And, but I don't know what the solution is to that because you do want to then connect to it on web workflow and download a SD card image or whatever it is. So in summary, I'm not sure what the solution is, but this is a pain point that I noticed someone having with Memento specifically and web workflow or Wi-Fi, automatically Wi-Fi connecting at boot time. That's all. Right. Well, maybe for the Memento, that's an example of something that's used in a portable environment a lot. So maybe that needs to be discussed in the appropriate guide or guide. I think there's, I think there's optimizations that we can do. That could make all of this faster. Like if there's a timeout that we have to wait for, then we could try to set the timeout lower. We could also like, we could add a key that allows you to specify what channel the Wi-Fi's on or we could automatically save it ourselves so that like we know what channel to start searching for. Cause like, yeah, and even I have a to do in here. It says do our own scan so that we can find the channel we want before calling connect. Otherwise connect will do a full slow scan to pick the best AP. Yeah. I think there are other possibilities like asynchronously doing the Wi-Fi connect.  And that would be something we'd have to kind of take care of in the core, but it seems like. We would need to add that internally. It could happen asynchronously compared to starting your code.py potentially. It's probably tricky to do, but it's not impossible. Anybody else have something to say or Dan, do you want to say any wrap up to that? I don't know, I can reach a conclusion, but this is helpful that I got other input that everyone contributed to this discussion and I see where anybody is coming from. If we assume web workflows enabled there's simple examples that even need connect logic. I mean, maybe not. Maybe when we write those examples, we say explicitly because you set these things, circuit pipe them will auto connect for you. Right. I think it should be, it needs to be better documented for sure. Right now it's documented in the reedid docs, but not in the guides so much. That's not so great. And we could also use up bytes in the firmware, but we could, the default settings.toml could have information in it. Yeah. And the sample settings.toml could also have that same, like if you set these things, it will auto connect. And so whenever anybody copies a sample one and edits it, they'll know right away. So I'll kind of look at the guides and see if we can do something. Some nice asked, will Wi-Fi radio enabled equals false prevent auto connect? It will not. It's too late. It's too late because the auto connect happens before user code runs. Yeah. And then anecdote it says, when connect logic is desired, do we want some pseudo standard settings that toml credentials to user recommend? Yeah, I would do what you suggested I think anecdote, which is Wi-Fi SSID and Wi-Fi password. That's what I do in my own programs for what that's worth. Right. And there is, I think we do have some work on the web workflow side to work, like to do the reverse of like manually connect a Wi-Fi that then turn on web workflow automatically. If like, maybe we don't want auto Wi-Fi connect, but we do want auto web workflow. So like, if your user code does some more fancy logic for like multiple SSIDs if you're roaming, but you've set in your settings.toml, like the API password, then maybe we should auto start web workflow after a manual connect. I don't think that works either. Yeah, that's not even an issue that says that. So maybe we need to open that issue. Right. So I can file an issue for that. Okay. All right. Well, this is good. This is just what I wanted. Yeah, it was a little bit of brainstorming on this. Okay. All right. Well, thank you everybody for that discussion and for everything else. I'm going to wrap up this meeting. This has been the Circuit Python Weekly Meeting for April 1st, 2024. Thanks to everybody who participated. And just a reminder, we'd love it if you could support Adafruit and Circuit Python and folks like me who work on Circuit Python. And you can do that by purchasing from the Adafruit shop at adafruit.com. The video of this meeting will be released on YouTube at youtube.com slash Adafruit and the podcast will be available on major podcast services. It will also be featured in the Python for Microcontrollers newsletter. You can visit adafruitdaily.com to subscribe. The next meeting will be held Monday, April 8th, 2024 at the usual time of 2 p.m. Eastern, 11 a.m. Pacific. And that meeting is held on the Adafruit Discord, which you can join by going to adafruit.it slash discord. To be notified about the meeting and any changes to the time or day, you can ask to be added to the Circuit Pythonistas role on Discord. We hope to see you all next week. Thanks again, everybody.


We are here at ITU Telecom World 2015 in Budapest in Hungary and I'm very pleased to be joined by Mr Yoshikazu Yamae who is Executive Managing Officer of the first Japanese Internet ISP, the Internet Initiative of Japan. Mr Yamae, thank you very much indeed for being with us today. Now the theme of ITU Telecom World 2015 is accelerating innovation for social impact. I wanted to ask you, how do you see ICT innovation directly impacting on the socioeconomic development of your work? ICT innovation such as IoT has once again reminded us the importance of the fundamental infrastructure such as the data center and network. We've seen more business opportunities in those areas alongside with the need of constructing a business platform for cloud and certain applications. IAJ as a Japan's first and best internet service provider, we are greatly known for reliability and wish to give our clients the best solution they wish to have. What are the latest developments at IAJ with the data center business and cloud computing business? Yeah, we have working directly with this such Southeast Asia government or other European company, a country in business. They are national data center using our module data center technologies. We are using module data center, the container type data center, by ourselves at first in Japan and we developed our own free air cooling system and reducing the power consumption using the some such environmental energy for the cooling. And what is the value for you of attending events such as ITU Telecom World? Well, we have many many many opportunities to get some new business in this area because our module data center is all in one package and pre-engineered and we put some our internet related technology into the one boxes. It's just a function box so customer can make some their own function using that each function unit to combine as each other's then they will have some large data center and small data center and but many cases so the customer can have some great opportunity to have some function development for this area. And what is your main message to SMEs government and industry that have been gathered here around the world at ITU Telecom World 2015? We are ready to share our expertise with those that area in need. It is the Japan qualities. We have a good application for the IT infrastructure and software application and then startup company can have such technology by jump up on the existing to the newer area. I wish you the very best of the future and thank you very much indeed for being with us today in the studio. Thank you very much. Thank you.


Rennie would fall. The question is that amendment 77750.3 in the name of Patrick Harvie, which seeks to amend the motion in the name of Alec Rowley, be agreed. Are we all agreed? We're not agreed. We'll move to our division and members because the vote's now. The result of the vote on amendment 77750.3 in the name of Patrick Harvie is yes, 6, no 58. There were 60 abstentions and the amendment is therefore not agreed. The next question is the amendment 77750.2 in the name of Willie Rennie, which seeks to amend the motion in the name of Alec Rowley, be agreed. Are we all agreed? Yes. We're not agreed. We'll move to our division and members because the vote's now. The result of the vote on amendment 77750.2 in the name of Willie Rennie is yes, 6, no 59. Abstentions 60. The amendment is therefore not agreed. The next question is that motion 77750 in the name of Alec Rowley, on finance, be agreed. Are we all agreed? Yes. We're not agreed. We'll move to our vote and members because the vote's now. The result of the vote on motion 77750 in the name of Alec Rowley is yes, 33. No, 30. There were 61 abstentions. The motion is therefore agreed. The final question is that motion 77780 in the name of Joe Fitzpatrick, on designation of a lead committee, be agreed. Are we all agreed? Yes. We are agreed. And that concludes decision time. We'll move to members' business in the name of Linda Fabiani on fighting for tax jobs and tax justice. We'll just take a few moments to change seats.


This is what's left over the bus. This is all the junk. I got a window in there, doors, some wood. Obviously pallet wood is not out of the bus. We're going to run to town, get some supplies, and then we're going to try to do the tank install today, all the fuel lines, and install this here pump. And hopefully, we can maybe, oh, I need to get some pantyhose too, to filter this stuff. But hopefully, we can be up and running today or tomorrow and then get out of here in a couple of days. Picking up where we left off yesterday, we're actually going to try and mount the tank today. The only problem is, I can't find the cone bit. Then you've got a problem. Yeah, that's what I'm talking about.  So I had to buy a $100 cone bit. Yeah, it is here somewhere. We don't know where it is. So a cone bit's like this six bits in one, shaped like a cone. And I don't know. I would say overpriced, but it there. You probably just hit it so you wouldn't have to drill it. I'm looking forward to drilling it, because I want the tank up. I'm trying to get out of here. No, you're not.  Yep. Anyways, I think I'll just pre-drill with some metal screws. And I don't know. We'll find it someplace. All right, if anybody invites you over for a good time and says you want to drill through a frame, you might want to think twice, dent in this thing.  How did you drill that in five seconds? Just give me the camera, just quit lying to the people. OK, go ahead and show them what you're doing. OK, now you see that? It's not just disgusting. Now hold the camera, Jack. OK, now this is how you do it. You put the drill in the middle of the mass like this. Yeah, there's air line behind that. Look at that. I want that bit. Holy moly. He's got special bits. So then what you did. No, they're not special. They're just trained. Oh, man, I'm getting schooled. Every single day here is a new lesson. All right, new battery or memory card. You got something on your face. We've been working at this down here, by the way. It's going slightly better because I've been using better bits. Actually, I'm not lying to them. I just don't get to do it. That's all there's a difference. Well, true. Badge does no more than I do.  Don't recommend buying them. I'm actually using this as the back to drill into. Yes. This DeWalt set. Well, no, just the bits, not the brand. Actually, his drill bit is amazing.  And these are just a mixture of garbage bits from Canadian tires. The trick to them is you sharpen them. That is a good trick. But he's got an edge on his right now, so it's cut. This one's brand new. And this DeWalt, I don't know what type it is. Yeah, tape, I don't know what it is. I got it at whatever big box hardware store. Here, we hold this, and I'll show them how it's easy to drill. You show them how to do it. Watch. You show them how to do them, Jax. Well, Badge recommends using this product. Rooster snot. So then you just put a little dab on there. Rooster snot on there. A little dab on here. Put a little rooster snot on there. Yeah, there you go. Watch this, folks. Watch how fast it goes. Did you put your box in there?  You're not going over with that, baby. Here, try this one. All right. Try this drill bit. This is Badge's safety drill bit. Well, no, I want to try the same bit. No, come on, come on. No, because I was talking up DeWalt how good this bit was. So I got it. This is nothing special. It was like a $20 set. $20 set, folks. Nothing special. Look at that, right through there. Oh, my God. Look at that, Badge. It's going right through. I know. As you would say, it's a Christmas miracle. It's a Christmas miracle. Now, watch it. This thing has a lot of torque. I know. That's a Milwaukee, right? Now, you know, this is an M-A-P-O-N.  Actually, if we just go like that, nice. OK, now you're going to notice this, you know? What? Because a Z-man's going to go nuts, but we've been using this, and we're just using cordless drills, which is almost impossible. And we're not using a frame electric drill to clamp on a magnetic base. We're not using that either. But we're very lucky because this is a soft frame. Now, we sort of lucked out because, you see there, we've only got five holes that we already got drilled that we didn't have to drill, because they're already there. This one here, we got to drill three.  No, because I changed the mount to this. They're not side by side. Because remember, I drilled the thing to mount up with this? So these are frame ones. You always try to keep the ones that are there and make your own if you want, right? See, I've done all this. I've done two brackets, and he's still working on one. See, he gave me the tough stuff. I got six over here. He's got nothing behind you. True, but I'm doing six. I'm doing one, two, three, four, five, six, seven, eight.  Okay, guys, I put these two in for anchors. I'm gonna guide this through and drill out so it's perfectly lined up with that. As you can see, I was a little off on that one, so I'll re-drill these. It was actually significantly off. No big deal. We'll clean that up and it'll make it perfect. Okay, guys, this is what we got so far. We got one, two, three, four, five, six. All these work. Three of those work. On the other side, I'm gonna bore them out as well. So we'll have six bolts holding it up. These are grade eight bolts. I think Badge said they're rated 115,000 pounds. That could be wrong. And then we got this front one to do. Here's the current life update. I've bored out six holes for the rear, just for the rear. The middle one I think is good, if I remember correctly. Gotta work on the front one right now. And, man, if anybody says I'm not a hard worker, well, sometimes they're correct, but I'm also operating the camera and trying to document what's going on here. So I am definitely working. All right, day two update. We got the straps pretty much off. We just gotta take that other one. We are gonna mount the tank.  Do you have any predictions on this door? The door is the easy part. Getting that thing under there is the problem. So we need about three Z-man and bubble war bucks to give us a hand. We should be able to figure this out. Anybody wanna come help us? We're over in Squadronville, Alberta. This will also be about two weeks ago, by the time you guys are watching it.  Really funny, you know, Jack? What?  Yeah, like letting us use his car. Yeah, like letting us use his truck. Letting us use his wagon. And his tent.  And I says, Billy, what are we gonna use that for? Well, there you go, Jax. That's for hauling your tank. That's right. We now know the answer. Yeah, we know the answer. It's for hauling the tank. That's what it's for. That's right. Tank hauler. A tank hauler. Thanks, Nutbar. Yeah, thanks, Willie. That was much appreciated. 🎵 Why, why, why, why, why 🎵 Come on. This is a state of the world right now. We're using a 12 by 12s. Up. Just push it in right there. Push it towards you? Yeah. Okay. Alright, check this out. We have it. Okay. So here we go. Hold it away from yourself. We're gonna do that. I turned this, what does this mean? Nothing. Okay, I'm gonna take all the credit for this. Not him. Because Jax runs a Jax, right? and he got all screwed up with the jacks, but he got the jacks figured out so it's all good. Jacks was jacking two jacks. Jacks was jacking two jacks. So the story is, as you see, we got it all in there, which is almost a damn miracle. And we didn't have no help from bubble war box or suit girling or any of them people. Not even nut bar. Not even nut bar. It wasn't even that way. So yeah, but it's all in there and it's all good and we got lots of clearance. It's really looking good. I think it looks great. It looks awesome. Thanks, dude. Now I'm taking all the credit for this because he would have been here for months doing this. I'm going to take all the credit for this one. You've got to hold it away from yourself when you do that, like this. It looks better because you had it like this. You like up your nostrils and stuff. Well, let's see the nostril one. I haven't seen the nostril one. All right, so check it out. We have it. He left me a couple nuts and bolts to work on. We got a couple here and here, but this is more or less what it's going to look like. We're still going to tighten down these. These are the straps. This is the bracket. Oh crap, we got the, OK, we got to put rubber in between the metal. Never forget the rubber when you're putting in brackets and straps into a semi-truck fuel tank. Don't forget when you're working on a bus, don't forget your rubber. So this is what it looks like. The reason I didn't go with a round tank was I felt that it, the ground clearance. Yeah, it was really low. So this one, we doubled the ground clearance. And I feel like, you know, we're on a little tilt. So something like 12 inches, I think that's. It was 8 inches, the other one. The other one was 8. I just feel like you feel free to agree or disagree with me. It's just an opinion. Everybody's got one. I feel like 8 inches in the middle of a bus is a little bit too low. If you go over a railroad track, 8 inches is not a lot. I don't want to get stuck there and then have the same get demolished. See, that's why we left these on here for these brackets. That's where the step was. So that's where the outside deck will eventually go on there that'll fold down for the outside deck. That would be cool. So this is also a little storage space. And we have a couple, you know, some things here. I don't know. I don't really know what I would store in there. Maybe a chair? A full-grown deck. We could. These things are really strong and can hold a lot of stuff. I'm going to work on this. I got a couple of things to do here. The badge is doing the Gullwing door. Gullwing door. They know about the Gullwing door, right? Do you guys know about the Gullwing door? I feel like you guys know about the Gullwing door. They know about the Gullwing door. But honestly, you're telling about the Jax, the Jax and two Jax, though? No. Well, early in the video, they did find out about how many Jax the Jax could jack up. Right. You were doing Jax and two Jax at the same time. You know, I was feeling jacked up. That's the truth. So this is what we got here. People mechanically inclined will know what these are. Drill bit and a tap for everyone else. This is what's going to make a thread for a bolt to go in here and hold the hinge. But you didn't tell them that you put a piece of metal in there. Well, when I was out running errands, these guys Oh, running errands? What? I was. I had to go to town. Oh, yeah, sure. OK. By the way, town is an hour away. So while I was out doing errands, these nice gentlemen, very kind of them, were out here working on the thing. And they put in metal this way and metal this way. Because the door, remember the door cracked on the bus and it was all cracked up? So we welded the door. We put a reinforcement in the door and put two one inch bars in it. So basically the door is just a skin now, basically. These doors, by the way, they're just hollow. They're cheap. Yeah. They are super cheap. They're just hollow. So we added, it's basically this and it's square. So it goes over and around. Yeah. So anyways, I'm going to let you do the door. I'm going to do the door. I'm going to work on the tank. I'm going to do the tank. Well, I'm going to do whatever you didn't do over there. Well, I've been under the bus working on the other tank things. Well, what do we have here, badge? Should we show them from the inside? What do we have here, folks? What do we have here? We have a glowing door. Hey, are we serving tacos to? Tacos in a bag. We're serving tacos in a bag. We're serving tater, some tacos here. Yeah, tacos in a bag. And pancakes and maple syrup. Oh, man, look at that. My very own food truck window. How do you guys like that? I'll be serving absolutely nothing. You know, they're going to exactly.  No, I don't. Yeah, I don't have ambitions or a license to serve any food. Very, what do they call that? When they come up with ideas. Ingenious? Ingenious idea to come up with a food wagon when you go. I never thought of that one. Yeah, so badge created basically a nut, right? He created a nut by tapping into the metal, threaded the metal. So that's why he's just screwing it in, or I should say bolting it in. And as you can see, it goes in nice and easy, just like abracadabra, one, two, three. One, two, three, where did you go? All right, I'm going to get back under the bus. But we've got exciting things going on here. It's going to rain in two days. So we're trying to finish this whole thing up. And my guess is we'll have running on vegetable oil tomorrow. We've got to install still a pump, a filter, two filters, and return lines, and fuel lines. So we'll probably do that tomorrow. All right, next update. We have a fuel water separator installed. We just bolted it into the battery bank right here. So this thing is going to go fuel, or I should say veggie, right? It's going to go veggie through here, then to the pump, and then to the engine. All right, here's the update. Got a boo-boo. We are going to hold off until tomorrow. Campground host Brad is going to have a little barbecue. By the way, thank you, Brad, for all the hospitality and Heather. You guys were amazing. And I think after dinner, I'm going to play with some caulking and play with my caulk. And I'll put a nice little bead in here because it kind of seeped in when it was raining. So in the next video, we're going to fully install the rest of the vegetable oil components and probably fire it up, maybe even take it for a test drive. So thanks so much for watching. See you in the next video.