1
00:00:00,080 --> 00:00:07,520
as you can probably imagine time is very important when it comes to computers you

2
00:00:05,600 --> 00:00:11,200
want your computer to be in time especially if you have more than one

3
00:00:09,240 --> 00:00:15,679
computer say you have a thousand computers and you want to like do stuff

4
00:00:13,559 --> 00:00:21,039
across all of them well they better be in time sync and it's not really a

5
00:00:17,760 --> 00:00:24,640
problem that we have but when I saw this

6
00:00:21,039 --> 00:00:27,279
product the time beat time card mini and

7
00:00:24,640 --> 00:00:31,560
the other one in here this one called is called the g0 KK I don't know if you're

8
00:00:29,679 --> 00:00:35,719
supposed to call call it gawk I probably should have asked them how to pronounce

9
00:00:33,160 --> 00:00:41,280
it but it doesn't matter it was just too cool to not check out I've never played

10
00:00:37,960 --> 00:00:42,520
with one of these this guy right here

11
00:00:41,280 --> 00:00:47,680
the gawk one and this one as you could probably

12
00:00:45,239 --> 00:00:52,280
guess is the time card mini you may or may not be aware but basically every

13
00:00:49,640 --> 00:00:56,199
computer on the planet I think I imagine phones have them but definitely like

14
00:00:54,079 --> 00:01:00,800
your gaming computer on its motherboard will have something called a realtime

15
00:00:57,840 --> 00:01:05,040
clock usually the clocks on computer are not super accurate for example the

16
00:01:03,320 --> 00:01:09,520
real-time clock in your average computer will drift multiple seconds per day for

17
00:01:07,680 --> 00:01:16,439
example this little add-on chip right here can hold time down to 0.03 seconds

18
00:01:13,280 --> 00:01:18,360
per year which is very accurate let's

19
00:01:16,439 --> 00:01:22,400
focus on the time card mini for now because the actual bones of these two

20
00:01:20,560 --> 00:01:28,400
products are pretty much the same you've got a Raspberry Pi compute module

21
00:01:25,119 --> 00:01:31,159
4 we've got a little spacer board on the

22
00:01:28,400 --> 00:01:38,479
back but this is the important part this is the time teller right here you can

23
00:01:33,439 --> 00:01:41,320
see the ublock Lea M8 F0 it's a GPS chip

24
00:01:38,479 --> 00:01:47,079
so what this board basically does is connects to GPS glow Nas Galileo

25
00:01:44,079 --> 00:01:50,759
satellites gets very accurate time data

26
00:01:47,079 --> 00:01:53,079
from them and then outputs it through

27
00:01:50,759 --> 00:01:57,119
these pins to our little Raspberry Pi and then we've got two little spots over

28
00:01:54,399 --> 00:02:03,880
here for add-on modules these uh you can put little chips on them and this chip

29
00:01:59,280 --> 00:02:08,080
the SI T 5811 can hold one part per

30
00:02:03,880 --> 00:02:11,840
billion accuracy for up to 8 hours in

31
00:02:08,080 --> 00:02:14,120
terms of the rest of IO it has USB here

32
00:02:11,840 --> 00:02:17,720
it's got an SD card slot here bunch of dip switches primarily used for setup

33
00:02:16,680 --> 00:02:23,519
you've got your connection points for the raspy the full set of GPO pins for

34
00:02:20,959 --> 00:02:30,360
the raspy which is super nice an antenna connection USB on the- go connection two

35
00:02:27,120 --> 00:02:32,840
type-c USBS and Ethernet now you would

36
00:02:30,360 --> 00:02:37,040
use this Ethernet to well provide internet to the Raspberry Pi and also to

37
00:02:34,720 --> 00:02:41,879
send your time signaling out um as you can imagine it's a little weird to be

38
00:02:39,120 --> 00:02:46,640
plugging a computer into a computer right this is a PCIe card why would you

39
00:02:43,959 --> 00:02:51,640
plug this computer into your other computer the function of this is

40
00:02:48,800 --> 00:02:57,000
literally just to give power it's basically so you can add a very powerful

41
00:02:54,920 --> 00:03:01,080
very accurate time server to your existing infrastructure without having

42
00:02:59,239 --> 00:03:05,000
to put like a a whole new rack Unit in or like duct tape it to the side of your

43
00:03:03,000 --> 00:03:09,720
rack or whatever aside from these just being cool the reason I asked for them

44
00:03:07,159 --> 00:03:13,040
was to make a Time server at Linus Media Group for us the thing that kind of

45
00:03:11,159 --> 00:03:18,319
sparked this idea is we were setting up a cluster of computers using proxmox and

