WEBVTT NOTE This file was exported by MacCaption version 7.0.13 to comply with the WebVTT specification dated March 27, 2017. 00:00:01.835 --> 00:00:04.304 align:center line:-1 position:50% size:39% There are some other factors here in play, 00:00:04.304 --> 00:00:06.874 align:center line:-1 position:50% size:43% not just displaying the waveform or triggering, 00:00:06.874 --> 00:00:09.309 align:center line:-1 position:50% size:39% as we say here in this metric. 00:00:09.309 --> 00:00:11.178 align:center line:-1 position:50% size:45% The best triggering helps you see more of your signal. 00:00:11.178 --> 00:00:15.515 align:center line:-1 position:50% size:55% In this case, we're about 200 times faster with the EXR Series, specifically. 00:00:15.515 --> 00:00:18.218 align:center line:-1 position:50% size:36% We can also do faster hardware averaging. 00:00:18.218 --> 00:00:20.621 align:center line:-1 position:50% size:44% If you're looking at averaging out noise out of a signal 00:00:20.621 --> 00:00:21.989 align:center line:-1 position:50% size:24% or things like that, 00:00:21.989 --> 00:00:24.191 align:center line:-1 position:50% size:50% we can do that over 100 times faster. 00:00:24.191 --> 00:00:26.260 align:center line:-1 position:50% size:35% We can even do onscreen measurements faster. 00:00:26.260 --> 00:00:28.729 align:center line:-1 position:50% size:50% We can also plot eye diagrams faster. 00:00:28.729 --> 00:00:31.064 align:center line:-1 position:50% size:38% For those of you working on high-speed digital designs, 00:00:31.064 --> 00:00:33.467 align:center line:-1 position:50% size:37% you probably know the pain of sitting there and waiting 00:00:33.467 --> 00:00:36.036 align:center line:-1 position:50% size:54% for that unit interval count to accumulate 00:00:36.036 --> 00:00:43.744 align:center line:-1 position:50% size:55% so you can have confident accuracy in your eye diagrams and things like that. 00:00:43.744 --> 00:00:47.414 align:center line:-1 position:50% size:37% We can plot 50 times faster using this ASIC technology 00:00:47.414 --> 00:00:52.786 align:center line:-1 position:50% size:55% in our new Infiniium line of oscilloscopes. 00:00:52.786 --> 00:00:54.288 align:center line:-1 position:50% size:48% The next tool I'm going to show you 00:00:54.288 --> 00:00:58.091 align:center line:-1 position:50% size:46% is a new tool that we've developed for our Infiniium products 00:00:58.091 --> 00:01:00.093 align:center line:-1 position:50% size:26% called Fault Hunter. 00:01:00.093 --> 00:01:03.997 align:center line:-1 position:50% size:62% This takes some of the guesswork out for you. 00:01:03.997 --> 00:01:07.634 align:center line:-1 position:50% size:37% The issue we're looking at is about 1 in 200,000 or so, 00:01:07.634 --> 00:01:10.470 align:center line:-1 position:50% size:33% which means at 200,000 waveforms per second, 00:01:10.470 --> 00:01:15.509 align:center line:-1 position:50% size:52% the EXR Series is showing it on screen about once per second. 00:01:15.509 --> 00:01:16.910 align:center line:-1 position:50% size:30% Imagine for a moment you had a problem 00:01:16.910 --> 00:01:18.879 align:center line:-1 position:50% size:33% that was one in a billion, 00:01:18.879 --> 00:01:22.783 align:center line:-1 position:50% size:40% or one in hundreds of millions or something like that. 00:01:22.783 --> 00:01:25.886 align:center line:-1 position:50% size:41% You do a little bit of math there, and it may take minutes 00:01:25.886 --> 00:01:28.422 align:center line:-1 position:50% size:37% for even the fastest oscilloscopes on the planet 00:01:28.422 --> 00:01:30.390 align:center line:-1 position:50% size:22% to find this fault. 00:01:30.390 --> 00:01:31.725 align:center line:-1 position:50% size:25% With Fault Hunter, 00:01:31.725 --> 00:01:35.829 align:center line:-1 position:50% size:52% we've developed a tool that automates this fault-finding process for you. 00:01:35.829 --> 00:01:37.130 align:center line:-1 position:50% size:47% I'm going to enable it, 00:01:37.130 --> 00:01:38.332 align:center line:-1 position:50% size:33% and then we'll jump back to this slide. 00:01:38.332 --> 00:01:41.568 align:center line:-1 position:50% size:45% I'll explain what the tool does. 00:01:41.568 --> 00:01:44.071 align:center line:-1 position:50% size:41% I'm going to under the Analyze Quick Fault Hunter. 00:01:44.071 --> 00:01:47.040 align:center line:-1 position:50% size:40% One great thing here is we do have a lot of quick hits. 00:01:47.040 --> 00:01:49.309 align:center line:-1 position:50% size:39% If you're doing eye diagrams, jitter measurements, 00:01:49.309 --> 00:01:51.678 align:center line:-1 position:50% size:44% Fault Hunter, we saw the quick measurements already. 00:01:51.678 --> 00:01:56.450 align:center line:-1 position:50% size:52% We have a lot of one-click actions that let you jump into an advanced tool 00:01:56.450 --> 00:02:01.355 align:center line:-1 position:50% size:44% which helps with repeatability and finding the tool to begin with. 00:02:01.355 --> 00:02:03.657 align:center line:-1 position:50% size:39% As you can see, we've designed our menu structure 00:02:03.657 --> 00:02:06.660 align:center line:-1 position:50% size:32% so everything you need is a click or two away. 00:02:06.660 --> 00:02:09.463 align:center line:-1 position:50% size:43% There are a lot of things oscilloscopes can do nowadays. 00:02:09.463 --> 00:02:12.866 align:center line:-1 position:50% size:35% Having quick-jump setups is pretty helpful. 00:02:12.866 --> 00:02:15.369 align:center line:-1 position:50% size:36% I'm going to get that rolling. 00:02:15.369 --> 00:02:18.472 align:center line:-1 position:50% size:40% Let's talk about what Fault Hunter does. 00:02:18.472 --> 00:02:21.742 align:center line:-1 position:50% size:30% What it's doing is, first, you set it up. 00:02:21.742 --> 00:02:23.977 align:center line:-1 position:50% size:31% You tell it what channel you'd like to analyze. 00:02:23.977 --> 00:02:25.245 align:center line:-1 position:50% size:55% There are a couple different modes here. 00:02:25.245 --> 00:02:27.014 align:center line:-1 position:50% size:38% We're going to use the Default Triggering mode, 00:02:27.014 --> 00:02:28.915 align:center line:-1 position:50% size:37% which helps find rare faults. 00:02:28.915 --> 00:02:31.318 align:center line:-1 position:50% size:31% What it's doing is using hardware triggers 00:02:31.318 --> 00:02:33.887 align:center line:-1 position:50% size:49% to look for common signal problems. 00:02:33.887 --> 00:02:35.756 align:center line:-1 position:50% size:35% You can tell it how long you'd like to run. 00:02:35.756 --> 00:02:37.024 align:center line:-1 position:50% size:30% We selected 1 minute, 00:02:37.024 --> 00:02:40.727 align:center line:-1 position:50% size:32% but you can run this test for up to 48 hours. 00:02:40.727 --> 00:02:42.329 align:center line:-1 position:50% size:46% With hardware triggering enabled, 00:02:42.329 --> 00:02:45.766 align:center line:-1 position:50% size:38% 200,000 triggers per second for 48 hours, 00:02:45.766 --> 00:02:48.602 align:center line:-1 position:50% size:37% it's something like 34 billion waveforms you can test, 00:02:48.602 --> 00:02:51.138 align:center line:-1 position:50% size:34% and Fault Hunter can find a single error, 00:02:51.138 --> 00:02:54.307 align:center line:-1 position:50% size:46% that single needle in the haystack, for you reliably 00:02:54.307 --> 00:02:57.677 align:center line:-1 position:50% size:29% because of that ASIC triggering technology. 00:02:57.677 --> 00:02:59.079 align:center line:-1 position:50% size:26% One you tell it that, 00:02:59.079 --> 00:03:02.282 align:center line:-1 position:50% size:38% it begins its automatic setup and starts running tests. 00:03:02.282 --> 00:03:03.817 align:center line:-1 position:50% size:41% The automatic setup it's doing, 00:03:03.817 --> 00:03:06.686 align:center line:-1 position:50% size:54% it's using some common measurements, 00:03:06.686 --> 00:03:11.324 align:center line:-1 position:50% size:43% like amplitudes and frequencies, data rates, and things like that. 00:03:11.324 --> 00:03:15.062 align:center line:-1 position:50% size:49% It's trying to determine what's normal for the signal statistically. 00:03:15.062 --> 00:03:18.031 align:center line:-1 position:50% size:33% It's capturing a mean and a standard deviation 00:03:18.031 --> 00:03:19.999 align:center line:-1 position:50% size:54% for a number of different measurements. 00:03:19.999 --> 00:03:25.205 align:center line:-1 position:50% size:42% Then, it's applying that to find glitches, slow edges, and runts. 00:03:25.205 --> 00:03:27.074 align:center line:-1 position:50% size:33% To be very specific here, 00:03:27.074 --> 00:03:29.543 align:center line:-1 position:50% size:36% the automatic setup is looking for glitches that are 00:03:29.543 --> 00:03:32.179 align:center line:-1 position:50% size:45% 50% of the data rate of the signal. 00:03:32.179 --> 00:03:35.315 align:center line:-1 position:50% size:35% Whether it's a clock signal or a digital data signal, 00:03:35.315 --> 00:03:40.520 align:center line:-1 position:50% size:49% data rate determines the smallest fundamental frequency of the signal, 00:03:40.520 --> 00:03:42.823 align:center line:-1 position:50% size:31% then looks for anything half that size. 00:03:42.823 --> 00:03:44.791 align:center line:-1 position:50% size:29% For the rising edges and the falling edges, 00:03:44.791 --> 00:03:48.128 align:center line:-1 position:50% size:44% it's looking for anything three standard deviations slower 00:03:48.128 --> 00:03:50.030 align:center line:-1 position:50% size:37% than the mean edge speed. 00:03:50.030 --> 00:03:52.799 align:center line:-1 position:50% size:35% For the runts, it's using the top and base voltages 00:03:52.799 --> 00:03:56.503 align:center line:-1 position:50% size:46% and some timing measurements to determine what a runt would be 00:03:56.503 --> 00:03:58.738 align:center line:-1 position:50% size:33% in this signal statistically. 00:03:58.738 --> 00:04:01.975 align:center line:-1 position:50% size:33% That being said, you can defeat or override 00:04:01.975 --> 00:04:05.112 align:center line:-1 position:50% size:48% whatever Fault Hunter automatically determines on your behalf, 00:04:05.112 --> 00:04:08.582 align:center line:-1 position:50% size:35% and you can come in here and manually modify 00:04:08.582 --> 00:04:12.586 align:center line:-1 position:50% size:40% what you consider acceptable for your design. 00:04:12.586 --> 00:04:13.720 align:center line:-1 position:50% size:29% Once all that's set up, 00:04:13.720 --> 00:04:18.158 align:center line:-1 position:50% size:53% it can now run hardware triggering tests to look for these problems. 00:04:18.158 --> 00:04:19.860 align:center line:-1 position:50% size:37% In this case, to find a glitch, 00:04:19.860 --> 00:04:25.432 align:center line:-1 position:50% size:49% it was looking for anything less than roughly 70 ns, in this case. 00:04:25.432 --> 00:04:28.702 align:center line:-1 position:50% size:41% If it was less than 70 ns, the oscilloscope would trigger. 00:04:28.702 --> 00:04:30.237 align:center line:-1 position:50% size:28% It would fail that test, 00:04:30.237 --> 00:04:33.540 align:center line:-1 position:50% size:45% and then we would have the ability to either rerun that test, 00:04:33.540 --> 00:04:37.210 align:center line:-1 position:50% size:47% view a copy of that failure condition that got saved into memory, 00:04:37.210 --> 00:04:40.547 align:center line:-1 position:50% size:38% or copy that failure condition into the trigger, 00:04:40.547 --> 00:04:42.616 align:center line:-1 position:50% size:32% which I'll show next, which is pretty powerful 00:04:42.616 --> 00:04:46.286 align:center line:-1 position:50% size:40% and helps you skip to the next step of debugging. 00:04:46.286 --> 00:04:48.288 align:center line:-1 position:50% size:33% For this signal, it found some problems, 00:04:48.288 --> 00:04:52.559 align:center line:-1 position:50% size:26% some slow edges, a runt, and a glitch. 00:04:52.559 --> 00:04:55.462 align:center line:-1 position:50% size:39% We click View. 00:04:55.462 --> 00:05:00.934 align:center line:-1 position:50% size:51% We can see a copy of that glitch pulse was saved into memory slot #1. 00:05:00.934 --> 00:05:04.838 align:center line:-1 position:50% size:58% There are a number of waveform memories that the oscilloscope can save traces into 00:05:04.838 --> 00:05:08.542 align:center line:-1 position:50% size:35% for either further review or to use as a comparison 00:05:08.542 --> 00:05:11.444 align:center line:-1 position:50% size:49% versus a live waveform, for example. 00:05:11.444 --> 00:05:14.915 align:center line:-1 position:50% size:49% Found that glitch there pretty readily. 00:05:14.915 --> 00:05:17.484 align:center line:-1 position:50% size:32% While I was off perhaps getting a cup of coffee, 00:05:17.484 --> 00:05:20.620 align:center line:-1 position:50% size:45% I come back, and the oscilloscope has found the problem for me. 00:05:20.620 --> 00:05:22.255 align:center line:-1 position:50% size:22% That being said, 00:05:22.255 --> 00:05:25.091 align:center line:-1 position:50% size:42% what Fault Hunter is doing here can be done manually 00:05:25.091 --> 00:05:28.628 align:center line:-1 position:50% size:44% on any oscilloscope that may not have the Fault Hunter tool. 00:05:28.628 --> 00:05:30.997 align:center line:-1 position:50% size:33% It just of course requires some extra setup 00:05:30.997 --> 00:05:33.900 align:center line:-1 position:50% size:44% and may impact the repeatability of the process. 00:05:33.900 --> 00:05:36.970 align:center line:-1 position:50% size:47% I can show you how to do that now. 00:05:36.970 --> 00:05:38.672 align:center line:-1 position:50% size:47% I'll use a little bit of a shortcut here. 00:05:38.672 --> 00:05:40.507 align:center line:-1 position:50% size:32% One of the other great features of Fault Hunter 00:05:40.507 --> 00:05:42.509 align:center line:-1 position:50% size:40% is this Copy-to-Trigger button. 00:05:42.509 --> 00:05:45.512 align:center line:-1 position:50% size:44% Triggering, for those oscilloscope pros in the audience, 00:05:45.512 --> 00:05:48.848 align:center line:-1 position:50% size:39% is definitely the best way to go about finding problems. 00:05:48.848 --> 00:05:51.484 align:center line:-1 position:50% size:35% Even if you have a slower waveform update rate, 00:05:51.484 --> 00:05:53.253 align:center line:-1 position:50% size:32% if you set up the correct trigger condition, 00:05:53.253 --> 00:05:56.823 align:center line:-1 position:50% size:41% you can always find the fault that you're looking for. 00:05:56.823 --> 00:05:59.159 align:center line:-1 position:50% size:46% The problem is, you have to know the fault is there 00:05:59.159 --> 00:06:02.729 align:center line:-1 position:50% size:51% and know how to characterize it to set up the trigger condition properly. 00:06:02.729 --> 00:06:04.831 align:center line:-1 position:50% size:51% Let me show you what I mean by that. 00:06:04.831 --> 00:06:09.336 align:center line:-1 position:50% size:44% I'm going to copy the glitch condition to the trigger, 00:06:09.336 --> 00:06:10.770 align:center line:-1 position:50% size:24% close out of here, 00:06:10.770 --> 00:06:14.107 align:center line:-1 position:50% size:38% and close out the math function-- 00:06:14.107 --> 00:06:16.343 align:center line:-1 position:50% size:36% or, sorry, the memory here. 00:06:16.343 --> 00:06:18.745 align:center line:-1 position:50% size:46% Got to get back to where we were. 00:06:18.745 --> 00:06:20.880 align:center line:-1 position:50% size:36% Now I'm going to go ahead and run the oscilloscope. 00:06:20.880 --> 00:06:22.816 align:center line:-1 position:50% size:41% You can see, since I've clicked Copy to Trigger, 00:06:22.816 --> 00:06:24.718 align:center line:-1 position:50% size:28% now the oscilloscope has been instructed 00:06:24.718 --> 00:06:28.088 align:center line:-1 position:50% size:50% to only trigger and display information when that glitch is found. 00:06:28.088 --> 00:06:29.522 align:center line:-1 position:50% size:34% What does that look like? 00:06:29.522 --> 00:06:32.492 align:center line:-1 position:50% size:31% Up here, I can shortcut into this Trigger menu. 00:06:32.492 --> 00:06:34.594 align:center line:-1 position:50% size:49% On Infiniium, this is what it looks like. 00:06:34.594 --> 00:06:36.496 align:center line:-1 position:50% size:31% We get a list of triggers to select from-- 00:06:36.496 --> 00:06:38.798 align:center line:-1 position:50% size:33% edge, glitch, pulse width, various different ways 00:06:38.798 --> 00:06:41.801 align:center line:-1 position:50% size:29% to describe the shape of a waveform. 00:06:41.801 --> 00:06:43.536 align:center line:-1 position:50% size:17% In this case, 00:06:43.536 --> 00:06:45.639 align:center line:-1 position:50% size:33% if we wanted to find this problem on our own, 00:06:45.639 --> 00:06:48.742 align:center line:-1 position:50% size:41% we would have to know that we're looking for problems 00:06:48.742 --> 00:06:51.211 align:center line:-1 position:50% size:19% on Channel 1, 00:06:51.211 --> 00:06:57.284 align:center line:-1 position:50% size:33% that a pulse that crosses 1.05 volts up and down 00:06:57.284 --> 00:07:00.687 align:center line:-1 position:50% size:27% in less than 69.8 ns. 00:07:00.687 --> 00:07:02.989 align:center line:-1 position:50% size:41% Again, I could have set this up when I had the oscilloscope 00:07:02.989 --> 00:07:04.257 align:center line:-1 position:50% size:23% in its slow mode, 00:07:04.257 --> 00:07:05.692 align:center line:-1 position:50% size:40% and it would look just like this, 00:07:05.692 --> 00:07:09.029 align:center line:-1 position:50% size:32% but I didn't even know to look for this problem, 00:07:09.029 --> 00:07:11.564 align:center line:-1 position:50% size:52% because it wasn't appearing on screen. 00:07:11.564 --> 00:07:14.701 align:center line:-1 position:50% size:43% It's a chicken-and-egg situation, 00:07:14.701 --> 00:07:16.236 align:center line:-1 position:50% size:45% where the triggers work fantastic, 00:07:16.236 --> 00:07:18.171 align:center line:-1 position:50% size:27% but only if you know what to look for, 00:07:18.171 --> 00:07:19.572 align:center line:-1 position:50% size:25% and you only know what to look for 00:07:19.572 --> 00:07:22.475 align:center line:-1 position:50% size:25% if the oscilloscope can show it to you. 00:07:22.475 --> 00:07:24.311 align:center line:-1 position:50% size:22% That being said, 00:07:24.311 --> 00:07:27.314 align:center line:-1 position:50% size:49% things like glitches are very common to look for in signals, 00:07:27.314 --> 00:07:29.115 align:center line:-1 position:50% size:29% so the glitch trigger is fairly easy to set up. 00:07:29.115 --> 00:07:30.583 align:center line:-1 position:50% size:29% You can come in here and just play around 00:07:30.583 --> 00:07:34.254 align:center line:-1 position:50% size:42% with the time criteria until you find what you're looking for. 00:07:34.254 --> 00:07:37.991 align:center line:-1 position:50% size:47% We also make it pretty easy for you to find the trigger that you need. 00:07:37.991 --> 00:07:40.960 align:center line:-1 position:50% size:47% We have little shortcut buttons here within the Trigger menu itself, 00:07:40.960 --> 00:07:44.497 align:center line:-1 position:50% size:34% but in this dropdown box, you can find shortcuts. 00:07:44.497 --> 00:07:49.002 align:center line:-1 position:50% size:45% I can verbally describe what I'm looking for. 00:07:49.002 --> 00:07:53.773 align:center line:-1 position:50% size:39% Maybe I'm looking for a pulse that is too narrow, a glitch. 00:07:53.773 --> 00:07:55.408 align:center line:-1 position:50% size:23% I can click on this, 00:07:55.408 --> 00:07:58.678 align:center line:-1 position:50% size:39% and it would automatically snap me into the pulse width. 00:07:58.678 --> 00:08:01.081 align:center line:-1 position:50% size:34% Pulse width is a superset of the glitch trigger 00:08:01.081 --> 00:08:04.984 align:center line:-1 position:50% size:44% that gives you a few more things to tinker around with. 00:08:04.984 --> 00:08:07.987 align:center line:-1 position:50% size:38% It jumps you to that trigger for you to begin setting it up. 00:08:07.987 --> 00:08:09.422 align:center line:-1 position:50% size:31% In this case, it's not set up correctly, 00:08:09.422 --> 00:08:13.793 align:center line:-1 position:50% size:43% so the scope stopped triggering, but that's the idea. 00:08:13.793 --> 00:08:14.894 align:center line:-1 position:50% size:31% We also have a gallery 00:08:14.894 --> 00:08:17.297 align:center line:-1 position:50% size:32% so you can click in here and pictorially see 00:08:17.297 --> 00:08:19.733 align:center line:-1 position:50% size:28% all the different types of trigger conditions 00:08:19.733 --> 00:08:22.902 align:center line:-1 position:50% size:41% and hopefully find the kind of problem that you're looking for 00:08:22.902 --> 00:08:25.772 align:center line:-1 position:50% size:33% using hardware triggers. 00:08:25.772 --> 00:08:29.976 align:center line:-1 position:50% size:43% This is fantastic if you're looking for physical layer faults. 00:08:29.976 --> 00:08:32.812 align:center line:-1 position:50% size:33% Again, an oscilloscope with a fast display speed 00:08:32.812 --> 00:08:36.516 align:center line:-1 position:50% size:49% and waveform update rate helps you readily visualize problems 00:08:36.516 --> 00:08:39.853 align:center line:-1 position:50% size:49% to help you set up a trigger condition to lock in on it. 00:08:39.853 --> 00:08:42.122 align:center line:-1 position:50% size:37% Now that I'm triggered on it, I can take a screenshot. 00:08:42.122 --> 00:08:45.125 align:center line:-1 position:50% size:37% I can make measurements specifically on the problem. 00:08:45.125 --> 00:08:47.961 align:center line:-1 position:50% size:38% I can turn on other channels in my design 00:08:47.961 --> 00:08:51.865 align:center line:-1 position:50% size:38% to see if this glitch correlates with something else. 00:08:51.865 --> 00:08:54.234 align:center line:-1 position:50% size:36% Another great tool built into this oscilloscope, 00:08:54.234 --> 00:08:55.969 align:center line:-1 position:50% size:48% and many oscilloscopes nowadays, 00:08:55.969 --> 00:08:57.704 align:center line:-1 position:50% size:31% is a frequency counter. 00:08:57.704 --> 00:08:59.572 align:center line:-1 position:50% size:39% I can measure the frequency of a channel, 00:08:59.572 --> 00:09:02.842 align:center line:-1 position:50% size:50% but I can also measure the frequency of a trigger-qualified event. 00:09:02.842 --> 00:09:05.278 align:center line:-1 position:50% size:24% I can turn this on, and down here, 00:09:05.278 --> 00:09:10.583 align:center line:-1 position:50% size:49% it's covered up by my face a little bit, but you can see it, 23.809 Hz. 00:09:10.583 --> 00:09:15.221 align:center line:-1 position:50% size:52% This is telling me this glitch is occurring roughly 23.8 times per second. 00:09:15.221 --> 00:09:17.457 align:center line:-1 position:50% size:30% I can also do a period. 00:09:17.457 --> 00:09:19.192 align:center line:-1 position:50% size:27% I can also totalize it. 00:09:19.192 --> 00:09:22.262 align:center line:-1 position:50% size:28% Again, another great troubleshooting tool 00:09:22.262 --> 00:09:24.063 align:center line:-1 position:50% size:30% built into oscilloscopes 00:09:24.063 --> 00:09:26.566 align:center line:-1 position:50% size:38% to help you further not only identify the problem 00:09:26.566 --> 00:09:28.635 align:center line:-1 position:50% size:26% but try to figure out what's causing it. 00:09:28.635 --> 00:09:31.204 align:center line:-1 position:50% size:36% Ultimately, the oscilloscope can't solve that for you, 00:09:31.204 --> 00:09:34.240 align:center line:-1 position:50% size:35% but we try to give you as many tools as possible 00:09:34.240 --> 00:09:36.176 align:center line:-1 position:50% size:27% for you to put on that engineering hat 00:09:36.176 --> 00:09:37.143 align:center line:-1 position:50% size:22% and figure it out.