WEBVTT

00:00:00.000 --> 00:00:05.060
<v Chris Gammell>This is The Amp Hour Podcast, released July 9th, 2018.

00:00:07.800 --> 00:00:13.460
<v Chris Gammell>Episode 398, an interview with Felix Russo.

00:00:30.000 --> 00:00:33.540
<v Chris Gammell>Welcome to The Amp Hour. I'm Chris Gammell of Contextual Electronics.

00:00:33.960 --> 00:00:36.360
<v Chris Gammell>And this is Felix Russo of lowpowerlab.com.

00:00:36.520 --> 00:00:37.540
<v Chris Gammell>Welcome, Felix. How are you doing?

00:00:37.920 --> 00:00:39.060
<v Chris Gammell>Thank you. I'm good. How are you?

00:00:39.360 --> 00:00:42.400
<v Chris Gammell>I'm great, man. It's good to talk to you. It's good to talk to you again, actually.

00:00:42.400 --> 00:00:49.580
<v Chris Gammell>I was thinking, you and I had talked in Detroit, where you live, or nearby where you live, back in 2014, I think it was, right?

00:00:49.800 --> 00:00:52.680
<v Chris Gammell>Yep. It was a local meetup, and I met you there.

00:00:53.140 --> 00:01:00.680
<v Chris Gammell>Yeah. I was telling someone about that. I was saying that that's the party where I determined that Detroit is the Wild West of the party scene.

00:01:00.940 --> 00:01:05.640
<v Chris Gammell>I remember sitting outside at 2 in the morning. It was, I forget, the hackerspace downtown.

00:01:05.820 --> 00:01:13.500
<v Chris Gammell>We're outside the hackerspace. A art car pulled up in the shape of a dragon that breathed fire, and we were thumping dubstep at 2 in the morning with no one around.

00:01:13.920 --> 00:01:15.360
<v Chris Gammell>I was like, oh, this is weird.

00:01:16.080 --> 00:01:18.720
<v Dave Jones>Yep. I've never been in that part of the town, actually.

00:01:19.180 --> 00:01:19.360
<v Dave Jones>Yeah.

00:01:19.360 --> 00:01:27.200
<v Dave Jones>And I don't remember the place, but I went there because I was just trying to get a little social and see what's going on.

00:01:27.320 --> 00:01:36.440
<v Dave Jones>But usually, I don't get too much of a chance to go up at meetouts like that just because of everything else and going on.

00:01:37.000 --> 00:01:40.920
<v Chris Gammell>Well, you got a business. You got a family. So, your business is called Low Power Lab. Is that right?

00:01:40.940 --> 00:01:41.180
<v Chris Gammell>Yes.

00:01:41.420 --> 00:01:41.620
<v Chris Gammell>Yes.

00:01:41.760 --> 00:01:45.380
<v Chris Gammell>Cool. And so, are you in the outskirts of Detroit? Where are you actually located?

00:01:46.020 --> 00:01:47.180
<v Chris Gammell>I'm in Canton, Michigan.

00:01:47.500 --> 00:01:48.540
<v Chris Gammell>Oh. Is that?

00:01:49.340 --> 00:01:50.100
<v Chris Gammell>It's a suburb.

00:01:50.600 --> 00:01:53.040
<v Chris Gammell>Okay. Canton, you said? C-A-N-T-O-N?

00:01:53.360 --> 00:01:53.660
<v Chris Gammell>Yes.

00:01:54.140 --> 00:01:58.200
<v Chris Gammell>Cool. That's great. Yeah. There's tons. I mean, that's the thing. Detroit really spreads, too.

00:01:58.940 --> 00:01:59.620
<v Chris Gammell>Yep. Definitely.

00:01:59.740 --> 00:02:08.080
<v Chris Gammell>Yeah. Cool. So, let's kind of walk through your story. So, how did you get to where you are, and what is Low Power Lab?

00:02:08.080 --> 00:02:15.220
<v Dave Jones>Well, I guess we should go back to college years, maybe.

00:02:16.000 --> 00:02:17.280
<v Dave Jones>Okay. Where was college?

00:02:17.540 --> 00:02:19.680
<v Dave Jones>College was at ASU, Arizona State.

00:02:20.080 --> 00:02:20.700
<v Dave Jones>Nice. Okay.

00:02:20.700 --> 00:02:34.460
<v Dave Jones>So, I started computer science, and right about second year or third year, I decided that I already know how to program.

00:02:34.800 --> 00:02:36.460
<v Dave Jones>Why am I doing this?

00:02:36.460 --> 00:02:57.100
<v Dave Jones>So, I felt like I could do something else, and I thought, why not try computer engineering? So, I went for that, and that was probably one of the best decisions that I made, because it opened up a whole lot of new doors for me, and the world of electronics and understanding electrical engineering and all that.

00:02:57.100 --> 00:03:01.000
<v Dave Jones>In fact, for a long time, as a kid, I used to play with wires.

00:03:01.440 --> 00:03:07.700
<v Chris Gammell>I was going to ask, yeah. So, college was not your first introduction to hardware, but that was the formal kind of thing?

00:03:08.420 --> 00:03:21.680
<v Dave Jones>Yes. That was the formal introduction to electronics. So, like I said, as a kid, I used to play with light bulbs and LEDs and wires and batteries, but to that extent was my exposure at that time.

00:03:21.680 --> 00:03:33.780
<v Dave Jones>I even had a soldering iron, actually, and I used to solder wires and desolder some old electronics through whole stuff, but I didn't really understand how electronics works.

00:03:34.720 --> 00:03:36.100
<v Chris Gammell>Most days, I still feel like I don't.

00:03:37.520 --> 00:03:38.280
<v Chris Gammell>Don't we all?

00:03:38.680 --> 00:03:39.280
<v Dave Jones>Right. Yeah.

00:03:39.420 --> 00:03:39.840
<v Dave Jones>Yes.

00:03:40.260 --> 00:03:40.880
<v Dave Jones>I think so.

00:03:40.880 --> 00:03:58.360
<v Dave Jones>So, go fast forward, back to college here. You know, I thought, since I already know how to program, I could benefit from actually learning something new and, you know, learning about electronics, electrical engineering, all that.

00:03:58.360 --> 00:04:21.020
<v Dave Jones>So, computer engineering, which is sort of a hybrid between computer science and computer engineering or electrical engineering, exposes you to both those worlds and you get a chance to learn how to program and get really deep down into the computer, you know, computer architecture, logic design, and all those low-level things.

00:04:21.020 --> 00:04:27.680
<v Chris Gammell>I always think about people doing like FPGA stuff. A lot of the people that I knew that were CE degrees ended up in FPGA fields.

00:04:27.680 --> 00:04:43.480
<v Dave Jones>Yeah. In both of these degrees, you actually get a chance to take the others' core classes as selectives, which actually did. But usually, the computer science people don't really dip too much into the EE side.

00:04:43.540 --> 00:04:47.300
<v Dave Jones>Yeah. So, you were programming for a long time before that or what?

00:04:47.300 --> 00:05:04.720
<v Dave Jones>Yeah. So, I actually grew up in Romania and over there in high school, the profile of the curriculum was mathematics, physics, and computer science or informatics as they called it there.

00:05:04.720 --> 00:05:25.580
<v Dave Jones>So, we learned Pascal and C++. Not too much of the advanced stuff in C++, but the languages were a means to solve problems in math or to do backtracking to solve chess problems and do fractals and all kinds of crazy stuff.

00:05:25.780 --> 00:05:26.940
<v Chris Gammell>Yeah. Nerdy math stuff. It's great.

00:05:26.940 --> 00:05:27.940
<v Chris Gammell>Yeah. That's awesome.

00:05:27.940 --> 00:05:40.860
<v Dave Jones>Yeah. So, not too much into the language structures and that, but it taught us how to think in programmatic terms and how to approach problems programmatically.

00:05:41.400 --> 00:05:44.640
<v Chris Gammell>What made you end up going from Romania to Arizona State?

00:05:44.640 --> 00:05:59.060
<v Dave Jones>Well, I was all set up to go there to the university. So, I was planning to do that, but the opportunity came to come here and study here. So, I took the chance and here I am.

00:05:59.140 --> 00:06:09.340
<v Chris Gammell>Yeah. That's great, man. Yeah. Cool. So, okay. So, you're a computer engineer now. Leave the womb of academia and then what?

00:06:09.340 --> 00:06:31.720
<v Dave Jones>Well, then after college, I moved from Arizona here in Michigan. I got married and well, that's why I moved. And I spent about 11 years in the corporate world of software engineering. So, I worked as a software engineer. But in the meantime, I did start a little bar lab.

00:06:32.420 --> 00:06:36.100
<v Chris Gammell>Detroit, Detroit, Detroit. What do they do in Detroit? Was it automotive perhaps?

00:06:36.100 --> 00:06:37.280
<v Chris Gammell>It was not automotive.

00:06:37.740 --> 00:06:39.580
<v Chris Gammell>Really? Wow. They do other stuff in Detroit.

00:06:39.600 --> 00:06:40.560
<v Chris Gammell>Yeah. It seems like.

00:06:41.040 --> 00:06:45.560
<v Chris Gammell>Yeah. That's cool. Okay. So, like industrial, like Midwestern type stuff or what?

00:06:45.800 --> 00:06:51.260
<v Dave Jones>It was actually property tax assessment and taxation.

00:06:51.260 --> 00:06:51.380
<v Dave Jones>Oh, wow. Okay.

00:06:51.380 --> 00:06:53.760
<v Dave Jones>And yeah, it was a larger corporation.

00:06:54.480 --> 00:06:59.900
<v Chris Gammell>Yeah. Okay. So, pretty much, you know, not even electronics focused then.

00:07:00.260 --> 00:07:00.660
<v Chris Gammell>No, not at all.

00:07:00.660 --> 00:07:01.960
<v Chris Gammell>But still software focused and.

00:07:02.300 --> 00:07:03.940
<v Dave Jones>Yeah. Software focused very much so.

00:07:03.940 --> 00:07:09.220
<v Chris Gammell>Great. So, what brought you back to the electronics world then? I mean, did it ever stop or what?

00:07:09.720 --> 00:07:18.460
<v Dave Jones>Well, sometime after I started working for that company, probably a couple of years into it, one of my colleagues there, we started chatting about electronics.

00:07:18.460 --> 00:07:23.500
<v Dave Jones>And he had started his own company doing some audio video stuff.

00:07:23.640 --> 00:07:26.920
<v Dave Jones>And he had given me some challenges.

00:07:26.920 --> 00:07:36.700
<v Dave Jones>And that's how I actually got back into, you know, what I learned in college, getting back to Arduino, the basics.

00:07:37.300 --> 00:07:41.780
<v Dave Jones>You know, college doesn't actually teach you how to do a lot of things that I do now.

00:07:42.020 --> 00:07:42.780
<v Dave Jones>Yeah, right.

00:07:42.840 --> 00:07:43.780
<v Dave Jones>Because a bunch.

00:07:44.140 --> 00:07:45.100
<v Dave Jones>Manufacturing side of things.

00:07:45.520 --> 00:07:46.820
<v Dave Jones>The hard hands-on type stuff.

00:07:46.980 --> 00:07:52.720
<v Dave Jones>Exactly. You know, most of that is self-taught, basically, if you get into one of these things.

00:07:52.720 --> 00:08:00.100
<v Dave Jones>But, you know, having been given those challenges, I was motivated to actually do something.

00:08:00.500 --> 00:08:03.260
<v Dave Jones>So, I actually built something for him.

00:08:03.800 --> 00:08:10.260
<v Dave Jones>And that's how I, you know, ended up reading a whole lot more about Arduino and, you know, what's trending.

00:08:10.680 --> 00:08:15.520
<v Dave Jones>And I wanted to get into home automation really badly.

00:08:16.020 --> 00:08:18.180
<v Chris Gammell>And it sounds like you got back in on a dare.

00:08:18.360 --> 00:08:19.000
<v Chris Gammell>Is that right?

00:08:19.000 --> 00:08:19.440
<v Chris Gammell>Yeah.

00:08:21.340 --> 00:08:25.360
<v Dave Jones>So, you know, at that time, I actually bought a house.

00:08:25.560 --> 00:08:26.740
<v Dave Jones>So, we moved into a house.

00:08:26.860 --> 00:08:33.560
<v Dave Jones>And I started thinking about how can I not only monitor but also control things in the house.

00:08:33.620 --> 00:08:35.680
<v Dave Jones>So, that's how I looked at home automation.

00:08:37.060 --> 00:08:42.200
<v Dave Jones>So, back then, home automation and IoT were becoming trendy.

00:08:42.640 --> 00:08:45.600
<v Dave Jones>And IoT was not even a term back then.

00:08:45.600 --> 00:08:47.700
<v Chris Gammell>Give us a timeline for a reference here.

00:08:47.700 --> 00:08:49.000
<v Chris Gammell>What about time is this?

00:08:49.180 --> 00:08:52.380
<v Chris Gammell>Probably 2011, 2012-ish.

00:08:53.000 --> 00:08:53.160
<v Chris Gammell>Okay.

00:08:53.440 --> 00:08:53.560
<v Chris Gammell>Yeah.

00:08:53.560 --> 00:08:55.200
<v Chris Gammell>So, IoT was just entering the scene.

00:08:55.700 --> 00:08:58.260
<v Chris Gammell>And I'm sure Dave and I were making fun of the term at the time.

00:08:58.420 --> 00:08:58.740
<v Chris Gammell>Oh, yeah.

00:08:58.780 --> 00:08:59.180
<v Chris Gammell>Me too.

00:08:59.380 --> 00:08:59.720
<v Chris Gammell>I mean...

00:08:59.720 --> 00:09:00.700
<v Dave Jones>We still are, I suppose.

00:09:01.100 --> 00:09:02.900
<v Dave Jones>Unfortunately, we're stuck with that term.

00:09:03.140 --> 00:09:06.040
<v Dave Jones>I'm not sure how many people actually like it.

00:09:06.160 --> 00:09:09.740
<v Dave Jones>But, you know, even large corporations actually use it these days.

00:09:09.880 --> 00:09:10.880
<v Dave Jones>So, yeah.

00:09:10.900 --> 00:09:11.580
<v Dave Jones>We're stuck with it.

00:09:11.580 --> 00:09:18.600
<v Chris Gammell>I don't know if I've ever said it on the show, but I've actually realized that the term IoT, and this is how I've come to accept it.

00:09:18.760 --> 00:09:19.920
<v Chris Gammell>It actually means money.

00:09:20.620 --> 00:09:27.140
<v Chris Gammell>So, when a company says, we want to invest in IoT, it's saying, we want to give you money for electronics.

00:09:27.720 --> 00:09:28.420
<v Chris Gammell>I'm like, oh, okay.

00:09:28.760 --> 00:09:29.000
<v Chris Gammell>Yeah.

00:09:29.120 --> 00:09:29.280
<v Chris Gammell>Yeah.

00:09:29.380 --> 00:09:30.700
<v Chris Gammell>I got some IoT for you.

00:09:33.260 --> 00:09:33.580
<v Chris Gammell>Cool.

00:09:33.700 --> 00:09:33.880
<v Chris Gammell>Yeah.

00:09:33.880 --> 00:09:34.200
<v Chris Gammell>Whatever.

00:09:34.300 --> 00:09:34.620
<v Chris Gammell>I don't care.

00:09:34.820 --> 00:09:35.540
<v Chris Gammell>Call it whatever you want.

00:09:37.520 --> 00:09:37.840
<v Chris Gammell>Yeah.

00:09:37.940 --> 00:09:38.100
<v Chris Gammell>All right.

00:09:38.100 --> 00:09:38.460
<v Chris Gammell>That's cool.

00:09:38.560 --> 00:09:38.840
<v Chris Gammell>So, yeah.

00:09:38.960 --> 00:09:39.400
<v Chris Gammell>So, that's good.

00:09:39.460 --> 00:09:39.700
<v Chris Gammell>That's good.

00:09:39.780 --> 00:09:41.900
<v Chris Gammell>So, you were bought into it, though.

00:09:42.260 --> 00:09:42.940
<v Chris Gammell>And that's...

00:09:42.940 --> 00:09:44.040
<v Chris Gammell>So, that's about the...

00:09:44.040 --> 00:09:45.200
<v Chris Gammell>You and I met in 2014.

00:09:45.380 --> 00:09:47.740
<v Chris Gammell>So, you had started a couple years before you and I met.

00:09:47.740 --> 00:09:47.840
<v Chris Gammell>Yeah.

00:09:47.840 --> 00:09:50.440
<v Dave Jones>I probably put my site up in 2012.

00:09:51.180 --> 00:09:51.380
<v Dave Jones>Okay.

00:09:51.380 --> 00:09:59.060
<v Dave Jones>That's when I started experimenting with, you know, hand assembly of SMD components.

00:09:59.480 --> 00:10:07.300
<v Dave Jones>I came up with a Motino, which I designed to be small, yet breadboard friendly.

00:10:08.520 --> 00:10:14.540
<v Dave Jones>But I wanted it small enough to be able to fit it in, you know, tiny places.

00:10:15.300 --> 00:10:19.660
<v Dave Jones>I had a vision for, you know, light switches and small sensors.

00:10:19.660 --> 00:10:25.240
<v Dave Jones>One of the first things I made was a monitor for my mailbox.

00:10:25.680 --> 00:10:28.740
<v Dave Jones>So, it can tell me when the mailbox opens.

00:10:28.820 --> 00:10:29.640
<v Dave Jones>It can alert me.

00:10:30.200 --> 00:10:31.560
<v Dave Jones>And, of course, all this is wireless.

00:10:31.960 --> 00:10:39.440
<v Dave Jones>So, unfortunately, I don't have luxury to rewire my house to make it all wired for anything, right?

00:10:39.520 --> 00:10:41.660
<v Dave Jones>And nobody has, you know, when you have a house, that's it.

00:10:41.680 --> 00:10:45.100
<v Chris Gammell>Even if you did, you wouldn't want to dig a trench in the front yard to get out to the mailbox, right?

00:10:45.140 --> 00:10:45.820
<v Dave Jones>Sure, sure.

00:10:45.820 --> 00:10:54.660
<v Dave Jones>So, all these things around my property or in my property and all the obstacles have to be overcome by something that's wireless that can penetrate all those obstacles.

00:10:55.740 --> 00:11:02.260
<v Dave Jones>And, you know, that's when I started making a Motino, researching which wireless technology I want to focus on.

00:11:03.440 --> 00:11:07.920
<v Chris Gammell>So, you know, so, like, I would like to stop for a second and call out the fact that you're just like, yeah, of course it has to be wireless.

00:11:07.920 --> 00:11:10.620
<v Chris Gammell>Like, to me, I'm like, oh, my God, it's wireless, you know?

00:11:10.720 --> 00:11:17.220
<v Chris Gammell>But I love, I really, really appreciate and am impressed by people who are just like, yep, that's the way it's got to be.

00:11:17.380 --> 00:11:18.340
<v Chris Gammell>I'm going to go learn it, you know?

