 Today is December 17th. This is the Minecraft DevSync. Let's just jump into it here, because how are things going? Great. Had just so much sleep last night. Just feel super rested. Oh, you too, huh? Yeah, yeah. But I spent a bit of time merging Ken's Mart 2 skill changes into the latest version of that skill, and then I added some play-folder event handlers for Wi-Fi setup so we can make sure to provide the instructions that we had on the CD image when using the Wi-Fi Connect, you know, set it up on your mobile device, that sort of thing. Still need to look at what the best way of tying that together is, you know, whether Wi-Fi Connect emits messages on the bus or whether we respond to the state of the Plasma Network manager or, you know, figure that out. The end score has been tracking along with all the audio output working. Ken's been working with them a lot over the last... Thanks, Josh. Ken's been working with them a lot over the last overnight or, you know, all day today looking at their audio record and the ICC and that sort of stuff. So they still haven't got that squared away. But the other stuff seems to be coming in well. Yeah, we should be on track. Presuming we can get over this hump, we should be on track for a nice demo tomorrow. Excellent. All right. Excellent. Thank you. I apologize. I was using my other mute button and I did not realize that it was the wrong microphone that was connected to the call. So that's why you guys were hearing all the kids screaming in the background. So apologies for that. All right. Great. Oh, that's good. I'm looking forward to the demo. And do they have the R4 board up? That's what they're using now? Awesome. That's great. Great. Okay, Ken, let's go to you. I heard your name mentioned. Let's get back to this guy real quick. Okay, then let's go to Chris there. So right now I am running a very long job to rename all the wake word files on the precise server with the naming convention that we came up with a while back. The naming convention was causing me problems. The fact that the old files were not named correctly was causing me problems, because I changed code to, you know, have a naming convention. So I am doing that as part of my effort to get data for Ken. And I made some more changes to my commercial process as well as as I ran it, I found some, some more issues with it. And we're just related to all the changes we've made so far. So yeah, I'm still working on that. It's taking me longer than I'd like, but hopefully today we'll have some data out there for Ken to play with. Okay, are you waiting for a process to complete or are you still actively like debugging things? I know I'm waiting for a process to complete, but preparing for the production push as I watched this job run. Okay. Yeah. Okay, great. Thanks. Ken, are you are you back with us? I am. I am. So yeah. So let's see. So I reviewed the blue system skill pull requests this morning and approved that I finished the code I need to get the counts using the Selene URLs instead of pulling directly from the database like I was doing. I will be integrating I started actually integrating that with the existing code that I have already running but that's quite complex. It's been a while. I have some, not your tickets, but some confluence pages. I got to look up and remember what I was doing there. It's been a while. I'll continue with both of those things tomorrow. So I'm working with panic or right now on on their bill. They're getting really close. He's got everything running on his image except for not able to get a record working, which ultimately appears to be an issue with the itc bus and the XMOS reset strategy or whatever. Now he verified that he was able to pull one of our QT builds. I pointed him to 26. I don't know if he took that or 37. I told him all bets are off on 37 because I haven't tested it yet. But whatever he did he took one of our QT builds he applied the monkey patch and he verified that everything on his end works. So it's not hardware. It's something to do in their image. And that's where we're at right now in that process. So they're really close. I'm confident. Pretty confident. He'll figure it out. So, you know, hopefully we'll have something image wise from them soon. Yeah. So like I said, I'll continue work with panic or tomorrow and I'll continue and I'll continue on the wakeward tagging integration stuff. Awesome. Okay, great. Derek, you have anything for us. Yeah. See so this morning I got the laser cut files uploaded and did some quotes and stuff and I sent that over to all those involved. I could get some stuff if we want to move quickly in early January without expediting, you know, expediting, you can get stuff much quicker. And then I've been working on the Wi-Fi stuff in terms of the GUI side of that. And as Ricardo had asked me to review the active portal side of the GUI, and I've got a couple just tweets and the copy that I'm going to request just to make it a little bit more instructional and then at the end to add a link to account, well, not necessarily link but instruction to go to account.microsoft.ai just to give people a jump on that and a little styling team. And the rest has been on the actual screens that display on the mark to itself. The screens will need to change from what we were doing in the vertical orientation. So it's getting the assets together so we can finish that and updating a few things because it's changed slightly with the panic or design versus what we did internally before. So we're getting those to guess maybe by the end of the day here. And yeah, that's me and the other thing is always kind of reviewing the SJ222 specs that you put together, Michael, and the fan and I got a comparable one to test that I could get very quickly. Yeah, both Kevin and I actually already have fans that we've tested. So in terms of the, you know, testing our circuitry and stuff, what I'm looking for now is a supplier that will, you know, that can give us a fan at a reasonable price that actually, you know, gives us the thing that we're asking for, because I just don't want to, you know, fall victim to miscommunication about what the specs are. And since there's not really any hard standards about these things. I don't even care if it's, yeah. Okay. I had a little glitch there. I think, yeah, Internet dropout. But yeah, to be clear, I don't even care if a thing plugs in and turns on. I'm just going to make sure I don't have any clearance issues in the design. And then, you know, I can, I can use the wires and stuff to like finalize the wire link and everything. But yeah, I don't necessarily care if it works. But it's the right dimensions. Gotcha. Okay, great. Thanks. Josh walked away just in time for me to call on him. I got the, this auto update thing done for the, for the Raspberry Pis. So, and then they gave me a repo to push that through into and then I have a What repo did you use? I haven't pushed it to any repo, but you guys told me the repo and I saw an email from you. Yeah. No, I didn't see it. What repo did they tell you to use? I suggested Microsoft devices or DevOps. Any preference from anyone on the team? No, the only reason I asked is I may have some similar scripts I'll need to put somewhere and I wasn't sure where they would go. Okay, so my craft devices where it is great. Top level directory that's like, you know, hardware setup. Okay. And then I'm sending Derek's final test for the laser cut to the thing right now and then I'm holding a ridiculous amount of clear PETG filament and starting that thing rolling. And then I wrote a children's book. So, we just want to interject on the location for that script. Josh, is that a script that is supposed to flash the Raspberry Pis firmware? Is that what we're talking about? It's the one that checks the firmware, checks for the latest firmware and then grabs it and updates the Pi if necessary. That's a two step process. You have to boot the device once to pull that down, check it and then push it and then you have to reboot it and make sure the firmware actually updates. So, I just threw a toggle into a little temporary file that says either you're on first boot or second boot and then it'll just toggle back and forth. And let me point out that if you don't do that, the second step, or if you don't do it correctly, it's not that you'll break your Pi, but it won't allow you to update the firmware anymore and you'll be stuck with using an SD card, because I have one in that state right now that I have to figure out how to hard reset. Yeah, so anyway, it's a two step process and then the LEDs, when it's confirmed everything's good, they flash green and away you go. Okay, so this is just a utility for us before we package up the pies to stick into the dev kits, right? Yes, because otherwise the USB stick that we ship with it won't be a boot device. So actually, I would like to offer that maybe we should stick this in a utility directory off the Mark II hardware repo. Yeah, so good point. And I was going to say, for example, I'm going to have a similar need for maybe power on self tests or hardware testing scripts, which are specific to the Mark II. What you're talking about, Michael doesn't really exist. What you're talking about is a branch that's off of my cruft core. So even though it's. I know. It was in my proposal for how we organize things though. Did you mean, sorry, when you first said it, I thought you meant the actual Mark II hardware repo, like the one that specs out the SJ201? That would be a good place for it as well. Maybe, yeah. Anyway, somebody just point me at the where they want it and I will show all that stuff. I will send you a link to that one. Okay, and then I, and then yeah, I was productive. So yeah. Cool. I've been less productive. I had another day of doctor appointments with the kids. So chugging along on getting the fan specced out, we should have a bunch of samples arriving next week. And so we can put in fans in the kit that don't cost $15. And we're getting the PCBA is underway. Kevin and I have approved the final SJ201 layout. It's on revision 11 now. But so yeah, so now the rev we'll call them rev five boards. Kevin should get some in next week. And we'll that'll be our test just to make sure we didn't break anything on the new layout changes and then there at the same time we're getting quotes back from the fabs for the high volume runs. All right, I'm doing this. So yeah, I guess that's it for everybody. Anybody have any other. I'm in charge way. Who thought that was a good idea. So, what's next. Anybody have any things that we need to talk about or like what's exciting is we might have a working image by tomorrow from panic or everybody and test early next week when they get their hardware. I think that's that's a good thing to kind of end the meeting on. Yeah, I agree at the good point. Yeah, so we'll record that and if it goes well, we'll show it to everybody. And if it doesn't go well, we'll show it to everybody anyway. We can always edit it out. We'll fix it and we can go back and say that was fake news. We didn't say that. Yeah, no, no more fixing it in post for showing you the real something I forgot to mention. Okay, something I forgot to mention was one of the reasons I'm renaming these files is I was finding as I copied some files over initially. I had like 15,000 copied over. I was playing with the tiger. And a lot of the the samples I was getting back for like zero length audio files. So there wasn't anything in them. And because of that, the thing that shows the audio is just a blank and I didn't know what to do with it. So part of this script that I'm running now that we're naming these files also looking for the correct headers in the way of file and looking for the number of frames of greater than zero in the audio file. And basically I'm writing out an error file any files that I find that meet that criteria that we can we can deal with later but it was going to be a bad user experience if you know half the, you know, half the samples you try to tag or for empty. Oh, that's a good catch. Yeah. So it sounds like we may not have as many samples as we thought. That'll be another consequence. You know, it was just the first, I don't know, several that I tried to tag. So it may just be that I, I'm luckily got the, got the worst ones in the beginning but yeah, I'll let you know how many wind up in my air bucket when this job is running. Great. Yeah, that's good to know. Awesome. Anything else. Okay, great. Well, we'll see you all again tomorrow then. Thanks very much.