Okay, we're back again with a little demo of telemetry metano. Now, so here we have our thing, we're going to start up ground control. And we start, we see that serial is okay, that means the radio is connected, but we have no information about the 3.3s and no data connection, no data coming in. So now if we start, major Tom, who's running up there in the drone, up, we immediately discover that D3s has been located, and data is now coming in. So we'll let this come in for a little while. We can see now we receive one complete waiting for 17 bytes over here. We send the out byte of seven, that means that everything is good, sent it again. We got some data coming in. Okay, now what happens if major Tom crashes, literally are figuratively. So we crashed, we don't have ways to tell him he's not running but takes a few minutes, well, a few seconds for this ground station to realize it because it's only expecting data every 10 seconds or so. So we have to give it a few minutes, a few seconds for it to realize that there's something wrong, but it will realize that there is something wrong. And oh, there we go. See now it tells us the D3O s is not okay and data is not okay and there's been an incoming data failure at that time. Every time out or so, it will continue to repeat that little message. But now, suppose that major Tom recovers and he's flying around again. What happens? Oh, it recovers. Yes, it recovers. Simply recovers and everything is cool and everything is fine. But if major Tom crashes again, of course, the same thing happens. That's how telemetry works. I don't know if that's an advantage or not. But there you go. There you go. See how there's no more major Tom, there's no more D3s and no more data. But as soon as major Tom starts up, he finds a D3s and everything's okay but data is still not available. Up, there's some data. There we go. Everything's okay. Hope you enjoy that. Bye.