00:11:18.440 --> 00:11:19.960
<v Chris Gammell>And it's awesome.

00:11:19.960 --> 00:11:35.440
<v Dave Jones>You know, for instance, when I started looking into home automation, you know, the backbone of all these projects was probably Arduino Uno, you know, the AdMega 328 and various forums and clones and development boards.

00:11:35.440 --> 00:11:46.680
<v Dave Jones>And people were just kind of doing their own thing the best way they could and wiring stuff up, you know, hanging wires on walls and having some relays, turning on some light bulb.

00:11:46.820 --> 00:11:54.160
<v Dave Jones>And that was home automation, you know, and slowly it evolved and it got them better with the dedicated things for home automation.

00:11:54.160 --> 00:12:01.300
<v Dave Jones>But back then, there wasn't as much wireless as there is now.

00:12:01.720 --> 00:12:06.640
<v Dave Jones>And a lot of it was 2.4 gigahertz, Wi-Fi type wireless.

00:12:06.920 --> 00:12:08.660
<v Chris Gammell>Yeah, I remember a lot of like Z-Wave.

00:12:08.820 --> 00:12:12.240
<v Chris Gammell>I remember that one and I think it's still around, but it's not, I'm not hearing about it as much.

00:12:12.500 --> 00:12:13.940
<v Chris Gammell>Z-Wave and Zigbee and a lot of the ISM band.

00:12:13.940 --> 00:12:17.240
<v Dave Jones>Yeah, those things are, I believe, are 900 megahertz.

00:12:17.640 --> 00:12:18.300
<v Chris Gammell>Yeah, I think so.

00:12:18.300 --> 00:12:24.040
<v Dave Jones>So, yeah, but those are, I think those are commercial and their stacks are not open.

00:12:24.660 --> 00:12:34.700
<v Dave Jones>And so you can buy them, you can buy 900 megahertz automation stuff from like Home Depot and Lowe's light switches and things like that.

00:12:34.860 --> 00:12:39.880
<v Dave Jones>Even though a lot of them are still Wi-Fi, some of them will be Zigbee and they're 900 megahertz.

00:12:39.880 --> 00:12:53.520
<v Dave Jones>So, I'm not so much of an expert in that area, but back when I looked into it, it was not open and you had to buy dedicated hardware to talk to those things and it was not always reliable.

00:12:54.360 --> 00:12:54.460
<v Chris Gammell>Right.

00:12:55.120 --> 00:12:59.300
<v Chris Gammell>I think, yeah, I think generally that not always reliable and definitely not open.

00:12:59.600 --> 00:13:02.660
<v Chris Gammell>I think those two things are indicative of like the home automation market.

00:13:03.000 --> 00:13:06.880
<v Chris Gammell>But I think that one of the things that I always noticed was like there were just tons of price pressures.

00:13:06.880 --> 00:13:10.800
<v Chris Gammell>So, even if you wanted to design something that market, it has to be dirt cheap.

00:13:11.200 --> 00:13:14.960
<v Chris Gammell>So, was that something that you were kind of targeting from the beginning or was it more just I want to get it working?

00:13:15.220 --> 00:13:18.220
<v Dave Jones>Well, I wanted to get it working first and foremost.

00:13:18.640 --> 00:13:24.980
<v Dave Jones>I wanted to get to a point where I know I have a platform that I can build on, right?

00:13:24.980 --> 00:13:32.640
<v Dave Jones>Because I experimented with various wireless chips.

00:13:33.140 --> 00:13:35.160
<v Dave Jones>I started with 2.4 gigahertz.

00:13:35.320 --> 00:13:44.040
<v Dave Jones>There were a couple of popular ones like the NRF and a bunch came after that.

00:13:44.300 --> 00:13:49.440
<v Dave Jones>But Wi-Fi and Bluetooth and all these 2.4 gigahertz were not working very well.

00:13:49.440 --> 00:13:54.520
<v Chris Gammell>Is that because of distance or complexity or just reliability?

00:13:56.460 --> 00:14:05.080
<v Dave Jones>I don't think reliability so much, but just the inherent physical properties of 2.4 gigahertz.

00:14:06.200 --> 00:14:13.300
<v Dave Jones>And so, at 2.4 gigahertz, you're just not going to have the range or you need a lot more power to get the range.

00:14:14.280 --> 00:14:16.080
<v Chris Gammell>Pesky water molecules keep getting in the way, huh?

00:14:16.080 --> 00:14:24.260
<v Dave Jones>Well, the physics of 2.4 gigahertz is different than the physics of sub-gigahertz.

00:14:24.920 --> 00:14:31.540
<v Dave Jones>So, to get more range, you're going to have to look at lower frequencies, just keeping all things equal.

00:14:32.520 --> 00:14:35.200
<v Dave Jones>Or you will need to throw more power at it.

00:14:35.200 --> 00:14:46.280
<v Dave Jones>And, of course, the stacks of 2.4 gigahertz, if you're looking at Wi-Fi, that's way different, way more complex than sub-gigahertz FSK modules.

00:14:47.000 --> 00:14:54.640
<v Dave Jones>So, that's one of the factors that drove me towards looking into sub-gigahertz modules.

00:14:54.640 --> 00:15:07.280
<v Dave Jones>And I believe back then, the more popular one was the RFM-12B precursor to RFM-69, which is what I use most commonly now, these days.

00:15:07.460 --> 00:15:08.480
<v Dave Jones>There's the LoRa, of course.

00:15:09.220 --> 00:15:12.580
<v Dave Jones>So, I had started with RFM-12B.

00:15:12.680 --> 00:15:14.120
<v Dave Jones>That worked out very well.

00:15:15.220 --> 00:15:18.480
<v Dave Jones>It was a lower power module, just about 5 dBm.

00:15:18.480 --> 00:15:21.500
<v Dave Jones>And it was still pretty good.

00:15:21.640 --> 00:15:22.880
<v Dave Jones>It reached most areas.

00:15:23.020 --> 00:15:26.900
<v Dave Jones>There were some dead spots in my home where I couldn't reach with that.

00:15:27.980 --> 00:15:31.100
<v Chris Gammell>And this is the RFM-12B, you said?

00:15:31.400 --> 00:15:31.700
<v Chris Gammell>Yes.

00:15:32.560 --> 00:15:32.820
<v Chris Gammell>Okay.

00:15:33.080 --> 00:15:35.880
<v Chris Gammell>Is that made by microchip, or who is it made by?

00:15:35.900 --> 00:15:42.040
<v Dave Jones>I think the transceiver chip in that module was made by Silicon Labs, if I'm not mistaken.

00:15:42.240 --> 00:15:42.480
<v Dave Jones>Okay.

00:15:42.480 --> 00:15:48.880
<v Dave Jones>But yeah, so it's made by a U.S. company, and it was packaged by a Chinese company.

00:15:49.540 --> 00:15:51.520
<v Chris Gammell>So, how did this evaluation look for you?

00:15:51.600 --> 00:15:54.640
<v Chris Gammell>I mean, were you actually trying side by side?

00:15:54.760 --> 00:15:56.000
<v Chris Gammell>How did you actually test the...

00:15:56.000 --> 00:16:03.360
<v Chris Gammell>Were you doing laboratory-style tests, or was it more like, I've got a thing in a mailbox, I've got a receiver on the other side of the house?

00:16:03.780 --> 00:16:05.620
<v Dave Jones>What level of testing were you talking about here?

00:16:05.620 --> 00:16:07.080
<v Dave Jones>I've done a fair bit of testing.

00:16:08.860 --> 00:16:15.020
<v Dave Jones>Learning the RF part of things was alongside learning the electronics and hardware part of things.

00:16:15.380 --> 00:16:27.320
<v Dave Jones>So, the extent of my RF testing was putting a transmitter in one spot, somewhere in a field or on my street, and just walking with the other one.

00:16:27.320 --> 00:16:30.620
<v Dave Jones>And seeing how far it gets with different settings.

00:16:31.760 --> 00:16:32.920
<v Dave Jones>And of course, yeah.

00:16:33.080 --> 00:16:33.360
<v Dave Jones>Oh, wow.

00:16:33.360 --> 00:16:39.420
<v Dave Jones>So, of course, 24 gigahertz started cutting out at a couple dozen feet or so, you know.

00:16:40.020 --> 00:16:45.840
<v Dave Jones>And the sub-giguahertz modules were far more successful.

00:16:46.100 --> 00:16:48.500
<v Dave Jones>I was getting several hundred meters, you know.

00:16:48.760 --> 00:16:51.080
<v Dave Jones>That's way more.

00:16:51.340 --> 00:16:54.260
<v Dave Jones>So, it was a no-brainer to just use that.

00:16:54.260 --> 00:17:01.100
<v Chris Gammell>So, you would have like a receiver, the receiver would be in your hand, your transmitter would be in a certain spot, you just wait until you couldn't see data packets coming through anymore, or what?

00:17:02.600 --> 00:17:03.220
<v Dave Jones>Sort of, yes.

00:17:03.280 --> 00:17:10.740
<v Dave Jones>So, the transmitter, I would just put on an elevated thing or something, just not on the ground.

00:17:11.120 --> 00:17:11.360
<v Dave Jones>Okay.

00:17:11.440 --> 00:17:19.540
<v Dave Jones>And I'd have the receiver hooked up to a laptop, I'd just walk away, trying to keep antennas, you know, parallel to each other.

00:17:20.360 --> 00:17:20.680
<v Chris Gammell>Nice.

00:17:21.220 --> 00:17:21.660
<v Chris Gammell>That's great.

00:17:21.760 --> 00:17:22.080
<v Chris Gammell>Yeah, okay.

00:17:22.080 --> 00:17:29.360
<v Dave Jones>So, that way I would see, you know, signal is slowly decreasing in power, in received power, yeah.

00:17:29.360 --> 00:17:31.420
<v Dave Jones>And still, so still all line of sight.

00:17:31.860 --> 00:17:33.060
<v Dave Jones>Yeah, line of sight, yeah.

00:17:33.100 --> 00:17:39.680
<v Dave Jones>Because if you add obstacles and random things in between, then there's no way to compare apples to apples.

00:17:39.860 --> 00:17:43.260
<v Chris Gammell>And you said FSK before, that's frequency shift key, is that right?

00:17:43.560 --> 00:17:45.360
<v Dave Jones>Yeah, frequency shift key, yes.

00:17:45.360 --> 00:17:46.020
<v Dave Jones>Cool.

00:17:46.020 --> 00:17:54.300
<v Dave Jones>So, it's basically the digital form of FM, where you have a carrier frequency, which modulates ones and zeros.

00:17:54.300 --> 00:17:57.700
<v Chris Gammell>I like that digital form of FM.

00:17:57.880 --> 00:17:58.920
<v Chris Gammell>That's a good way to say it.

00:18:00.300 --> 00:18:04.900
<v Chris Gammell>And what level of, like, so when you're interacting with these modules, what does that actually look like?

00:18:04.960 --> 00:18:08.000
<v Chris Gammell>Is that you're basically throwing commands at it over and over again?

00:18:08.040 --> 00:18:11.300
<v Chris Gammell>Or what is the actual interface layer that you were dealing with it?

00:18:11.300 --> 00:18:18.200
<v Dave Jones>You mean from an interfacing, getting commands over to the modules?

00:18:18.200 --> 00:18:20.560
<v Chris Gammell>Yeah, so you said, like, you're talking to this RFM-12B.

00:18:21.480 --> 00:18:26.200
<v Chris Gammell>And so, is it like you're kind of just throwing, you're like, you're reading from a register?

00:18:26.540 --> 00:18:31.860
<v Chris Gammell>Or are you actually driving the, so, and I'm really asking from the people that are listening.

00:18:32.000 --> 00:18:36.780
<v Chris Gammell>So, like, if they wanted to start working with it tomorrow, what would it take for them to start using that same module?

00:18:36.780 --> 00:18:41.840
<v Dave Jones>Okay, first of all, I would probably point them to RFM-69 at least.

00:18:42.040 --> 00:18:42.660
<v Dave Jones>Sure, sure, yeah.

00:18:42.680 --> 00:18:46.220
<v Dave Jones>Because that's a more, it's a better module overall.

00:18:46.220 --> 00:18:47.360
<v Dave Jones>Okay, but any of these modules then.

00:18:47.760 --> 00:18:53.160
<v Dave Jones>But all these, all these subgears modules have a register set.

00:18:53.360 --> 00:18:55.460
<v Dave Jones>And pretty much they handle the RF part.

00:18:55.600 --> 00:18:59.260
<v Dave Jones>You just play with the parameters and you have a lot to play with.

00:18:59.260 --> 00:19:16.760
<v Dave Jones>But I built a library for myself to use on my own to interact with those chips and, you know, be able to use a standard set of default settings that are good all around settings.

00:19:16.760 --> 00:19:23.560
<v Dave Jones>And that library, I built the library for RFM-12B back then when I was using that module.

00:19:23.660 --> 00:19:25.860
<v Dave Jones>And then I built one for RFM-69.

00:19:26.140 --> 00:19:27.000
<v Dave Jones>And that's what I use now.

00:19:27.120 --> 00:19:31.200
<v Dave Jones>And that's what my users probably use as well.

00:19:31.260 --> 00:19:32.940
<v Dave Jones>Although there's others out there.

00:19:32.940 --> 00:19:45.900
<v Dave Jones>So it's pretty much made so that you can just call out some commands and tell the radio module to, you know, set yourself at 950 megahertz center frequency.

00:19:45.900 --> 00:19:48.680
<v Dave Jones>Or you can set a custom frequency if you'd like.

00:19:49.600 --> 00:19:52.160
<v Dave Jones>And here's an encryption key that you can use.

00:19:52.160 --> 00:20:02.460
<v Dave Jones>And there's various other settings to get that module to communicate with whatever other modules you have out there.

00:20:03.380 --> 00:20:08.560
<v Dave Jones>So you don't have to deal with the RF part too much.

00:20:09.000 --> 00:20:10.200
<v Chris Gammell>Even though you can do...

00:20:10.200 --> 00:20:11.200
<v Chris Gammell>Yeah, so set it and forget it almost, right?

00:20:11.940 --> 00:20:12.320
<v Chris Gammell>Almost.

00:20:12.320 --> 00:20:12.760
<v Chris Gammell>Sort of, kind of.

00:20:12.900 --> 00:20:14.560
<v Dave Jones>You can get into it if you'd like.

00:20:14.820 --> 00:20:17.160
<v Dave Jones>And, you know, there's a long data sheet to read on.

00:20:17.160 --> 00:20:22.180
<v Dave Jones>But you're quickly getting into RF concepts at that point.

00:20:23.060 --> 00:20:23.520
<v Chris Gammell>Right, right.

00:20:23.600 --> 00:20:29.000
<v Chris Gammell>The amplification amounts and I'm sure the demodulation schemes, all that stuff.

00:20:29.160 --> 00:20:31.660
<v Chris Gammell>Depends how many knobs they basically give you to play with, huh?

00:20:31.940 --> 00:20:32.420
<v Dave Jones>Sure, yep.

00:20:32.960 --> 00:20:35.220
<v Chris Gammell>And so at the time you were basically...

00:20:35.220 --> 00:20:41.160
<v Chris Gammell>You figured out RFM-12B or more generically the 900 megahertz band was kind of the way forward because...

00:20:42.380 --> 00:20:44.160
<v Chris Gammell>Just because the transmit distance and...

00:20:44.740 --> 00:20:46.160
<v Chris Gammell>Yeah, better penetration.

00:20:47.160 --> 00:20:47.980
<v Dave Jones>Of obstacles.

00:20:48.280 --> 00:20:49.220
<v Dave Jones>Much lower power.

00:20:49.460 --> 00:20:50.740
<v Dave Jones>That's a very notable thing.

00:20:50.880 --> 00:20:59.500
<v Dave Jones>My whole focus is on low power in general because a lot of these nodes are running on batteries and they need to last a long time.

00:21:00.420 --> 00:21:02.040
<v Dave Jones>A conveniently long time.

00:21:02.140 --> 00:21:05.700
<v Dave Jones>I'm not going to go into the extreme of low power.

00:21:06.360 --> 00:21:08.220
<v Dave Jones>And that may surprise some people.

00:21:08.220 --> 00:21:17.880
<v Dave Jones>But for me, you know, having a node in my mailbox that's going to last one to two years is probably going to be beyond my servicing interval for that node.

00:21:18.140 --> 00:21:20.900
<v Dave Jones>So that's very convenient to me.

00:21:21.400 --> 00:21:25.660
<v Dave Jones>You know, some people may think, oh, you need to get five years or 10 years or it's not good enough.

00:21:25.780 --> 00:21:27.080
<v Dave Jones>You know, to me, that's good enough.

00:21:27.080 --> 00:21:35.740
<v Dave Jones>And I think for most uses, you can optimize a whole lot and you can get a whole lot better than that.

00:21:35.740 --> 00:21:50.920
<v Dave Jones>But a node that's transmitting every minute or so and is dynamically adjusting its transmit power, I think, is very good if it can do one to two years on a small battery.

00:21:50.920 --> 00:21:52.420
<v Chris Gammell>Yeah, I mean, and it depends.

00:21:52.500 --> 00:21:59.900
<v Chris Gammell>I think it all depends on the application, like the really harsh territory type stuff, right, that does need 10 years because you're never going to be able to get the device back again.

00:21:59.960 --> 00:22:00.220
<v Chris Gammell>Sure.

00:22:00.980 --> 00:22:10.360
<v Chris Gammell>If you're doing that, you're probably paying an engineering company or you're getting more depth into the radio or whatever it is to actually get that further engineering effort in there.

00:22:10.640 --> 00:22:11.200
<v Dave Jones>Yep, yep.

00:22:11.440 --> 00:22:16.600
<v Dave Jones>But I bet a node like that won't transmit every minute or every 30 seconds.

00:22:17.380 --> 00:22:18.240
<v Dave Jones>Yeah, that's a good point.

00:22:18.240 --> 00:22:29.900
<v Chris Gammell>I mean, when you are doing this, I mean, so like for the mailbox example, right, does it dynamically adjust or does it need to dynamically adjust or is it easier just to say every minute, tell me if there's mail?

00:22:30.360 --> 00:22:41.100
<v Dave Jones>So my own node transmits every minute and it tells me, it calculates the time elapsed from the last event or the mailbox being opened.

00:22:41.100 --> 00:22:51.420
<v Dave Jones>So it uses a PIR sensor, a motion sensor essentially, and that's actually the most costly component as far as power consumption.

00:22:51.580 --> 00:23:06.600
<v Dave Jones>It uses about 50 to 60 microamps, whereas the Motino itself and the radio use less than about 7 microamps, you know, in sleep mode using a watchdog timer.

00:23:06.600 --> 00:23:13.080
<v Dave Jones>We could eliminate the watchdog timer and save another 4-ish microamps, right?

00:23:13.220 --> 00:23:16.480
<v Dave Jones>But it's still a lot less than the actual sensor.