46
00:03:15,920 --> 00:03:22,040
proxmox requires that the time sync be within about 5 milliseconds you can

47
00:03:20,280 --> 00:03:26,040
achieve that pretty easily by having any local time server for instance most

48
00:03:24,000 --> 00:03:30,040
routers will let you enable an ntp server that runs on them which is what

49
00:03:27,560 --> 00:03:35,239
we did and it worked totally fine but you know it's me I want to do it like

50
00:03:32,720 --> 00:03:38,560
fancy or silly and that's what we're going to do with these do you think that

51
00:03:36,959 --> 00:03:45,640
this I mean it just needs to provide Power right I run the time card mini in

52
00:03:41,319 --> 00:03:48,120
the gawk One Mini it's like time server

53
00:03:45,640 --> 00:03:54,799
setion okay now I think I have to try that I really hope this doesn't break it

54
00:03:51,799 --> 00:03:58,000
I'd feel kind of bad if I broke it oh

55
00:03:54,799 --> 00:04:00,239
look at that they're both blinking look

56
00:03:58,000 --> 00:04:06,159
at that wow it works okay we've got a Time server in the time

57
00:04:03,439 --> 00:04:10,879
server can you see how this makes perfect sense now it should be running

58
00:04:08,959 --> 00:04:16,280
already you can see from the logs it's connecting to cloudflare um that's an

59
00:04:13,040 --> 00:04:18,320
ntp server a public time server uh that

60
00:04:16,280 --> 00:04:22,479
I configure just as like a secondary source usually you'd see a bunch of GPS

61
00:04:20,600 --> 00:04:27,199
logs but that's because I haven't told you about today's sponsor thanks to MSI

62
00:04:25,040 --> 00:04:31,160
for sponsoring this video unlike your homework there's one thing you won't

63
00:04:28,919 --> 00:04:36,039
want to put off msi's amazing back to school deals they're offering a wide

64
00:04:32,840 --> 00:04:38,919
selection of laptops gaming PCs gpus and

65
00:04:36,039 --> 00:04:43,600
more check out the MSI cyborg 14 an entrylevel gaming laptop that's sleek

66
00:04:41,199 --> 00:04:48,880
and Powerful perfect for gamers students or anyone who needs both it's equipped

67
00:04:45,680 --> 00:04:51,960
with a 14in full HD screen an NVIDIA

68
00:04:48,880 --> 00:04:53,400
4000 series GPU and an Intel i7

69
00:04:51,960 --> 00:04:58,639
processor not quite what you're looking for no worries MSI has plenty of other

70
00:04:56,120 --> 00:05:02,280
laptops on sale right now be a good student and check out MS back to school

71
00:05:00,560 --> 00:05:07,080
deals using the link in the description below sorry wrong thing I mean I haven't

72
00:05:04,479 --> 00:05:11,600
plugged in the antennas yet so let's do that you can use basically any GPS

73
00:05:09,759 --> 00:05:16,199
antenna as far as I'm aware I got these ones on Amazon this is meant for a boat

74
00:05:14,280 --> 00:05:21,960
and I needed to get an adapter cuz this uses BNC connectors now I wonder will we

75
00:05:19,440 --> 00:05:29,319
have GPS reception in here zero satellites in view look at that 10

76
00:05:25,319 --> 00:05:32,120
satellites in view ooh wah wa we woo all

77
00:05:29,319 --> 00:05:37,000
right look at this we got our gawk one oh look it's ripping dude nothing like

78
00:05:34,120 --> 00:05:41,240
measuring your time in Nan seconds it's a very in-depth config file you can mess

79
00:05:39,639 --> 00:05:46,039
around with a lot of different settings and some far more advanced than others

80
00:05:43,680 --> 00:05:50,639
um but what we're most interested in is the primary clocks and secondary clocks

81
00:05:48,600 --> 00:05:56,000
primary clocks usually you set as your most accurate source of time in our case

82
00:05:52,639 --> 00:05:58,400
we're going to use PPS from the GPS chip

83
00:05:56,000 --> 00:06:01,919
and that's one pulse per second PPS stands for and basically Bally what's

84
00:06:00,039 --> 00:06:05,759
happening is the GPS chip on the time card is sending a little electrical

85
00:06:03,560 --> 00:06:10,120
signal at the start of every second and that's going to sink our time down to

86
00:06:07,440 --> 00:06:14,199
like Nan seconds or micros seconds and be very accurate then in the secondary

87
00:06:12,000 --> 00:06:19,360
clock section we're getting our major time which is like what time of day it

88
00:06:16,240 --> 00:06:20,759
is just down to the minute or second uh

89
00:06:19,360 --> 00:06:26,319
we're getting that from cloud flare time. cloudflare.com wow look at

