WEBVTT - TechStuff Plays with Microcontrollers

0:00:00.280 --> 0:00:02.840
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.160 --> 0:00:09.160
<v Speaker 1>It's ready, are you? Didn't touch? With technology? With tech

0:00:09.200 --> 0:00:17.560
<v Speaker 1>Stuff from how stuff flix dot com. Hello there, everyone,

0:00:17.600 --> 0:00:19.880
<v Speaker 1>and welcome to tech Stuff. My name is Chris Poulette

0:00:19.880 --> 0:00:22.160
<v Speaker 1>and I am an editor at how Stuff works dot com.

0:00:22.160 --> 0:00:26.200
<v Speaker 1>Sitting across from me, as always, is senior writer Jonathan Strickland.

0:00:26.360 --> 0:00:30.720
<v Speaker 1>Hey there, all right, today I wanted to take control

0:00:31.000 --> 0:00:33.960
<v Speaker 1>of the podcast. This is different from any other week

0:00:33.960 --> 0:00:38.120
<v Speaker 1>how us. Yeah, we'll see now I'm singing Janet Jackson

0:00:38.200 --> 0:00:40.960
<v Speaker 1>in my head. That's how it's different from every other week. Yeah,

0:00:41.000 --> 0:00:44.360
<v Speaker 1>we were going through some other songs before we started

0:00:44.400 --> 0:00:46.640
<v Speaker 1>the podcast. It was it was kind of a loopy morning.

0:00:46.640 --> 0:00:48.880
<v Speaker 1>But today we wanted to talk about something that's not loopy,

0:00:48.960 --> 0:00:52.240
<v Speaker 1>although you can have a loop in the programming for it.

0:00:52.840 --> 0:00:57.200
<v Speaker 1>It is a micro controller. We've actually touched on these

0:00:57.240 --> 0:00:59.880
<v Speaker 1>in the past, well a segment of these, because we've

0:01:00.000 --> 0:01:02.720
<v Speaker 1>talked about the Ardueno, which is a kind of micro controller.

0:01:02.760 --> 0:01:05.960
<v Speaker 1>But Jonathan said, why don't we take a step back

0:01:06.240 --> 0:01:08.520
<v Speaker 1>and look at them as a whole. Yeah, we actually

0:01:08.520 --> 0:01:11.400
<v Speaker 1>had some people ask us about micro controllers. We even

0:01:11.400 --> 0:01:13.639
<v Speaker 1>had one person to say, could you explain the difference

0:01:13.640 --> 0:01:17.760
<v Speaker 1>between a micro controller and a microprocessor? And uh, and

0:01:17.760 --> 0:01:22.360
<v Speaker 1>and really the distinction is not black and white. There

0:01:22.400 --> 0:01:26.119
<v Speaker 1>are sort of black and silver. I'm just kidding. It's

0:01:26.120 --> 0:01:29.479
<v Speaker 1>also green in some places. Yeah, now there's um, there's

0:01:29.520 --> 0:01:34.039
<v Speaker 1>a there's certain characteristics that micro controller has, and if

0:01:34.040 --> 0:01:35.720
<v Speaker 1>it has enough of them, that's when we tend to

0:01:35.720 --> 0:01:38.560
<v Speaker 1>call it a micro controller versus a microprocessor. Now, in general,

0:01:39.200 --> 0:01:46.839
<v Speaker 1>a microprocessor tends to be a general purpose component. UM. Basically,

0:01:47.400 --> 0:01:51.440
<v Speaker 1>when most people talk about a microprocessor, they're speaking primarily

0:01:51.440 --> 0:01:53.480
<v Speaker 1>of the chip that does a lot of the computing

0:01:54.000 --> 0:01:57.000
<v Speaker 1>central process and unit is a very that's that's a

0:01:57.040 --> 0:01:59.240
<v Speaker 1>type of microprocessor. That's what I think of when I

0:01:59.240 --> 0:02:03.800
<v Speaker 1>think micropross UM. And there is a processor as part

0:02:03.840 --> 0:02:07.280
<v Speaker 1>of a micro controller. But a micro controller is a

0:02:07.400 --> 0:02:10.360
<v Speaker 1>very very tiny computer. UM. What doesn't have to be

0:02:10.440 --> 0:02:14.280
<v Speaker 1>very very tiny, but it is basically a computer on

0:02:14.320 --> 0:02:18.680
<v Speaker 1>a board. UM. So it would have the board, which

0:02:18.720 --> 0:02:21.040
<v Speaker 1>is the green I was referring to before, the circuit board,

0:02:21.200 --> 0:02:24.120
<v Speaker 1>and it would have a processor sawdered into it. But

0:02:24.160 --> 0:02:26.880
<v Speaker 1>it also might have other inputs and outputs on it,

0:02:27.320 --> 0:02:31.240
<v Speaker 1>maybe an USB output that's wired in and uh, a

0:02:31.280 --> 0:02:33.600
<v Speaker 1>couple of LEDs for example. It could be it could

0:02:33.600 --> 0:02:35.320
<v Speaker 1>be a lot of different things, but usually it's a

0:02:35.400 --> 0:02:39.160
<v Speaker 1>general purpose or i'm sorry, a specific purpose that the

0:02:39.200 --> 0:02:42.320
<v Speaker 1>micro controller is designed to do. And so you find

0:02:42.360 --> 0:02:47.040
<v Speaker 1>them in all kinds of things ovens, toasters, cars, microwaves,

0:02:47.560 --> 0:02:50.160
<v Speaker 1>um and you know, it is a computer, but it

0:02:50.280 --> 0:02:52.200
<v Speaker 1>is it's not like the kind of computer that sits

0:02:52.200 --> 0:02:55.240
<v Speaker 1>in your desktop, right. It's a very specific use. So

0:02:55.480 --> 0:02:57.000
<v Speaker 1>we know we've talked about these and things like we

0:02:57.080 --> 0:03:01.040
<v Speaker 1>had our our podcast about microwavest about a little bit

0:03:01.120 --> 0:03:04.440
<v Speaker 1>on that. But yeah, these are these are computers that

0:03:04.520 --> 0:03:09.119
<v Speaker 1>have very specific uses and because they have these narrow parameters,

0:03:09.120 --> 0:03:12.400
<v Speaker 1>they don't need to be general purpose, so they tend

0:03:12.440 --> 0:03:16.600
<v Speaker 1>to have a fairly limited number of of uses that

0:03:16.639 --> 0:03:20.360
<v Speaker 1>they can they can actually be UM employed for otherwise,