00:23:17.380 --> 00:23:25.380
<v Dave Jones>And since I've made that one mailbox sensor, I found different sensors that can use 2 microamps.

00:23:25.880 --> 00:23:29.240
<v Dave Jones>Still motion sensors, they're made by Panasonic.

00:23:29.660 --> 00:23:33.920
<v Dave Jones>They're far more expensive, like 30 bucks a piece or so.

00:23:34.160 --> 00:23:34.840
<v Dave Jones>Whoa, okay.

00:23:34.840 --> 00:23:40.840
<v Dave Jones>They're tiny, they're much more power efficient, but, you know, they cost a lot more.

00:23:40.960 --> 00:23:45.120
<v Dave Jones>So I decided to just go with that and not change it ever since.

00:23:45.220 --> 00:23:49.880
<v Dave Jones>And it still works and the battery still lasts about a year and a half.

00:23:50.480 --> 00:23:54.500
<v Dave Jones>And I'm happy with it, you know, every year and a half when I have to service it.

00:23:54.680 --> 00:24:00.640
<v Dave Jones>In fact, I find some corrosion, some, you know, being abused quite a bit.

00:24:00.640 --> 00:24:01.040
<v Dave Jones>Right.

00:24:01.040 --> 00:24:04.980
<v Chris Gammell>I was going to say mail is getting shoved in there, so that ups your service time anyways, right?

00:24:05.280 --> 00:24:07.820
<v Chris Gammell>So, I mean, Detroit's not particularly warm.

00:24:08.540 --> 00:24:09.400
<v Chris Gammell>Not at all.

00:24:10.280 --> 00:24:12.740
<v Dave Jones>We have a six-month, very long winter.

00:24:13.300 --> 00:24:14.380
<v Dave Jones>Yep, I know that goes.

00:24:14.380 --> 00:24:17.500
<v Dave Jones>And it's humid in the summers.

00:24:17.500 --> 00:24:25.680
<v Dave Jones>And so, you know, for that note to last so long and to be so reliable was actually quite remarkable.

00:24:26.360 --> 00:24:33.020
<v Dave Jones>I'm very happy with it and how it performs and the fact that it can last so long is very convenient.

00:24:33.520 --> 00:24:33.880
<v Chris Gammell>That's great.

00:24:33.880 --> 00:24:37.560
<v Chris Gammell>So we're still almost at the point where you were evaluating, right?

00:24:37.620 --> 00:24:38.880
<v Chris Gammell>So you were evaluating this module.

00:24:39.680 --> 00:24:40.120
<v Chris Gammell>You ended up up.

00:24:40.180 --> 00:24:44.300
<v Chris Gammell>It sounds like you've upgraded over time, going from the RFM12 to the 69.

00:24:46.180 --> 00:24:49.720
<v Chris Gammell>What is actually the processor that's on board as well?

00:24:49.780 --> 00:24:54.760
<v Chris Gammell>Because it sounds like at 7 microamps, rather, it's a pretty low-powered processor.

00:24:54.760 --> 00:25:06.720
<v Dave Jones>All the Motinos, well, not all, but the small Motinos, the red ones and the Motino USB are using the Edmega 320 AP.

00:25:07.300 --> 00:25:13.420
<v Dave Jones>It's the same chip you find on Arduino Uno, the very popular Edmega 320 AP.

00:25:13.640 --> 00:25:14.100
<v Chris Gammell>Yeah, okay.

00:25:14.100 --> 00:25:25.900
<v Dave Jones>And it can achieve very low power, sub-microamp, if you know how to drive it.

00:25:26.000 --> 00:25:33.580
<v Dave Jones>You have to power it from not use an LDO or voltage regulator because that's going to need some power.

00:25:33.900 --> 00:25:34.100
<v Dave Jones>Yeah.

00:25:34.400 --> 00:25:38.060
<v Dave Jones>And you have to dial down the clock and all that.

00:25:38.060 --> 00:25:45.860
<v Dave Jones>But I found that for most uses, you don't need to do that, and you can still get very good battery life.

00:25:46.880 --> 00:25:49.360
<v Dave Jones>So all the Motinos have a standard bootloader.

00:25:49.500 --> 00:25:50.900
<v Dave Jones>They have a standard set of settings.

00:25:51.040 --> 00:25:55.660
<v Dave Jones>They run from a 16 megahertz external resonator.

00:25:56.820 --> 00:26:01.400
<v Dave Jones>And they have an LDO that uses just 2 microamps of quiescent current.

00:26:01.400 --> 00:26:11.280
<v Dave Jones>So, you know, you can get down to 2 microamps if you don't use the watchdog and just use external hardware interrupts to wake it up.

00:26:11.560 --> 00:26:21.260
<v Dave Jones>Or you could use the watchdog to have the Motino itself wake itself up and do various things at intervals of multiples of 8 seconds.

00:26:21.660 --> 00:26:22.640
<v Dave Jones>It's what it is.

00:26:23.000 --> 00:26:24.520
<v Chris Gammell>So I'm actually looking at the board right now.

00:26:24.660 --> 00:26:25.980
<v Chris Gammell>I think this is the main one.

00:26:26.180 --> 00:26:28.540
<v Chris Gammell>It's red board, product ID 99.

00:26:28.540 --> 00:26:32.800
<v Chris Gammell>And so I'm looking at the picture, though.

00:26:32.980 --> 00:26:40.580
<v Chris Gammell>And is the picture that's on the main site where it's just a Winbond chip and an Atmel chip and then it looks like a 3-pin regulator or something?

00:26:41.020 --> 00:26:43.560
<v Chris Gammell>Is that actually the one with the RF?

00:26:44.200 --> 00:26:46.820
<v Dave Jones>Yes, that's the very first Motino that I designed.

00:26:47.780 --> 00:26:51.540
<v Dave Jones>And on the bottom side is where the RF chip is.

00:26:52.380 --> 00:26:53.040
<v Chris Gammell>Oh, I see.

00:26:53.100 --> 00:26:53.300
<v Chris Gammell>I see.

00:26:53.300 --> 00:26:53.500
<v Chris Gammell>Okay.

00:26:53.600 --> 00:26:59.020
<v Chris Gammell>So this one is not showing it actually populated, but it could go in there with the transceiver.

00:26:59.220 --> 00:26:59.500
<v Chris Gammell>I see.

00:26:59.640 --> 00:27:01.020
<v Chris Gammell>And that changes the price then, too.

00:27:01.080 --> 00:27:01.460
<v Chris Gammell>I see.

00:27:01.580 --> 00:27:01.760
<v Chris Gammell>Okay.

00:27:02.460 --> 00:27:03.360
<v Chris Gammell>That makes sense.

00:27:03.620 --> 00:27:03.740
<v Dave Jones>Cool.

00:27:03.860 --> 00:27:03.980
<v Dave Jones>Yeah.

00:27:04.020 --> 00:27:11.280
<v Dave Jones>Well, some people prefer to just get it as a bare board, you know, and they might not use the transceiver.

00:27:11.440 --> 00:27:15.040
<v Dave Jones>They might just use it for driving LEDs or motors or whatever.

00:27:15.440 --> 00:27:15.720
<v Chris Gammell>Sure.

00:27:16.000 --> 00:27:16.140
<v Chris Gammell>Yeah.

00:27:16.140 --> 00:27:32.500
<v Dave Jones>So I'd like to offer all these in as modular and diverse as possible of a way so that people can get just a bare board or they can get even the Winbond chip.

00:27:32.500 --> 00:27:49.880
<v Dave Jones>That's actually extra storage, and I use it for wireless programming of these boards so that if you have a node somewhere in a wall, in a light switch, or in your attic, or in a tree, or, I don't know, crazy places where you can't reach easily, you can wirelessly reprogram them.

00:27:50.600 --> 00:27:51.720
<v Dave Jones>So that's an option, right?

00:27:51.720 --> 00:27:51.880
<v Dave Jones>Oh, okay.

00:27:51.880 --> 00:27:57.280
<v Dave Jones>You can get the board with that or without that, or with the transceiver, without the transceiver, with headers, without headers.

00:27:58.000 --> 00:28:04.660
<v Dave Jones>So pretty much all these boards, you can have various options and add-ons you can add on to them.

00:28:05.020 --> 00:28:05.260
<v Chris Gammell>Okay.

00:28:05.400 --> 00:28:07.140
<v Chris Gammell>And so, like, what are most people doing?

00:28:07.280 --> 00:28:11.200
<v Chris Gammell>Are they most people are ordering with transceivers, with flash memory, all that stuff?

00:28:11.260 --> 00:28:12.380
<v Chris Gammell>I mean, how does it go?

00:28:13.380 --> 00:28:17.100
<v Dave Jones>So probably most people ordered with the transceiver.

00:28:17.100 --> 00:28:25.120
<v Dave Jones>I think some people that are a fair amount of people order with the flash chip as well, yes.

00:28:26.120 --> 00:28:30.960
<v Dave Jones>So they like to experiment or just try wireless programming, I guess.

00:28:31.160 --> 00:28:36.100
<v Dave Jones>I'm not sure because I haven't run a survey or anything, but...

00:28:36.100 --> 00:28:37.180
<v Chris Gammell>Yeah, I got to know your users, man.

00:28:37.740 --> 00:28:40.560
<v Chris Gammell>Okay, so tell us about the wireless programming, too.

00:28:40.620 --> 00:28:46.760
<v Chris Gammell>So is this the idea is, like, I go and push a new update to the firmware, it stores it in this chip, or how does it actually work?

00:28:47.100 --> 00:28:54.560
<v Dave Jones>So, the bootloader is what handles the...

00:28:54.560 --> 00:28:55.880
<v Dave Jones>Actually, let me take that back.

00:28:56.900 --> 00:29:06.880
<v Dave Jones>Your program runs on this Atmel, now microchip, Atmengad 320p, and it will listen to commands.

00:29:07.000 --> 00:29:10.500
<v Dave Jones>And you can send it a command saying, okay, I need you to upgrade the firmware.

00:29:10.500 --> 00:29:22.520
<v Dave Jones>And it will basically switch from whatever it's doing to taking in the new hex file, essentially, is what you compile in Arduino IDE.

00:29:23.060 --> 00:29:34.060
<v Dave Jones>You take the hex file and have a little GUI, and you need another Motino as a programmer to send that firmware over to your target node.

00:29:34.060 --> 00:29:36.780
<v Dave Jones>And all that is done wirelessly.

00:29:37.540 --> 00:29:44.700
<v Dave Jones>And once that transfer is completed, basically, that new firmware is going to sit in the flash chip.

00:29:44.980 --> 00:29:54.880
<v Dave Jones>And the last thing that happens after transfer is for that command to essentially reboot the processor.

00:29:54.880 --> 00:30:06.460
<v Dave Jones>So, once that happens, it'll enter the bootloader, where the bootloader is going to look at the flash chip, and it's going to see there's a new flash image or new program to be flashed on the Atmega.

00:30:06.700 --> 00:30:10.380
<v Dave Jones>So, it takes over, and it erases the old one.

00:30:10.680 --> 00:30:12.180
<v Dave Jones>It flashes in the new one.

00:30:12.640 --> 00:30:17.880
<v Dave Jones>And then it just jumps at the program location at the new...

00:30:17.880 --> 00:30:19.040
<v Dave Jones>It's going to run the new program.

00:30:19.300 --> 00:30:19.720
<v Chris Gammell>That's great.

00:30:19.720 --> 00:30:22.560
<v Chris Gammell>Yeah, it sounds like a standard over-the-air type update.

00:30:24.320 --> 00:30:26.220
<v Chris Gammell>What happens if it fails?

00:30:27.520 --> 00:30:30.280
<v Chris Gammell>I'm sure that there's problems once in a while, right?

00:30:32.640 --> 00:30:34.280
<v Dave Jones>It can happen, yes.

00:30:34.680 --> 00:30:35.480
<v Dave Jones>There's collisions.

00:30:35.780 --> 00:30:36.680
<v Dave Jones>There's all kinds of things.

00:30:36.880 --> 00:30:39.240
<v Dave Jones>And when you don't have a wire, anything can happen, right?

00:30:39.880 --> 00:30:48.020
<v Dave Jones>So, that's why I put that external flash chip on the Motino, so that you can use that for anything.

00:30:48.020 --> 00:30:50.260
<v Dave Jones>It's basically just storage, right?

00:30:50.300 --> 00:31:02.120
<v Dave Jones>You can use it for data logging or anything, but it's essentially meant for ensuring that you have an integral transfer of your hex file before anything happens.

00:31:02.240 --> 00:31:11.200
<v Dave Jones>So, if it breaks up in the middle, then your bootloader is not going to see a completed image and is not going to do anything.

00:31:11.200 --> 00:31:11.700
<v Dave Jones>Got it.

00:31:11.980 --> 00:31:12.140
<v Chris Gammell>Okay.

00:31:12.320 --> 00:31:14.200
<v Chris Gammell>So, is the bootloader really...

00:31:14.200 --> 00:31:20.160
<v Chris Gammell>So, you're saying the first thing it does is it checks internally on the Atmega chip to see if there's something...

00:31:20.160 --> 00:31:24.000
<v Chris Gammell>If there's a new program to load from the...

00:31:24.000 --> 00:31:26.300
<v Chris Gammell>Sorry, the bootloader is on the Atmega 328?

00:31:26.580 --> 00:31:26.840
<v Chris Gammell>Yes.

00:31:26.900 --> 00:31:30.180
<v Chris Gammell>And then it goes out to see, first off, is there a chip out there?

00:31:30.340 --> 00:31:32.160
<v Chris Gammell>And then does it have a new program for me?

00:31:32.180 --> 00:31:32.620
<v Chris Gammell>Is that the idea?

00:31:33.760 --> 00:31:34.460
<v Dave Jones>Exactly, yes.

00:31:34.460 --> 00:31:35.640
<v Chris Gammell>Okay, cool.

00:31:35.780 --> 00:31:39.340
<v Chris Gammell>And then if it needs to, it shuffles the data and reprograms itself.

00:31:39.600 --> 00:31:41.460
<v Chris Gammell>And then does it verify at that point too?

00:31:43.080 --> 00:31:51.620
<v Dave Jones>So, when the program is completely transferred, it's already verified to be complete.

00:31:51.620 --> 00:31:58.900
<v Dave Jones>So, that's the whole point of having the transfer like that in the flash chip so that you can...

00:32:00.380 --> 00:32:05.440
<v Dave Jones>If you're talking about verification and CRC, that's done on the transmitting end.

00:32:06.560 --> 00:32:06.940
<v Chris Gammell>Oh, okay.

00:32:07.000 --> 00:32:08.940
<v Chris Gammell>So, it says, here's my block of data.

00:32:09.040 --> 00:32:10.200
<v Chris Gammell>Here's what the CRC should be.

00:32:10.500 --> 00:32:12.760
<v Chris Gammell>If you don't see the CRC, whatever that...

00:32:12.760 --> 00:32:13.600
<v Chris Gammell>What does CRC stand for?

00:32:13.620 --> 00:32:14.040
<v Chris Gammell>I always forget.

00:32:18.400 --> 00:32:19.540
<v Chris Gammell>Google, remember?

00:32:19.540 --> 00:32:20.080
<v Chris Gammell>Google, yes.

00:32:21.620 --> 00:32:25.760
<v Dave Jones>So, it's an integrity check that a bunch of bytes are what they should be.

00:32:25.780 --> 00:32:26.920
<v Chris Gammell>Cyclic redundancy check.

00:32:26.980 --> 00:32:27.380
<v Chris Gammell>There we go.

00:32:27.460 --> 00:32:28.100
<v Chris Gammell>Thank you, Wikipedia.

00:32:28.520 --> 00:32:29.660
<v Chris Gammell>Donate to Wikipedia, everybody.

00:32:29.740 --> 00:32:30.480
<v Chris Gammell>We do every year.

00:32:30.820 --> 00:32:32.080
<v Chris Gammell>100 bucks from the amp hour every year.

00:32:34.840 --> 00:32:36.080
<v Chris Gammell>It's a checksum, right?

00:32:36.340 --> 00:32:39.200
<v Dave Jones>It's going to add all those bytes and do a twos compliment.

00:32:39.640 --> 00:32:43.120
<v Dave Jones>And you're going to have a checksum that needs to add up.

00:32:43.500 --> 00:32:43.940
<v Chris Gammell>Yeah, that's great.

00:32:44.040 --> 00:32:44.200
<v Chris Gammell>Okay.

00:32:44.300 --> 00:32:47.220
<v Chris Gammell>And so, that sounds like pretty good.

00:32:47.220 --> 00:32:49.580
<v Chris Gammell>I mean, so, would you...

00:32:51.580 --> 00:32:57.720
<v Chris Gammell>What is the benefit of doing this over programming it by person, like by wire?

00:32:58.880 --> 00:33:03.320
<v Dave Jones>Well, take for example, the light switches that I've designed.

00:33:03.320 --> 00:33:07.000
<v Dave Jones>They all have a Motino, one of these in them.

00:33:08.280 --> 00:33:12.140
<v Dave Jones>So, all of these are installed in walls, right?

00:33:12.640 --> 00:33:17.200
<v Dave Jones>Behind cover plates, behind screws, and they're wired to mains electricity.

00:33:18.240 --> 00:33:27.860
<v Dave Jones>So, to be able to reprogram them, you would, at the very least, have to have some way of tapping into that microcontroller, right?

00:33:27.860 --> 00:33:31.620
<v Dave Jones>With a header or with a USB jack at best.

00:33:32.160 --> 00:33:38.820
<v Dave Jones>And even then, you'd have to ensure that, you know, you're not tied to mains in any way, you know, galvanically.

00:33:39.780 --> 00:33:42.580
<v Dave Jones>You need to be isolated, you know, for your own safety.

00:33:42.840 --> 00:33:43.200
<v Dave Jones>Right, right.

00:33:43.320 --> 00:33:47.540
<v Dave Jones>So, all those worries are taken care of when you can do wireless programming.

00:33:48.340 --> 00:33:49.000
<v Dave Jones>Yeah, that's a good point.

00:33:49.560 --> 00:33:52.340
<v Chris Gammell>Well, speaking on the wireless side of things, so I'm looking down the page as well.

00:33:52.740 --> 00:33:55.740
<v Chris Gammell>And it looks like there's a couple of modules you can get here, too.

00:33:55.740 --> 00:33:57.680
<v Chris Gammell>So, these look familiar.

00:33:58.040 --> 00:33:59.400
<v Chris Gammell>Are these all Hope RF modules?

00:33:59.520 --> 00:34:00.920
<v Chris Gammell>Is that the manufacturer you're talking about?

00:34:01.080 --> 00:34:01.200
<v Chris Gammell>Yes.

00:34:01.200 --> 00:34:01.820
<v Dave Jones>Or is it someone else?

00:34:02.160 --> 00:34:02.460
<v Dave Jones>Yes.

00:34:03.120 --> 00:34:03.960
<v Dave Jones>It's Hope RF.

