WEBVTT 00:00.000 --> 00:11.120 Okay, so we've got to turn on everyone, I think you'll be here today to share a story 00:11.120 --> 00:16.520 behind the crucial for test RC car from the insha'l ID to the challenge we faced along 00:16.520 --> 00:17.520 the way. 00:17.520 --> 00:22.760 It'll be about me, I'm a full-site developer, Simon Misretor, but we don't care. 00:22.760 --> 00:26.160 What we bring me here is my passion for building things. 00:26.160 --> 00:32.760 So about the OVCS project, so with my two-site marketing team, we spend six-year building 00:32.760 --> 00:37.200 up and banking regulator in Elexia and wanted to push up the boundaries and try Elexia 00:37.200 --> 00:38.680 in the automotive world. 00:38.680 --> 00:43.360 So in 2024, we created the Open Vehicle Control System, which is an Elexia base developed 00:43.360 --> 00:46.440 on kits for vehicle enhancement. 00:46.440 --> 00:53.080 So with OVCS, we want to allow vehicle modernization, like including electric vehicle 00:53.080 --> 00:58.040 conversion, infotainment, enhancements, or advanced feature, like a remote control, or 00:58.040 --> 01:00.920 autonomous driving. 01:00.920 --> 01:06.840 So the OVCS project started with a VWP of 2007, but testing features, like a remote 01:06.840 --> 01:12.240 control, or autonomous driving with a one-ton vehicle on the public road, or a two-wisky. 01:12.240 --> 01:17.280 So we decided to scale a bit down and build an RC car with the similar components that 01:17.280 --> 01:21.560 provide a much safer way for testing. 01:21.560 --> 01:25.000 Those are the steps toward the build for a rocket RC car. 01:25.000 --> 01:30.240 So we went for a truck-sac slash 4x4, truck-sac is a well-known brand, so if you can find parts 01:30.240 --> 01:34.960 to repair it, or a tuning it if you want to, plus this one can reach the 100-wisky 01:34.960 --> 01:37.320 meter per hour. 01:37.320 --> 01:41.800 Then we had to design some cab-file for 3D printing, we want to all those components 01:41.800 --> 01:46.000 to fit perfectly, we want to swap them easily and replace them if needed. 01:46.000 --> 01:51.000 We also had to manufacture some PCBs, like Arduino Raspberry Pi Hats, we also built 01:51.000 --> 01:57.120 the modules to fit the parts in the small area, and then the assembly wiring, because 01:57.120 --> 02:03.120 there are a lot of wiring and integrate everything inside the video records body. 02:03.120 --> 02:06.400 So those are the components actually present in this RC car. 02:06.400 --> 02:11.040 We have a whole snail AGFPV with one camera and expressed a red thread receiver, those two 02:11.040 --> 02:13.720 come from the drone words for those who know. 02:13.720 --> 02:18.240 We have an AMU, we have two more cameras for a few specific vision, and then we have 02:18.240 --> 02:22.680 all the components for a OVCS, we have the core, which is called vehicle management system, 02:22.680 --> 02:28.480 then we have bridges that make the link between OVCS and ROS 2, for example, then the link 02:28.480 --> 02:35.280 between Muffling and OVCS, Muffling is protocol we use to communicate with the radio receiver, 02:35.280 --> 02:40.560 and then the MSPUSD also to display useful things inside the FPV system. 02:40.560 --> 02:45.320 All those components are running on a separate Raspberry Pi, using electric and nerves. 02:45.880 --> 02:50.440 We also have an Arduino with a aspeculate generic controller, which is making the link between 02:50.440 --> 02:56.320 OVCS and component at a lower level, like generating PDWM for steering or the throttle 02:56.320 --> 02:57.520 of the tracksets. 02:57.520 --> 03:02.560 We also built some custom 5 volt PSU to convert the battery to 5 volt for the components, 03:02.560 --> 03:07.400 multiple can if the controller on a SPI, because all those components communicate as the 03:07.400 --> 03:13.280 full-scale car using canvas, and we also have switch and Wi-Fi OS butts. 03:14.240 --> 03:17.600 There is no more space as you can see, you have the switch on the front, you have the 03:17.600 --> 03:23.120 3 cameras, also the FPV system, a hat to Raspberry Pi, and it's again to Raspberry Pi on the 03:23.120 --> 03:27.840 other side and Arduino, but nice, so that's cool. 03:27.840 --> 03:33.440 So, what we learned along the way, we wanted to make a composable architecture, because in 03:33.440 --> 03:38.720 OVCS you have the V, a Vsten for vehicle, so I wanted to find a way for the user to 03:38.720 --> 03:44.200 customize their vehicle to fit their needs at best. 03:44.200 --> 03:49.040 Neutronization challenge, yes, because using the same component in a full-scale car into 03:49.040 --> 03:54.920 a 110 earthy car was a bit complicated, so it was difficult to put all the parts together. 03:54.920 --> 04:01.040 I wanted to keep it clean, because all the goal is to make something simple and accessible 04:01.040 --> 04:04.480 to that you can try it at home here if you want to. 04:04.560 --> 04:09.680 Next step, we'll finalize the autonomous parts with Rust2, just set that high speed, and 04:09.680 --> 04:13.200 much more, because there is so much change that we can do with the past form that there's no 04:13.200 --> 04:14.200 real limits. 04:14.200 --> 04:19.280 So, thank you for listening, everything will be available on the VCS.be, if you want more detail, 04:19.280 --> 04:23.600 we have a talk at 4pm today, also, and please switch me, if you want to try at home, 04:23.600 --> 04:27.600 if you want to think about it with us, there is my email, thank you.