0:03:21.000 --> 0:03:23.440
<v Speaker 1>you know, it's outside the realm of their scope. So

0:03:24.320 --> 0:03:28.000
<v Speaker 1>here are some general guidelines as to what makes a

0:03:28.080 --> 0:03:31.120
<v Speaker 1>micro controller, and I'm pulling these from our article on

0:03:31.160 --> 0:03:35.320
<v Speaker 1>how micro controllers work, which is an extensive article. It

0:03:35.480 --> 0:03:37.440
<v Speaker 1>is it is one of our I mean, and it

0:03:37.480 --> 0:03:41.120
<v Speaker 1>goes into detail if you want technical details about micro controllers.

0:03:41.520 --> 0:03:44.280
<v Speaker 1>It's an excellent resource, and it was written by Marshall Brain,

0:03:44.320 --> 0:03:47.000
<v Speaker 1>who was the founder of how Stuff Works dot com.

0:03:47.000 --> 0:03:49.880
<v Speaker 1>In fact, he uh he took a specific kind of

0:03:49.960 --> 0:03:53.320
<v Speaker 1>micro controller and talks about programming and how that you

0:03:53.440 --> 0:03:55.920
<v Speaker 1>how you would get into that and um, you know,

0:03:56.160 --> 0:03:59.880
<v Speaker 1>it depends on the micro controller how you would program one.

0:04:00.080 --> 0:04:02.000
<v Speaker 1>So we're not going to get into that much detail.

0:04:02.080 --> 0:04:04.720
<v Speaker 1>We're really going to touch on, uh, the uses of

0:04:04.800 --> 0:04:08.000
<v Speaker 1>micro controllers in general and and what goes into you know,

0:04:08.080 --> 0:04:10.520
<v Speaker 1>the makeup of them. Yeah, we might talk a little

0:04:10.520 --> 0:04:13.119
<v Speaker 1>bit excellent, Yeah, we'll talk a little bit about programming,

0:04:13.200 --> 0:04:16.640
<v Speaker 1>but we're going to take a very general approach because otherwise,

0:04:16.800 --> 0:04:19.200
<v Speaker 1>you know, you have to do a specific podcast over

0:04:19.240 --> 0:04:21.520
<v Speaker 1>each one and that would just be ridiculous. But but

0:04:22.360 --> 0:04:25.040
<v Speaker 1>Marshall went into detail on that specific kind of micro

0:04:25.080 --> 0:04:28.200
<v Speaker 1>controller and which is a programmed in basic Yes, which

0:04:28.240 --> 0:04:30.520
<v Speaker 1>is kind of cool because I don't usually typically think

0:04:30.560 --> 0:04:33.400
<v Speaker 1>of that as a micro controller language. Right, So let's

0:04:33.520 --> 0:04:36.279
<v Speaker 1>let's get down to the basic features of what a

0:04:36.320 --> 0:04:40.000
<v Speaker 1>micro controller is. So as as Marshall pointed out, they

0:04:40.080 --> 0:04:44.320
<v Speaker 1>are typically embedded in something else. So a micro controller

0:04:44.400 --> 0:04:48.039
<v Speaker 1>is not its own thing, it is part of something else.

0:04:48.080 --> 0:04:52.040
<v Speaker 1>So for an example, the microwave. The micro controller is

0:04:52.120 --> 0:04:55.919
<v Speaker 1>what allows the commands you put into the microwave to

0:04:55.960 --> 0:05:01.200
<v Speaker 1>be transferred into action within the microwave itself. Then they

0:05:01.240 --> 0:05:06.080
<v Speaker 1>are dedicated to a specific task or specific program, and

0:05:06.120 --> 0:05:10.040
<v Speaker 1>that program tends to be stored and read only memory

0:05:10.040 --> 0:05:13.320
<v Speaker 1>and does not change. So, in other words, it's something

0:05:13.600 --> 0:05:16.960
<v Speaker 1>that you're going to do over and over again, you

0:05:17.000 --> 0:05:19.760
<v Speaker 1>know it's it's it's dedicated to a task that is

0:05:19.839 --> 0:05:23.600
<v Speaker 1>repeatable and is not changing after you've done it once.

0:05:24.279 --> 0:05:27.880
<v Speaker 1>So like a calculator and you you use a calculator

0:05:27.920 --> 0:05:31.880
<v Speaker 1>to add five to five, that's never going to change

0:05:32.839 --> 0:05:34.920
<v Speaker 1>unless the laws of the universe change, in which case

0:05:35.040 --> 0:05:39.359
<v Speaker 1>or you know, some some sort of crazy, wacky parallel

0:05:39.440 --> 0:05:44.080
<v Speaker 1>universe thing happens. Yeah, remind me to get a new calculator, right,

0:05:44.400 --> 0:05:48.599
<v Speaker 1>so then you have. They also tend to be very efficient.

0:05:48.720 --> 0:05:52.680
<v Speaker 1>They tend to not require a lot of power to operate.

0:05:53.040 --> 0:05:56.520
<v Speaker 1>So for example, you know, you might have a full

0:05:56.520 --> 0:05:59.440
<v Speaker 1>computer that has its own onboard battery, but you tend

0:05:59.520 --> 0:06:01.760
<v Speaker 1>to keep bit plugged in because it drains a lot

0:06:01.760 --> 0:06:05.080
<v Speaker 1>of power. Right, Well, micro controllers do not require so

0:06:05.160 --> 0:06:07.920
<v Speaker 1>much power, so they can be battery operated and last

0:06:07.960 --> 0:06:10.119
<v Speaker 1>for a long time and they're only pulling power whenever

0:06:10.160 --> 0:06:13.560
<v Speaker 1>they're in use. So that's why you could have a

0:06:13.560 --> 0:06:15.880
<v Speaker 1>calculator that's battery operated and you don't have to change

0:06:15.920 --> 0:06:19.000
<v Speaker 1>the batteries out that frequently. And of course you have

0:06:19.040 --> 0:06:21.440
<v Speaker 1>one that has also the little solar panels on it,

0:06:21.560 --> 0:06:24.120
<v Speaker 1>you may not ever have to change the batteries, depending

0:06:24.120 --> 0:06:26.680
<v Speaker 1>on you know, the the environment you are in when

0:06:26.720 --> 0:06:31.760
<v Speaker 1>you are using it. UH. It has a dedicated input

0:06:32.000 --> 0:06:36.280
<v Speaker 1>device and usually, but not always, has some sort of