00:34:04.360 --> 00:34:13.160
<v Chris Gammell>So, like, from the library perspective, so it looks like you have RFM69 HCW, and then the CW version, the RFM95 and 96, and RFM12V.

00:34:13.240 --> 00:34:14.700
<v Chris Gammell>So, you have a couple different versions here.

00:34:15.380 --> 00:34:18.780
<v Chris Gammell>I assume that's just footprint differences in the backside or something like that.

00:34:19.300 --> 00:34:21.240
<v Chris Gammell>Maybe it's not even, you don't even need to do that.

00:34:21.240 --> 00:34:23.240
<v Dave Jones>Or is that like a...

00:34:23.240 --> 00:34:31.180
<v Dave Jones>There's some compatibilities, both in terms of how you interact with them and how you actually mount them.

00:34:31.760 --> 00:34:38.500
<v Dave Jones>So, as far as footprints, the RFM69 HCW is compatible with the LoRa radios.

00:34:38.500 --> 00:34:43.260
<v Dave Jones>But the LoRa's are not, you know, they're different.

00:34:43.560 --> 00:34:52.720
<v Dave Jones>Even though the LoRa radios actually can do FSK, they're, you know, you're not going to buy a LoRa module to use it at, you know, FSK.

00:34:53.080 --> 00:34:55.140
<v Dave Jones>Use the chirpy LoRa protocol.

00:34:55.400 --> 00:34:55.680
<v Chris Gammell>Exactly.

00:34:56.360 --> 00:34:56.540
<v Chris Gammell>Yeah.

00:34:56.540 --> 00:34:56.940
<v Chris Gammell>Okay.

00:34:57.040 --> 00:34:57.440
<v Chris Gammell>Okay.

00:34:57.580 --> 00:35:01.040
<v Chris Gammell>And so, then that was actually my other question is on the software side.

00:35:01.120 --> 00:35:03.500
<v Chris Gammell>So, now you have four different types of modules you could add to it, right?

00:35:03.540 --> 00:35:04.680
<v Chris Gammell>Those are all order options, whatever.

00:35:05.260 --> 00:35:05.420
<v Chris Gammell>Yes.

00:35:06.520 --> 00:35:09.280
<v Chris Gammell>Does it look different from the library side as well?

00:35:09.300 --> 00:35:11.920
<v Chris Gammell>Because I assume that the configuration details are different.

00:35:12.460 --> 00:35:12.580
<v Dave Jones>Yeah.

00:35:12.620 --> 00:35:23.060
<v Dave Jones>So, for all the RFM69 radios, whether they are the W, HCW, HW, or CW, they're all compatible with each other.

00:35:23.060 --> 00:35:25.340
<v Dave Jones>They use the same transceiver chip.

00:35:25.340 --> 00:35:25.780
<v Dave Jones>Same register sets.

00:35:26.140 --> 00:35:26.280
<v Chris Gammell>Yeah.

00:35:26.480 --> 00:35:26.880
<v Dave Jones>Exactly.

00:35:27.240 --> 00:35:43.060
<v Dave Jones>They're just different in terms of how they're wired on the actual module and how their passives are wired to enable lower power for the W and CW variants and higher power for the HW and HCW, which are 20 dBm or 100 milliwatts.

00:35:44.480 --> 00:35:44.780
<v Dave Jones>Oh, okay.

00:35:44.820 --> 00:35:49.880
<v Chris Gammell>So, that's about transmit distance, like the trade-off between longer battery life and longer transmit kind of thing?

00:35:49.880 --> 00:35:54.080
<v Dave Jones>Well, you can still use the higher power module at lower power.

00:35:54.220 --> 00:35:55.280
<v Dave Jones>So, you can dial down the power.

00:35:55.380 --> 00:36:06.200
<v Dave Jones>That's very important when you have modules that are in close proximity to each other and they don't need to transmit at full blast 20 dBm.

00:36:06.200 --> 00:36:22.140
<v Dave Jones>You know, you can just tell them, okay, self-adjust your power and only transmit enough power that you can comfortably hear each other and talk to each other, but not, you know, blast your message in the whole neighborhood.

00:36:23.340 --> 00:36:26.480
<v Dave Jones>Oh, so there's like state machines that go between the modules or how does that work?

00:36:26.480 --> 00:36:38.380
<v Dave Jones>Yeah, so in my library, I can't talk for other libraries, but in my library, there's a module called, it's essentially ATC, so Automatic Transmission Control.

00:36:38.740 --> 00:36:39.900
<v Dave Jones>That's what it stands for.

00:36:39.900 --> 00:36:50.500
<v Dave Jones>So, it's enabling these modules to self-adjust their transmit power based upon feedback that they receive through the ACKs.

00:36:51.340 --> 00:37:06.020
<v Dave Jones>So, when they send this message and they request an ACK or an acknowledgement, that will contain or it will be able to tell it how loud the message was or the transmit signal was.

00:37:06.020 --> 00:37:12.720
<v Dave Jones>You know, so essentially, let's say we have a node here that's called A and we have a node B.

00:37:12.960 --> 00:37:18.260
<v Dave Jones>A is the gateway or the main node and B is just trying to transmit some messages over.

00:37:19.220 --> 00:37:29.280
<v Dave Jones>And if you load them with that ATC module, that's part of the library, it's going to request ACKs from the main node, from node A.

00:37:29.280 --> 00:37:37.560
<v Dave Jones>And node A is going to tell it, okay, so I heard your signal at, you know, 65 dB, negative 65 dBm, your received signal.

00:37:38.180 --> 00:37:39.760
<v Dave Jones>So, that's very loud, right?

00:37:39.800 --> 00:37:40.700
<v Dave Jones>It's a very strong signal.

00:37:40.940 --> 00:37:48.160
<v Dave Jones>So, node B is going to figure out, okay, I was set at 85 dB, so I can really dial down my power quite a bit.

00:37:48.160 --> 00:38:05.860
<v Dave Jones>So, it's going to gradually lower its transmit power until it's going to race around that target value of negative 85, which I would consider still very good signal strength, but doesn't have to be, you know, strong in that to have a strong link.

00:38:06.160 --> 00:38:13.180
<v Chris Gammell>So, could you, since you've, you know, taught yourself a lot of RF stuff as well, could you quickly explain the dB thing for people who might not know that?

00:38:13.180 --> 00:38:15.280
<v Dave Jones>So, dB stands for decibels.

00:38:15.540 --> 00:38:26.140
<v Dave Jones>It's a log scale representation of power in the RF world, and not only, but in engineering, you're going to find that term a lot.

00:38:27.380 --> 00:38:30.760
<v Dave Jones>So, you know, it's not linear, it's log.

00:38:31.420 --> 00:38:38.800
<v Dave Jones>So, it's treated differently at transmit and receive.

00:38:38.800 --> 00:38:48.320
<v Dave Jones>So, on a transmit, you're putting out 20 dBm, which is in relationship to milliwatts, right?

00:38:48.420 --> 00:38:51.780
<v Dave Jones>So, 20 dBm will equate to 100 milliwatts of power.

00:38:52.580 --> 00:38:57.060
<v Dave Jones>30 dBm will be 1 watt, so it's 10 times more.

00:38:57.980 --> 00:38:59.840
<v Dave Jones>So, you see how it's not linear.

00:39:00.020 --> 00:39:01.820
<v Dave Jones>We're going from 20 dBm to 30.

00:39:02.020 --> 00:39:07.100
<v Dave Jones>We're jumping all the way from 100 milliwatts of actual power to 1 watt.

00:39:07.100 --> 00:39:10.160
<v Dave Jones>So, that's a 10 times increase.

00:39:10.860 --> 00:39:11.300
<v Chris Gammell>Okay, that's good.

00:39:11.380 --> 00:39:21.020
<v Chris Gammell>Yeah, and I mean, I think that's one thing that, from my perspective as a not very RF-y type person, it's a little confusing at first, but it becomes part of the lingo pretty fast, right?

00:39:21.060 --> 00:39:27.080
<v Chris Gammell>It's just, it's a different measure of, like, you understand that one value is good, another value is not so good.

00:39:27.200 --> 00:39:33.720
<v Chris Gammell>And like you were saying with the ATC, it sounds like you're trying to just kind of target around that, would you say it was minus 85 dB?

00:39:33.720 --> 00:39:37.520
<v Chris Gammell>Yeah, that's what I find works well for me.

00:39:38.200 --> 00:39:38.420
<v Chris Gammell>Right.

00:39:38.620 --> 00:39:40.780
<v Chris Gammell>Well, because you're specifically targeting low power as well.

00:39:40.920 --> 00:39:44.200
<v Chris Gammell>So, you don't, that's always that trade-off of transmit power.

00:39:44.220 --> 00:39:47.740
<v Dave Jones>I could probably comfortably go to negative 90.

00:39:48.180 --> 00:39:48.680
<v Dave Jones>Okay.

00:39:48.680 --> 00:39:50.240
<v Dave Jones>And that's on the receiving end.

00:39:50.240 --> 00:40:05.160
<v Dave Jones>So, when you're transmitting that strong signal of 100 milliwatts at maximum power from your transmitting node, at the receiving node, it's actually a very weak signal, which gets amplified and processed.

00:40:05.160 --> 00:40:14.880
<v Dave Jones>And, you know, compared to the 100 milliwatt or 20 dBm, the negative 85 dBm is a very weak signal.

00:40:15.120 --> 00:40:23.540
<v Dave Jones>But it's still strong enough to be processed by the RF chip and demodulated into your expected message.

00:40:23.540 --> 00:40:34.300
<v Chris Gammell>And like you were saying, it sounded like the, you don't have to really, from the interfacing side, you, Felix, you've already done all this stuff in the library, right?

00:40:34.320 --> 00:40:36.620
<v Chris Gammell>You don't have to even dig too much into the RF stuff.

00:40:36.820 --> 00:40:39.480
<v Chris Gammell>You might have to kind of optimize the knobs that are given to you.

00:40:39.800 --> 00:40:44.280
<v Chris Gammell>It sounds like then you are presenting this at the library level, the API above that.

00:40:44.280 --> 00:40:46.800
<v Chris Gammell>But it's pretty simple for someone like me.

00:40:46.980 --> 00:40:53.000
<v Chris Gammell>If I go and buy a Motino, I can basically just be like, adjust, adjust ATC or whatever you're talking, whatever it's called.

00:40:53.020 --> 00:40:56.480
<v Dave Jones>It's pretty much only a handful of settings that you need to set.

00:40:56.920 --> 00:41:03.180
<v Dave Jones>There's a network ID, which means that all the nodes on that network ID can hear each other.

00:41:04.480 --> 00:41:05.400
<v Dave Jones>There's a node ID.

00:41:05.680 --> 00:41:11.400
<v Dave Jones>So, you want to keep each node separate from the others, have a unique ID for each node.

00:41:11.400 --> 00:41:14.420
<v Dave Jones>And then, typically, there's a gateway ID.

00:41:14.580 --> 00:41:20.500
<v Dave Jones>So, all the nodes typically will transmit to one gateway or one node.

00:41:20.620 --> 00:41:31.400
<v Dave Jones>That's the main node that's going to relay all that data into whatever else you may have your cloud or, you know, aggregate your data in whatever way you need to.

00:41:32.160 --> 00:41:32.260
<v Chris Gammell>Right.

00:41:32.420 --> 00:41:38.200
<v Chris Gammell>And, yeah, it's an important point, I think, because people think about IoT or really just talking between different modules.

00:41:38.200 --> 00:41:47.000
<v Chris Gammell>But it seems like at one point, at a certain point, you know, each module, even though the promise of, you know, having every module on the Internet, quote unquote, right?

00:41:47.040 --> 00:41:51.300
<v Chris Gammell>It's like you could have every module have an IP address if it was a Wi-Fi based thing.

00:41:51.640 --> 00:41:54.280
<v Chris Gammell>But the power needed for that is ridiculous.

00:41:54.680 --> 00:42:02.440
<v Chris Gammell>So, instead, you're saying have one node talking to something that is a gateway to the Internet, like a ESP module or something that is higher power.

00:42:02.440 --> 00:42:06.120
<v Chris Gammell>And then it talks to all these subnodes that are very low power.

00:42:06.660 --> 00:42:07.100
<v Dave Jones>Sure.

00:42:07.240 --> 00:42:14.160
<v Dave Jones>So, keeping all those nodes online all the time would be probably terribly inefficient and wouldn't scale very well.

00:42:14.880 --> 00:42:15.420
<v Chris Gammell>Well, that's good.

00:42:15.660 --> 00:42:17.800
<v Chris Gammell>I mean, you're not called Low Power Lab for nothing.

00:42:18.080 --> 00:42:18.300
<v Chris Gammell>Yeah.

00:42:20.260 --> 00:42:21.000
<v Chris Gammell>That's great.

00:42:21.360 --> 00:42:25.820
<v Chris Gammell>So, well, let's talk about – so, you and I were emailing about this before the show.

00:42:25.820 --> 00:42:30.600
<v Chris Gammell>And we were talking – you know, I was actually on the wrong side here.

00:42:30.680 --> 00:42:32.800
<v Chris Gammell>I was confounding LoRa with all these other things.

00:42:33.200 --> 00:42:34.120
<v Chris Gammell>And I think it's a little confusing.

00:42:34.460 --> 00:42:36.140
<v Chris Gammell>It's still a little confusing for me, honestly.

00:42:36.480 --> 00:42:39.380
<v Chris Gammell>All these Hope RF modules are called RFM something.

00:42:39.840 --> 00:42:46.800
<v Chris Gammell>But, like you were telling me, the LoRa stuff, the RFM 95 module, which I've seen and I'm designing in right now, is different.

00:42:46.900 --> 00:42:48.320
<v Chris Gammell>I mean, it's just the protocol difference.

00:42:48.460 --> 00:42:50.820
<v Chris Gammell>So, like, what is the one that you're normally using?

00:42:50.980 --> 00:42:53.600
<v Chris Gammell>And, like, what are you targeting here?

00:42:53.600 --> 00:43:02.260
<v Dave Jones>So, early in my days of experimentation with this whole RF thing, I started with RFM 12B, right?

00:43:02.400 --> 00:43:08.260
<v Dave Jones>And then at some point, about a year or two into it, RFM 69 came along.

00:43:08.560 --> 00:43:14.600
<v Dave Jones>And it was a higher power module, had encryption, and a whole bunch of other goodies.

00:43:14.740 --> 00:43:17.380
<v Dave Jones>So, I decided to switch to that, upgrade to that.

00:43:17.460 --> 00:43:20.660
<v Dave Jones>And at that time, I had far fewer nodes myself.

00:43:20.660 --> 00:43:27.160
<v Dave Jones>So, it was relatively easy to upgrade from RFM 12B to RFM 69.

00:43:27.500 --> 00:43:42.420
<v Dave Jones>And, frankly, I never felt the need to upgrade from that to LoRa because RFM 69 still does very well in terms of penetrating all the obstacles, all the walls in structures like a house.

00:43:42.420 --> 00:43:47.700
<v Dave Jones>And, you know, my farthest node is across the street, right?

00:43:47.780 --> 00:43:52.680
<v Dave Jones>The mailbox and the receiving node or the gateway is below grade in the basement.

00:43:53.020 --> 00:43:57.520
<v Dave Jones>So, it goes through concrete, a bunch of dirt, and there's a bunch of distance to it.

00:43:58.000 --> 00:43:58.540
<v Chris Gammell>Yeah, right.

00:43:58.600 --> 00:43:59.900
<v Dave Jones>It still has a very strong signal.

00:44:00.200 --> 00:44:02.320
<v Dave Jones>So, why do I need to upgrade?

00:44:02.320 --> 00:44:09.240
<v Dave Jones>And LoRa is a little bit more complicated and also a much lower data rate in general.

00:44:09.440 --> 00:44:17.960
<v Dave Jones>So, if you want to get maximum data rates from LoRa, it's probably a tenth of the maximum data rate you can get from RFM 69.

00:44:17.960 --> 00:44:21.960
<v Dave Jones>And that's part of the protocol for LoRa.

00:44:22.440 --> 00:44:29.320
<v Dave Jones>Or one way to achieve even longer range, even with RFM 69, is decreasing the bit rate of the data.

00:44:30.240 --> 00:44:40.820
<v Dave Jones>So, instead of transmitting lots of bits in one given timeframe, you transmit fewer bits so that your receiver can hear them louder and clearer.

00:44:41.260 --> 00:44:42.980
<v Chris Gammell>And have more things to compare against, it seems like, too.

00:44:42.980 --> 00:44:50.240
<v Chris Gammell>So, like, Richard, who's been on the show from TWTG, that was many, many months ago now.

00:44:50.500 --> 00:44:52.660
<v Chris Gammell>But that was a good show to reference people to.

00:44:52.780 --> 00:44:53.860
<v Chris Gammell>So, he was telling us about LoRa.

00:44:54.080 --> 00:44:55.400
<v Chris Gammell>And then I went off and studied a little bit.

00:44:55.460 --> 00:44:59.020
<v Chris Gammell>I went to that conference, came back from the Things Conference thing, knew a little bit more.

00:44:59.100 --> 00:45:00.940
<v Chris Gammell>I'm still getting a feel for it, to be completely honest.

00:45:01.320 --> 00:45:02.300
<v Chris Gammell>I'm still struggling.

00:45:02.480 --> 00:45:03.460
<v Chris Gammell>I still struggle a little bit.

00:45:03.480 --> 00:45:08.500
<v Chris Gammell>And I think it's confusing for me because it's like some of this stuff, like the 69, like you're talking, the RFM 69,

00:45:08.500 --> 00:45:14.100
<v Chris Gammell>it is operating on the same ISM bands, right?

00:45:14.180 --> 00:45:17.140
<v Chris Gammell>So, the industrial and scientific, I forget what the M is.

00:45:17.660 --> 00:45:18.140
<v Chris Gammell>Medical?

00:45:18.400 --> 00:45:18.720
<v Chris Gammell>Medical.

00:45:19.240 --> 00:45:19.400
<v Chris Gammell>Yeah.

00:45:19.460 --> 00:45:19.840
<v Chris Gammell>Is it medical?

00:45:20.020 --> 00:45:20.180
<v Chris Gammell>Okay.

00:45:20.700 --> 00:45:23.460
<v Chris Gammell>And that's just the frequencies that are allowable, right?

00:45:24.220 --> 00:45:26.900
<v Chris Gammell>Like 433, 868, 915.

00:45:27.260 --> 00:45:27.560
<v Dave Jones>Yes.

00:45:28.000 --> 00:45:28.200
<v Dave Jones>Yeah.

00:45:28.240 --> 00:45:31.480
<v Dave Jones>So, different parts of the world have the various bands.

00:45:32.060 --> 00:45:32.500
<v Dave Jones>Yeah.

00:45:32.640 --> 00:45:33.700
<v Dave Jones>As ISM.

00:45:34.200 --> 00:45:34.500
<v Chris Gammell>Right.

