WEBVTT 00:00.400 --> 00:03.480 Hello everyone, this is Sebastian, I'm Thomas from 00:03.480 --> 00:04.300 Lichtvision Engineering. 00:04.660 --> 00:06.180 We're here to give you a little update 00:06.180 --> 00:07.800 on our ProbitSite. 00:08.420 --> 00:11.580 We just launched our firmware release 1.5 00:11.580 --> 00:13.660 and would like to inform you on a 00:13.660 --> 00:15.100 couple of new things. 00:15.440 --> 00:18.600 In short, as a summary, we launched the 00:18.600 --> 00:19.360 expert mode. 00:19.640 --> 00:23.880 It's a mode that allows customers to change 00:23.880 --> 00:26.600 something in the configuration once it's set into 00:26.600 --> 00:28.520 this expert mode. 00:29.000 --> 00:30.080 And the other thing we would like to 00:30.080 --> 00:32.100 inform you about is a feature that has 00:32.100 --> 00:34.200 been there from the beginning but is not 00:34.200 --> 00:37.040 known to many of you, which is the 00:37.040 --> 00:38.200 data logging function. 00:38.520 --> 00:40.960 But the details will be explained by Sebastian. 00:41.880 --> 00:44.940 So let's start by powering up the device. 00:46.100 --> 00:49.500 With the new firmware you have the expert mode 00:49.500 --> 00:53.680 that you can enable inside the 00:53.680 --> 00:54.800 Probit Site App. 00:54.960 --> 00:56.820 The difference is you can see there's a 00:56.820 --> 00:59.260 small special icon on the bottom right that 00:59.260 --> 01:00.800 indicates you are in the expert mode. 01:01.500 --> 01:04.900 Normally when you get the device, it starts 01:04.900 --> 01:07.440 in the normal mode, like you can see 01:07.440 --> 01:07.720 here. 01:07.980 --> 01:10.520 There's a different boot screen and there's no 01:10.520 --> 01:13.280 special icon on the bottom right side. 01:14.240 --> 01:16.100 How to change into the expert mode 01:16.100 --> 01:16.760 I will show you later. 01:17.500 --> 01:21.960 For this example, I made a small configuration. 01:22.300 --> 01:25.560 I have three devices that I'm going to 01:25.560 --> 01:28.080 connect to the ProbitSite and we got 01:28.080 --> 01:30.120 some problems here that I'm going to show 01:30.120 --> 01:30.740 you just now. 01:31.560 --> 01:34.100 First, let's start a scan. 01:39.000 --> 01:41.800 You can see that there are already some problems. 01:42.080 --> 01:44.740 We have one addressed device and one unaddressed 01:44.740 --> 01:45.160 device. 01:45.960 --> 01:48.000 In this example, let's say you have an 01:48.000 --> 01:50.480 installation with two devices and you put another 01:50.480 --> 01:52.420 one additionally. 01:53.200 --> 01:56.840 In this case, it already has a short address. 01:57.240 --> 01:59.240 You can see we have a possible address conflict. 02:00.180 --> 02:04.220 It detected a device with short address zero 02:04.220 --> 02:05.300 with a possible conflict. 02:06.180 --> 02:08.639 There's a high possibility that there are two 02:08.639 --> 02:10.039 devices with the same address. 02:11.100 --> 02:13.940 We have one device that has no short address. 02:14.780 --> 02:17.800 If you go into this address conflict device, 02:18.020 --> 02:19.460 you can go into device options. 02:20.320 --> 02:21.920 We can identify the device. 02:22.160 --> 02:24.620 It's going to blink and we can also 02:24.620 --> 02:25.360 set an address. 02:26.000 --> 02:28.480 Because we have an address conflict, we can only 02:28.480 --> 02:29.980 delete this short address. 02:31.280 --> 02:34.020 All devices that have the short address zero 02:34.020 --> 02:36.940 are not going to have any address. 02:37.700 --> 02:40.040 You see, I just had a warning and 02:40.040 --> 02:44.420 if I confirm, it should remove the short 02:44.420 --> 02:46.700 address zero from all devices that have this address. 02:47.200 --> 02:49.620 You can also set an address. 02:50.180 --> 02:53.300 For this device, it doesn't have any address. 02:53.740 --> 02:55.940 Maybe you wanted to have one, so you 02:55.940 --> 02:56.700 go into the options. 02:57.100 --> 02:59.800 You can go into set address and you 02:59.800 --> 03:02.560 can give it any address that is not 03:02.560 --> 03:03.020 occupied. 03:03.660 --> 03:05.560 Let's say we give it the address number two. 03:06.520 --> 03:08.700 You see the warning screen again. 03:09.160 --> 03:12.480 You need to confirm and after a short 03:12.480 --> 03:14.840 time, it should have the address number two. 03:16.440 --> 03:20.120 After we resolved this problem with the same 03:20.120 --> 03:23.540 short addresses, you can do another scan. 03:23.940 --> 03:26.880 So you can detect what kind of devices you 03:26.880 --> 03:27.340 have here. 03:27.940 --> 03:30.320 You can read all the information about them. 03:31.840 --> 03:35.440 You see, we have one addressed device and 03:35.440 --> 03:37.280 two unaddressed devices. 03:40.320 --> 03:44.580 Because we resolved this conflict, we can see 03:44.580 --> 03:46.740 the information about these devices. 03:47.440 --> 03:50.980 We have the device number two that we 03:50.980 --> 03:53.700 gave this address to and we have two 03:53.700 --> 03:56.040 devices that do not have an address. 03:56.700 --> 03:59.300 Those are the devices that had this conflict. 04:01.160 --> 04:04.340 Like Thomas already said, the time you turn 04:04.340 --> 04:06.520 on the device, it's going to start recording 04:06.520 --> 04:08.340 everything that happens on the DALI bus. 04:09.020 --> 04:11.360 The time you power it off, 04:11.360 --> 04:13.120 it's going to save this log. 04:13.440 --> 04:16.400 We call it DALI log, sometimes sniffer. 04:17.900 --> 04:20.920 If I connect it to my computer, 04:20.920 --> 04:21.800 like so. 04:24.390 --> 04:27.270 As you can see on my screen, 04:27.270 --> 04:30.730 if I click on the connect button, it is 04:30.730 --> 04:32.110 going to connect to this device. 04:32.850 --> 04:35.230 If it's powered off, it's going to power 04:35.230 --> 04:35.790 on again. 04:37.350 --> 04:39.010 You can see it's booting. 04:40.230 --> 04:42.130 It is downloading the scans. 04:42.550 --> 04:44.730 The first scan with the conflicts and the 04:44.730 --> 04:47.110 second scan after we've resolved everything. 04:49.320 --> 04:51.460 It's also importing the log data for them 04:51.460 --> 04:53.980 and now it's importing the full log data. 04:54.200 --> 04:56.320 The data from the time the device was 04:56.320 --> 04:58.340 powered on until it was powered off again. 04:59.720 --> 05:02.940 That means we can put this ProbitSite 05:02.940 --> 05:06.740 into an electrical cabinet or into the false 05:06.740 --> 05:08.040 ceiling to have it recorded. 05:08.660 --> 05:11.380 If you wait for some ghost telegrams or 05:11.380 --> 05:13.260 whatever you have, you can use this as 05:13.260 --> 05:13.840 a data logger. 05:13.900 --> 05:14.140 Exactly. 05:14.660 --> 05:16.940 For example, if you have a problem like 05:16.940 --> 05:19.460 there are some lights that are turning off 05:19.460 --> 05:22.520 every half an hour, you can connect the 05:22.520 --> 05:24.140 ProbitSite to this installation. 05:24.940 --> 05:26.640 If you want to record for more than 05:26.640 --> 05:30.200 one day, I would recommend to plug in 05:30.200 --> 05:33.260 a power supply so the battery doesn't get 05:33.260 --> 05:33.560 empty. 05:34.400 --> 05:38.500 Then you can record for a really long time. 05:39.220 --> 05:41.140 And later on you can see on the 05:41.140 --> 05:44.820 computer what kind of telegrams were sent on 05:44.820 --> 05:48.740 this DALI line and maybe figure out what's 05:48.740 --> 05:49.860 the problem with your installation. 05:52.580 --> 05:54.580 If you want to change into the expert 05:54.580 --> 05:58.680 mode, you need to extend this window on 05:58.680 --> 05:59.180 the left side. 05:59.780 --> 06:02.480 You see all the information about this device. 06:03.240 --> 06:05.460 You see it is already in the expert 06:05.460 --> 06:05.760 mode. 06:05.980 --> 06:07.980 You can change it back to normal mode. 06:08.760 --> 06:10.840 The device is going to turn off and 06:10.840 --> 06:13.960 on again and it is not in the 06:13.960 --> 06:14.820 expert mode anymore. 06:16.400 --> 06:17.880 If you want to go back to expert 06:17.880 --> 06:21.260 mode, you click this button again and you 06:21.260 --> 06:23.980 see you are back to expert mode. 06:24.560 --> 06:26.240 I think this comes in handy if you 06:26.240 --> 06:28.880 want to give this device to a less 06:28.880 --> 06:31.640 trained person to do some testing and you 06:31.640 --> 06:35.040 don't want to endanger the installation with faults 06:35.040 --> 06:35.600 being made. 06:35.980 --> 06:38.120 But if you yourself are the expert, you 06:38.120 --> 06:39.820 activate the expert mode and you can change 06:39.820 --> 06:40.360 things. 06:40.500 --> 06:43.960 That's how we thought we basically allow for 06:43.960 --> 06:46.100 changes at the same time, keep our promise 06:46.100 --> 06:50.960 that we prevent installations from being corrupted by 06:50.960 --> 06:52.540 misuse. 06:52.920 --> 06:53.160 Exactly. 06:55.100 --> 06:58.820 Like I said before, it imports the log data. 06:58.830 --> 07:02.560 All the imported data goes into this imported 07:02.560 --> 07:03.140 directory. 07:04.520 --> 07:06.120 You can see we have the two scans. 07:06.280 --> 07:07.940 The first scan with the conflicts, the second 07:07.940 --> 07:10.700 scan without the conflicts, the other way around. 07:11.000 --> 07:12.940 This is with the conflicts, this is without 07:12.940 --> 07:13.420 the conflicts. 07:14.100 --> 07:17.300 You can go inside and we see all 07:17.300 --> 07:18.480 the devices that we have detected. 07:19.980 --> 07:22.740 The special feature that was already there but 07:22.740 --> 07:25.260 not many people knew about is the logging 07:25.260 --> 07:25.660 feature. 07:26.060 --> 07:27.140 It's on this tab, logs. 07:27.720 --> 07:31.520 You can see the scan we just did. 07:31.800 --> 07:33.880 We can see the time we just had, 07:34.400 --> 07:38.200 10:53, and you can open the log 07:38.200 --> 07:41.340 data for this power cycle. 07:43.000 --> 07:45.120 On the left side, you can see everything 07:45.120 --> 07:46.320 that happened with the device. 07:46.600 --> 07:49.460 It was powered up, we started the scan, 07:50.100 --> 07:54.200 there were some address changes and another scan. 07:54.800 --> 07:56.820 Exactly what we just did today. 07:57.700 --> 07:59.920 On the right side, you can see everything 07:59.920 --> 08:01.120 that happened on the DALI line. 08:02.420 --> 08:04.440 If we would not do any scan and 08:04.440 --> 08:07.600 there would be some installation that's already in 08:07.600 --> 08:09.840 use, you would see all the telegrams on 08:09.840 --> 08:10.320 the right side. 08:10.640 --> 08:13.140 If I expect some behavior, can I also 08:13.140 --> 08:14.240 search in the log? 08:14.420 --> 08:16.320 Yes, in the top, you can see this 08:16.320 --> 08:17.540 search button. 08:18.500 --> 08:24.960 You can search, for example, for address number 08:24.960 --> 08:25.980 one. 08:26.620 --> 08:27.340 I hope there is one. 08:28.020 --> 08:29.540 Yes, there is one. 08:29.980 --> 08:33.780 You can see there's something that is happening 08:33.780 --> 08:36.800 with the device number, with the short address one. 08:37.419 --> 08:39.860 If you see this icon, it means this 08:39.860 --> 08:41.659 is something that we have sent, that ProbitSite 08:41.659 --> 08:43.660 has sent, if there's an arrow up, 08:43.860 --> 08:45.520 that means we have sent it. 08:50.220 --> 08:52.080 I think I didn't forget anything. 08:52.380 --> 08:52.980 No, good. 08:53.240 --> 08:53.520 Thank you. 08:53.560 --> 08:54.960 Thank you so much for the update, Sebastian, 08:55.380 --> 08:56.740 and have fun with our product.