0:06:36.320 --> 0:06:41.040
<v Speaker 1>display to show the output for the device. And UH

0:06:42.800 --> 0:06:46.160
<v Speaker 1>normally you have this display there when you are first

0:06:46.240 --> 0:06:50.920
<v Speaker 1>building or programming your micro controller, and it's in order

0:06:50.960 --> 0:06:52.880
<v Speaker 1>for you to make sure that the program you have

0:06:52.960 --> 0:06:56.240
<v Speaker 1>built is operating properly before you start to go into

0:06:56.279 --> 0:06:59.799
<v Speaker 1>like a manufacturing phase and you start implementing it into

0:06:59.839 --> 0:07:02.240
<v Speaker 1>a product. So you would want to be able to

0:07:02.279 --> 0:07:07.560
<v Speaker 1>test this extensively before you went into full production, otherwise

0:07:07.600 --> 0:07:10.760
<v Speaker 1>you could end up producing a line of of things

0:07:10.840 --> 0:07:14.120
<v Speaker 1>that are flawed because there was some line of code

0:07:14.160 --> 0:07:16.600
<v Speaker 1>that you left out, or there was an extra character

0:07:16.680 --> 0:07:19.080
<v Speaker 1>or something. And now when you add five to five

0:07:19.600 --> 0:07:22.240
<v Speaker 1>you get cake. Like I said, I need a new

0:07:22.280 --> 0:07:29.000
<v Speaker 1>calculator cake. Now, the the use of microwave in this

0:07:29.040 --> 0:07:32.920
<v Speaker 1>case is a good example because um, you know, in

0:07:33.080 --> 0:07:36.600
<v Speaker 1>the in the chips baked into them, not baked into

0:07:36.600 --> 0:07:39.880
<v Speaker 1>soldered into I'm just tripping all over stuff today, UM,

0:07:39.960 --> 0:07:43.440
<v Speaker 1>soldered into the board inside the micro controller in the microwave. UM,

0:07:43.480 --> 0:07:46.000
<v Speaker 1>it's got instructions on you know what each of those

0:07:46.000 --> 0:07:50.160
<v Speaker 1>digits does. On the keypad, it's got UM instructions on

0:07:50.160 --> 0:07:52.280
<v Speaker 1>on what to do when you press the coffee button

0:07:52.360 --> 0:07:56.000
<v Speaker 1>versus the the popcorn button. UM. So many of these

0:07:56.000 --> 0:08:00.520
<v Speaker 1>microwaves have these dedicated buttons now UM. But it basically

0:08:00.600 --> 0:08:03.040
<v Speaker 1>the instructions are, hey, if he presses the pizza button,

0:08:03.160 --> 0:08:06.640
<v Speaker 1>that means put the microwave on high for seventy five

0:08:06.720 --> 0:08:11.040
<v Speaker 1>seconds and that's it, you know, start. So it has

0:08:11.040 --> 0:08:13.120
<v Speaker 1>those instructions in there, and it also has a display

0:08:13.720 --> 0:08:17.360
<v Speaker 1>UM instructions, so it shows what is going on to

0:08:17.560 --> 0:08:19.920
<v Speaker 1>the user, so that he or she has an idea

0:08:20.080 --> 0:08:22.000
<v Speaker 1>of how long it's going to be cooked for and

0:08:22.200 --> 0:08:24.920
<v Speaker 1>what power. But you know, it doesn't have to do

0:08:25.000 --> 0:08:29.640
<v Speaker 1>things like tuna radio or um uh try to find

0:08:29.680 --> 0:08:32.560
<v Speaker 1>Facebook or something like that, or or do WiFi, because

0:08:32.880 --> 0:08:34.760
<v Speaker 1>it's not a program to do that, so they can

0:08:34.800 --> 0:08:37.480
<v Speaker 1>they can mass produce these boards with the ROMs already

0:08:37.480 --> 0:08:39.679
<v Speaker 1>in them and assemble it as part of the microwave,

0:08:39.880 --> 0:08:42.400
<v Speaker 1>and every microwave should work that comes off the line

0:08:42.440 --> 0:08:44.800
<v Speaker 1>with that board, and it should work the same, right

0:08:44.960 --> 0:08:49.079
<v Speaker 1>and UH, and it doesn't have to be a manual

0:08:49.880 --> 0:08:54.320
<v Speaker 1>input for a micro controller to produce an output. So,

0:08:54.440 --> 0:08:57.160
<v Speaker 1>for example, the micro controllers you have in your car

0:08:57.800 --> 0:09:01.440
<v Speaker 1>could be connected to various sensors in your car, and

0:09:01.520 --> 0:09:04.040
<v Speaker 1>what happens is the sensor sends an input to the

0:09:04.040 --> 0:09:08.080
<v Speaker 1>micro controller, which then UH creates the appropriate output for

0:09:08.120 --> 0:09:10.600
<v Speaker 1>whatever that might be. And it might be that it

0:09:10.720 --> 0:09:13.480
<v Speaker 1>changes the settings of something else it's in your car,

0:09:14.080 --> 0:09:15.960
<v Speaker 1>or it might be that sends a signal so that

0:09:16.000 --> 0:09:18.560
<v Speaker 1>the little check engine light pops up on your on

0:09:18.640 --> 0:09:21.120
<v Speaker 1>your dashboard, so that you then have to figure out

0:09:21.200 --> 0:09:25.080
<v Speaker 1>what the heck has gone wrong. So for example, in

0:09:25.160 --> 0:09:27.640
<v Speaker 1>my house, you figure out where you put the electrical

0:09:27.679 --> 0:09:31.320
<v Speaker 1>tape so that you can tape over the check engine like, well,

0:09:31.600 --> 0:09:35.839
<v Speaker 1>problem solved. Well that anybody who's actually watched when they

0:09:36.600 --> 0:09:39.960
<v Speaker 1>do the diagnostics on a car, And this would be

0:09:40.000 --> 0:09:42.400
<v Speaker 1>good for the folks over car stuff to talk about

0:09:42.440 --> 0:09:45.000
<v Speaker 1>but um in more detail. But you know, there is

0:09:45.040 --> 0:09:48.360
<v Speaker 1>a board that they plug into so that the mechanic

0:09:48.440 --> 0:09:50.880
<v Speaker 1>can plug in and it will read what the micro

0:09:50.920 --> 0:09:54.160
<v Speaker 1>controllers inside the car, and there are several for different functions.

0:09:54.760 --> 0:09:56.960
<v Speaker 1>Um you know will say, hey, the check engine line