00:45:34.500 --> 00:45:36.640
<v Chris Gammell>And that's like the sandbox that they're allowed to play in.

00:45:36.640 --> 00:45:41.000
<v Chris Gammell>And then what we're talking about here is some of it, at least for the Laura stuff,

00:45:41.080 --> 00:45:43.620
<v Chris Gammell>Laura is a, what's it called?

00:45:43.660 --> 00:45:44.340
<v Chris Gammell>A protocol, right?

00:45:45.300 --> 00:45:45.580
<v Dave Jones>Yeah.

00:45:45.640 --> 00:45:49.340
<v Dave Jones>So, it's a proprietary protocol owned by Semtech.

00:45:49.860 --> 00:45:51.620
<v Chris Gammell>And so, that is there.

00:45:51.980 --> 00:45:56.520
<v Chris Gammell>Now, the RFM 69, though, like between two of those modules, what is the actual protocol that's happening there?

00:45:57.200 --> 00:45:59.020
<v Chris Gammell>Is it just packets?

00:45:59.200 --> 00:46:01.380
<v Chris Gammell>Like just some defined packet kind of thing?

00:46:02.580 --> 00:46:04.340
<v Chris Gammell>Between them, you mean?

00:46:04.340 --> 00:46:08.520
<v Chris Gammell>So, like if I went and snooped on the traffic, what would it look like, I guess?

00:46:09.180 --> 00:46:15.100
<v Chris Gammell>So, I know that if I looked at the Laura traffic on like a spectrum analyzer, I'd see like these slopes up and down as the frequency changes.

00:46:15.520 --> 00:46:19.620
<v Chris Gammell>So, would the RFM 69 just look like just a frequency shift key?

00:46:19.620 --> 00:46:20.140
<v Dave Jones>It would be more static.

00:46:20.480 --> 00:46:20.660
<v Dave Jones>Yeah.

00:46:20.780 --> 00:46:21.820
<v Dave Jones>It would be in just one place.

00:46:21.960 --> 00:46:32.320
<v Dave Jones>So, you have your center frequency and then you can, in the library, the default parameters, part of those are how wide the bandwidth of the modulation is and things like that.

00:46:32.320 --> 00:46:33.560
<v Dave Jones>But it would be in one place.

00:46:33.700 --> 00:46:38.800
<v Dave Jones>You would just see one waterfall, you know, in one static place.

00:46:38.940 --> 00:46:40.880
<v Dave Jones>It wouldn't be all over like Laura.

00:46:41.320 --> 00:46:45.600
<v Chris Gammell>From like the next step up then, like what is the actual, what does the packet look like?

00:46:45.600 --> 00:46:46.860
<v Chris Gammell>You mentioned there's encryption in there.

00:46:46.860 --> 00:46:51.760
<v Chris Gammell>So, like, and I know that most of the time, especially if people are using Motinos, they wouldn't see any of this stuff.

00:46:51.820 --> 00:46:52.620
<v Chris Gammell>But I'm just kind of curious.

00:46:52.620 --> 00:46:55.000
<v Chris Gammell>I'm guessing you had to look at this at some point.

00:46:55.100 --> 00:47:00.760
<v Chris Gammell>Like, what does that actually look like from a, you know, if you're looking at the packet, what does that look like?

00:47:00.760 --> 00:47:17.420
<v Dave Jones>So, the packet has various headers and a synchronizing sequence of, you can predefine it to be certain character or certain sequences of ones and zeros, right?

00:47:17.420 --> 00:47:23.620
<v Dave Jones>And all those things are coming before your actual payload.

00:47:24.480 --> 00:47:32.740
<v Dave Jones>And if you're using encryption, then the nice thing about these modules, the RFM 69, is they have hardware encryption, AES 128.

00:47:32.740 --> 00:47:40.620
<v Dave Jones>So, it's still going to cost a little bit of time, like a couple microseconds to encrypt your message.

00:47:40.780 --> 00:47:43.000
<v Dave Jones>But you can do that on the fly pretty much.

00:47:43.500 --> 00:47:55.180
<v Dave Jones>And transparently, once you set that encryption key, and it's simply going to, you know, shift all those bits, encrypt them, and it's going to have a CRC.

00:47:55.660 --> 00:47:58.080
<v Dave Jones>And that's your packet.

00:47:58.440 --> 00:47:58.980
<v Dave Jones>So, headers.

00:47:59.380 --> 00:48:02.700
<v Dave Jones>And that's a different CRC than we were talking about.

00:48:02.740 --> 00:48:03.720
<v Dave Jones>With the programming, right?

00:48:04.440 --> 00:48:04.700
<v Dave Jones>Yes.

00:48:04.800 --> 00:48:06.000
<v Dave Jones>It's different, obviously.

00:48:06.180 --> 00:48:09.800
<v Dave Jones>But it's still going to be a CRC that is used by the radio.

00:48:10.200 --> 00:48:10.580
<v Dave Jones>Yeah.

00:48:10.580 --> 00:48:17.320
<v Dave Jones>So, that the receiving end will see the, you know, we'll start seeing the synchronizing sequence.

00:48:17.940 --> 00:48:20.140
<v Dave Jones>And it's going to read all the headers and then the payload.

00:48:20.320 --> 00:48:23.620
<v Dave Jones>And then once it receives the CRC, it's going to compare that to the payload.

00:48:23.620 --> 00:48:32.640
<v Dave Jones>So, that's how it actually is able to receive a good packet and dismiss the ones that are gibberish.

00:48:32.960 --> 00:48:33.260
<v Chris Gammell>Right.

00:48:33.360 --> 00:48:33.600
<v Chris Gammell>So, yeah.

00:48:33.640 --> 00:48:43.780
<v Chris Gammell>If something, if there's like a sunspot that happens in the middle of a packet transmission and that part of the spectrum gets messed up, it'll just say, nope, this is a bad transmission.

00:48:44.080 --> 00:48:44.600
<v Chris Gammell>Try again.

00:48:44.780 --> 00:48:45.260
<v Chris Gammell>Yeah, sure.

00:48:45.380 --> 00:48:47.780
<v Dave Jones>And that, something like that, that's random like that.

00:48:47.780 --> 00:48:52.580
<v Dave Jones>It would probably fail much sooner than when it gets to the CRC.

00:48:52.960 --> 00:48:54.720
<v Dave Jones>Oh, why is that actually?

00:48:55.240 --> 00:49:02.340
<v Dave Jones>Well, because of all the preconditions that you set in the headers of the transmission.

00:49:02.540 --> 00:49:03.320
<v Dave Jones>Oh, okay.

00:49:03.340 --> 00:49:03.740
<v Dave Jones>Interesting.

00:49:03.740 --> 00:49:03.780
<v Dave Jones>Interesting.

00:49:04.300 --> 00:49:16.220
<v Dave Jones>When a transmitting module starts modulating the bits in the air, at nearly the same time, your receiver is going to start demodulating them into its receiving end.

00:49:16.220 --> 00:49:23.400
<v Dave Jones>So, the receiver might actually demodulate lots of things that you don't even realize, right?

00:49:23.600 --> 00:49:26.580
<v Dave Jones>Ones and zeros that are out there from some other sources.

00:49:26.580 --> 00:49:43.260
<v Dave Jones>But the way you set the settings in the library or the way they're set for you in the library, there's all these conditions that have to be met before the radio will even accept or even start demodulating the payload part of the message.

00:49:43.260 --> 00:49:47.340
<v Chris Gammell>Yeah, it kind of feels like a, what's that type of puzzle?

00:49:47.720 --> 00:49:50.420
<v Chris Gammell>It's like, what's that puzzle thingy?

00:49:51.100 --> 00:49:52.580
<v Chris Gammell>Or it's almost like a lock, right?

00:49:52.600 --> 00:49:58.820
<v Chris Gammell>If you don't have the right combination of ones and zeros, then you'll never actually get to the point where the thing clicks to unlock.

00:49:59.020 --> 00:49:59.500
<v Chris Gammell>Yeah, yeah.

00:49:59.500 --> 00:50:00.300
<v Chris Gammell>And let the payload through.

00:50:00.500 --> 00:50:04.220
<v Dave Jones>It'll fail very soon if it's not even close to being right.

00:50:04.760 --> 00:50:05.040
<v Chris Gammell>All right.

00:50:05.060 --> 00:50:05.620
<v Chris Gammell>Yeah, that makes sense.

00:50:05.660 --> 00:50:08.560
<v Chris Gammell>So, you're saying if it's a super noisy channel, the bits will never make it through.

00:50:08.980 --> 00:50:10.740
<v Dave Jones>Yeah, they won't make it through.

00:50:10.740 --> 00:50:17.440
<v Dave Jones>It might keep the receiver busy, which is undesirable, but the bits won't make it through.

00:50:18.240 --> 00:50:18.580
<v Chris Gammell>That's great.

00:50:18.780 --> 00:50:24.860
<v Chris Gammell>I mean, we should also say here that it seems like all this stuff is actually hidden from the user from your perspective, right?

00:50:25.360 --> 00:50:26.760
<v Dave Jones>Yeah, and that's the great thing.

00:50:26.880 --> 00:50:39.060
<v Dave Jones>You don't have to worry about how your packets are actually going in the air, how they're demodulated and modulated, and what's the receiving doing, and what's the transmitting doing,

00:50:39.060 --> 00:50:42.320
<v Dave Jones>and are they at the right time and right place and all that.

00:50:42.480 --> 00:50:44.360
<v Dave Jones>You have a couple commands.

00:50:45.760 --> 00:50:46.720
<v Dave Jones>Call the radio.

00:50:46.940 --> 00:50:49.020
<v Dave Jones>Tell it what frequency you want.

00:50:49.520 --> 00:50:57.140
<v Dave Jones>Network ID, node ID, a couple other settings to set the right module.

00:50:57.660 --> 00:50:59.480
<v Dave Jones>Transmit power, and that's it.

00:50:59.480 --> 00:51:03.880
<v Dave Jones>Then you're just ready to start sending messages.

00:51:04.440 --> 00:51:05.260
<v Chris Gammell>Yeah, that's awesome.

00:51:05.600 --> 00:51:06.160
<v Chris Gammell>That's awesome.

00:51:06.600 --> 00:51:13.220
<v Chris Gammell>Yeah, and then it sounds like it's at that level of, I mean, Arduino-esque level of like, send something, receive something pretty much, right?

00:51:13.260 --> 00:51:16.440
<v Chris Gammell>I mean, that's kind of the level people used to.

00:51:16.440 --> 00:51:35.380
<v Dave Jones>To be able to offer these modules to people that want to use them, you're pretty much bound to having to offer them software that's free and ready to use and easy to use, and it has to work with Arduino IDE or else nobody's interested.

00:51:35.620 --> 00:51:38.220
<v Chris Gammell>Or if the wrath of the makers falls upon you.

00:51:38.600 --> 00:51:38.860
<v Chris Gammell>Yeah.

00:51:38.860 --> 00:51:42.180
<v Chris Gammell>So what are people using it for?

00:51:42.260 --> 00:51:43.840
<v Chris Gammell>I mean, let's get into that use case.

00:51:43.960 --> 00:51:49.040
<v Chris Gammell>I mean, it seems like, I mean, and we're, like I should also mention, we were talking about one product, but you have many products.

00:51:49.240 --> 00:51:52.760
<v Chris Gammell>So maybe walk us through some of that other stuff as you tell us about what people are using them for.

00:51:52.760 --> 00:51:53.060
<v Chris Gammell>Sure.

00:51:53.060 --> 00:52:11.960
<v Dave Jones>So, Motino, I designed Motino, like I said, to be able to build other products on top of it, like light switches that can be used in a, you know, smart home so that I can monitor and control lights in the house.

00:52:12.160 --> 00:52:15.120
<v Dave Jones>I can monitor my garage doors.

00:52:15.300 --> 00:52:16.300
<v Dave Jones>So that's another product.

00:52:17.160 --> 00:52:18.620
<v Dave Jones>It's called the GarageMote.

00:52:18.620 --> 00:52:35.420
<v Dave Jones>It's a little shield or motherboard, actually, where Motino mounts on top of it, and it has a relay, and it has two magnetic sensors that can detect magnets on your chain or on your opener belt.

00:52:35.960 --> 00:52:42.400
<v Dave Jones>So you can tell when the garage is open, when it's closed, or when it's in between, so unknown status.

00:52:42.720 --> 00:52:46.860
<v Dave Jones>And it can also trigger an opening or closing action through that small relay.

00:52:46.860 --> 00:52:47.760
<v Dave Jones>So that's one example.

00:52:48.620 --> 00:52:57.160
<v Dave Jones>There's MotionMote, which is sort of very similar to the MyMailbox sensor.

00:52:57.420 --> 00:53:05.380
<v Dave Jones>It has a PIR motion sensor, and that comes in various different options.

00:53:05.520 --> 00:53:08.180
<v Dave Jones>So we have the Chinese sensor that I'm using in MyMailbox.

00:53:08.280 --> 00:53:08.900
<v Dave Jones>It's the same one.

00:53:09.680 --> 00:53:13.000
<v Dave Jones>It's more power hungry, but still pretty good.

00:53:13.000 --> 00:53:20.840
<v Dave Jones>And I also offer the Panasonic sensors for those that are more extreme and look for longer battery life.

00:53:20.840 --> 00:53:28.680
<v Dave Jones>So the MotionMote can be placed anywhere in your house, right, or anywhere in your environment, and it can detect motion.

00:53:28.880 --> 00:53:29.680
<v Dave Jones>It's very accurate.

00:53:29.680 --> 00:53:36.160
<v Dave Jones>It's going to last, again, years, depending on how big the battery is.

00:53:37.120 --> 00:53:38.680
<v Dave Jones>It runs on LiPo batteries.

00:53:38.680 --> 00:53:43.000
<v Dave Jones>And, you know, it can tell you motion.

00:53:43.280 --> 00:53:45.080
<v Dave Jones>And it's not stuck to a wall.

00:53:45.200 --> 00:53:46.300
<v Dave Jones>It's not stuck to a wire.

00:53:47.080 --> 00:53:48.820
<v Dave Jones>And it's very convenient.

00:53:48.940 --> 00:53:53.860
<v Dave Jones>It can actually be used as both as security and as convenience.

00:53:54.120 --> 00:53:55.720
<v Dave Jones>So you walk into a room.

00:53:56.060 --> 00:53:56.800
<v Dave Jones>Motion is detected.

00:53:57.040 --> 00:53:58.840
<v Dave Jones>Light turns on, right?

00:53:59.580 --> 00:54:01.340
<v Dave Jones>So that's one use case right there.

00:54:01.420 --> 00:54:01.940
<v Chris Gammell>Yeah, that's great.

00:54:02.260 --> 00:54:05.760
<v Chris Gammell>So, like, in that case, so let's talk about the MotionMote because you've already kind of talked about it a little bit.

00:54:06.160 --> 00:54:07.460
<v Chris Gammell>So, okay, so I buy this kit.

00:54:07.780 --> 00:54:08.280
<v Chris Gammell>And I'm looking at it.

00:54:08.280 --> 00:54:08.780
<v Chris Gammell>This is nice.

00:54:09.280 --> 00:54:11.000
<v Chris Gammell>It looks like there's a baseboard.

00:54:11.100 --> 00:54:11.900
<v Chris Gammell>There's actually the Motino.

00:54:12.060 --> 00:54:13.940
<v Chris Gammell>There's a case for it.

00:54:13.960 --> 00:54:15.120
<v Chris Gammell>And then the sensor itself.

00:54:16.960 --> 00:54:21.040
<v Chris Gammell>Do I need to then have another node that acts as the gateway?

00:54:21.160 --> 00:54:21.740
<v Chris Gammell>Is that kind of the idea?

00:54:22.180 --> 00:54:27.100
<v Dave Jones>Just having one node with one module, radio module on it, is not very useful.

00:54:27.200 --> 00:54:28.120
<v Dave Jones>How are you going to talk to it?

00:54:28.120 --> 00:54:30.440
<v Dave Jones>So you need to have some kind of magic.

00:54:30.680 --> 00:54:31.760
<v Dave Jones>I believe magic is the other way.

00:54:32.760 --> 00:54:40.440
<v Dave Jones>You're going to have to have another node to, you know, receive messages from that Motion node.

00:54:41.320 --> 00:54:43.920
<v Chris Gammell>So someone goes to buy a kit, though.

00:54:44.300 --> 00:54:51.220
<v Chris Gammell>So that's just kind of what I'm getting towards is if they buy a kit, they should also plan to buy a second Motino with the same radio on it so that they can talk between them.

00:54:51.500 --> 00:54:52.840
<v Dave Jones>Yes, that would be correct.

00:54:52.840 --> 00:54:53.040
<v Dave Jones>Okay.

00:54:53.040 --> 00:55:01.060
<v Chris Gammell>But it sounds like if you then buy that Motino as the gateway, you can then add as many nodes around it as you want it to.

00:55:01.060 --> 00:55:01.300
<v Chris Gammell>Sure.

00:55:01.380 --> 00:55:02.900
<v Chris Gammell>That's kind of the benefit, right?

00:55:02.900 --> 00:55:03.080
<v Chris Gammell>Yeah.

00:55:03.460 --> 00:55:03.660
<v Chris Gammell>Yeah.

00:55:03.740 --> 00:55:10.880
<v Dave Jones>The most convenient way would probably be a Motino USB, which has an FTDI chip to take care of all the USB translation.

00:55:11.220 --> 00:55:16.960
<v Dave Jones>So you just plug that into USB on your, could be your PC or it could be your Raspberry Pi.

00:55:16.960 --> 00:55:28.620
<v Dave Jones>Or if you're more hardcore and you want to just buy a regular Motino with no USB on it, you can just connect, you know, power and TXRX, which is serial, to your Raspberry Pi.

00:55:28.720 --> 00:55:29.120
<v Dave Jones>And there you go.

00:55:29.220 --> 00:55:30.520
<v Dave Jones>You have a gateway.

00:55:30.780 --> 00:55:40.440
<v Chris Gammell>And that's what a lot of people are doing is using it to a Raspberry Pi as like the, so it's like extending a Raspberry Pi as another RF module on there.

00:55:40.440 --> 00:55:41.080
<v Chris Gammell>Yes.

00:55:41.520 --> 00:55:41.780
<v Dave Jones>Yes.

00:55:41.860 --> 00:55:56.840
<v Dave Jones>So I guess Raspberry Pi or similar small computers are the most convenient way to get that data onto the internet and not have a full-blown computer on 24-7.

00:55:57.280 --> 00:55:57.720
<v Dave Jones>Right.

00:55:57.920 --> 00:55:58.060
<v Dave Jones>Yeah.

00:55:58.800 --> 00:55:59.480
<v Dave Jones>For that purpose.

00:55:59.540 --> 00:55:59.640
<v Dave Jones>Yeah.

00:55:59.660 --> 00:56:02.380
<v Chris Gammell>And it makes sense too that that, so then the Raspberry Pi acts as a gateway.

