 Welcome. Today is December 4th. This is the Microsoft Developer Sync. All right. I hope everybody had a good week. We had a lot of good things happen this week. Let's see how many more good things have happened this week. Let's start with Ken. How's it going, Ken? You got those boards working? So I've got my board. Yeah. I mean, the LEDs and GPIO switches and the volume appear to be working and I pretty much can start work on converting or creating a personality for this particular type of board with the existing infrastructure. The rabbit hole I went down to today, though, was trying to get the audio working on the QT image. And that's the whole I2S, compiling and everything. So I'm actually recompiling the kernel and I've got some issues that I could follow up with the blue system's people on regarding QT. But then I remembered that this is actually Panicor's issue. So I'm probably not going to bother building the I2S driver and stuff for here. I have some information on what needs to be set up, but I'm assuming Panicor already would know that. So I'm just going to go ahead and get the other pieces of the hardware working for our environment so that when the Panicor image is ready, it can be pushed to the Mark II branch and it can be part of it. And assuming they do their job with getting the I2S drivers compiled and working and all the issues I've seen here, we should be good to go. Okay, great. So Kevin verified that the I2S was working. I assume he did that on a basic Raspbian image. Right. And I validated that work here as well. So I have the Raspbian image up and running. I can see the device. I can listen to it play. So that's absolutely true. But getting it running on a 32 bit Raspberry Pi versus a 64 bit Alpine image, there's some work to be done. Okay. All right. That's good to know. So you're going to, so you've punted that over officially to Panicor to get some I2S drivers and they already have this Jira ticket in there from last week. Okay. We're two weeks ago, right? So I haven't followed up on that. The only follow up I would do is once I get our stuff working, you know, the volume, the switches and the LEDs integrated in our code. If I had to spare a bandwidth, I can go ahead and recompile the Linux headers and stuff on the QT image and give them any pointers if they get stuck. But I suspect that's probably, I suspect they'll have it working before I get to that point. Okay. Yeah. It seems like there might need to be some collaboration there to get this all working because, you know, I don't really know what's involved with the I2S drivers, but, you know, if you've got an example of them working in one operating system and, you know, you need them working in a different operating system, you know, it seems like you both, you each have half of the puzzle that you need, right? Like, they're not going to, you know, be able to monkey around with Core the same way you are to get the audio drivers working and that sort of thing. Yeah, but this has nothing to do with Core. This is OS level stuff. This is, yeah, this is simply to get the I2S device driver for audio showing up under Aplay. As far as, yeah, as far as the underlying configuration goes for the boot config.txt stuff and everything, I've got that kind of cloned over from the Raspberry Pi image working. Okay. So I see that stack correct. There's a couple of kernel modules that'll have to be installed that, again, I'm assuming they'll know. So the point is, I'm going to get our stuff going and then as soon as I'm done, I'll turn to the image and say, now I want to see it working on the Panicore image. And if they haven't done their, you know, that work by then, then I'll engage with them and go over the steps necessary to get it working, which may require us to reach out to Blue Systems. I just don't know yet. Okay. Well, let's try to push that as quickly as we can because, you know, depending on whether what the state of the rest of the system is, I don't want to just get into a deadlock of, you know, people waiting for you. The reason I decided to go this route is we have to have our stuff integrated into our code anyway. So I'll do that first. If Panicore is not done, then obviously we'd both want to do a full corp press on getting the image, the kernel, you know, with the right drivers running. Remember that they switched over from 32-bit to 64-bit recently. So some of that work would have been throw away if they would have got it done on the 32-bit anyway. 64-bit requires different headers and different stuff. I mean, I, you know, I got it running on 32-bit, but on 64-bit there's a missing byte shift, you know, header file and stuff like that. So I just decided to punt on that, get our stuff, which we absolutely need done first, done anyway, and then rally back around with Panicore early next week. Okay. Sounds good. All right, thanks. Let's go on to Gez then. How's it going, Gez? Yeah, it's going all right. The Panicore guys got the Wi-Fi connect stuff all wired up, and so the images, there was a small breakage as they were transferring everything across to that, so 64-bit builds. So it's connected, but it's not, it's not, you know, going through the processes as you'd expect it to. So I need to get back with them and figure out what's going on there. They were expecting another, a separate edition coming in, but my understanding was that that was all branding kind of stuff, and EAP support, but everything else was meant to work at the moment. Anyway, so I've got to follow up with them on that. That was all overnight. Other than that, I got the Ken stuff working and went back and forth with him a little bit to make sure we had the steps to reproduce that, which is mostly, I think we're pretty there, aren't we? You said you had an issue doing it on a different image, recently. Are you talking about me and getting everything running? Yeah. So I've adopted a hands-off attitude regarding the Panicor image and have switched to working off the QT image since everything in the Panicor image. You said that the GPIO stuff, like, did you, anyway, I'll follow up with you after. Yeah, so I've just been sending across all the details of that in the Panicor so they don't have to mess around. They can just drop it straight in, hopefully. And started looking at the, I had a quick look at the VF control USB source, and the licensing for that means that we can't distribute the source at all. So we can only distribute binaries, which is a bit of a... Cool. I have an update on that. I did actually get permission to distribute the source for that. Really? I'll, yeah. If I don't send that over to you, ping me on that. But I did get at least an email from them saying that, sure, we can use it. So we can put the source in a publicly available repo? That was my understanding, but let's go take a look at it. Yeah, cool. Because the licensing file says otherwise, so we want to make sure that we have that in writing. So we won't get... Yeah, it just... Obviously, you know, particularly with our community, they're very keen to see the source for everything and make sure that everything running on the devices is open and not containing anything that shouldn't inside there. But anyway, I've dropped the binary and the Microsoft devices repo for the moment anyway, just so that it lives somewhere and we can reference it and stuff. That's about it, you know, I think. Oh, and we did... Okay, did a translation run, which was really good. So a lot of skills getting translation updates and it also came in an opportune time to test the CI updates that we did recently. So we're running concurrent builds and it all seems to be working really smoothly. So that's good. All right, cool. Yeah, I saw a lot of translation tickets coming through recently. Yes, it's something that we need to look at from a higher level. But for the moment, that's what it is. All right, cool. All right, Chris Vair. So today, I spent time looking at the... Adding some device level metrics to our metric stack in Rafauna. Did some coding around that. Just about done with the coding and start testing this afternoon. Once that is done, I think my initial pass at metrics will be done. And then I'll move on to the... On Monday, I'll move on to the new membership stuff. Okay, that sounds great. Derek, you're up. All right, so today I've been balancing a little bit of helping mostly Chris to dare and start the ordering process for the initial run and just kind of handing over things and answering some questions. We had a meeting about that earlier as well. Also got the quote back. Everybody that was on that meeting got, I think, copied on it the quote back from the fulfillment and kit assembly solution. So we reviewed that. And personally, I think it's going to work out and we need to discuss a few more things, right? I'm feeling good about it. And then the thing, the other things I was wrapping up was I had a successful print last night of the full audio chamber and one print solution. So this is all just one print, which means we can double the capacity of printing these. I was actually really happy with this. So I had a couple of changes to that this morning because I had to move a few things, but that was quick. And then I've been working on getting the camera oriented a little bit better on the laser cut version. I finished that. And I'm tweaking a few things still in the 3d print version. So now this guy will sit right in the middle of the top. It's got a little part of the laser cut design that holds it in place. I think it's going to be in the middle. Yeah. Yeah. The middle right in, and it sits and I tested it. So it sits back. Actually sits behind. The screen. Like this. But it's, you know, you don't catch the edge of the screen or anything in the view of the camera. So it's all good. Great. Okay. That's me. That sounds awesome. So what's next up for you? Well, I got to finish this on the 3d print. No late, mostly this, like, I'm still going back and forth a little bit on how the slider works. So close off the, you know, our mechanical shutter, kind of digital music thing. So I got to finish that. And then I need to re quote. This will save us maybe three bucks, three, four bucks. And so I need to re quote a bunch of stuff. For Josh and Chris. And have that all packaged up and ready in account. So when it's time to order, we just hit go. So that's my goal Monday to have all that ready. So that, you know, I'm going to go to the next, whoever says when it's time to go, can just go to the accounts and say, you know, we're part of the X. And we'll be good. That sounds awesome. All right. Josh, do you have anything you want to share with us? Sure. We bought many, many things. So things are on the move. The pie order just dropped a few minutes ago. And the screens were on the move as of last night, although we're still working out how to transfer money to China safely. And basically anything that's over $5. I should be moving by the end of the day. A lot of it already is moving. The 3d print went extremely well. So I have a copy of the one that Derek has as well. And I've got a copy of the 3d printer and it has been reported that it is solid. I did want to provide one quick piece of feedback Derek. The ventilation holes on the 3d printed enclosure are. Right angle corners. Right. The little ventilation stack of holes that goes around the outside of the rim. Yeah. It'd be awesome if those were rounded corners because they would print much, much better. Yeah. Awesome. And then, and then I guess I will. We'll come at it and come at this with a question more than anything else. So do we have a working mark too? You missed the first bit. Yes. We have all of the parts of a working mark too. But we do not have it integrated with the Pantacore image yet. So. That's the next seems like the next step. Okay. And we're having some discussions about some promotions and stuff now that we have working stuff. So. Is there a. Estimated ETA on the working Pantacore version because the first ETA was two days ago and the second ETA was today. So. Yeah. So, I mean, I've got an image that I can use. I don't have. Like I've got the old SJ to a one says that the audio app has been used for a long time. I can talk to the device on my, on my kitchen counter. What they're working on at the moment is the wifi connected and getting that squared away. And then there's a bunch of stuff. Like currently you can't use any of the buttons, for example, on the LEDs and all that sort of stuff. So. And the SJ201 is in there. Yeah. Is that working on the core functionality first and then getting to all the other tickets. Yeah. And then is, is. We got an SJ201 rev four to 10. Kevin was working on some more. What's, what's the, I am not advocating for one of these for me. So let me just start with that. What's the, where do these need to be? Do we need to get two to Europe and one to you guys? Okay. And. Okay. I mean, yeah, I can do everything else. Okay. And we can drop those overnight in a FedEx box. So, and we will simply mark them. Itar. Weapons. Weapons targeting hardware. And I just see what happens. Excellent. Cool. So. So we're very, very, very close on that. It sounds like everything's coming together. Yeah. I'm shut up now. Yeah. It does sound like we should coordinate a bit. On our priorities for Panticor because. Yeah. The, it seems like we have a, a working image now. That runs on the. On the hardware. Right. But now we need to start getting our drivers and that kind of stuff that really, you know, makes it a mark to. Integrated. And now we've got two versions of the hardware out there that are not compatible. So we have to decide which versions they're going to actually work on. Obviously they can't really work on the Rev four until they have one of those boards in house. So let's try to prioritize the work that they're doing on the Rev three. That syncs up with the Rev four stuff. Right. So like getting. Communicating over the eye. To see bus. That's common work. That's going to be useful for both systems. Right. Communicating over the USB to the XMOS chip is not useful because we don't need that in the Rev four. Getting the I two S version up and running is absolutely necessary for the Rev four board, but I don't know if they can work on that until they actually have a Rev four board at house. So I don't know. If you, you know. Try to coordinate their priorities there. Make sure they're not like, you know, wasting cycles on things that they don't need to do for the Rev three boards at this point. Yes. We shouldn't need VF control USB anymore anyway, right? No, but we do need it. There's an I two C version of the same thing. Yeah. Yeah. So ultimately we'll, you know, we'll need that version. Yeah. Yeah. Cool. Yeah. Okay. Great. Yeah. Hey, this is excellent progress with all the pieces are definitely coming together. We've got parts on order. This is very exciting. So thanks everybody. We will check in again on Monday. But if you've got anything that you need to share issues in the meantime, obviously feel free to reach out. So. Thanks.