0:09:57.040 --> 0:10:01.120
<v Speaker 1>is on because you know error code five seven five

0:10:01.240 --> 0:10:02.800
<v Speaker 1>one two, and they look it up in a book

0:10:02.800 --> 0:10:04.520
<v Speaker 1>and they go, oh, well, that means that the e

0:10:04.679 --> 0:10:06.920
<v Speaker 1>g R valve needs replacing or yeah, or there's a

0:10:07.000 --> 0:10:11.439
<v Speaker 1>belt that is not working properly. Yeah, and then it

0:10:11.520 --> 0:10:13.760
<v Speaker 1>turns out. Just in case you're wondering, there are apps

0:10:13.800 --> 0:10:17.280
<v Speaker 1>out there for smartphones where you can get a proprietary

0:10:17.400 --> 0:10:20.360
<v Speaker 1>cable that will hook up into a smartphone and you

0:10:20.480 --> 0:10:23.440
<v Speaker 1>hook the other end of the cable to your your

0:10:24.000 --> 0:10:27.079
<v Speaker 1>cars computer and it will actually tell you what the

0:10:27.160 --> 0:10:28.679
<v Speaker 1>code is. Now, you may still have to go and

0:10:28.760 --> 0:10:31.920
<v Speaker 1>look up what the code means, because not all of

0:10:32.000 --> 0:10:34.800
<v Speaker 1>these apps have a complete database on what every single

0:10:34.880 --> 0:10:38.319
<v Speaker 1>code for every single model of vehicle translates to. But

0:10:38.400 --> 0:10:40.160
<v Speaker 1>at least then you can have an idea of what's

0:10:40.160 --> 0:10:44.040
<v Speaker 1>actually wrong. Which that's for that, you know, if I'm

0:10:44.040 --> 0:10:46.480
<v Speaker 1>gonna do it yourself. Yeah, we're getting off topic of it,

0:10:46.600 --> 0:10:49.080
<v Speaker 1>but the idea being that you will you'll be able

0:10:49.080 --> 0:10:51.240
<v Speaker 1>to diagnose what's wrong with your car. So that way,

0:10:51.280 --> 0:10:53.480
<v Speaker 1>when you take it into a mechanic, you can be

0:10:53.600 --> 0:10:58.400
<v Speaker 1>reasonably sure that whatever the mechanics telling you is either

0:10:58.720 --> 0:11:01.319
<v Speaker 1>true or not true, because there's always that worry, you know,

0:11:01.400 --> 0:11:03.640
<v Speaker 1>when cars get more and more sophisticated and becomes more

0:11:03.640 --> 0:11:05.719
<v Speaker 1>and more difficult to understand what's going on with them.

0:11:06.120 --> 0:11:08.920
<v Speaker 1>You never really know if what the mechanics telling you

0:11:09.240 --> 0:11:11.600
<v Speaker 1>is actually what's wrong with your car, or maybe they're

0:11:11.640 --> 0:11:16.160
<v Speaker 1>adding onto it. Yeah. Well, of course not every mechanic

0:11:16.360 --> 0:11:21.079
<v Speaker 1>is untrustworthy, but sometimes there there there's some good mechanics

0:11:21.160 --> 0:11:22.880
<v Speaker 1>out there. But that's the thing is that because you

0:11:23.000 --> 0:11:25.559
<v Speaker 1>don't know, you have to entirely on them exactly. I

0:11:25.679 --> 0:11:29.679
<v Speaker 1>don't think you're so off topic, Jonathan, because, uh, you

0:11:29.720 --> 0:11:34.760
<v Speaker 1>know that that really indicates how pervasive micro controllers really are. Um.

0:11:35.280 --> 0:11:37.839
<v Speaker 1>You know, people talk about the computers in their cars

0:11:38.040 --> 0:11:39.839
<v Speaker 1>or you'll see. Uh. I have a toaster that I

0:11:39.880 --> 0:11:41.680
<v Speaker 1>thought was kind of funny a few years ago because

0:11:41.679 --> 0:11:45.760
<v Speaker 1>it said, you know that it it had a microprocessor inside,

0:11:45.840 --> 0:11:47.680
<v Speaker 1>and I was thinking, really, is that a selling point

0:11:47.760 --> 0:11:51.520
<v Speaker 1>for my toaster? Um. But yeah, I mean, these these

0:11:51.600 --> 0:11:54.559
<v Speaker 1>devices are in just about anything that we plug in

0:11:54.720 --> 0:11:56.880
<v Speaker 1>these days, and some things that we don't, like your cars,

0:11:57.200 --> 0:12:00.719
<v Speaker 1>and um, you know. The the good the advantage to

0:12:00.880 --> 0:12:03.319
<v Speaker 1>that is that, you know, it does make these devices

0:12:03.360 --> 0:12:05.800
<v Speaker 1>more sophisticated. It gives us more control in some cases,

0:12:05.840 --> 0:12:09.319
<v Speaker 1>it gives us more um options as far as what

0:12:09.480 --> 0:12:12.199
<v Speaker 1>we can do with all the I mean this gigantic

0:12:12.320 --> 0:12:15.480
<v Speaker 1>range of devices. It also provides more points to break

0:12:15.559 --> 0:12:21.000
<v Speaker 1>down because you know, typically the more complex a thing is,

0:12:21.559 --> 0:12:25.480
<v Speaker 1>the more chances it has to bust. This is something

0:12:25.600 --> 0:12:31.000
<v Speaker 1>we yes, well, systems have a tendency. The more the

0:12:31.080 --> 0:12:34.720
<v Speaker 1>more organized and complex a system, the greater the tendency

0:12:34.840 --> 0:12:37.000
<v Speaker 1>is for it to slowly break down into the simplest

0:12:37.040 --> 0:12:40.559
<v Speaker 1>form right right, And that's you know that. I think

0:12:40.600 --> 0:12:45.959
<v Speaker 1>that is why it's interesting to look at micro controllers because, um,

0:12:46.160 --> 0:12:48.160
<v Speaker 1>it gives you a sense of what's going on behind

0:12:48.240 --> 0:12:51.040
<v Speaker 1>the scenes and what may or may not be at

0:12:51.240 --> 0:12:54.200
<v Speaker 1>at play. Um. But it's good that micro controllers can

0:12:54.240 --> 0:12:56.079
<v Speaker 1>help us track these things down to when it's not

0:12:56.280 --> 0:12:59.959
<v Speaker 1>the micro controller itself that's the fault. Um. But yeah,

