The DCU archery team took another shot at success at the DCU Interbarsity on Sunday the 25th of November. This follows their recent win at Carlo IT, where they took home six medals earlier this month. On Sunday, their compound team took first place, and the mixed team took third. I was pretty happy with how I got on. I finished first in my category this time, so that's kind of what I'm hoping for all the time. But I know that there are a few people who'd like to do better, but I'm actually happier hearing people annoyed that they're not doing as well as they can, because it means that they want to win and they want to get higher scores, so that's really encouraging for me to see, because it means that the standard of the whole club is going to go higher, which is what I'm looking for. Chairperson Rhiannon O'Connor said the competition host in DCU was a success. It was just a bit of fun the whole day, and everyone seemed to enjoy it, like the other colleges all like this at the end. It was just, it was good. It ran really nicely, and we were just happy with the current win. Martin Cunningham currently coaches archery in five different institutions across the country. Great, better archers. That's my only aim and objective. If they win, great. If they set records, brilliant. If they go on to be a national team member, if they go to Tokyo, whichever, it doesn't matter to me. As long as I get the archery in the door, and I make them a better archer by the time they go out the door, that's my only goal. Emily Sheehan, DCU TV News.


Live from Las Vegas, it's theCUBE. Covering VMworld 2017, brought to you by VMware and its ecosystem partner. Welcome back, I'm Stu Miniman joined by my co-host John Troyer. You're watching SiliconANGLE's production of theCUBE here at VMworld 2017 in Las Vegas. Happy to welcome to the program two first-time guests, but from a company we've talked to many times. Rex Backman and Rob Young, both with Red Hat. Rex is the Senior Principal Product Marketing Manager and Rob is the Senior Manager of Red Hat Product Management. Gentlemen, thanks so much for joining us. Thanks for having us. We're happy to be here. So sorry, tripping over sometimes titles and things like that, just like acronyms go out there sometimes. So I go back, I started working with Red Hat before. Red Hat Advanced Server came out, which became Red Hat Enterprise Server. Then when we talk about virtualization, it used to be Rev, R-H-E-V, and now it's R-H-V. So sometimes the people say in the same place and the badges change other times that things change a lot. So why don't we start with Rob, tell us a little bit about how long you've been at Red Hat, your role there. So I've been with Red Hat now for two years, almost to the date. I come from an open-source pedigree. So I worked with companies like MySQL, MongoDB to develop not only the open-source model, but a community around those products and a commercialized version that people trust to run in their data centers. All right, and Rex yourself? I'm fairly new to Red Hat joined about three months ago. Virtualization background is really from the world of Microsoft. So happy to be at Red Hat. We've got a strong offering with Rev and we just want to help get people more educated on it and the opportunities we have to help solve their problems. All right, it's always an interesting dynamic. You talk virtualization, we spent a decade. It was VMware's ascendancy and the threat of Microsoft and KVM and Rev and everything were going to be there. There's a nice Red Hat booth on the show floor. Always customers have had Linux sitting as guests in there and lots of those. I'm sure you probably have stats for me as to how much of that's been Red Hat over the year, but tell us about the relationship. VMware, Red Hat, virtualization. So we see the relationship with VMware and other companies and partners within our ecosystem as very positive. If you look at the workloads that are running on VMware primarily, a lot of those are Red Hat Enterprise Linux, applications that are running on Red Hat Enterprise Linux. So we see it as a very positive relationship and moving ahead, we see a challenge in maintaining a virtualization footprint within VMware, within the market because of the evolution of the market. And we see that virtualization is becoming more of a commodity based feature and the challenges that it poses to partners like VMware going forward to evolve along with that model within the market. Well, if virtualization is a commodity and it's becoming a commodity, what is the Red Hat approach with KVM and RHEL in terms of, it's parts of it a commodity, but certainly the stack and the system it plugs into is not. Yeah, I would say it's also very foundational. Virtualization is everywhere. And I think the value Red Hat brings to it is the capabilities we have in our team, capabilities we derive from the open source model, and then virtualization with Rev, bundled in with Red Hat Enterprise Linux. It's foundational and then if you bring in other aspects of the Red Hat stack around manageability, cloud, things of that nature, I think we have a strong offering, a good offering that people can choose from. And I think that's really important for us is our customers have choice. And then us, we differentiate ourselves on the open source model primarily. It keeps becoming a more and more complex world. We've been watching for years, it was the pull of kind of cloud against the data center. Now we're even seeing edge pulling at the cloud, but let's go back to the data center. What's Red Hat's viewpoint? What are you hearing from customers? What do they need in the data center and how are they viewing that these days? So what we see in the modern data center one, the workloads that we see around mode one applications that are legacy applications, that footprint is not going away. It's going to continue to have a bare metal footprint as well as a virtualized and private cloud. So what we're doing and what our customers are asking us for is a transition from pure virtualization or bare metal to virtualization to hybrid cloud. And what we're doing now with our engineering efforts, not only upstream, but also from a proprietary and a configuration standpoint, all open source by the way, is we are giving customers the option to standardize on a virtualization platform built on KVM that shares components with hybrid cloud technologies for mode two. So what we see from our customers is they're maintaining mode one, but buying and planning for mode two. And that's how we see the on-premise data center market heading at this point. Like you don't unpack that a little bit for our audience because you know, the big discussion this week is public cloud. Yeah, sure it has virtualization, but it's not VMware. So now we've got this one option, VMware and AWS starting to roll out. Are you saying that my data center, I can really be compatible with the public clouds and is that the red hat pieces on both side or is it native to what AWS and Google are doing? How does that dynamic work? So the way that we're approaching it is we look at it not only as a software solution, but also as a paradigm shift in more openness, APIs. Things are more generic. So if you want to plug into a common framework for management as an example or deployment, you can easily do that via the open APIs that are available in the open source community. So as an example, we provide a management solution called CloudForms and with that platform, it's part of the red hat stock and solution, we allow customers to manage not only their virtualized environment, but also their hybrid or private clouds, but also AWS as well. So if they've got instances running on AWS, they can manage it through one pane of glass. And this is our strategy going forward, but it's not tomorrow. This is happening today with our red hat stock platform. Yeah, so Rex, you've got a background in networking, networking front and center, and networking security even more than ever that I've seen is at VMworld. How does that fit into red hat's whole story?  And you know, I think red hat with what we provide and red hat enterprise Linux, obviously the foundation started with, you know, the knowledge that our R&D team brings from their open source background around rev and server virtualization, but also now network virtualization capabilities. And also what red hat has around storage, you know. So I think we cover those three Annie's into the game of virtualization. And then, you know, it adds to, you know, the equation Rob was talking about, which is the whole red hat stack, which I think is a good, good, good story. And again, choice for our customers. I think actually 2017 is actually a really interesting year for virtualization. We're at an interesting era, right? 10 years ago, you had some, you know, market dominance, you had, you know, you're looking at Microsoft and VMware like we talked about, but, and another, we had Zen and KVM came up and they were a little scary for people, right? They were developing, they weren't as, they weren't as mature of a stack. I do think now that the average admin in an average, you know, IT estate is actually dealing with the fact that, oh, I could actually manage multiple hypervisors, look at a mixed estate. It's not as scary anymore. The technology is more mature, more manageable. Can you talk a little bit about that scenario of a mixed estate? Like if you have a, you know, part of your data center is running VMware, what kinds of use cases and what kinds of management scenarios would you, as you start to add, you know, red hat virtualization to the mix? So the way that the dynamic that we see and play right now is there's a huge install base on VMware and a lot of customers, a lot of clients, a lot of partners are looking at that relationship now and deciding if they should invest elsewhere in other solutions. So what we provide is the ability to manage those environments. The clients for Hyper-V, for VMware, for Red Hat, all within one pane of glass, but it allows customers, one, the choice to manage that heterogeneous environment built on multiple hypervisors, but it allows them to evaluate if maybe the Red Hat solution is better for them. And if we can help them with V2V migrations as well, workload migration, mobility, I think that's the perfect scenario for Red Hat and open source company and choice. And I think, you know, some of the customers, you know, public case studies that we've promoted, some of the attributes that they've been looking at that shifted them over towards the Red Hat side was, you know, performance, you know, was very, very important. Scalability was very, very important. So I think, you know, it depends, customer to customer. I was actually wondering about, so do we see like replatforming as people are re-architecting, are these green field opportunities? I mean, I imagine that, again, it's all across the board, but any, have you seen any particular kind of common patterns of people standing up, maybe a new business critical app on a new platform? Maybe they're re-architecting it to be a little bit more cloud native. Any particular directions like that?  And then that kind of is a strong point for us. You know, Intermountain Health is a company that there's some news on from us last week is an example of that. You know, British Airways is another customer like that. And as Rob has said, it's large companies, big brands, down to commercial companies as well, or governments or education. So I think it could be performance, it could be open source. Open source is definitely one of the drivers. Yeah, yeah. Yeah, and what we're seeing there with open source is that the more trust is built in open source, the more enterprise adoption and the cost-effectiveness of working with a development team that's worldwide, a QE team that's worldwide, really helps to build the stability of the products that companies like Red Hat build subscription models around. So there's no vendor lock-in as well for a proprietary licensing model. And we find that many customers are very open to that discussion as opposed to the alternatives. One of the other discussions we've been having at VMworld for the last couple of years is this whole containers discussion. Is it VMs versus containers? Is it containers inside VMs? Red Hat Summit, I mean, huge discussion. There was a super popular t-shirt on one side that said Linux is containers, and on the other side it says containers are Linux. So where do you see that discussion? Any, what do you think about how VMware's been looking at things? There was a big announcement about VMware and through the Pivotal activity, kind of embracing Kubernetes. Red Hat, I'm sure is saying, hey, welcome to the party, right? So there's an interesting dynamic with containers because containers, Kubernetes, you name the project, is purely an open-source play. And if you look at the projects, the contributors, most of this is going to be built on an open-source model. So proprietary software companies like VMware are going to be challenged to adapt and evolve how they develop, how they contribute, the presence within those communities. Now Red Hat is uniquely positioned in that our model has been for the last 25 years that we're purely open-source. Everything we do is out in the community and it lends itself very naturally, not only the way we've done commercialization of Linux, but we're doing that now with containers as well. And if you look at the dynamic in the market, you know, a lot of people believe that there's VM and or containers and this is really a symbiotic complementary relationship. 85% of the workloads for containers runs within a virtualized environment and containers and virtualization fill gaps for each other that is just a natural compliment and because Red Hat is already comfortable operating in the open-source environment in this way, we think we're just in a very good position to lead in both areas. So. The, you mentioned open-source commercialization and Jim Whitehurst, the CEO of Red Hat has been on theCUBE. Stu and I talked with him at the last OpenStack Summit. I was super impressed by his insight and grasp into the economics of open-source and how Red Hat has been able to build a model like that. Can you talk at all about data centers or IT spend in general and CapEx and OpEx, where it's going in a more open-source-driven world? Where do you put your money then? So do you want to answer or do you want? I'll take a stab at it. Where can you now invest your money? How don't we, that's a little better. Yeah, I think it's really interesting and you know, I'm going to answer this question from the perspective of a three-month Red Hat employee but with, you know, a lot of experience in the industry with proprietary companies, if you will. I think the value, the commercialization of what Red Hat has done is, you know, there's the upstream aspects of open-source and the programs available there and then there's the downstream commercialization of what Red Hat has done, which is wrapping the value of a Red Hat subscription around that open-source project. And I think what we see in our customers in terms of budget spend, you know, more on the OPEC side than the CAPEX side in our case is, you know, looking at that price point because some of our customers, well, many of our customers, if not all of our customers, there is a price sensitivity. I think a lot of customers now maybe not be, and this may be kind of a crazy thing to say, may not be as price sensitive as they used to be. Now it's more about innovation, agility, speed to market, but still the economics is important and I think the value Red Hat provides and the uniqueness in the model that Jim and his crew cracked early on to start Red Hat is the ability to provide that Red Hat subscription at value for open-source. And what we see is that it's most of the time in cases, you know, it's an attractive price point and that's how we win customers. So I think, you know, long-winded answer to your question is I think there's a strong future. You see more and more companies adopting open-source in their programs. I think Red Hat is the leader of that in good shape. Rob, why don't you just give us the final word, conversations you're having at the show, how are people here in the VMware community embracing, is it an open-source discussion, is it the innovation and kind of the new features, what's bringing them by to talk to Red Hat? So I think it's a mixture. So what we're seeing is a lot of interest in Red Hat solutions, the Red Hat stock. And I think customers are now looking at Red Hat as a good enough alternative to more pricey alternatives or more pricey options. And if you look at what we've done from a strategic standpoint is much like we did with Red Hat Enterprise Linux, we are now using Enterprise Linux as a foundational support pillar, so to speak, for the Red Hat stock. So if you look at the APIs that we've generated, a lot of the interest that I'm getting, the question I'm getting, not only from customers, but from folks out on the show floor, other vendors, is what's your API look like? Can I learn more about it? And to me, that's the leading edge of a wave of maybe that Parker Favillion looking a little bit more red in the days to come. So just my opinion. Absolutely, I know John Troyer and I have been talking for a few years now, that API economy, something that's been coming into this world and that intersection between what all the Linux admins have known for a long time as to their operational model matches a lot of what we're seeing in the cloud. So Rob Young, Rex Backman, really appreciate you joining us. For John Troyer, I'm Stu Miniman, we'll be back with a lot more coverage here from VMworld 2017. You're watching theCUBE.