90
00:06:23,720 --> 00:06:30,880
that hey I don't know I feel like something's funky is going on with this

91
00:06:27,880 --> 00:06:30,880
one

92
00:06:36,000 --> 00:06:41,720
the thing that's strange is it's like reporting to the

93
00:06:39,880 --> 00:06:48,919
dashboard very infrequently ooh look at our offset it's

94
00:06:45,120 --> 00:06:51,840
terrible we have 5c

95
00:06:48,919 --> 00:06:55,039
variants I don't know what to do boys it's been a few days but we've got the

96
00:06:53,160 --> 00:06:58,599
GPS antennas outside we've got them hooked up and we've sorted out the

97
00:06:57,199 --> 00:07:02,879
couple little issues we were running into I worked out with the time beat

98
00:07:00,800 --> 00:07:06,520
guys and now this all makes a lot more sense and it isn't crashing anymore I

99
00:07:05,199 --> 00:07:10,960
want to just give you guys a little bit of background here on the Raspberry Pi

100
00:07:08,800 --> 00:07:15,280
there's like an issue with the kernel code that they use to run the time beat

101
00:07:13,240 --> 00:07:20,680
software it doesn't like having the GPS serial connection which we call nmea as

102
00:07:18,400 --> 00:07:23,599
well as PPS at the same time and they did admit to me it is kind of their own

103
00:07:22,120 --> 00:07:28,280
fault because they wrote the code but they are working on a fix but for now we

104
00:07:26,400 --> 00:07:32,000
can't really do both at the same time at least not on the newer version

105
00:07:30,039 --> 00:07:35,840
this is the older version you can see here I'm running this on the time card

106
00:07:34,280 --> 00:07:39,479
mini you can see we're reading the major time from the GPS chip and it's several

107
00:07:38,000 --> 00:07:45,599
hundred milliseconds out which makes sense and then if we look at our

108
00:07:42,680 --> 00:07:49,280
PPS it's pretty accurate but it's also a bit all over the place for the most part

109
00:07:48,360 --> 00:07:58,159
we're talking within 10 nond accuracy but then

110
00:07:53,039 --> 00:08:00,360
on other times it's 14 or 45 nond out

111
00:07:58,159 --> 00:08:04,759
which is still mindboggling accurate but they were telling me on a proper setup

112
00:08:01,639 --> 00:08:10,639
without this bug they usually within 1 2

113
00:08:04,759 --> 00:08:13,400
3 NS at all times which is so so stable

114
00:08:10,639 --> 00:08:18,639
generally they recommended to me to just disable this nmea data and use a public

115
00:08:16,240 --> 00:08:22,159
time server like time. Windows.com time. cloudflare.com as your major time Source

116
00:08:21,080 --> 00:08:28,479
now you might have a problem if the internet goes out because you're losing your major time Source but the GPS chip

117
00:08:26,639 --> 00:08:32,080
does still have that information and the pulse per second should still stay

118
00:08:30,159 --> 00:08:36,399
relatively accurate but generally if you have downtime of your main internet you

119
00:08:33,719 --> 00:08:42,080
probably have bigger problems let's sync my laptop to it hey it worked look at

120
00:08:39,200 --> 00:08:47,040
that look how accurate the time is if I sync to this local time server or like

121
00:08:44,800 --> 00:08:49,399
half a millisec out some of that is just going to be the clock on this Mac

122
00:08:48,279 --> 00:08:54,360
probably not being the greatest thing ever but uh we're also syncing over

123
00:08:51,640 --> 00:09:00,000
Wi-Fi but there you go we have a local time server getting its data from GPS

124
00:08:57,440 --> 00:09:05,040
and from public time servers our gawk One Mini our very own generally pretty

125
00:09:02,079 --> 00:09:10,000
much within 10 NS which is kind ofing insane I like this thing it's not

126
00:09:07,440 --> 00:09:15,200
necessary for us at all don't get me wrong what for our cluster setup as long

127
00:09:13,519 --> 00:09:21,200
as they're all synced to like a local time server we have our router acting as

128
00:09:18,480 --> 00:09:25,800
that it's got a pretty accurate Nick and maybe it's not true to actual time but

129
00:09:24,399 --> 00:09:31,839
as long as they all think that they're on the same time it doesn't really matter but this is just cool and I like

130
00:09:29,880 --> 00:09:35,760
doing cool stuff like this and I like sharing it with you so get subscribed

131
00:09:34,279 --> 00:09:40,279
hit like and tell me what you think about acurate time you probably don't

132
00:09:37,560 --> 00:09:43,399
need it either but it is fun and not that expensive if you buy the normal

133
00:09:41,600 --> 00:09:47,040
version of this and build it yourself bye