0:13:00.040 --> 0:13:02.760
<v Speaker 1>typically these are not things that we program ourselves like

0:13:02.880 --> 0:13:05.360
<v Speaker 1>you program a computer. You might learn Java or Ruby

0:13:05.480 --> 0:13:08.720
<v Speaker 1>or Python to go program a computer. Most of these

0:13:08.800 --> 0:13:11.320
<v Speaker 1>things are behind the scenes that ROMs are soldered onto

0:13:11.320 --> 0:13:14.920
<v Speaker 1>the boards. We never touched them. Yeah, now that doesn't

0:13:14.960 --> 0:13:19.160
<v Speaker 1>mean you can't, but right, but they're they're specific types

0:13:19.200 --> 0:13:21.120
<v Speaker 1>of micro controllers you would have to get in order

0:13:21.160 --> 0:13:24.040
<v Speaker 1>to be able to to program on top of them.

0:13:24.240 --> 0:13:30.280
<v Speaker 1>I'm going to overclock my toaster like cold toast way well,

0:13:30.480 --> 0:13:34.480
<v Speaker 1>you know, never toasts anymore, reduced the resistance. Uh, it's

0:13:34.520 --> 0:13:38.280
<v Speaker 1>pretty amazing. Now the there are a couple of other

0:13:38.440 --> 0:13:41.079
<v Speaker 1>little things I want to talk about, other features that

0:13:41.200 --> 0:13:45.200
<v Speaker 1>could possibly uh mark something as a micro controller. They

0:13:45.280 --> 0:13:49.040
<v Speaker 1>tend to be small, They tend to be fairly cheap,

0:13:49.600 --> 0:13:51.480
<v Speaker 1>which is important. I mean, that's one of the reasons

0:13:51.520 --> 0:13:53.720
<v Speaker 1>why you want a micro controller. You want something that's

0:13:53.720 --> 0:13:56.679
<v Speaker 1>focused and narrow because you don't have to worry about

0:13:56.760 --> 0:13:59.920
<v Speaker 1>building in all these other features, and that helps red

0:14:00.080 --> 0:14:03.280
<v Speaker 1>is the cost, which, of course you then turn around

0:14:03.480 --> 0:14:07.679
<v Speaker 1>and you can you can competitively priced whatever your product is,

0:14:08.120 --> 0:14:11.960
<v Speaker 1>whether it's a toaster or a car. And then they

0:14:12.040 --> 0:14:17.680
<v Speaker 1>also often but not always, are made to be pretty

0:14:17.760 --> 0:14:21.200
<v Speaker 1>tough to work in a variety of conditions because obviously,

0:14:21.240 --> 0:14:24.520
<v Speaker 1>if you have a car, the operating conditions inside a

0:14:24.560 --> 0:14:28.160
<v Speaker 1>car tend to be pretty warm. Engines. Engines give off

0:14:28.160 --> 0:14:31.360
<v Speaker 1>a lot of heat, um, and so you need to

0:14:31.480 --> 0:14:34.480
<v Speaker 1>have electronics that can withstand that heat because, as we

0:14:34.600 --> 0:14:42.560
<v Speaker 1>all know, heat plus electronics often equal sad faith. Yes. Well,

0:14:42.800 --> 0:14:45.720
<v Speaker 1>and in the cases of things like uh, now that

0:14:45.800 --> 0:14:49.360
<v Speaker 1>we have these these wireless handheld game controllers and things

0:14:49.440 --> 0:14:53.200
<v Speaker 1>like that, um, you know, sometimes they tend to fly

0:14:53.400 --> 0:14:56.480
<v Speaker 1>around the room when people get a little bit over zealous,

0:14:57.040 --> 0:14:59.560
<v Speaker 1>you know, things like that. You don't want it to

0:15:00.040 --> 0:15:02.520
<v Speaker 1>uh the components to be exposed, because if you do,

0:15:02.720 --> 0:15:06.280
<v Speaker 1>then they're gonna break. Yeah. Yeah, And then you might

0:15:06.320 --> 0:15:10.600
<v Speaker 1>want to know generally how powerful these micro controllers are. Well,

0:15:10.640 --> 0:15:13.240
<v Speaker 1>they don't need to be terribly powerful, and so a

0:15:13.320 --> 0:15:15.640
<v Speaker 1>lot of them, yeah, a lot of them are have

0:15:15.920 --> 0:15:20.320
<v Speaker 1>have some incredibly bare bones specs. Now, one of the

0:15:20.360 --> 0:15:22.880
<v Speaker 1>ones that Marshall wrote about was he said, like, if

0:15:22.920 --> 0:15:25.400
<v Speaker 1>you were to take a low end micro controller chips,

0:15:25.440 --> 0:15:27.840
<v Speaker 1>so this is not the state of the art biting means,

0:15:28.360 --> 0:15:31.480
<v Speaker 1>it would have around it could have around a thousand

0:15:31.560 --> 0:15:35.120
<v Speaker 1>bytes of read only memory and twenty bites of RAM

0:15:35.440 --> 0:15:39.880
<v Speaker 1>on the chip and then eight input output pins. And

0:15:40.160 --> 0:15:43.760
<v Speaker 1>so you know, if you're buying a whole bunch of these,

0:15:43.920 --> 0:15:47.840
<v Speaker 1>they'd be pretty cheap because they're they're not very sophisticated. Um,

0:15:48.520 --> 0:15:51.200
<v Speaker 1>Whereas if you were to get a micro processor, then

0:15:51.320 --> 0:15:53.560
<v Speaker 1>you would have to spend more money because you're going

0:15:53.600 --> 0:15:55.800
<v Speaker 1>to be packing a lot more components, a lot more

0:15:56.160 --> 0:16:01.000
<v Speaker 1>features onto the same size chip. You could certainly build

0:16:01.040 --> 0:16:03.840
<v Speaker 1>one of these yourself. Um. There are plenty of places

0:16:03.920 --> 0:16:06.160
<v Speaker 1>where you can get the chips and boards and other

0:16:06.240 --> 0:16:10.160
<v Speaker 1>components where um you could do you could essentially build

0:16:11.200 --> 0:16:13.800
<v Speaker 1>a micro controller to take over any kind of project

0:16:13.920 --> 0:16:17.320
<v Speaker 1>like this that you wanted to undertake. UM. And you'll

0:16:17.320 --> 0:16:20.280
<v Speaker 1>see that these the processes that you can buy are

0:16:20.520 --> 0:16:24.640
<v Speaker 1>you know, they're fairly inexpensive and they are not designed