Aneuploidy happens when you have an odd number of chromosomes, an abnormal number of chromosomes in your karyotype. Your cells end up with an abnormal number of chromosomes. Now, most cases of aneuploidy, most cases of too many chromosomes or not enough chromosomes result in death. This is miscarriage when when if you make a kid that has the wrong number of chromosomes, you might not even know that you made a kid because that it's not going to survive. There are a few examples of aneuploidy that are survivable and the the malfunction happens in meiosis. There's a process in my that moment of separating chromosomes either in meiosis one or meiosis two when anaphase happens. In anaphase one we had homologous chromosomes separate, non-disjunction is this process of failure to separate. So if those sisters or homologs say nice try this is my homey this is my homey log I'm not leaving that guy that's non-disjunction follow it through if non-disjunction occurs in meiosis one look what happens one of our resulting cells is missing an entire chromosome and the other one has two copies where there should just be one. So it ends up with two half of the gametes have one too few chromosomes and half the gametes have one too many from this one event this one non-disjunction event non-disjunction can happen between sisters and so it can happen here in my meiosis two and it's the same thing it's non-disjunction only this time we end up with half the chromosomes are normal or half the gametes have the normal number of chromosomes and only half of them one of them has one too many and one of them has one too few because the non-disjunction event happened later in meiosis after we had one normal division take place non-disjunction um you end up with the full chromosome extra in the gamete and then imagine if any of those gametes meet up with a another gamete that has the normal number you're gonna end up with one too many or one too few how do you know and why genetic testing is one of the things that they're looking for is when they do genetic testing on a pregnant human they'll look at the they'll do a karyotype and they'll be like dude let's count and see what happens you push pause go ahead and push pause and then see if you can find the place or the the aneuploidy event in this karyotype right here so you push pause I almost pushed pause because I was following my own directions super important to follow directions but I'm assuming that you're back now did you do the job did you go and find the issue well sometimes these karyotypes are interesting to peel apart or to look at but you can sort of go through and go okay yeah I see my pairs I see my homologous pairs and I see how like the staining of them I could if I were given a big pile of these chromosomes I could actually sort them out into groups and I can see everything and it looks like am I right that there are two of everything I see two of everything some things are like kind of bent and weird but I still can look at it and be like okay I see the banding the dark and the light lines like that they still look the same they just look bent yeah yeah yeah I feel good I'm assuming that there's one chromosome here so I'm like this is at the end of our giddy up I probably should count except that I know that that's the X chromosome this should be the 22nd chromosome and this should be the 21st chromosome right we could probably count back you could push pause and count back and make sure I'm correct we have one X chromosome what's that that's the Y chromosome except what's true there are two Y chromosomes that's an example of aneuploidy we shouldn't have two Y chromosomes now interesting that's an example of an aneuploidy you may never know about an extra Y chromosome doesn't have a huge impact an extra X chromosome will one X chromosome and know why chromosomes will you will see but it you survive that's something you can survive probably the most common aneuploidy is trisomy 21 do you know what that is that's the condition that that's the non-disjunction event that results in Down syndrome and one extra chromosome 21 is totally survivable and you just have a little extra DNA and and you have Down syndrome okay how do we feel about where we going next next up we're going to talk about pedigrees and pedigrees are a strategy for analyzing human inheritance patterns when we can't like go around making babies in vials and dumping them into counting chambers yeah we're not going to do that with humans so let's talk about pedigree