00:56:02.900 --> 00:56:06.480
<v Chris Gammell>And in my experience, at least gateways have always been, you know, higher power.

00:56:06.560 --> 00:56:07.680
<v Chris Gammell>They're going to be plugged into a wall.

00:56:07.680 --> 00:56:13.380
<v Chris Gammell>You're not going to, you know, you might want them on a battery, but most of the time, because they're also going and doing backhaul.

00:56:13.560 --> 00:56:15.840
<v Chris Gammell>The term I always hear is backhaul to the internet.

00:56:16.160 --> 00:56:19.320
<v Chris Gammell>And since you're doing that, you need, you need a little bit more juice for that.

00:56:19.920 --> 00:56:21.160
<v Dave Jones>A little bit more juice.

00:56:21.240 --> 00:56:21.500
<v Dave Jones>Yes.

00:56:22.320 --> 00:56:31.860
<v Dave Jones>And in fact, I designed a hat for the Raspberry Pi, which hosts the same processor, the Atmega 328.

00:56:31.860 --> 00:56:38.080
<v Dave Jones>It can be powered by a LiPo battery, which actually acts as a backup, power backup.

00:56:38.320 --> 00:56:43.320
<v Dave Jones>So power goes out, you know, my gateway and my, all these nodes are still functional.

00:56:43.500 --> 00:56:44.940
<v Dave Jones>They can still send data.

00:56:45.300 --> 00:56:47.460
<v Dave Jones>Data can still be logged and all that.

00:56:47.460 --> 00:56:54.180
<v Dave Jones>And it has the same radio module, or you could choose either LoRa or RFM69.

00:56:55.180 --> 00:57:01.360
<v Dave Jones>And it's a very compact, convenient way to turn your Raspberry Pi into a gateway.

00:57:02.700 --> 00:57:10.560
<v Dave Jones>But like I said, of course, you can just use a Bayer Motino and wire it up with just a couple wires.

00:57:10.560 --> 00:57:12.840
<v Dave Jones>And that can act as your gateway.

00:57:13.100 --> 00:57:17.300
<v Dave Jones>But then you don't have the backup and other conveniences that come with this hat.

00:57:17.960 --> 00:57:18.060
<v Chris Gammell>Yeah.

00:57:18.080 --> 00:57:26.540
<v Chris Gammell>It kind of sounds like it's like a DIY, anywhere from DIY, you know, breadboarding together up to, yeah, you can kind of pull these into a product if you really wanted to.

00:57:27.460 --> 00:57:32.600
<v Chris Gammell>And then, you know, reuse a lot of this stuff as a, you know, product level type thing.

00:57:32.900 --> 00:57:33.100
<v Dave Jones>Sure.

00:57:33.440 --> 00:57:33.700
<v Dave Jones>Sure.

00:57:33.700 --> 00:57:34.340
<v Dave Jones>Yeah.

00:57:34.340 --> 00:57:49.820
<v Dave Jones>And for my own use to make this whole network of sub-gigahertz modules convenient to access and use and control, I built my own platform that is not in the cloud.

00:57:50.100 --> 00:57:53.620
<v Dave Jones>Or if you consider the Raspberry Pi the cloud, then that's the cloud.

00:57:53.760 --> 00:57:55.480
<v Dave Jones>But it runs on the Raspberry Pi.

00:57:56.200 --> 00:58:01.880
<v Dave Jones>It's essentially a little web server that runs a web page that's driven by WebSockets.

00:58:01.880 --> 00:58:04.680
<v Dave Jones>And it's secure.

00:58:05.380 --> 00:58:07.160
<v Dave Jones>So, nobody can.

00:58:07.180 --> 00:58:07.860
<v Chris Gammell>So, what is this called?

00:58:07.980 --> 00:58:09.200
<v Chris Gammell>I actually have not seen this.

00:58:09.340 --> 00:58:16.120
<v Dave Jones>It's called the Gateway Dashboard, Motino Gateway Dashboard.

00:58:16.220 --> 00:58:19.460
<v Dave Jones>I never really came up with a proper official name for it.

00:58:19.620 --> 00:58:19.760
<v Dave Jones>All right.

00:58:20.080 --> 00:58:22.940
<v Chris Gammell>We're going to work on a name after this show is finished recording.

00:58:23.120 --> 00:58:24.320
<v Chris Gammell>We need to get some branding in here.

00:58:24.500 --> 00:58:24.520
<v Chris Gammell>Yeah.

00:58:24.520 --> 00:58:26.100
<v Dave Jones>But you can find all about it.

00:58:26.160 --> 00:58:29.340
<v Dave Jones>Find out all about it at lowparlab.com slash gateway.

00:58:29.340 --> 00:58:34.760
<v Dave Jones>So, if you go there, you'll see some hardware.

00:58:34.760 --> 00:58:37.280
<v Chris Gammell>I think you should just call it the LPL Gateway or something like that.

00:58:37.400 --> 00:58:37.540
<v Dave Jones>Yeah.

00:58:37.940 --> 00:58:40.500
<v Dave Jones>You know, I call it the IoT Gateway Project.

00:58:41.240 --> 00:58:43.000
<v Dave Jones>I'm not sure that's the official name.

00:58:43.260 --> 00:58:45.640
<v Dave Jones>So, that's why I'm saying it's not really...

00:58:45.640 --> 00:58:49.180
<v Dave Jones>It hasn't been named with a trademark or anything.

00:58:49.180 --> 00:58:51.480
<v Dave Jones>But it's just the...

00:58:51.480 --> 00:58:57.380
<v Dave Jones>It has evolved as with all the hardware and all the other things that I've done has evolved over time.

00:58:57.520 --> 00:59:01.160
<v Dave Jones>And it has become this thing which runs on my Raspberry Pi.

00:59:01.400 --> 00:59:02.980
<v Dave Jones>And lots of other people actually use it too.

00:59:04.360 --> 00:59:06.860
<v Dave Jones>So, it's a free piece of software.

00:59:06.860 --> 00:59:13.880
<v Dave Jones>It's not binding you to any cloud or any other platform which, you know, we've seen a bunch come and go.

00:59:14.180 --> 00:59:15.840
<v Dave Jones>And, you know, now they're here.

00:59:15.960 --> 00:59:16.500
<v Dave Jones>They're great.

00:59:16.660 --> 00:59:18.120
<v Dave Jones>Everyone uses them.

00:59:18.440 --> 00:59:18.920
<v Dave Jones>They're promoted.

00:59:18.920 --> 00:59:19.240
<v Dave Jones>The new hot thing.

00:59:19.680 --> 00:59:21.680
<v Dave Jones>And then you never hear about them again.

00:59:22.100 --> 00:59:22.640
<v Dave Jones>So, you know...

00:59:22.640 --> 00:59:25.920
<v Chris Gammell>The arc of hardware is long and software is not.

00:59:26.080 --> 00:59:26.300
<v Dave Jones>Yeah.

00:59:26.300 --> 00:59:31.060
<v Dave Jones>So, and the idea for me to keep my data in someone else's cloud kind of seemed odd.

00:59:31.240 --> 00:59:33.060
<v Dave Jones>So, I just wanted to run my own thing.

00:59:33.080 --> 00:59:34.340
<v Dave Jones>Yeah, I mean, there's risk in that, right?

00:59:34.360 --> 00:59:34.960
<v Dave Jones>Some risk.

00:59:35.140 --> 00:59:43.680
<v Dave Jones>And, you know, I felt a little better having control over my own data and my own automation.

00:59:44.460 --> 00:59:47.520
<v Dave Jones>And, you know, if it fails on me, I can make it better.

00:59:47.660 --> 00:59:49.160
<v Dave Jones>I have control over that.

00:59:49.160 --> 00:59:56.060
<v Dave Jones>I don't depend on someone else addressing my issues and, you know, ending up owning my data in various ways.

00:59:56.300 --> 01:00:01.860
<v Dave Jones>And then changing privacy rules and how my data is handled and all that.

01:00:01.940 --> 01:00:03.500
<v Dave Jones>So, everything is on my own.

01:00:03.640 --> 01:00:05.160
<v Chris Gammell>Oh, that was a GDPR comment there, huh?

01:00:06.800 --> 01:00:10.180
<v Dave Jones>Yeah, well, what can I say?

01:00:11.140 --> 01:00:12.860
<v Chris Gammell>I started doing this.

01:00:12.940 --> 01:00:14.080
<v Chris Gammell>It changed some things, right?

01:00:14.140 --> 01:00:15.120
<v Chris Gammell>I mean, it changed some things.

01:00:15.200 --> 01:00:15.920
<v Chris Gammell>Sure, sure.

01:00:16.660 --> 01:00:17.260
<v Chris Gammell>That's great.

01:00:17.260 --> 01:00:18.740
<v Chris Gammell>So, I mean, I actually...

01:00:18.740 --> 01:00:21.640
<v Chris Gammell>I was in your shop there for a second.

01:00:21.740 --> 01:00:22.620
<v Chris Gammell>I couldn't get back out of it.

01:00:22.680 --> 01:00:25.000
<v Chris Gammell>But it seems like you do have a lot of user projects as well.

01:00:25.000 --> 01:00:33.680
<v Chris Gammell>So, like, a lot of great projects get started from, you know, automation of kitchen scales and plants and bikes and coffee makers, all that stuff.

01:00:33.820 --> 01:00:36.820
<v Chris Gammell>A lot of the things that I think a lot of people are getting started with.

01:00:37.420 --> 01:00:41.520
<v Chris Gammell>I mean, what do you suggest as a first project?

01:00:42.080 --> 01:00:46.200
<v Dave Jones>I think the mailbox is a pretty cool project.

01:00:46.200 --> 01:00:51.160
<v Dave Jones>So, you can just take a motion mode and program it with that sketch to make it into a mailbox.

01:00:52.580 --> 01:00:53.920
<v Dave Jones>And it's very useful, right?

01:00:54.080 --> 01:00:58.400
<v Dave Jones>You can actually get something out of it, not just bling some LEDs and, wow, that's so cool.

01:00:58.400 --> 01:01:03.040
<v Chris Gammell>You can even probably put it in your fridge and see if someone stole your cake, too, right?

01:01:03.120 --> 01:01:04.140
<v Chris Gammell>Not everybody has a mailbox.

01:01:04.140 --> 01:01:10.880
<v Dave Jones>Yeah, well, when I first started with the motion mode, it was for the mailbox, right?

01:01:10.940 --> 01:01:13.280
<v Dave Jones>That was my first, probably one of my first notes.

01:01:13.800 --> 01:01:18.380
<v Dave Jones>And I used magnetic sensors with a read switch or something.

01:01:19.140 --> 01:01:25.900
<v Dave Jones>And, you know, you had to get the right angle from the sensor to the magnet or otherwise it doesn't trigger.

01:01:25.900 --> 01:01:27.260
<v Dave Jones>And just a lot of issues.

01:01:27.720 --> 01:01:32.700
<v Dave Jones>The door for the mailbox could be left open or partially open and it just wasn't reliable.

01:01:32.880 --> 01:01:36.460
<v Dave Jones>So, I ended up just using a motion sensor because it works every time.

01:01:36.500 --> 01:01:39.480
<v Dave Jones>As long as nobody messes with your mailbox, there's no motion.

01:01:39.680 --> 01:01:40.900
<v Dave Jones>So, it's very accurate.

01:01:41.380 --> 01:01:48.240
<v Dave Jones>There's no dependence on wiring to external sensors or aligning with a magnet or anything like that.

01:01:48.240 --> 01:01:51.740
<v Dave Jones>So, that turned out, worked out very good.

01:01:51.900 --> 01:01:55.520
<v Dave Jones>And it's probably a very fun project as a starter.

01:01:55.900 --> 01:01:57.560
<v Chris Gammell>What about when things go wrong?

01:01:57.660 --> 01:02:00.040
<v Chris Gammell>So, I mean, I'm guessing you have to support a lot of your users.

01:02:00.260 --> 01:02:03.720
<v Chris Gammell>And with RF, it seems like there's a lot more that can go wrong.

01:02:03.820 --> 01:02:05.960
<v Chris Gammell>It's less you can be like, hey, get out your scope.

01:02:06.160 --> 01:02:12.940
<v Chris Gammell>So, how are you working with users or working yourself when things go wrong in the RF spectrum?

01:02:13.160 --> 01:02:17.040
<v Dave Jones>So, I'm trying to keep my site forum as my main support platform.

01:02:17.040 --> 01:02:28.520
<v Dave Jones>There's a lot of contribution from third-party users or independent users that use my hardware or just hang out there to share their projects and share their knowledge.

01:02:28.760 --> 01:02:30.160
<v Dave Jones>So, I'm very grateful for that.

01:02:30.160 --> 01:02:33.700
<v Dave Jones>So, they help a lot with answering questions.

01:02:34.080 --> 01:02:41.680
<v Dave Jones>And I also try to be active every day to make sure that people, you know, their questions are addressed.

01:02:41.820 --> 01:02:48.020
<v Dave Jones>And if they have any issues with my hardware, I can actually help them out and not just leave them out hanging.

01:02:48.020 --> 01:02:51.500
<v Dave Jones>So, I offer support through the forum.

01:02:51.660 --> 01:02:54.480
<v Dave Jones>And then if there's email, right?

01:02:54.540 --> 01:02:55.900
<v Dave Jones>There's the contact page.

01:02:55.900 --> 01:02:56.280
<v Dave Jones>Sure, sure.

01:02:56.300 --> 01:02:57.440
<v Dave Jones>People just contact me directly.

01:02:57.860 --> 01:03:01.640
<v Chris Gammell>But I meant more like, what are the steps that you kind of walk people through?

01:03:02.080 --> 01:03:04.280
<v Chris Gammell>So, I buy a Motino tomorrow.

01:03:04.360 --> 01:03:05.560
<v Chris Gammell>It's got an RFM69 on there.

01:03:05.960 --> 01:03:07.300
<v Chris Gammell>And I'm like, yeah, it's just not working.

01:03:07.620 --> 01:03:08.960
<v Chris Gammell>Like, is it like you'll step through?

01:03:09.080 --> 01:03:11.660
<v Chris Gammell>Is it like, is it a lot of pebcac?

01:03:11.780 --> 01:03:14.420
<v Chris Gammell>Or is there other actual RF issues that come up?

01:03:14.420 --> 01:03:14.980
<v Chris Gammell>You know what I mean?

01:03:15.020 --> 01:03:18.800
<v Chris Gammell>Like, I'm trying to get a feel for how hard is RF actually with all this stuff going on?

01:03:19.280 --> 01:03:21.460
<v Dave Jones>With the library, there's a bunch of examples.

01:03:21.460 --> 01:03:26.800
<v Dave Jones>So, that's probably the first step where people should go and see the examples, start with examples.

01:03:27.440 --> 01:03:29.220
<v Dave Jones>There's also a guide on my website.

01:03:29.720 --> 01:03:40.060
<v Dave Jones>And I try to go through all the relevant issues that have been popular over the years and where people have issues.

01:03:40.060 --> 01:03:45.100
<v Dave Jones>And try to address those things so that hopefully we narrow down on support time.

01:03:45.280 --> 01:03:49.220
<v Dave Jones>So, that I don't get, you know, how do I even get started type questions.

01:03:49.980 --> 01:03:51.860
<v Chris Gammell>So, maybe that's a good place for people to start as well.

01:03:52.080 --> 01:03:55.220
<v Chris Gammell>If they're thinking about getting into this, they could just go and check out the guide.

01:03:55.380 --> 01:03:57.920
<v Chris Gammell>Check out some of the different projects that are on there.

01:03:58.020 --> 01:04:01.040
<v Chris Gammell>I mean, I guess I'll link in the guide for the motion mode.

01:04:01.140 --> 01:04:03.740
<v Chris Gammell>Maybe that's a good place to, like you said, that's a good project to start with.

01:04:03.940 --> 01:04:07.940
<v Chris Gammell>So, maybe they could see all the things that they need to buy and have to get started.

01:04:07.940 --> 01:04:14.920
<v Dave Jones>Sure. And, you know, there's a lot more stuff on the internet relating to these radios as well.

01:04:15.040 --> 01:04:17.880
<v Dave Jones>So, there's lots of projects, you know.

01:04:18.720 --> 01:04:25.380
<v Chris Gammell>Yeah, I guess my concern with this kind of stuff is always like, okay, it doesn't work.

01:04:25.900 --> 01:04:29.040
<v Chris Gammell>I'm going to assume it's the radio.

01:04:29.200 --> 01:04:29.520
<v Chris Gammell>You know what I mean?

01:04:29.560 --> 01:04:34.620
<v Chris Gammell>But, like, my experience has always been like, well, usually it's like, no, you took the power up wrong.

01:04:34.620 --> 01:04:36.100
<v Chris Gammell>Or, you don't have enough power.

01:04:36.300 --> 01:04:37.980
<v Chris Gammell>Or, you didn't do A, B, and C.

01:04:38.060 --> 01:04:39.180
<v Chris Gammell>You didn't initialize it right.

01:04:39.280 --> 01:04:39.740
<v Chris Gammell>You know what I mean?

01:04:40.000 --> 01:04:40.180
<v Chris Gammell>Yep.

01:04:40.500 --> 01:04:45.820
<v Dave Jones>So, it's usually, most commonly, it's usually a setting for the radio.

01:04:46.700 --> 01:04:50.660
<v Dave Jones>Or a mismatch between what you're telling the hardware.

01:04:51.320 --> 01:04:54.980
<v Dave Jones>Or what you're using, what you're telling the sketch that your hardware is.

01:04:55.500 --> 01:04:57.280
<v Dave Jones>And it's not matching.

01:04:57.280 --> 01:04:57.460
<v Dave Jones>Okay.

01:04:58.160 --> 01:05:04.620
<v Dave Jones>So, obviously, if you use a 433 megahertz at the wrong frequency, it might still work.

01:05:04.700 --> 01:05:06.260
<v Dave Jones>It might still push out some signal.

01:05:06.460 --> 01:05:12.160
<v Dave Jones>But it'll be heavily filtered by that passive network of components.

01:05:12.160 --> 01:05:12.380
<v Dave Jones>Right.

01:05:12.380 --> 01:05:19.080
<v Dave Jones>Which is meant to, you know, help you out and narrow down only to the frequency that's intended to be used at.

01:05:19.080 --> 01:05:27.060
<v Dave Jones>And then there's that setting that distinguishes between the lower power modules and the higher power modules.

01:05:27.720 --> 01:05:37.740
<v Dave Jones>The HCW and HW need that extra radio call to tell the library, yeah, you're dealing with a higher power module.

01:05:37.880 --> 01:05:40.560
<v Dave Jones>And you have to call things a little bit different.

01:05:40.560 --> 01:05:47.620
<v Dave Jones>So, once you make that call, you know, it has to be done in the initializing staging of your sketch.

01:05:47.780 --> 01:05:48.300
<v Dave Jones>You're done.

01:05:48.580 --> 01:05:49.420
<v Dave Jones>It's the same.

01:05:49.620 --> 01:05:50.700
<v Dave Jones>But it has to be done.