0:16:24.720 --> 0:16:28.080
<v Speaker 1>to handle that kind of instruction set um. But what

0:16:28.320 --> 0:16:31.240
<v Speaker 1>what's really cool about that is that you can customize

0:16:31.320 --> 0:16:34.440
<v Speaker 1>a micro controller to do whatever it is that you

0:16:34.880 --> 0:16:37.720
<v Speaker 1>want to do, provided that you have the programming expertise

0:16:37.800 --> 0:16:39.840
<v Speaker 1>to do it. Right now, so you may remember, we

0:16:39.960 --> 0:16:44.520
<v Speaker 1>did an episode about logic gates while back now. Logic

0:16:44.600 --> 0:16:47.640
<v Speaker 1>gates are what allow you to control the flow of

0:16:47.840 --> 0:16:49.840
<v Speaker 1>electrons in such a way, so that you can have

0:16:50.040 --> 0:16:55.560
<v Speaker 1>a meaningful output depending upon particular types of input. And uh,

0:16:56.040 --> 0:16:59.080
<v Speaker 1>what these micro controllers do is they provide you the

0:16:59.240 --> 0:17:05.159
<v Speaker 1>opportunity to build gates in a software environment as opposed

0:17:05.160 --> 0:17:07.960
<v Speaker 1>to a hardware environment. So in other words, you could

0:17:08.640 --> 0:17:12.000
<v Speaker 1>accomplish the same thing that a micro controller does by

0:17:12.160 --> 0:17:16.199
<v Speaker 1>hard wiring things together. But that would make the components

0:17:16.480 --> 0:17:19.639
<v Speaker 1>enormous by comparison, right, because you would have all these

0:17:19.680 --> 0:17:22.919
<v Speaker 1>different wires and all these different components that that were

0:17:22.960 --> 0:17:25.840
<v Speaker 1>connected together, so that let's say you push a button

0:17:26.320 --> 0:17:28.639
<v Speaker 1>and you want this one particular light to come on,

0:17:29.280 --> 0:17:31.200
<v Speaker 1>but not any of these other lights to come on,

0:17:31.560 --> 0:17:33.280
<v Speaker 1>because those lights should only come on if you push

0:17:33.320 --> 0:17:36.879
<v Speaker 1>another button. Well, all the wires you would need to

0:17:37.040 --> 0:17:40.720
<v Speaker 1>put this entire system together might be pretty cumbersome, and

0:17:40.840 --> 0:17:42.680
<v Speaker 1>it might be that, you know, you could not fit

0:17:42.760 --> 0:17:45.119
<v Speaker 1>this in a very small package. And in fact, we

0:17:45.200 --> 0:17:47.440
<v Speaker 1>see this if we look at the history of electronics,

0:17:47.520 --> 0:17:50.560
<v Speaker 1>you'll see that the older the electronics are, in general,

0:17:50.760 --> 0:17:55.359
<v Speaker 1>the larger the the particular version of whatever it is

0:17:55.440 --> 0:17:59.400
<v Speaker 1>you're looking at was. So, for example, the earliest computers

0:17:59.640 --> 0:18:03.800
<v Speaker 1>took up sometimes an entire floor of a building, because

0:18:04.240 --> 0:18:08.240
<v Speaker 1>you know, you had to accomplish with basic electronic parts

0:18:08.320 --> 0:18:11.920
<v Speaker 1>what we can do with chips today. So a micro controller,

0:18:12.000 --> 0:18:14.080
<v Speaker 1>what that allows you to do with this read only memory,

0:18:14.200 --> 0:18:18.720
<v Speaker 1>that's where you can imprint on that a program that

0:18:19.400 --> 0:18:24.639
<v Speaker 1>through software creates a virtual series of logic gates so

0:18:24.880 --> 0:18:29.119
<v Speaker 1>that depending upon the inputs that the chip receives, it

0:18:29.240 --> 0:18:34.280
<v Speaker 1>will give out a specific type of output. So you

0:18:34.359 --> 0:18:38.200
<v Speaker 1>don't have to hardwire stuff as much with a micro controller,

0:18:38.280 --> 0:18:40.600
<v Speaker 1>although there is still hardwiring because you do have to

0:18:41.040 --> 0:18:44.800
<v Speaker 1>you know, you do have to actually connect inputs to

0:18:45.119 --> 0:18:48.639
<v Speaker 1>those those input pens, those input output pins, and you

0:18:48.720 --> 0:18:50.800
<v Speaker 1>have to connect the output to whatever it is that

0:18:51.000 --> 0:18:53.399
<v Speaker 1>you are you know, using as an output. Often it

0:18:53.480 --> 0:18:56.160
<v Speaker 1>tends to be a little l c D or LED

0:18:56.359 --> 0:18:59.560
<v Speaker 1>screen when you're at least when you're first programming it,

0:18:59.800 --> 0:19:01.600
<v Speaker 1>so that you can make sure that you're getting the

0:19:01.680 --> 0:19:05.760
<v Speaker 1>response that you want. Uh, you know, there is still that,

0:19:06.000 --> 0:19:08.920
<v Speaker 1>but the majority of the work comes from building out

0:19:09.000 --> 0:19:15.119
<v Speaker 1>the logic within the program itself. Now as yeah, and

0:19:15.320 --> 0:19:17.720
<v Speaker 1>and it it really is programming. It really is saying

0:19:18.480 --> 0:19:22.280
<v Speaker 1>for this instance, when this happens, this is what needs

0:19:22.359 --> 0:19:25.399
<v Speaker 1>to happen as a result. That's the basic idea of

0:19:25.440 --> 0:19:31.800
<v Speaker 1>a program, right and given this, given this instance, this output. Yeah,

0:19:31.800 --> 0:19:33.920
<v Speaker 1>and I think it's it's fair to say. And I haven't.

0:19:34.080 --> 0:19:36.600
<v Speaker 1>I'll be honest, I haven't. As much as I want

0:19:36.680 --> 0:19:40.640
<v Speaker 1>to get into, uh some basic hacking, I haven't really

0:19:41.000 --> 0:19:44.959
<v Speaker 1>worked with any microprocessors yet A sorry micro controller, I've

0:19:44.960 --> 0:19:48.000
<v Speaker 1>worked with either one of them. Frankly, um, I'm going

0:19:48.080 --> 0:19:50.200
<v Speaker 1>to trip over everything I say today. I'm just gonna

0:19:50.200 --> 0:19:52.200
<v Speaker 1>stop talking. But what I was gonna say is that,