It's crazy. Travel time. We got big things. Big things happening. This is something I don't normally do. I don't normally take you all on days like today, but I'm gonna attempt to. I'm gonna attempt to take you along. As y'all know, I used to be deep within the outdoor business of industries. I did sales. I've done camera work. I've done a little TV time. I've done just about everything. And I still like to do that stuff. And we got manager Matt with us, which you guys have seen on this channel. He does a lot of the business stuff for the Gugans and myself. And he just helps us out in so many ways. He's an amazing man. Anyway, he needed a little company on this trip. And I'm just the man to go do it. So let's head on to the deep swampy south of the Georgia. Actually, we're not going to the deep south, but we're just going to Georgia. We cannot forget OSG's chauffeur service. Yes, welcome aboard. Welcome aboard with Emmy as well. This is your co-pilot. She's going to be a great co-pilot one day. And we're also accompanied by some friends. I have a stick here. This is actually one of the sticks that y'all made me. Thought I'd start taking it along for my run since it's lighter than my other stick. And I've got a fly rod in here for some reason. Don't really know. We're on our way to the airport, but I've got to do something first. Hopefully it's successful. I'll tell you about it in just a second. It's good news, folks. I went in for the drawing first come first serve for the public hunting land. It's just for that. There's only like a hundred left. We got in and I didn't have a renewed license. My license isn't even expired, but I had to have a renewed license. I did not get drawn for the deer, which is extremely disappointing. I did get drawn for hogs, ducks, and anything else for general. So big win. Now we got to get on a flight and head to Georgia. Emmy, can you just stay put? Stay put in there until daddy gets back, all right? We'll see you tomorrow. Okay, love you. It is never a dull day at the Chick-fil-A. Anywhere you go, even in Atlanta, Georgia. Today is CKPK day. There's a bit of a line, but at least we know we're helping kids out. I was born in the state of Georgia. I sometimes don't let that out, because I'm so proud to be a Texan now. Just about on the Florida, Georgia line, just like the songs, the song Writers, that's them. I miss the excitement of helping the children. They forgot to put some nuggets in our deal. I do need myself a napkin right now, because I have got the most. I've gotten yellow, honeydijon juice on my shorts, about to go to a meeting. This is, what do you do right here? No, they didn't give us napkins. Well, here we are, back at the Fish Cave, back from our meetings. We got going down the road that night and it turned into what some folks in the South might call an absolute gully washer. So I really wasn't able to film anything else past that point.  In this trip, the Me and Matt went on, a perfect example of just having connections, meeting people. I really wanted to go on this trip just to meet some people on the other side of the industry that I haven't met yet and you never know where that might go. One of my latest videos, people were pumped about me seeing the deer and I've also just been seeing tons of hog activity and as you guys know from the beginning of this video, I got pulled for general. So I'm super excited and I need to go make some preparations. I need to get some things. And I already have some trail cameras. I'm taking them out of the treehouse yard and I'm gonna be placing them in some areas. Even areas I can't hunt just to try to get you guys to be able to see some of these giant deer that I've been seeing and hog activity. It's crazy. I've really been going and I've been running as my scouting and I'm kind of going off paths and going into different areas that I know that a hog's in the deer or living. So it's almost time. Hunting season is almost here and hog season is year round in Texas, y'all. So we're gonna go hang some of these up. We're gonna go get some other supplies and get ready for the hunting year. I was planning on going to send them in Crete here but there seems to be a car. There was a car that had gone over the bridge. I wasn't sure if anyone was dead so I didn't film it. It's not really something I wanna put on the internet. Ladies and gentlemen, we're back here in the basket. We're going to be putting these trail cams out here very shortly. I'd love to know a good recommendation on trail cam. I picked these up very cheaply and I got them for like 40 bucks a piece. So these were wild game innovations. I know they've got something to have Wi-Fi and crazy stuff like that. I may wanna put one of those close to the house but these I'm going rogue with. We're gonna take them out here just a little bit and plant those. So I got one of these Sniper Hoglight. I heard this guy that runs this company is a very nice gentleman. I think his name is Rob. That's what the archery store told me, my buddy JT. This is what I used, a video you guys never saw. This deal's pretty neat.  It becomes your stabilizer. Someone's calling me, Los Angeles. I'm gonna take this, could be big. Yes sir, I'm good. How are you doing? Wishing you were fishing? Yeah, I understand that, yeah. All right, well that was actually an important phone call. It was a potential sponsor. Always looking for more of those especially in the outdoor industry. So that's really cool. Thank you guys for all the support on this channel and just the positive comments and everything like that. That sometimes helps when there's sponsors and partners, you know, checking things out. They go and they see positive stuff. Helps me out. So I appreciate you guys being so positive here on this channel and I get a lot of comments on that from other brands. Screw that in there and then it has a light connects and then it has a trigger on it and it has two different settings. There's a low and a high. So when you're hunting, feel out the hog, see the reacting to the light and then it has a bright mode where you can just hit it and then trying to figure out a good thermal scope for a rifle, but they're just so darn expensive. This right here, you can literally just put it in your pocket or in your sack.  And I got some hunts coming up. So let me know in the comments if you wanna see more about the gear and I'll do a more detailed video with it on my next adventure. Right now let's head out into the great outdoors itself and go set ourselves up. Some trap cans. I could literally be a spa right there. Just look at them. Little pigs, mama pigs, big pigs. Looking at heavy mudwallers right here. I mean just tracks. I gotta put a camera up here. All right, camera one set up. Got number two set. Big time game trail right here. Tons of activity. The crazy thing is I can smell them right here. I know that sounds kind of weird, but I literally can. Let me know in the comments what you think this is. It's got a fishtail. It looks like a big catfish. Super hard skin. Looks like some big old rib cage bones. It's throwing me off. It looks like fish. I've seen catfish with that thick of bones. The big bones sticking out to the side. Y'all seriously, let me know what you think that is. That is crazy. That might be one of the funniest hats I found by the lake just giving the circumstances. Lake hair don't care. The person obviously just gave up on the boat ride. He's like, you know what? Just gonna let it all fly. Wonder how many cooers, lats were on that little deal. Found me in another spot and gonna set up a camera a long ways away from where I was. There's a lot of activity going through in the bushes right here behind me. Throw down another camera over here and see what we can get. This is a big time bedding area. All up in these roots, little ditches. That's a big one right there. All right, final one set up. Now it is time to hike back. I have returned. It's always good to get out there. Just enjoy the sweet sounds and nature. A lot of sweat in this case. But not only did I put the cameras up. Some good places I think. I also got some good recalling tracks and seeing how those little pathways where the brush has been. Also just from recent rains, that's made it a lot easier. I ended up finding some wallows. I don't know how old they are, but wallows with tracks in them. The cameras are pretty spread out and I've got one more I need to put up in a little oak thicket where I saw those deer. That's all we got for today guys. You know what's next. We're gonna go check those trail cameras. Got a weird vlog today running around with so many places, but I just wanted to take you guys with me show you what's going on in life. And pretty much from here on into September, I'm not gonna be doing a whole lot of traveling. I've got a couple of trips that aren't too far away that I'm gonna be doing some hunts and different fishing trips on. But if I get that call of my mother's broken, you gotta get over here, quick. I gotta be ready. So that's why I'm not traveling out of state. Stay pretty close within a couple hours drive where I can get to the hospital. If need be, I don't wanna miss the birth of my first born baby girl. And if y'all wanna check out other stuff that's going on with that, you can check out the Lake Life family channel. I'll have it linked down below. It's kind of OSG's point of view on Lake Life around here, but also just stuff we do around the house and family stuff. Don't forget to hit that ding dong notification button so you don't miss a single episode. And I will see you on the next one.