01:05:50.760 --> 01:05:53.200
<v Dave Jones>Otherwise, your radio won't transmit anything.

01:05:53.320 --> 01:05:54.980
<v Dave Jones>It's just going to not work.

01:05:55.940 --> 01:05:56.100
<v Dave Jones>Got it.

01:05:56.100 --> 01:06:00.000
<v Dave Jones>And that's not, all of that is only valid for RFM69.

01:06:00.780 --> 01:06:07.880
<v Dave Jones>For RFM95, 96, and the lower, so the lower radios, they have a separate set of things.

01:06:07.880 --> 01:06:16.120
<v Dave Jones>Of course, you have to match the frequency and, you know, get your network ID right and all that.

01:06:16.220 --> 01:06:21.660
<v Dave Jones>But they don't have the power, the setting issue like the RFM69.

01:06:22.040 --> 01:06:25.280
<v Chris Gammell>Oh, because it's just a, I guess it's a different type of setting there, right?

01:06:25.300 --> 01:06:27.020
<v Dave Jones>It's like the window or whatever they call it.

01:06:27.380 --> 01:06:31.520
<v Dave Jones>Well, the RFM95 and 96, they only come in 20 dBm variants.

01:06:31.520 --> 01:06:37.200
<v Dave Jones>So, you don't have to worry about setting the right transmission settings for that.

01:06:37.880 --> 01:06:41.300
<v Chris Gammell>But it's pretty similar in terms of you kind of just set it up and you go, huh?

01:06:41.620 --> 01:06:41.980
<v Chris Gammell>Yeah.

01:06:42.060 --> 01:06:43.120
<v Chris Gammell>Otherwise, it's pretty similar.

01:06:43.480 --> 01:06:43.940
<v Chris Gammell>That's great.

01:06:44.720 --> 01:06:49.940
<v Chris Gammell>I mean, this seems like a really nice way to kind of get started into RF and talking between nodes.

01:06:50.080 --> 01:06:55.060
<v Chris Gammell>I mean, I've, other people that I've talked to in the past and they, you know, there's, there are some things out there, right?

01:06:55.080 --> 01:06:57.460
<v Chris Gammell>I know Zigbee was a big thing for XP, Zigbee, whatever.

01:06:57.460 --> 01:07:05.220
<v Chris Gammell>Like there's a lot of different modules in that space, but it seems like this is a good way to, to start at a really high level and then kind of dig your way down into it.

01:07:05.260 --> 01:07:10.100
<v Chris Gammell>And if you wanted to then eventually see like, oh, well, I can go look at the library and see what it's doing.

01:07:10.100 --> 01:07:14.160
<v Chris Gammell>And then, you know, maybe dig down a little bit deeper and implement the library myself.

01:07:14.440 --> 01:07:15.960
<v Chris Gammell>It seems like this would be a good way to do that.

01:07:16.160 --> 01:07:16.300
<v Chris Gammell>Sure.

01:07:16.400 --> 01:07:16.580
<v Chris Gammell>Yeah.

01:07:16.600 --> 01:07:21.640
<v Dave Jones>You could, you could get as hardcore as you can, as, as you want with, with the RF settings.

01:07:22.400 --> 01:07:23.400
<v Dave Jones>What is the library called?

01:07:23.700 --> 01:07:25.680
<v Dave Jones>The library is called RFM 69.

01:07:26.740 --> 01:07:27.220
<v Dave Jones>Oh, okay.

01:07:27.220 --> 01:07:40.100
<v Dave Jones>So if you go to, it's on GitHub and if you go to the Motino guide, which is at lowpowerlab.com slash Motino or just Motino.com, it'll land you on the same page.

01:07:42.300 --> 01:07:47.660
<v Dave Jones>If you go to, there's a section down at, on that page called programming and libraries.

01:07:47.660 --> 01:07:57.320
<v Dave Jones>So that's going to tell you all about how to set up your IDE and how to get libraries and how to get started on the right track.

01:07:57.340 --> 01:07:58.820
<v Dave Jones>And you've got a YouTube channel as well, it looks like.

01:07:59.060 --> 01:08:01.980
<v Dave Jones>So you can go check out some of the tutorials there.

01:08:02.180 --> 01:08:02.360
<v Dave Jones>Yep.

01:08:02.720 --> 01:08:11.660
<v Dave Jones>I try to keep it, you know, diverse so that people have various resources, both more static as in the form of guides or videos.

01:08:11.660 --> 01:08:29.140
<v Dave Jones>I put up some, some guides recently for, for the radios just to, to get people started with the, the main differences between these modules, how to differentiate between them, how to identify them and how to deal them, deal with them correctly.

01:08:29.400 --> 01:08:29.440
<v Dave Jones>Right.

01:08:30.000 --> 01:08:30.200
<v Chris Gammell>Yeah.

01:08:30.200 --> 01:08:33.600
<v Chris Gammell>Make sure you have the right one for you, whatever your application is too, I'm sure.

01:08:33.600 --> 01:08:34.040
<v Chris Gammell>Yeah.

01:08:34.040 --> 01:08:34.720
<v Dave Jones>Yeah.

01:08:35.100 --> 01:08:35.320
<v Dave Jones>Yeah.

01:08:35.360 --> 01:08:44.040
<v Dave Jones>So both in terms of firmware and hardware, how to help, help them identify which they should get.

01:08:45.160 --> 01:08:49.580
<v Dave Jones>I would probably recommend just going with RFM 69HCW.

01:08:51.080 --> 01:08:51.720
<v Dave Jones>Okay.

01:08:51.920 --> 01:08:52.300
<v Dave Jones>Why is that?

01:08:52.800 --> 01:09:00.580
<v Dave Jones>Well, it has the extra power of, you know, the, the, the W and the CW are 13 dBm.

01:09:00.580 --> 01:09:03.200
<v Dave Jones>So seven dBm difference, that's just quite a bit.

01:09:03.780 --> 01:09:09.460
<v Dave Jones>So in most cases, probably you don't need, need the low power.

01:09:10.480 --> 01:09:12.820
<v Dave Jones>And you can always dial down the higher power.

01:09:13.640 --> 01:09:14.260
<v Chris Gammell>Got it.

01:09:14.280 --> 01:09:14.500
<v Chris Gammell>Okay.

01:09:14.660 --> 01:09:14.960
<v Chris Gammell>Right.

01:09:15.060 --> 01:09:18.360
<v Chris Gammell>So, so optimize for power after you get it up and working that kind of idea.

01:09:18.360 --> 01:09:18.880
<v Dave Jones>Yeah.

01:09:19.160 --> 01:09:24.360
<v Dave Jones>And I think most of my nodes are HW or HCW.

01:09:24.360 --> 01:09:33.900
<v Dave Jones>I never really had a need or a point in time where I'm determining that, oh, this node has to really go down to a CW or a W.

01:09:33.900 --> 01:09:42.980
<v Dave Jones>Cause the extra HW is using so much more power and I need to get an extra, I don't know how many days or months from that battery.

01:09:43.100 --> 01:09:50.580
<v Dave Jones>You know, it's just, I'm trying to optimize and spend my energy where it's getting the most return.

01:09:50.580 --> 01:10:04.060
<v Dave Jones>And just standardize and, and spend my time trying to make sure that I sleep all my sensors and all the extra hardware that I have on a node rather than try to squeeze out a couple extra micro amps.

01:10:04.860 --> 01:10:04.980
<v Chris Gammell>Yeah.

01:10:05.020 --> 01:10:07.580
<v Chris Gammell>It's like that lowest, lowest hanging fruit kind of thing, right?

01:10:07.580 --> 01:10:11.040
<v Chris Gammell>Where you're solving the problems that are actually going to have the most impact on the battery.

01:10:11.220 --> 01:10:11.480
<v Chris Gammell>Yep.

01:10:11.480 --> 01:10:24.440
<v Chris Gammell>What is the, um, so, so you mentioned, we've talked a little bit about power and range and things like that, but what is, what is the expected range that you tell the users?

01:10:24.440 --> 01:10:31.620
<v Chris Gammell>Like, so if someone, someone's listening to this and they're like, oh, this sounds like this might be a good application or a good, a good tool for my application.

01:10:32.300 --> 01:10:34.900
<v Chris Gammell>What, what is like data rates you expect to get?

01:10:34.900 --> 01:10:41.980
<v Chris Gammell>And I know, I know these are all configurables, but like average data rate, average power of battery and like average distance you'd expect to get.

01:10:42.560 --> 01:10:44.980
<v Dave Jones>So again, it all depends on.

01:10:44.980 --> 01:10:47.380
<v Chris Gammell>I know there's so, I know there's so much stuff here, but let's stick to that.

01:10:47.480 --> 01:10:50.320
<v Chris Gammell>So like RF 69, RFM 69, right?

01:10:50.420 --> 01:10:52.060
<v Chris Gammell>You've got that high power version.

01:10:52.900 --> 01:10:54.360
<v Chris Gammell>Maybe we even take the battery out of that.

01:10:54.420 --> 01:10:57.200
<v Chris Gammell>We just say like, I, I want to go.

01:10:57.620 --> 01:10:59.640
<v Chris Gammell>So I come to you and I say, I want to go 20 miles.

01:10:59.680 --> 01:11:01.620
<v Chris Gammell>You're going to instead say, no, you can't go 20 miles.

01:11:01.660 --> 01:11:02.340
<v Chris Gammell>You can only go.

01:11:02.520 --> 01:11:02.880
<v Dave Jones>Yeah.

01:11:02.880 --> 01:11:05.820
<v Dave Jones>If you need 20 miles, you'll probably have to look at Laura.

01:11:06.660 --> 01:11:06.980
<v Chris Gammell>Okay.

01:11:07.240 --> 01:11:07.800
<v Dave Jones>And all right.

01:11:07.820 --> 01:11:08.220
<v Chris Gammell>That's good to know.

01:11:08.300 --> 01:11:08.400
<v Dave Jones>Yep.

01:11:08.520 --> 01:11:14.040
<v Dave Jones>And when we're talking about power figures here, I need to ask you, are you going to keep that radio listening all the time?

01:11:14.040 --> 01:11:21.020
<v Dave Jones>Because the listening part of the radio uses, you know, about 15, 14, 15, 16 milliamps.

01:11:21.320 --> 01:11:23.180
<v Dave Jones>That's a whole lot, you know, for battery.

01:11:23.560 --> 01:11:26.120
<v Dave Jones>So are you going to keep that on for any reason?

01:11:26.120 --> 01:11:32.260
<v Dave Jones>Well, your gateway is surely going to have it on because it's probably powered by main somewhere.

01:11:32.260 --> 01:11:35.180
<v Dave Jones>It's going to have a, or a beefier battery.

01:11:35.360 --> 01:11:42.560
<v Dave Jones>So you're not going to worry about power at your gateway, but your node, is that going to have your listening part on all the time?

01:11:42.720 --> 01:11:43.880
<v Dave Jones>Well, probably not, right?

01:11:43.900 --> 01:11:56.120
<v Dave Jones>You're just going to have motion and only going to transmit when motion happens, or you're going to measure temperature and you're going to only going to transmit temperature every so often, every couple of minutes or whatever.

01:11:56.120 --> 01:12:02.660
<v Dave Jones>So you're transmitting part of the radio is only going to be on for a very short amount of time, a couple of milliseconds.

01:12:03.600 --> 01:12:09.180
<v Dave Jones>And then it's going to turn itself off or the MCU is going to turn the radio off completely.

01:12:09.180 --> 01:12:10.460
<v Dave Jones>Just going to put it to sleep.

01:12:10.660 --> 01:12:13.020
<v Dave Jones>That's how you achieve long battery life.

01:12:13.020 --> 01:12:17.520
<v Dave Jones>The radio, like all the other peripherals in your node have to be asleep.

01:12:17.620 --> 01:12:23.520
<v Dave Jones>Otherwise, you know, even one milliamp is a ton of power for a battery operated node.

01:12:24.340 --> 01:12:24.440
<v Dave Jones>Sure.

01:12:24.640 --> 01:12:24.800
<v Dave Jones>Yeah.

01:12:24.840 --> 01:12:32.660
<v Dave Jones>But to get back to your original question, what you can expect in terms of range, it's probably one of the first questions that people ask.

01:12:32.660 --> 01:12:39.860
<v Dave Jones>Well, what's the range to even come close to giving an accurate answer?

01:12:40.740 --> 01:12:49.640
<v Dave Jones>We, you have to realize that when it comes to obstacles and the medium where you transmit, right?

01:12:49.720 --> 01:12:51.600
<v Dave Jones>It's going to be air here on earth.

01:12:52.380 --> 01:12:53.560
<v Dave Jones>It could be water.

01:12:53.640 --> 01:12:55.700
<v Dave Jones>I suppose there's applications for that.

01:12:55.840 --> 01:13:01.000
<v Dave Jones>I know someone's using them in caves, you know, and they have probes underwater to measure data.

01:13:01.000 --> 01:13:11.440
<v Dave Jones>But let's just assume that we're in air and to even come close to being accurate, you're going to have to compare apples to apples.

01:13:11.660 --> 01:13:14.800
<v Dave Jones>Meaning you try to eliminate obstacles.

01:13:15.220 --> 01:13:20.140
<v Dave Jones>You're not going to transmit in rain or in very humid air.

01:13:20.980 --> 01:13:23.120
<v Dave Jones>And it's going to be line of sight, right?

01:13:23.280 --> 01:13:26.740
<v Dave Jones>So to get a feel of what you can expect.

01:13:26.740 --> 01:13:27.840
<v Chris Gammell>We made the boundary box.

01:13:28.240 --> 01:13:28.560
<v Chris Gammell>Right.

01:13:28.740 --> 01:13:30.800
<v Dave Jones>And then you have to worry about antennas.

01:13:30.800 --> 01:13:32.000
<v Dave Jones>What antennas are you going to use?

01:13:32.040 --> 01:13:35.100
<v Dave Jones>Are you just going to use the monopole wire, which is a very good option.

01:13:35.300 --> 01:13:36.660
<v Dave Jones>Very, very performant.

01:13:36.820 --> 01:13:42.220
<v Dave Jones>I think all my nodes, except my gateway, have wires, wire monopoles.

01:13:42.420 --> 01:13:44.920
<v Dave Jones>It's a very simple antenna, just a piece of wire that...

01:13:44.920 --> 01:13:46.100
<v Dave Jones>Piece of wire at a certain distance, right?

01:13:46.140 --> 01:13:47.120
<v Dave Jones>It's a quarter wavelength.

01:13:48.240 --> 01:13:52.020
<v Dave Jones>So the length of the wire is a quarter wave of the actual transmitting frequency.

01:13:52.020 --> 01:13:58.000
<v Dave Jones>And so you're going to have to have equal antennas or the same antennas.

01:13:58.360 --> 01:14:07.780
<v Dave Jones>And they have to be properly oriented to get the maximum benefit from them being oriented right.

01:14:08.000 --> 01:14:14.960
<v Dave Jones>Otherwise, if they're orthogonal or things like that, we're getting into RF stuff that's a bit more hairy.

01:14:14.960 --> 01:14:18.200
<v Dave Jones>But they should be oriented the same.

01:14:19.580 --> 01:14:21.980
<v Dave Jones>And so you have line of sight.

01:14:22.640 --> 01:14:24.320
<v Dave Jones>Make sure your antennas are the same.

01:14:24.460 --> 01:14:25.720
<v Dave Jones>They're oriented the same way.

01:14:26.600 --> 01:14:34.020
<v Dave Jones>And you're probably going to expect from the RFM69 with the default settings of 55.5.

01:14:34.120 --> 01:14:35.620
<v Chris Gammell>This is a lot of buildup at this point, man.

01:14:35.620 --> 01:14:36.480
<v Chris Gammell>I'm really nervous.

01:14:36.720 --> 01:14:37.320
<v Chris Gammell>I'm like, really...

01:14:37.320 --> 01:14:37.680
<v Chris Gammell>Yeah, see?

01:14:37.860 --> 01:14:38.460
<v Chris Gammell>It's really...

01:14:38.460 --> 01:14:38.740
<v Chris Gammell>What's it going to be?

01:14:39.300 --> 01:14:40.120
<v Chris Gammell>What's it going to be?

01:14:41.720 --> 01:14:42.840
<v Chris Gammell>It's three meters.

01:14:43.680 --> 01:14:47.480
<v Chris Gammell>It's probably going to be a couple hundred meters at the least.

01:14:48.860 --> 01:14:49.340
<v Chris Gammell>So that's...

01:14:49.340 --> 01:14:49.460
<v Chris Gammell>That's great.

01:14:49.540 --> 01:14:49.700
<v Chris Gammell>Yeah.

01:14:50.040 --> 01:14:51.160
<v Chris Gammell>Yeah, that's good to know, right?

01:14:51.180 --> 01:14:54.280
<v Chris Gammell>So it's somewhere between 100 meters and a couple K.

01:14:54.440 --> 01:14:55.920
<v Chris Gammell>What's the longest you've seen?

01:14:56.340 --> 01:14:58.760
<v Chris Gammell>In my own use or in my user's use?

01:14:58.760 --> 01:14:59.860
<v Chris Gammell>Just even hearing about it.

01:14:59.860 --> 01:15:00.500
<v Chris Gammell>Yeah, anecdotally.

01:15:00.500 --> 01:15:09.220
<v Dave Jones>I think in my email to you, I mentioned that there was one user that used this RFM69 module in high altitude ballooning.

01:15:10.640 --> 01:15:12.500
<v Dave Jones>And, you know, ground to...

01:15:13.320 --> 01:15:17.360
<v Dave Jones>Actually, the balloon was transmitting down to ground where his position was.

01:15:17.560 --> 01:15:19.940
<v Dave Jones>And it was almost...

01:15:19.940 --> 01:15:23.000
<v Dave Jones>So it was over 160 kilometers.

01:15:23.940 --> 01:15:24.800
<v Dave Jones>I want to say kilometers.

01:15:24.920 --> 01:15:25.900
<v Dave Jones>I don't think it was miles.

01:15:25.900 --> 01:15:30.620
<v Dave Jones>But it was really long range.

01:15:31.480 --> 01:15:32.440
<v Dave Jones>And he achieved that with...

01:15:32.440 --> 01:15:34.060
<v Chris Gammell>I thought you said that was Laura.

01:15:34.280 --> 01:15:35.540
<v Chris Gammell>I didn't think that was an RFM...

01:15:35.540 --> 01:15:37.100
<v Dave Jones>No, it was RFM69.

01:15:37.580 --> 01:15:37.800
<v Dave Jones>Yep.

01:15:37.960 --> 01:15:38.280
<v Dave Jones>It was.

01:15:38.360 --> 01:15:38.480
<v Dave Jones>Okay.

01:15:38.560 --> 01:15:40.900
<v Dave Jones>And it was at some extreme...

01:15:40.900 --> 01:15:44.560
<v Dave Jones>Extremely tweaked settings, like 600 baud.