0:19:53.040 --> 0:19:56.600
<v Speaker 1>you know, from many things, many people think of programming

0:19:56.760 --> 0:20:00.800
<v Speaker 1>as you know, egad, it's programming that's not for me,

0:20:01.119 --> 0:20:05.440
<v Speaker 1>and you know, really programming is for anyone. But if

0:20:05.480 --> 0:20:09.520
<v Speaker 1>you are concerned about that, you shouldn't be as far

0:20:09.560 --> 0:20:13.160
<v Speaker 1>as micro controllers are concerned, because we're again talking about

0:20:13.240 --> 0:20:17.639
<v Speaker 1>some very simple things. Um. You know, literally, if somebody

0:20:17.680 --> 0:20:20.760
<v Speaker 1>pushes this button, then you want to do that, and

0:20:20.840 --> 0:20:23.560
<v Speaker 1>if they don't, don't do it. So you know, it's

0:20:23.600 --> 0:20:26.200
<v Speaker 1>not we're not talking about lines and lines and lines

0:20:26.240 --> 0:20:28.240
<v Speaker 1>of code. You're not writing a new operating system for

0:20:28.400 --> 0:20:33.200
<v Speaker 1>a desktop computer. You're writing a very simple, uh set

0:20:33.240 --> 0:20:37.080
<v Speaker 1>of commands to a very simple computer, right, especially since

0:20:37.160 --> 0:20:38.520
<v Speaker 1>you know you've got to keep in mind, these micro

0:20:38.600 --> 0:20:42.000
<v Speaker 1>controllers have very little memory on board. They can't hold

0:20:42.440 --> 0:20:44.359
<v Speaker 1>lines and lines and lines of code. What were we

0:20:44.400 --> 0:20:47.560
<v Speaker 1>talking about again? Yeah? Uh. In fact, the one that

0:20:47.880 --> 0:20:51.280
<v Speaker 1>that Marshall reads about in how micro controllers Work, the

0:20:51.359 --> 0:20:54.439
<v Speaker 1>basic stamp. He explains that it can hold about seventy

0:20:54.520 --> 0:20:58.160
<v Speaker 1>five lines of code. So you have to make sure

0:20:58.280 --> 0:21:02.600
<v Speaker 1>that your program is very succinct, that it's compact, that

0:21:02.760 --> 0:21:05.040
<v Speaker 1>you're not taking up lines and lines and lines to

0:21:05.080 --> 0:21:08.920
<v Speaker 1>accomplish wherever the goal is. So uh, you know, by

0:21:09.200 --> 0:21:14.000
<v Speaker 1>by necessity you are kept to a pretty small amount

0:21:14.160 --> 0:21:16.800
<v Speaker 1>of coding, which if you are just getting into coding,

0:21:16.880 --> 0:21:18.440
<v Speaker 1>might be a great thing. It might be, you know,

0:21:18.520 --> 0:21:22.720
<v Speaker 1>to teach yourself how to think in a sequential way,

0:21:23.240 --> 0:21:26.359
<v Speaker 1>the way a machine processes information. I was about the

0:21:26.400 --> 0:21:29.240
<v Speaker 1>way the machine thinks, but really thinking is well, it's

0:21:29.320 --> 0:21:32.680
<v Speaker 1>not quite the right word thinking in quotes. We like

0:21:32.800 --> 0:21:34.840
<v Speaker 1>to to say that the machine is thinking when you

0:21:34.880 --> 0:21:37.720
<v Speaker 1>see the the hour glass or the spinning beach ball.

0:21:37.840 --> 0:21:40.920
<v Speaker 1>But yeah, it's really just processing data. It's just it's

0:21:41.000 --> 0:21:44.200
<v Speaker 1>going through whatever the data is that's coming into it

0:21:44.600 --> 0:21:49.639
<v Speaker 1>and saying, uh, what's the right response to this? I

0:21:49.760 --> 0:21:55.000
<v Speaker 1>got it our glass? Yeah, Well, and and uh that's

0:21:55.240 --> 0:21:57.119
<v Speaker 1>that's sort of what I was getting at. If this is,

0:21:57.200 --> 0:22:01.520
<v Speaker 1>if um, you're interested in get into hacking. And I

0:22:01.600 --> 0:22:04.000
<v Speaker 1>mean that in the the classical sense, not in the

0:22:04.240 --> 0:22:08.000
<v Speaker 1>we're going to break into government computers and take over

0:22:08.080 --> 0:22:11.560
<v Speaker 1>the world sense. Um. You know, a micro controller. Working

0:22:11.600 --> 0:22:15.280
<v Speaker 1>with a micro controller might be a good UM experiment

0:22:15.560 --> 0:22:17.320
<v Speaker 1>because then it would give you something that you could

0:22:17.560 --> 0:22:21.119
<v Speaker 1>physically that you could work with, UM maybe come up

0:22:21.160 --> 0:22:24.639
<v Speaker 1>with your own experiment or your own UM component for

0:22:25.000 --> 0:22:29.439
<v Speaker 1>doing something cool. And it doesn't require an extensive amount

0:22:29.440 --> 0:22:32.239
<v Speaker 1>of programming to make it work. UM, so it might

0:22:32.280 --> 0:22:34.200
<v Speaker 1>be it might be a fun project for somebody who's

0:22:34.280 --> 0:22:38.360
<v Speaker 1>just getting into programming. Yeah, so uh yeah, I would

0:22:38.440 --> 0:22:43.439
<v Speaker 1>recommend anyone who is really interested in learning about programming

0:22:43.520 --> 0:22:46.840
<v Speaker 1>micro controllers and what they can do go to the

0:22:47.440 --> 0:22:50.240
<v Speaker 1>how micro controllers work article first of all, so that

0:22:50.359 --> 0:22:55.200
<v Speaker 1>you can get a basic understanding of the way that

0:22:55.359 --> 0:23:00.720
<v Speaker 1>you would design a micro controller, uh circuit really or

0:23:01.240 --> 0:23:05.840
<v Speaker 1>a component. And then you can their instructions on how

0:23:05.920 --> 0:23:10.399
<v Speaker 1>to build a digital clock with a micro controller and

0:23:10.560 --> 0:23:14.440
<v Speaker 1>also a digital thermometer, so that way you can actually

0:23:14.920 --> 0:23:18.560
<v Speaker 1>learn different things that you can do with the same

0:23:18.800 --> 0:23:23.639
<v Speaker 1>basic component um. And again, these are both very specific