The crisscross method of testing fuses is utilized when the circuit is generally live. However, if at all possible, you should always kill the circuit and have it locked out for safety's sake. So in this case here, we're going to be using a 208 volt system. We have three fuses, fuse A, B, C. I've set up some testing points. So we have testing point one, two, three, four, five, and six. Right now with all fuses good, we're going to analyze and see exactly how the circuit works when we put the leads on. So the first thing I want to do when I use the crisscross method is I want to make sure that voltage is all right coming in up from the top so that my voltage incoming voltage is not my problem. So we're going to take our red lead and go to point one and we'll take our black lead and go to point two. And as long as our power coming in is all right, we should read 208.  And if everything's good, I should read 208 volts. And then lastly, what I'm going to do is take my red lead and move it over to two and read from two to three. And if everything is as it should be coming in, we have 208 from two to three. So that verifies that all my lines coming in are good. So I have no problem upstream. So what we're going to do now is we're going to look at what happens to our voltage drops as we go across the fuses themselves. So here I've set up from point one to point four and I'm going to be reading the volt drop across these two points here. Now here's the thing. If this fuse is good, there's means there's continuity here, which means that this point here and this point here will be the same electrically. If that is true, there's no potential difference across this fuse, which would mean that I would have a zero volt potential. So using the volt meter in this way, one to four would read zero volts. And that would stay true for two to five as well as three to six. So you can't really go ahead and read across a fuse when you're using a live circuit. Because this point and this point, as long as they're good, are going to be the same points and you're going to have zero volt potential. Now if I look here, I've taken from point one and I've gone across to point five. Now again, if B is good, that would mean that two and five are the same point potential because it'd be like having just a wire going through there. So if that's true, what we looked at before was from one to two was 208. If this fuse is good from one to five should be 208 volts as well because points two and five are the same points electrically. So you might as well, if this fuse is good, this lead might as well be up on two. It'd be the same thing. So we have 208 volts coming in. We're going to read 208 volts like that. And the same would hold true if I went from one to six or any variation thereof. If you're reading the cross and all three fuses are good, you should read 208. So if we're crossing over here, and this is why we call it the crisscross method, if the fuse is good, it will read 208 volts. Or if we went over to six, it'd be 208 volts would tell me that C and B are both good as far as the fuses are concerned. Now let's take a look at what happens when we actually have a blown fuse. So here I've physically drawn it so that you can see that point A or sorry, fuse A is broken. You wouldn't physically see this out in the field. That's why we're using this method, but this is just to prove the point. So again, if I would read it coming across one to two is 208, one to three is 208, and two to three is 208. Then what we did was we measured one to four. And when I measured one to four, I read zero volts when the fuse was good. However, when the fuse is blown here, you notice I have a reference point here. I've got this attached to 208 volts here, and I have this attached down here. Yes, this is blown, but you notice that this is open and these contacts are open. That means that four has zero reference point. So it's not in reference to anything. So it'd be like taking this lead and sticking it up in the air, which would mean that from this point to the air, I've got a difference potential of nothing because it's not reading anything. So if I try to read my voltage across this with it blown, I'm going to read zero volts as well. When the fuse was good, I read zero volts. When the fuse is bad, I read zero volts. So we can't measure the voltage across a fuse to determine whether or not the fuse is good. We need to measure it across. And so what we're going to do now is we're going to move this black lead over to two. So I've kept my red lead on four, and I'm going from two. So we know that we tested these voltages coming in, so two has a reference voltage to it. So reading a reference voltage from that point to this point here. So when we do that, we know that there's voltage here. We know that there should be voltage there, but with this fuse blown, it has no reference as well. So we confirm that A is blown because we're trying to read from two to four. Now, if we read one to two, we should read 208. But if we read four to two, we're reading zero volts because of this blown fuse here, which in turn tells me that fuse A is blown. You could do the same thing with two to four, or sorry, three to four. You're going to get the same thing. Three to four would read zero volts as well. Let's take a look at what happens when we have another fuse blown. So let's blow fuse B. So we'll start out, we'll read across two to five. But again, that's a moot point because two and five would be either the same point electrically if this fuse was good, or because this fuse is blown, two has a reference, five has no reference, so it's going to read zero volts. So again, we have to measure across. We have to do a crisscross, so we could actually take the leads and measure from five to one, or five to three. We want to keep one lead downstream of the fuse because we want to determine if this fuse is blown. So let's move this over to three just to prove a point. So we've kept five there, and we've got our other lead going to three. So if we read two to three, we should read 208 volts, which we did earlier, because we have good power coming in. But if we see here, if this fuse was good, points two and five would be the same, so we should read 208. But with this fuse blown, there again, there's no reference at this point. So three to no reference point is going to give us zero volts, which would tell us that B is blown. We would expect if this fuse was good to read 208, but now because this fuse is blown, we're reading zero volts. And so that fuse C doesn't feel left out. Let's take a look at what happens when we blow fuse C. Again, if we go ahead and we go across here, whether this fuse is good or fuse is blown, we're going to read zero volts. So what we need to do is use the crisscross method. We're going to keep this lead on, and we're going to measure voltage across to these two points here. Before, when this voltage is good, we checked two and three. We had 208 volts coming through. If we have this point here as having a reference point, we know that there's power coming to this point, but we have a blown fuse here. Before, when it was 203 up here, it was 208. If this fuse is good, we should read 208, because this point and this point should be the same electrically, but with a blown fuse, this is open. This now has no reference point. So three and six are no longer the same, and I'm going to end up reading zero volts across there. So we've used a crisscross to get across the voltage. So that's how you use the crisscross method. Again, you'd never want to read the voltage across the fuse itself because whether the fuse is good is zero volts or if it's blown is zero volts. So that could be dangerous. So we want to make sure that you're checking all points. You want to measure voltages across the different points.