01:15:45.500 --> 01:15:45.540
<v Dave Jones>Right.

01:15:45.540 --> 01:15:46.060
<v Dave Jones>Exactly.

01:15:46.060 --> 01:15:58.680
<v Dave Jones>You know, temperature compensated oscillator settings and some crazy tweaks that I haven't encountered in other applications or from anyone else.

01:15:58.800 --> 01:16:02.660
<v Dave Jones>But you can, you know, you can achieve quite a long range with these in line of sight.

01:16:02.840 --> 01:16:08.460
<v Chris Gammell>That's like the QRP contesting of the RFM69, it sounds like.

01:16:08.700 --> 01:16:13.160
<v Dave Jones>That's the extreme end example, right?

01:16:13.160 --> 01:16:19.160
<v Dave Jones>On the normal side of things, you can expect up to...

01:16:19.160 --> 01:16:21.740
<v Dave Jones>I probably heard a mile or two.

01:16:22.340 --> 01:16:24.720
<v Dave Jones>There's a couple of threads in the forum.

01:16:24.860 --> 01:16:33.020
<v Dave Jones>If you go in the Motino forum, main forum, there's some range threads.

01:16:34.020 --> 01:16:35.640
<v Dave Jones>There are sticky threads.

01:16:36.540 --> 01:16:38.160
<v Dave Jones>And I see one...

01:16:38.160 --> 01:16:44.000
<v Chris Gammell>It's almost like you need like a Venn diagram of like what technology you're really looking at.

01:16:44.100 --> 01:16:50.040
<v Chris Gammell>You know, and it sounds like this is in that, you know, one meter to one kilometer, like, is a good...

01:16:50.040 --> 01:16:54.220
<v Chris Gammell>I mean, that's a good range to know that you're not going to be like, I need to go 100K.

01:16:54.360 --> 01:16:56.720
<v Chris Gammell>It's like, nope, sorry, you know, don't even bother, right?

01:16:56.800 --> 01:16:57.020
<v Chris Gammell>Yeah.

01:16:57.020 --> 01:17:00.160
<v Chris Gammell>And it's like, I'm going to go, I need to go one centimeter.

01:17:00.300 --> 01:17:03.480
<v Chris Gammell>It's like, well, yeah, I guess you'll get the low power, but there's a ton of options at that point.

01:17:03.560 --> 01:17:09.680
<v Chris Gammell>I mean, one centimeter, you might want to do like, you know, even with the contactless NFC type stuff.

01:17:09.760 --> 01:17:10.020
<v Chris Gammell>You know what I mean?

01:17:10.040 --> 01:17:16.080
<v Chris Gammell>Like there's always just all these different ranges, but then the trade-offs are battery and cost and all of the other things.

01:17:16.200 --> 01:17:17.920
<v Chris Gammell>So it sounds like this is pretty flexible though.

01:17:17.920 --> 01:17:18.180
<v Dave Jones>Sure.

01:17:18.860 --> 01:17:29.480
<v Dave Jones>So I'm trying to cater to 99.5% of the use cases that are common and where this is useful.

01:17:29.500 --> 01:17:30.700
<v Chris Gammell>Especially for the home, it sounds like.

01:17:30.700 --> 01:17:33.260
<v Dave Jones>For the home and way beyond.

01:17:33.260 --> 01:17:48.520
<v Dave Jones>I mean, industrial, commercial, farming, and all kinds of interesting use cases where range is less important than other important aspects of what these areas can do.

01:17:49.000 --> 01:17:49.060
<v Dave Jones>Right.

01:17:49.120 --> 01:17:51.440
<v Dave Jones>So you have a beekeeping operation.

01:17:52.700 --> 01:17:58.100
<v Dave Jones>You're not going to worry that, you know, your gateway is going to be somewhere around, right?

01:17:58.140 --> 01:17:59.560
<v Dave Jones>It's not going to be miles away.

01:17:59.560 --> 01:18:07.300
<v Dave Jones>So range is less important than making sure that these things are reliable, that they can run on batteries for a long time.

01:18:07.360 --> 01:18:10.760
<v Dave Jones>So you don't have to be out there all the time and things like that.

01:18:10.760 --> 01:18:17.220
<v Dave Jones>So, yeah, you know, I would say people shouldn't get stuck up on the range question.

01:18:17.900 --> 01:18:21.120
<v Dave Jones>These can be optimized for range, for very long range.

01:18:21.380 --> 01:18:28.620
<v Dave Jones>And then if you really need very, very long range, then look at LoRa because that's optimized for that.

01:18:29.340 --> 01:18:29.460
<v Chris Gammell>Yeah.

01:18:29.560 --> 01:18:29.840
<v Chris Gammell>Okay.

01:18:30.220 --> 01:18:30.440
<v Chris Gammell>Okay.

01:18:30.460 --> 01:18:31.040
<v Chris Gammell>That's good to know.

01:18:31.300 --> 01:18:31.420
<v Chris Gammell>Yeah.

01:18:31.440 --> 01:18:37.760
<v Chris Gammell>And I think that's really, you know, like from my perspective, at least, and I, you know, ascribe my qualities to some of the Empire listeners.

01:18:38.160 --> 01:18:40.460
<v Chris Gammell>It's just like, I want to know what's kind of out there.

01:18:41.220 --> 01:18:46.560
<v Chris Gammell>I'm not necessarily going to try everything, but when I get into a problem, I want to know what solutions are possible.

01:18:46.560 --> 01:18:50.360
<v Chris Gammell>And it sounds like this is a good, flexible one for a lot of that stuff.

01:18:50.360 --> 01:18:52.180
<v Chris Gammell>Yeah, there's definitely a lot of flexibility here.

01:18:52.180 --> 01:18:57.840
<v Chris Gammell>So, I guess another question would be, what would be the reason to use this over LoRa?

01:18:57.940 --> 01:19:00.560
<v Chris Gammell>Is it just simplicity at this point or cost?

01:19:00.660 --> 01:19:01.700
<v Chris Gammell>Or what is that difference?

01:19:01.700 --> 01:19:11.700
<v Dave Jones>For me personally, convenience and the fact that it works and I'm already set up with RFM69.

01:19:12.040 --> 01:19:14.040
<v Dave Jones>So, I don't really have a reason to upgrade.

01:19:14.580 --> 01:19:19.100
<v Dave Jones>LoRa is more costly per transceiver module.

01:19:19.100 --> 01:19:22.420
<v Dave Jones>So, the cost is higher for those.

01:19:23.280 --> 01:19:24.860
<v Dave Jones>And, yeah, complexity.

01:19:25.580 --> 01:19:27.600
<v Dave Jones>There's more complexity with LoRa.

01:19:27.720 --> 01:19:31.820
<v Dave Jones>Or at least, you know, libraries make it easy for LoRa as well.

01:19:32.300 --> 01:19:32.580
<v Dave Jones>Sure.

01:19:32.880 --> 01:19:37.020
<v Dave Jones>But, you know, LoRa is inherently more complex as a protocol.

01:19:37.660 --> 01:19:37.820
<v Chris Gammell>Okay.

01:19:38.120 --> 01:19:38.820
<v Chris Gammell>Yeah, it's good to know.

01:19:38.960 --> 01:19:39.060
<v Chris Gammell>Yeah.

01:19:39.100 --> 01:19:42.000
<v Chris Gammell>I mean, like, I think that is the, you know, we've been talking about LoRa a lot here.

01:19:42.800 --> 01:19:45.300
<v Chris Gammell>Is there more than one vendor for the RFM69 chip?

01:19:45.300 --> 01:19:49.860
<v Chris Gammell>I mean, like, who, so that's, you said it was a SILabs chip?

01:19:50.780 --> 01:19:52.460
<v Dave Jones>So, that was for RFM12B.

01:19:53.020 --> 01:19:56.880
<v Dave Jones>The chips in the RFM69 are made by Semtek, as far as I know.

01:19:57.780 --> 01:19:58.360
<v Dave Jones>Oh, they are too.

01:19:58.440 --> 01:19:58.560
<v Dave Jones>Okay.

01:19:58.580 --> 01:20:02.740
<v Dave Jones>They're custom packaged by Hope RF and that's how they make their margins.

01:20:03.600 --> 01:20:03.940
<v Dave Jones>Got it.

01:20:04.080 --> 01:20:05.180
<v Dave Jones>You know, they're made in China.

01:20:05.440 --> 01:20:10.320
<v Dave Jones>Not sure why these can't be made in the US.

01:20:10.320 --> 01:20:14.760
<v Dave Jones>Maybe because of pricing and maybe because the Chinese can just squeeze that much more.

01:20:15.300 --> 01:20:19.940
<v Dave Jones>Uh, out of them and sell them at, you know, cheaper prices, cheaper labor and all that.

01:20:20.140 --> 01:20:22.280
<v Dave Jones>Uh, I'm not sure how tariffs are going to impact that.

01:20:22.800 --> 01:20:26.360
<v Dave Jones>But, uh, I would like one day to see these being made in the US.

01:20:26.460 --> 01:20:29.240
<v Dave Jones>I actually had an attempt to, to make these on my own.

01:20:29.600 --> 01:20:30.000
<v Dave Jones>Um.

01:20:30.540 --> 01:20:31.020
<v Dave Jones>Interesting.

01:20:31.160 --> 01:20:31.300
<v Dave Jones>Yeah.

01:20:31.320 --> 01:20:31.520
<v Dave Jones>Okay.

01:20:32.060 --> 01:20:32.260
<v Dave Jones>Yeah.

01:20:32.260 --> 01:20:35.760
<v Dave Jones>So, I made an, uh, a variant of, uh, HHW.

01:20:36.120 --> 01:20:37.880
<v Dave Jones>Of the RFM69HW.

01:20:37.880 --> 01:20:40.500
<v Dave Jones>And I was able to make it work, right?

01:20:40.520 --> 01:20:46.840
<v Dave Jones>It worked and it was, uh, it was just more expensive to make it here in the US.

01:20:46.840 --> 01:20:49.520
<v Dave Jones>So, and it uses all four or two components.

01:20:49.840 --> 01:20:53.200
<v Dave Jones>That's a little bit more tricky to, to pick and place.

01:20:53.700 --> 01:21:00.400
<v Dave Jones>And, uh, you know, it's just not cost effective to me for, for me to buy those chips, the transceiver

01:21:00.400 --> 01:21:06.340
<v Dave Jones>chips and the crystal and everything else from, from DigiKey, you know, from us distributors

01:21:06.340 --> 01:21:11.780
<v Dave Jones>is just the component costs, uh, almost exceed.

01:21:12.000 --> 01:21:13.140
<v Dave Jones>Versus, versus buying the mods.

01:21:13.140 --> 01:21:14.200
<v Dave Jones>Yeah, exactly.

01:21:14.480 --> 01:21:14.620
<v Dave Jones>Yeah.

01:21:14.800 --> 01:21:16.000
<v Dave Jones>So, it was not worth it.

01:21:16.440 --> 01:21:21.880
<v Chris Gammell>I've looked up the RFM65, or 95 rather, the RFM95 module in the past.

01:21:21.940 --> 01:21:23.460
<v Chris Gammell>It's not FCC certified or anything like that.

01:21:23.500 --> 01:21:25.480
<v Chris Gammell>It is just a, a convenience thing, right?

01:21:25.660 --> 01:21:32.280
<v Dave Jones>Well, I think they actually ran some tests in, on their own in China, just to be able

01:21:32.280 --> 01:21:37.280
<v Dave Jones>to say that they meet, uh, the FCC guidelines.

01:21:38.120 --> 01:21:38.560
<v Dave Jones>Sure, yeah.

01:21:38.760 --> 01:21:40.680
<v Dave Jones>You know, they meet those limits and things like that.

01:21:41.080 --> 01:21:41.320
<v Chris Gammell>Right.

01:21:41.320 --> 01:21:44.820
<v Chris Gammell>You can't put in a product though and be like, I'm certified, this is a pre-certified

01:21:44.820 --> 01:21:45.140
<v Chris Gammell>module.

01:21:45.220 --> 01:21:45.740
<v Chris Gammell>It's not like that.

01:21:45.820 --> 01:21:46.080
<v Dave Jones>Yeah.

01:21:46.240 --> 01:21:51.700
<v Dave Jones>You know, there's, uh, even if you put them in a product, you're still gonna, I don't

01:21:51.700 --> 01:21:55.040
<v Dave Jones>think they have modular certification at this point.

01:21:55.120 --> 01:21:58.700
<v Dave Jones>I haven't seen any, any FCC ID for them.

01:21:59.460 --> 01:22:04.020
<v Dave Jones>Um, and even if you end up putting them in a product, you're going to have to end up doing

01:22:04.020 --> 01:22:06.920
<v Dave Jones>FCC cert on your whole product as a whole.

01:22:06.920 --> 01:22:12.600
<v Dave Jones>Of course, having a modular cert would help, but you're still gonna be, you know, spending

01:22:12.600 --> 01:22:13.560
<v Dave Jones>time and money on that.

01:22:14.040 --> 01:22:14.080
<v Chris Gammell>Yeah.

01:22:14.100 --> 01:22:17.520
<v Chris Gammell>It seems like it's more of a convenient thing to get it out in the world and, and try this

01:22:17.520 --> 01:22:18.420
<v Chris Gammell>thing to get it working.

01:22:18.520 --> 01:22:18.640
<v Chris Gammell>Right.

01:22:18.720 --> 01:22:18.880
<v Dave Jones>Yeah.

01:22:19.040 --> 01:22:21.920
<v Chris Gammell>Well, where can people find out more about you and find out more about low power lab?

01:22:21.920 --> 01:22:24.240
<v Dave Jones>Uh, at low power lab.com.

01:22:25.140 --> 01:22:29.920
<v Dave Jones>Uh, I have a YouTube channel, try to post things, uh, from time to time.

01:22:30.160 --> 01:22:35.780
<v Dave Jones>Um, very busy in general, but, um, that's one other avenue where I post updates.

01:22:35.780 --> 01:22:37.620
<v Dave Jones>The blog is at low power lab.com.

01:22:37.620 --> 01:22:40.480
<v Dave Jones>The, the guide is at low power lab.com slash guide.

01:22:40.480 --> 01:22:43.120
<v Dave Jones>And then the shop is at low power lab.com slash shop.

01:22:43.360 --> 01:22:43.840
<v Chris Gammell>Cool.

01:22:43.920 --> 01:22:45.440
<v Chris Gammell>Any tweeting, tweeting in your future?

01:22:45.720 --> 01:22:46.720
<v Dave Jones>Well, not so much.

01:22:46.720 --> 01:22:49.740
<v Dave Jones>I guess I, I tweet when I post updates.

01:22:49.740 --> 01:22:52.740
<v Dave Jones>Uh, got it, but people can use it as a feed of sorts.

01:22:53.040 --> 01:22:53.180
<v Dave Jones>Yeah.

01:22:53.240 --> 01:22:53.500
<v Chris Gammell>Yeah.

01:22:53.860 --> 01:22:58.640
<v Chris Gammell>And people can, first project they can do is build an RFM 69, uh, that, uh, alerts them.

01:22:59.100 --> 01:23:03.940
<v Chris Gammell>The Raspberry Pi gets the feed update, goes over an RFM 69, goes a little flag that pops up

01:23:03.940 --> 01:23:06.080
<v Chris Gammell>and then they, they know that you've posted a new video maybe.

01:23:06.080 --> 01:23:06.320
<v Dave Jones>Yeah.

01:23:08.220 --> 01:23:08.620
<v Dave Jones>Yep.

01:23:08.640 --> 01:23:09.180
<v Dave Jones>That's about it.

01:23:09.240 --> 01:23:13.200
<v Dave Jones>Unfortunately, I'm not very, uh, socially present on the internet.

01:23:13.200 --> 01:23:14.920
<v Dave Jones>I just, uh, don't have the time for that.

01:23:15.000 --> 01:23:19.640
<v Dave Jones>Uh, you know, my whole time is, is trying to, uh, be balanced between, uh,

01:23:19.740 --> 01:23:20.740
<v Dave Jones>family and work.

01:23:20.840 --> 01:23:22.320
<v Dave Jones>So that takes my whole time.

01:23:22.660 --> 01:23:22.740
<v Chris Gammell>Yeah.

01:23:22.860 --> 01:23:25.060
<v Chris Gammell>Making hardware and making, making family happy.

01:23:25.080 --> 01:23:26.520
<v Chris Gammell>That's a good, that's a good balance right there though.

01:23:26.580 --> 01:23:26.800
<v Chris Gammell>Yeah.

01:23:27.440 --> 01:23:27.760
<v Chris Gammell>Awesome.

01:23:27.820 --> 01:23:28.840
<v Chris Gammell>Well, thanks Felix for being on.

01:23:28.900 --> 01:23:29.920
<v Chris Gammell>And I really, I'm excited.

01:23:29.980 --> 01:23:33.160
<v Chris Gammell>I hope, I hope people will go and check it out and, uh, try out, try out the Motinos

01:23:33.160 --> 01:23:33.900
<v Chris Gammell>and all your products.

01:23:33.900 --> 01:23:35.440
<v Chris Gammell>That sounds like a great starting point.

01:23:35.540 --> 01:23:35.740
<v Dave Jones>Yep.

01:23:35.820 --> 01:23:36.100
<v Dave Jones>Definitely.

01:23:36.320 --> 01:23:36.540
<v Dave Jones>Yeah.

01:23:36.560 --> 01:23:37.080
<v Dave Jones>Thanks a lot.

01:23:37.120 --> 01:23:38.300
<v Dave Jones>It was my pleasure to be on your show.

01:23:38.860 --> 01:23:39.100
<v Chris Gammell>All right.

01:23:39.100 --> 01:23:39.680
<v Chris Gammell>We'll talk to you soon.

01:23:39.900 --> 01:23:40.180
<v Dave Jones>All right.

01:23:40.240 --> 01:23:40.520
<v Dave Jones>Take care.

01:23:40.520 --> 01:23:40.660
<v Dave Jones>Bye.

01:23:40.660 --> 01:23:40.660
<v Speaker ?>

01:23:40.660 --> 01:23:40.660
<v Speaker ?>

01:23:40.660 --> 01:23:40.660
<v Speaker ?>

01:23:40.660 --> 01:23:40.660
<v Speaker ?>

01:23:40.660 --> 01:23:40.660
<v Speaker ?>

01:23:40.660 --> 01:23:42.660
<v Speaker ?>Bye.

01:23:42.660 --> 01:23:42.660
<v Speaker ?>

01:23:42.660 --> 01:23:44.660
<v Speaker ?>Bye.

01:23:44.660 --> 01:23:44.660
<v Speaker ?>

01:23:44.660 --> 01:23:44.660
<v Speaker ?>

01:23:44.660 --> 01:23:46.660
<v Speaker ?>Bye.

01:23:46.660 --> 01:23:55.580
<v Speaker ?>Bye.

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:55.580
<v Speaker ?>

01:23:55.580 --> 01:23:59.580
<v Speaker ?>x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x