0:23:23.840 --> 0:23:28.159
<v Speaker 1>use cases. So your digital thermometer isn't suddenly going to

0:23:28.200 --> 0:23:31.200
<v Speaker 1>be able to play pac Man, you know, it's it's again,

0:23:31.280 --> 0:23:36.080
<v Speaker 1>it's a dedicated UH task that it's you know, designed for,

0:23:36.240 --> 0:23:40.640
<v Speaker 1>and that's it. So I I do recommend checking it out.

0:23:40.760 --> 0:23:43.160
<v Speaker 1>It is a good way to sort of cut your

0:23:43.200 --> 0:23:47.119
<v Speaker 1>teeth on on programming. Again, this one being in the

0:23:47.200 --> 0:23:50.560
<v Speaker 1>Basic language, but there are of course other languages you

0:23:50.600 --> 0:23:53.680
<v Speaker 1>can learn as well. That tends to be pretty easy

0:23:53.760 --> 0:23:57.160
<v Speaker 1>to learn if you know anything about programming already, even

0:23:57.200 --> 0:24:00.439
<v Speaker 1>if you've never used Basic before. Because it's Basic, I mean,

0:24:00.520 --> 0:24:04.080
<v Speaker 1>it was the language itself was designed as a teaching tool.

0:24:04.680 --> 0:24:10.120
<v Speaker 1>It wasn't necessarily intended to be a fully fledged programming

0:24:10.200 --> 0:24:14.880
<v Speaker 1>language to build out sophisticated UH software. It was meant

0:24:14.960 --> 0:24:19.159
<v Speaker 1>to teach people how to think in that way so

0:24:19.320 --> 0:24:22.560
<v Speaker 1>that then they could move on and graduate two more complex,

0:24:23.480 --> 0:24:27.480
<v Speaker 1>more sophisticated programming languages. We did an episode about programming

0:24:27.520 --> 0:24:29.920
<v Speaker 1>languages to where we kind of talked about that. Yeah. Yeah,

0:24:30.040 --> 0:24:32.920
<v Speaker 1>and both Jonathan and I have fiddled around with Basic

0:24:33.000 --> 0:24:35.320
<v Speaker 1>in the past, different versions of Basic. But yeah, yeah,

0:24:35.960 --> 0:24:38.760
<v Speaker 1>I did Apple Basic. Yeah, I did Amiga basics. So

0:24:39.119 --> 0:24:41.280
<v Speaker 1>there you go. So that's you know that and that

0:24:41.880 --> 0:24:47.119
<v Speaker 1>friends is where the split began. It was only compounded

0:24:47.480 --> 0:24:52.080
<v Speaker 1>by Chris's refusal to watch the movie Jaws. He's never

0:24:52.119 --> 0:24:54.240
<v Speaker 1>going to get over that. It's until I watched the movie.

0:24:54.320 --> 0:24:56.359
<v Speaker 1>You just see those splits, and you know how the

0:24:57.000 --> 0:25:01.480
<v Speaker 1>how the chasm widens further and further with every every episode.

0:25:02.320 --> 0:25:06.600
<v Speaker 1>It's amazing we've gotten through four hundred without hitting each other.

0:25:06.720 --> 0:25:08.520
<v Speaker 1>I think we're gonna need a bigger podcast. I think

0:25:08.560 --> 0:25:11.680
<v Speaker 1>we Hey, nice, nice, he's quoting something he's never seen before.

0:25:11.720 --> 0:25:12.959
<v Speaker 1>It doesn't make me want to hit him at all.

0:25:13.240 --> 0:25:16.320
<v Speaker 1>All right, So anyway, did you have anything else you

0:25:16.320 --> 0:25:19.040
<v Speaker 1>want to say about micro controllers? Um? No, not really,

0:25:19.119 --> 0:25:22.399
<v Speaker 1>but it's that's one of those unheralded things. I mean,

0:25:22.440 --> 0:25:24.720
<v Speaker 1>people just don't talk about. When we talk about computers,

0:25:24.760 --> 0:25:28.280
<v Speaker 1>we usually talk about those machines that we use every day.

0:25:28.320 --> 0:25:30.960
<v Speaker 1>But micro controllers are those machines that we use every

0:25:31.040 --> 0:25:34.479
<v Speaker 1>day and just pick up them as being computers. They

0:25:34.520 --> 0:25:37.800
<v Speaker 1>really are. Yeah, every just about every kind of electronic

0:25:37.800 --> 0:25:40.800
<v Speaker 1>so you can imagine, has some form of micro controller,

0:25:40.840 --> 0:25:45.280
<v Speaker 1>and it often multiple micro controllers. So yeah, very important

0:25:45.320 --> 0:25:47.159
<v Speaker 1>piece of electronics, and if we did not have them

0:25:47.200 --> 0:25:50.480
<v Speaker 1>and we were only relying upon microprocessors, everything would be

0:25:51.280 --> 0:25:56.200
<v Speaker 1>way more expensive or far more primitive. For example, your

0:25:56.240 --> 0:25:59.320
<v Speaker 1>remote control might be the closest kid to the TV.

0:26:00.800 --> 0:26:03.000
<v Speaker 1>That's what it was in my household until we got

0:26:03.760 --> 0:26:06.400
<v Speaker 1>That's why I'm laughing. I remember that, turning the dial

0:26:06.520 --> 0:26:12.080
<v Speaker 1>three spaces. Yeah, Paul Um never never really spoke quite

0:26:12.160 --> 0:26:15.879
<v Speaker 1>like that. Yeah. Anyway, all right, so guys, if you

0:26:16.000 --> 0:26:19.000
<v Speaker 1>have any suggestions for future topics that we can tackle

0:26:19.119 --> 0:26:22.160
<v Speaker 1>here on this podcast, let us know. You can say

0:26:22.240 --> 0:26:25.560
<v Speaker 1>us an email or address tech Stuff at Discovery dot com,

0:26:26.160 --> 0:26:29.000
<v Speaker 1>or let us know on Facebook or Twitter. Are handle

0:26:29.080 --> 0:26:32.359
<v Speaker 1>there is tech stuff? H. S. W and Chris and

0:26:32.440 --> 0:26:36.560
<v Speaker 1>I will talk to you again really soon for more

0:26:36.600 --> 0:26:38.919
<v Speaker 1>on this and thousands of other topics because it has

0:26:38.960 --> 0:26:45.520
<v Speaker 1>staff works dot com brought to you by the reinvented

0:26:45.600 --> 0:26:48.159
<v Speaker 1>two thousand twelve camera. It's ready, are you