I'm Kent Larson, I direct the City Science Initiative here at the MIT Media Lab. We have a network of projects working with different cities around the world. We're now working in Humber, Taipei, Andorra, Singapore, a number of other cities. What I am finding is, although there's a big emphasis on so-called smart cities, intelligent cities, et cetera, it's not really what the mayors care about. The mayors care about jobs and they care about how efficiently they use resources. They care about quality of life. So we're developing what we think of as an evidence-based data-driven process that privileges human interaction in the city. We're building three-dimensional physical models using augmented reality to then project data visualization as well as simulation onto this physical model. The goal is not so much to make expert systems for experts, but rather to democratize access to these powerful new tools to engage all of the stakeholders in a community that need to be part of the process. So we have a physical platform allowing people to stand around and enter into a discussion of what the important issues are. For example, we're working in Humber right now to help identify housing and communities for the 40,000 refugees that are now without shelter in the city. The mayor came to us and suggested, I could do this as a top-down process, but that is not a workable scenario for this very emotional politically charged problem we have to address. We developed a platform so it can be a bottom-up process to engage members of the community who might have different political viewpoints, different ideas about how to approach this problem. We do workshops with roughly 30 people, and that face-to-face interaction is so critically important. And having access to instant information as well as the ability to try out different scenarios that we're hoping, and we fully expect, that this will lead to a level of engagement allowing the community to reach a consensus about how to proceed. Now we can use the same tool for looking at what enables innovation. The issues such as density and proximity and diversity, how to bring together a diverse group of people at a critical mass, exchanging ideas which we think is the most important aspect of innovation. Mayors all over the world are interested in innovation districts, but for the most part they don't know what actually enables innovation. We believe we can model this and put this together as a tool to allow all the stakeholders to make informed decisions about that process. Now our long-term vision with this is to create an open-source platform. We can't do everything in our group, even all the researchers at MIT couldn't put all this together. It's a very complex, challenging problem to develop the simulation algorithms and the data visualization algorithms. What we intend to do is to put this out into the world as an open-source platform, have a whole community of developers using open APIs and data commons, allowing for standards for how this could come together not only in rich cities like Hamburg or Boston, but in the developing world that don't have access to the expensive consultants. In other words, to bring state-of-the-art technology and make it accessible in a very affordable way for cities all over the world. One of the most interesting challenges is to think about new models for the rules of the city. Right now they're very primitive. We have zoning ordinances that have very simplistic rules such as setbacks and building height and prescribed uses. This is really a 19th, early 20th century concept. There's no reason why we cannot have algorithmic zoning that is responsive to changing economic conditions and cultural values. So I think in the end what we need to do is to bring together really excellent ideas about design, state-of-the-art technology and public policy. I think these are the three elements and I think eventually we can model all of this in a more integrated way.


And thank you all. Over the last two weeks, the hearts of the American people have gone out to the people of Armenia as they grappled with the earthquake disaster and its aftermath, and the world wept at the terrible magnitude of the destruction and the tremendous loss of life. Whole villages and cities virtually leveled. Great numbers of men, women, and children were trapped beneath fallen buildings in one of the worst earthquake disasters ever to occur. Tens of thousands were killed, countless numbers injured, and many others tragically missing. But no sooner had we learned of the disaster and of the great need that existed than you and so many other Americans organized to help. Rescue workers and medical teams from across the country flew to the Soviet Union where you searched for the living and gave care to those who were injured. And thanks to your immediate response and special skills, precious lives were saved. Here in Washington, the people in AID's Office of U.S. Foreign Disaster Assistance worked around the clock to coordinate the effort. And thanks to people from this country and from throughout the international community, direct assistance and desperately needed supplies were able to reach the survivors. And throughout this period, American relief organizations, churches, and the American Armenian community have produced a great humanitarian response which continues, providing all forms of material assistance to that devastated area.  And for that, I want to personally thank you on behalf of every American. Those of you who answered the appeal for help, who have assisted in the relief effort, and those who flew to the Soviet Union and sifted through the rubble, searching for life against all odds, carried with you a message from America. It was a message of peace.  So whatever language we speak, whatever country we may live in, whatever our race or religious faith, we are all one people on this earth. And in times of suffering, in the face of natural disaster, we're drawn by our common humanity to help one another, to join in a great brotherhood of man. The lesson for this season is for us to love one another, and that's something you have shown in a very real and important way. So for this, let me say thank you and God bless you all.


and welcome to display data. Hey everybody and welcome to a Sunday night desk with Lady Aida. It's me, Lady Aida. I'm at my desk with me, Mr. Lady Aida. Hello. I'm camera control. We're just hanging out doing electronics. I don't, do we have any news and updates for folks watching? No, but just to give people a little bit idea of what good progress and maybe the end of these type of milestones. We had lunch with someone who we work with at a restaurant and we talked and hung out together and was awesome. So, you know, full speed ahead in every possible way. It's been a while. There's folks have, we haven't been able to do that with some folks for well over a year. So a lot of progress happened. New York is ready to fully open. Aidaford's been shipping around the clock. Thank you so much everyone. Play some orders when you can to support. One of the only, if not only, woman owned electronics companies in the world and in New York City and full schedule this week. The only thing that's different, Scott is not on deep dive, but JP's up too, right? JP, believe so, maybe. Yeah, so we don't have Scott on a JP show.  Okay, all right, well, so this weekend, what I worked on the most was I finally got around to porting over the CISO library from Simpsons slash make file stack build to Arduino supported as we covered about a month ago. I can't get SamD chips anymore. Like they're pretty much gone for like a year or two. And so I had a big collection of boards that people saw me design that were like STEMI QTC cell boards that would let you say, you know, connect a rotary encoder over I squared C or I had this like a Neo-key one by four. And I actually started releasing some of them. And then I would have had like, you know, way more products, but all of a sudden that can't get SamD09s anymore. Well, luckily I hadn't even ordered some of those PCBs like a month ago. I kind of noticed this was happening. And so decided, okay, I'm gonna turn around and redesign these using chips that I can get because even though I liked the SamD09, I didn't have to use it in effect. I was talking with Phil. That kind of forced me to reevaluate the chips that I was using and maybe find a chip that made more sense. So an earlier desk of LaVietta, we covered in great search. We covered finding a low-cost 8-bit microcontroller that could do the job. So let's go to the computer. I'll show, I think it was this one. So I wanted to find a very low-cost 8-bit microcontroller and you can watch this video. But basically it came up with the AT Tiny 816Y. It was basically 50 cents available in QFN. It's my favorite format. Three to five volt compatible. So you can use it with three volt or five volt, which is really nice. Regulator or level shifters, because you can use it with whatever. It had ADCs. It has I-squared C peripheral, which is the most important. But also all the other things like that. Enough stuff that it's not like, it's got way more pins in an AT Tiny 85, which I wouldn't use because it definitely does not have enough pins. I need at least 12 GPIO to kind of do all the things I want. You know, I have a four rotary encoder version of this like stick with I-squared C. Four rotary encoders plus four switches. That's 12 GPIOs just for the buttons, which is gonna need Neopixel and then Address Select and then I-squared. Yeah, basically you need 24 or 28 pins easily. So the Sambio 9, again, was a wonderful chip, but I can't get it. I love it because it's very powerful. You know, it's a 48 MHz Cortex M0 with a ton of flash. I think it was like 16 or 32K of flash. And then 2K of RAM. The 2K of RAM is really sweet because it means I definitely didn't have to worry about running out of memory. This chip doesn't have as much, but it still has quite a bit. I found this nice blog post which shows the entire family of this, you know, the AT Tiny series. You know, there's the 8K, 16K, 32K. And you can see they sort of like have the same core and they sort of build up and they get more expensive and more powerful. But, you know, in the 20 pin or 24 pin, this is kind of the zone I'm in, you know, the cost here is 63 cents, here 70 cents, you know, pretty good. Basically I want the 8K version. So these four are what I'm gonna be focusing on. These have two few pins. These down here have two little RAM and this is getting a little bit more expensive. It's starting to get into the dollar range. So these four are the ones that I like. To compare them, I looked up, here is this, you know, Aviar has a full comparison of their chip series. So this is the line. So it's like, what's the difference between the 816 and the 806? Basically, do they have a DAC? That's the big change here is like some of them have an 8-bit DAC and some of them have an extra timer. And then they have Q-touch, they have a built-in capacitive touch. So basically, you know, they're almost equivalent except for this one has the Q-touch, just self-capacitive touch, basically capacitive touch without needing any other components, an extra timer and a DAC. So they're basically equivalent, you know, they also can have a little bit more RAM and they go a little bit bigger. Basically the 806 and 817 and 816 are all very similar. One is a 20-pin QFN, one I think is a 24-QFN. So unfortunately they're like, the 806 and the 816 and the 817 and the 807 are pin compatible, but the 806 and the 807 are not because they're different packages. So it's like the bigger the number, the bigger the package, the more pins. That said, you know, I'm kind of like, what's available, turns out the 817 was more available than the 816 and whatever, the price is so similar that it was like, whatever was available, I purchased from Digikey and got, and you can see that there's still plenty in stock of these chips. So luckily there is this Arduino core by Spence Cunde called MegaTiniCorn. I remember that they did a pull request to add support for their core in Bassayo. Bassayo is the Adafruit I-Squirt C and SPI layer that just makes registers and it just simplifies like bit banging and it kind of abstracts away I-Squirt C and SPI for using with sensors and devices. Having written like 100 libraries, I was kind of like, I need something to help. And I remember they did a PR. They did a core and the core supports basically all of the ATtiny series chips. And it's great because having this core means I could jump right into the code porting and like releasing it and publishing it instead of what we had to do for seesaw originally, which is here, which is at the time this was written there was no the 8168, this is like five years old. I don't think the 806 and 816 those chips didn't exist or I probably would have used them. Yes, this is like four years ago I think because the original four maybe five years ago. So, at the time, the way to do this was we to fit everything in, we didn't use Arduino, there was no Arduino core, we wrote it as a can make file with ARM GCC. It was perfectly fine. I was good enough with the SAMD chip and Dean who was working with us at the time was comfortable enough with the chip that we basically did all in this low level C. It works wonderfully, it's great, but again, we wanted to move to porting this to Arduino. So not everything, I mean, we're still gonna have the old, let's see if I can find it. So now it's called seesaw peripheral. So we still have the old repository and some things like the Cricut are still gonna use the old seesaw code even though I could port it over that the Cricut's complicated enough I don't really wanna touch it. But for the little boards like the rotary encoder that I recently released and the NeoKey iSquared C and all the other, like I designed like 12 of these boards, all of those will be reported and written in this. So kind of forced my hand. I was like, oh, eventually I'll get around to changing chips but my hand was forced by the chip shorting. So the good news is that I did a bunch of code yesterday and the day before and one of the things I thought were, there's two things I did that I thought were kind of neat. First up, the seesaw library is iSquared C to anything. So just iSquared C to GPIO or ABC. This has a DAC, so I'm gonna add DAC. My head, I have NeoPixel and down here you can barely see it, but it says PWM. So I'm gonna add rotary encoder that's missing. There's a couple of things missing. Oh, and one thing that's kind of neat about this is it has EEPROM, this chip. So we can do reprogrammel iSquared C addresses. So instead of just hard coding it, you'll be able to connect to the chip and write a custom iSquared C address which some people were asking for. So to configure it, the way we did it with the old seesaw library was to have, okay, just gonna make this a little bit bigger. So with the old seesaw library, it's done in a makefile. And the nice thing about makefiles is you have a lot of, so if you go to like boards and you go to the NeoKey QT you see here above me, I've got all the configuration. Is there an ADC in which pins? Is there a timer? Which pin is the interrupt pin? So this would be all done in a makefile with Pound Defines is how many pins are for address configuration. This one has four address configuration pins. It has NeoPixel support. So you can't have everything, everything. You do go out of memory if you try to have all this stuff on the SAM D09. And with a makefile, everyone's used to this with doing the makefiles, right? You put a Pound Define and you're done. In Arduino you cannot do this. And like 5% of the pull requests I have to close are people thinking that you can put a Pound Define in your Arduino sketch and it affects a library. That's not true. That's not how C works. You can't have a Pound Define in one file affect another file. Each file is compiled separately. So this is one of the things that I kind of was like, I opened up an issue like a decade ago asking our Arduino to maybe have a way for us to add like command line defines on the command line which is where this would actually affect the libraries that you're including but that sort of never happened for whatever reason and then people use Platform IO which does do that. That's one of the things people like about Platform IO is you can do Pound Defines. But I'm both lazy and don't want to start reintegrating all my code into Platform IO. And also I realize that a lot of people don't have that but I do want to have the ability to use Pound Defines to manage the code and all the different boards like a rotary encoder that's going to need rotary support but it won't necessarily need PWM support. So how do you turn on and off that stuff? To really reduce code size you have to do it with a Pound Define and you if death away code areas, right? That's the only way to really make sure that that code isn't compiled in. Yeah, you can not refer to it but it's complicated and you can structure your code in a way I think without it but you have to do all sorts of like weird externs and constants and I didn't want to do that. So instead what I did is it's a terrible hack but it works wonderfully is you do have your Pound Defines. So like for example, the product code which is burned into the board to let you identify it, the default I scored C address, you know, the default interrupt pin, the default address configuration pins and then you include your library header file, right? And so I just told you you can't do this and I was right, you can't do this if your code isn't a C file. However, if you write all of your code in the header file, it's fine. So all of my code is in a header file that includes other header files but there's no C files and there's no C++ files. Just like poor taste but works great and I'm all into that. So the header file is where? Because header files, if you do have a Pound Define beforehand and you have header guards, the Arduino script will include it first after your Pound Defines, you can then use the Pound Defines to as you see here, you can like only include the NeoPixel code if you have config NeoPixel turn on, right? So all of your flags, do you have debug? Okay, you can have serial prints if you're debugging all of that stuff you can do if your code is in the header file. And we've done this in a few libraries where you have weird compilation problems because our Arduino again, it's greedy. It will compile every C++ file and C file it finds whether or not that is used in your code. Platform IO has a similar issue which I don't use it but a lot of people bumped into this where Platform IO tries to pre-compile all of your files for you, which is fine. The problem is that it pre-compiles files whether or not the code in them is being accessed, right? So at least the Arduino ID doesn't compile files that the code isn't, it'll compile files but only if they're being included in your library, like if they're accessed through your code. Whereas Platform IO is like, oh, any dependency we will compile even if that dependency isn't used because it's behind a if-deaf or whatever. So we have people who are like, I'm running STM32 and I'm trying to compile this, it's compiling this AVR code by accident. Why is that happening? Eventually we figured it out.  So compilers, I don't know, we love them but they're a problem. But this header hack, again, portaste works great. I love it. It makes my life a lot easier because I can then have my example scripts use the pound-defines to determine that this is what the code that will be compiled and then go on to the seesaw board. And then another nifty thing that is always fun to do is using CI as a way to verify code size. So for all of the code I'm writing, all the different boards, I wanna make sure that it fit, again, if I can get the 806 or the 807, one has more flash than the other. Sorry, one has more pins than the other and some have the zero series is different than the one series. And so I wanna make sure that the code that I'm writing compiles clearly on all four of this family because I'm not sure which chip I'm gonna be able to get in the next year and a half. So in CI, in the Action CI, I set up the test to compile all four chips. So I compile the 817 series, all of the examples. I compile the 816 series, the 807 and then finally the 806. And I just make sure that all four of them pass. And so this is my way of, as I'm writing the code, we'll talk about this in the great search. My dev board is an 817, but I wanna make sure that when I then finally make my final board designs and I solder in an 807, which is a less capable chip, I wanna make sure that I'm able to compile and fit the code because it is getting, I mean, I'm not like hitting the limits yet. I'm at like 5K, maybe 6K, but there will be some point which I start hitting the limitations of the flash memory and the flash memory will compile to different sizes based on the core because like the one series has hardware will multiply. Maybe it handles floating points a little bit differently. I don't know. I mean, they don't have floating point units, but like because of the hardware support, the code might get more and more bloated, the smaller the chip, the sort of a side effects that the smaller the chip, the less powerful often the code gets bigger because you have to do more stuff in software that normally would be done in hardware. So let's just finish up by going to the overhead and I'll show this and we'll get to the great search. Yeah, this is the thing I was like, we should make this. I don't know, I'll make it, but I just made it today. Yeah, whatever. Okay, so here I've got, this is my Metro Mini.  Like, no, I like to use whatever people are gonna be using because it helps me quickly find workflow issues. So I'm using a Metro Mini at 32, sorry, 328. One of the things I really like about 328, I gotta say like it's an old chip, but I really like that when I hit the reset button, I don't lose the serial port. So it's like, I can reset all the time in the serial port and Arduino doesn't go away. I've got it tied over here. This is ground I squared C clock in data. So those are the, I'm connecting to my seesaw peripheral, the thing that will be driving my little rotary encoder here. And underneath here, I've got a T tiny 817 explained. So as I'll cover in the great search, you can't always get the eval board you want, but you'll always get the eval board you need. That's the Rolling Stones. I don't know if you do that. They were saying about that. It's a lot of electronics. It's true. So the 817, I can barely see it. The 817 eval board was one of the nice things about it. And one of the reasons I picked this one up is it has, it didn't come with these socket headers, which I soldered in, but they are Arduino compatible. So it was very easy for me to grab a shield PCB that I had kicking around, put it on top and made this little dev board. So this is a cute little board and it has a little programmer here. This is the actual chip, right? This is the debugger slash programmer. And then here's your USB micro-B, but I can plug this in so that you can see it's on top. Let me reset this. And then this is running a basic program that kind of tests a little bit of everything. So here we've got PWM, so you can see the LED is getting dimmer and it's brightening. So it does analog right from Arduino, it's PWM. Here's a potentiometer. I've got here, I soldered in a little JST port just so I could plug in some NeoPixels. The NeoPixels are really bright, but this analog knob, when I dim it, it will lower it. It will dim the NeoPixels or brighten them, depending on how I turn it. So of course, this is not directly controlling the NeoPixels, this potentiometer is being read over I squared C by the host, which then sends the NeoPixel brightness data over again. So this is a, you know, it's brainless. It's not doing any thinking on its own. It's just reporting over I squared C the data, right? That's what CSaw does. It is I squared C to whatever back and forth. So I have it for doing one analog read. That's another thing about this chip is it's wonderful, there's a lot of analog pins, there's a lot of PWM pins. There's, you know, it has support through Arduino for piezo, so if I press this button. You know, this is a tone, just making one tone, but of course you can play different tones. And then I've got the rotary encoder ready here. I didn't get to adding support for that because we went out to this nice lunch instead, but that's next, I'm gonna add the rotary encoder and this is gonna be an interrupt LED. But I've got that and the eProm all working and this is just, you know, sending data back and forth. Another nice thing is I can sort of set this aside, come back to it in a couple of hours and make sure it's still working, but so far so good. So this is the code, which I can post. Sorry, what I was showing it off. It's over on GitHub under Adafruit CESA peripheral.  It can easily be ported to any chip set. One of the chips that I'm going to be porting this to is the RP2040, which again does have Arduino support. That's the nice thing about having Arduino core is that we can have it with the RP2040. I have some projects where the RP2040 again has very powerful capabilities over PIO. So what can we do with I squared C to PIO conversion? We could have I squared C to DVI display. We can have I squared C to, you know, eight NeoPixels output. We can have I squared C to camera peripheral. So, you know, it's a long time coming, four years coming, but I'm glad that we finally, I was kind of forced to port the code over to Arduino. And so I'll be redesigning all these boards like this rotary encoder. You know, we have enough chips to last for a few months, but eventually those will run out. And this is a very popular board. So I'm going to redesign it. Maybe next week I'll show off my redesign.  We order them. And then also we have to design a UPDI programmer. So UPDI is the programming system for these AT tiny chips, but they did a really good job. It's asynchronous UART, which I'm loving because it means it's going to be very easy for people. If they want to reprogram these boards on the fly, you don't need a J-Link. You actually only need a serial port cable because you can use an FTDI cable to program these chips using asynchronous UART, just tie the RX and TX together. It's pretty cool. All right, any questions before we move on to? No, folks are digging it. They're digging it. It's very, it'll deep-diving today, but that's how it is. So, all right, so let's get into the great search. Where? The great search every single week brought to you by Digikey and Interfere. Thank you Digikey, Adafruit, and Digikey team up to show you Lediata's Superpower, which is find the stuff on Digikey. This week, what are you showing? Okay, this week I'm gonna show how I found the eval board because I realized getting eval boards is a lot better these days than it used to be, but you do have to do a couple little, there's a couple of tricks that I have when searching for eval boards. So let's go to the overhead real fast. I'll show you what I got.  I'm gonna show you what I got and then how I got there. So this is the dev board I just showed by prototyping, getting this design together. So let me remove this. So this is the eval board that I picked. So this is the AT Tiny 817 Explained. And I'll show you what I like about it and then I'll show you how I found it. So one of the things I like about, of course if I didn't come with these socket headers, it just came with this board. Number one thing to look for in eval board. It seems silly, but it's really important. Getting eval board that has the programmer built in. A lot of chips these days, you need to program them. And if you don't have a programmer, now you need a second thing. Now, sometimes low cost of eval boards will come with a SWD or JTAG port. There's nothing wrong with those if you happen to already have a J-Link. But a lot of times, especially for a new chipset, I didn't have the programmer. I don't have a special programmer for this. So you'll often see that there's another chip, which in this case is bigger, that happens, which is the debug interface. So that's just something to look for. Second, I'm a big fan of less is more with eval boards. I used to have an STK500 for those two people who were on the STK500. This thing was a beast. It was like a hundred bucks and it had everything. It had seven segments and it had sockets and it had an LCD. And it was like so much, so much, so much, so much. I really like, again, seeing from a socket, it was unsoddered. It had a lot of, everything was broken out. It was ready to get wired up. It has just one button and one LED. These are the only two things that are built in to it. This LED is built in. This is a user controllable and this is a button that's user controllable. But other than that, and then there's like two capacitive touch pads if you want to use capacitive touch. That's it. I love it. I don't like eval boards that are over the top.  That's their goal, right? Their goal is you use them so much that they give up their blue smoke monster. So that's another thing. Get two, always, eval boards whenever you want. Okay, so let's go to the computer. I'm going backwards. Talked about the eval board. So this is the chip that I was gonna use, the 816 or the 806. We covered this in a previous great search. So I want to find an eval board for it, but you may notice that there isn't an eval board linked from here. Sometimes there's an eval board that's linked directly, but there isn't. And if I type in 80 tiny 816, you'll see I go straight to embedded microcontrollers. If I type in 80 tiny 816, actually I didn't type this in, but what if I type in eval? No results, okay? So are you gonna cry? No, you're not gonna cry. You're gonna use your great searching power. So most chip companies do not have an eval board for every chip that they make. And that's really common because they have to focus on one device in the family. So in this case, as we have shown, this chip is part of a family, a group of chips where, and this STM is 32s are all so famous for this, right?  It's all super configurable. So you will not necessarily be able to find each configuration of that chip family available as an eval board. So in this case, what you wanna do is, first off, you can just search for, you can search the microchip site, like you go to the site of the company that makes the chip. So if I type in 80 tiny 816 eval here, it'll actually pop up 80 tiny 817 development tools. And so that, again, that's not unusual. You'll often be able to get the higher level, the 817 is a better version of that chip. It has more flash, more RAM. So that's what you're gonna find. You're gonna find like usually near the top because they want to show off all the capabilities. So for example, I like the SAMD51. The SAMD51 doesn't actually have a nice eval board or at least at the time, it didn't have a nice eval board from microchip. Instead, they had the SAMD54, which has, or the SAME54, which has ethernet and CAN, but it's otherwise almost completely identical, right? It has some extra stuff. So in this case, there are two eval boards available. So let's go back to Digikey. So now that we know what to look for, nothing you can do, as my trick is, whatever chip you're looking for, so like I want the 816 eval board, you just take a number or two off. This doesn't always work because depending on how the company's structure, they're part numbers. But in this case, you can search for like 80 tiny 8 eval and then under here, you can see that there's some evaluation boards. So of course, there's evaluation boards that might use this. In this case, none of these are available because they're actually Q-tatch, which happened to use the 80 tiny 88. Under this eval board, you'll see that, okay, sorry, under 80 tiny 8 from within here. Right, so you'll see that there is, this is interesting. So within, of course, if you want to search from within a category, don't forget, I just, I forgot to mention before, you can search from within results. I don't usually use this, but if I'm looking, if I know I want an eval board and then I want one that uses a chip, you go to this section and then you search from within this result. So now I can see that there's only 10 options. There's of course the Trinket, yay, it's like my design, with the 80 tiny 85. And then you'll see the ones that we saw before, the 817 eval board. All-MX has a 80 tiny 85, but yeah, basically there's two boards you can get. So let's open up both, one second. So there's nothing wrong with picking either of these, but tell you what I like. So again, this was the 80 tiny 817 eval board. It's got the debug interface here. I always look for that. The main chip and then a lot of breakouts, but you know, very simple design. And then over here is the pro.  You don't see anything. It's actually a double-sided board. So what, you know, this has breakouts, but they're a header pin type. And this has a little bit more measurement. It has a little bit more pins. This is the pro version. If you actually want to see what's on the board itself, you need to go to the data sheet for the eval board. And then, I guess this isn't like the most amazingly great eval board data sheet because I wish they just had a photo of the bottom.  They do have a diagram on the bottom and they show that yeah, there is this like debug interface here and like all the circuitry and it probably does like high voltage reprogramming and all that stuff. So that said, given the choice between the two, I kind of like this one more because it's simpler. But if you want, I think this has like more high voltage. It has the current measurement disconnect. So it's a little bit more, you know, this is called the pro and the other one's called the mini. If you're doing like low power stuff or you're doing something where you need the high voltage programmer, I'd probably go with the pro. But it is 40 bucks compared to this one, which is like 14 bucks, 12 bucks. So this is my winner. This is the one I like. So again, get two. And then once you've done your development, again, as I've said this before, if you're designing with a microcontroller or any chip, you pick the highest pin count, highest flash, highest RAM, build your application, your prototype within it. And then you can tick down and pick the one that will fit. So the 817 has, you know, the slightly nicer chip than the 807, it has more pins than the 806. But it's easy for you to develop on this. And then in your compiler, just select the smaller chip when you're ready to go to production and like see how small you can get your compiler to compile for. And that's the chip you can actually use in production. And of course it's, you know, people forget, you can always rework this chip. You can remove this chip off of here and solder on a smaller, less flash, less RAM version if you need to. It takes a little bit of skill, but that's one thing that I do when I'm getting near to completion of my prototype. And I'm like, well, I really, before I order PCBs, before I go into a more intense design, order some chips, hot air this off, hot air my replacement on, and then I can actually develop with like, you know, a fresh chip in the exact package and size and capabilities that I'm going to target for production. So Valboards, it is. So I got two of these and they're quite nice. I do recommend them. It's great to hear. Where in the world is that part I need? All right, quick comments more. Someone said on Reddit, there's folks that are gonna buy a Valboards to pop the chips off because of a chip shortage. Yeah, I know. Well, you laugh when it's like for development, yes. I mean, if you really just need to get your prototype developed in a Valboard, you know, a $15 Valboard could be pretty good. I mean, usually I don't go with a Valboards, but in this case, it was so cheap and so convenient. It's kind of hard to say no. Okay, what material can I use for good heat conduction and high electrical isolation in, for example, a homemade soldering iron tip or heat gun? Well, there's, you know, there's like heat sink materials. So I'd look at like what people use for padding heat sinks, because that'll be electrically isolated, but thermally conductive. Okay. Do you think the chip shortage have accelerated open silicon movement in terms of new companies getting to make assembly conductors and follow up to that? Do you think it'll bring a greater variety of components to the hands of consumers? I think that it will force companies to get a little creative. Some people are like, oh, we're gonna do more in software than hardware, but I actually disagree because a lot of the chips are unavailable are the ones that are more advanced. So in this case, I'm downgrading. I'm going from a Cortex-M0 to an 8-bit AVR, which normally, again, I wouldn't do. I would have just stuck with the chip that I know that I have the core, you know, all the code working for, but I was forced to, and it's not a bad thing. Like it's working out. There's some benefits I really do like that has EEPROM, which the Cortex-M0 doesn't. I like that it's three in five, but compatible. That's kind of handy. And is the AVR core, you know, I grew up on AVR core. So I really know this core and I'm very comfortable with it. I'm very familiar with it. And I kind of like seeing how powerful they've gotten this chip. My little prediction is, I think folks will choose something like the RP2040 instead of a CMD because they can get the RP2040. So good timing Raspberry Pi Foundation and the chip release because more folks are gonna probably try it. They had really good timing. Obviously it wasn't on purpose, but they were very lucky. Next up, what is the probability of a collision when using iSquared-C chip setup having heavy iSquared-C traffic and also in the project using iSquared-C directly to the main chip, if that makes sense? iSquared-C doesn't collide. It's a polite bus platform. So as long as you have only one controller, if you have like, you know, what's called multi-master multiple controllers, I think it can get a little bit funky, but if you only have one controller, multiple peripherals, you can have very busy traffic. Like for this demo where I have the Neopixels going, it's very heavy traffic. And so to get better response, I bumped the speed up to 400 kilohertz and this chip is another nice thing. It can easily do one megahertz iSquared-C, no problem. But you won't have collisions, but you'll have slower responses. It'll take longer for you to be able to get to the bus. But almost all iSquared-C bus controllers will wait politely until the bus is free to put the, you know, to respond. Right, because it's all address. Like you're not gonna have, you have to have the controller send the request. Everything is controller-based. Like there's no device that's out of nowhere suddenly sending. There's only one controller. So you'll have slower responses because like everything is waiting until it gets its turn, but you're never gonna have a collision. It's not like Ethernet, which is a collision-based protocol. All right, and that is guest lady Aida. All right, thanks everybody. Bye everybody. See you during the week. Thank you once again. Bye bye. Have a great week.