First, it checks the data stream to make sure the car is in park and not moving. If all is well, it then gives a command to a power circuit that energizes the motors used to close the door. It goes even further, though—the ECU then monitors the voltage consumed by the motors. If it detects a voltage spike, which happens when a door is hindered by an errant handbag or a wayward body part, the ECU immediately reverses the direction of the door to prevent potential injury. If the door closes properly, the latch electrically locks the door shut.
In the old days, this would have been an engineering feat. Just electrically powering the doors would have required dedicated wires running between the shifter, the door switch, and the motor.
Before CAN was developed in the mid-'80s, every time an automaker added an electronic feature, like, say, heated seats, new, dedicated wires had to be added just to connect the heaters to a dash-mounted switch. Over the years, more features meant more wires, until there were literally miles of wire in wrist-thick vines snaking all over the car. With CAN, the seat heaters and the switch that powers them don't have to be directly wired together. They can simply "talk" over the existing CAN network—no special wires needed.
What is needed, however, is some additional programming to get all the devices networked. It's a choice to shift toward programming complexity over physical complexity. CAN has made software development more challenging, but it has had many more positive effects: significant cost savings to the consumer, much lighter weight, reduced reliance on rubber and copper resources, and far better reliability with fewer wires to break over time.
Those attributes may be important from a technical standpoint, but the most profound effect of this shift toward programming is on vehicle diagnostics and software updates.
The shrinking of the car's wiring harness and other benefits were not the main impetus for the creation of CAN. Your radio, for example, may forget its preset stations. However, you don't have to reset the date on any of these embedded computers because none of them care.
Sign up for our Newsletter! Mobile Newsletter banner close. Mobile Newsletter chat close. Mobile Newsletter chat dots.
Goal of this guide The goal of this step by step guide is to show you how a powerful car computer with a touch screen interface and a lot of functionality, can easily be built into your car. See more here. Raspberry Pi car computer carputer is a "computer" installed within the vehicle and is based on the Raspberry Pi board. Its purpose is to provide you with several cool features and additional features you wouldn't normally have within the vehicle.
It is a very helpful feature to have that will improve your driving experience and this should be the final result after assembly of our hardware:. Here are the steps 1. First we need to assemble everything in the SmartPi case. Next go ahead and mount the AutoPi Dongle board on top of the adapter board. Raspberry Pi Car Computer.
Find a place in your car where you want the touch screen located. In our example we have mounted it on the center console using strong double-sided tape. You can also attach is using two GoPro adhesive mounts if that works better for your specific installation. It is typically found under the dashboard, but varies from model to model. Insert the OBD extension cable into the car and then connect it to the AutoPi Dongle board located on the back of the touch screen.
Once connected the unit powers up and you will briefly see a small startup prompt on the screen. This is because the AutoPi IoT platform is optimized for fast boot and does not contain a graphical user interface. But this is easy to change. On your laptop or mobile phone, log into your AutoPi account on.
This will install a minimal X-windows server on your AutoPi Dongle; enabling display of graphical elements. I dont know how crazy i am, but you are insane. Macs suck, and I don't care who knows that I think that. The software is poorly designed as far as GUI and the user format, and the hardware makes no sense at all. I wonder why the great Microsoft company ever rewrote the Microsoft Office software or Internet Explorer to be Mac-compatible.
Reply 8 years ago on Introduction. Two different systems and require different logic. I use both and they both have pros and cons but for each system you have to forget what you know on either. It's like comparing a drag racer to a speed boat - they are fantastic but require different skills. Reply 7 years ago on Introduction.
If you BUY an operating system then you are buying into the system that made it If you can't read and change the code you don't own it- you are owned by it. How is this an instructable? There's nothing showing us how to do this Please remove this. Brendan, Of course it's an instructable, I show details of how to build a computer into a car..
This post is informing us what you did, not how you did it. Check out all the other instructables on this site.
0コメント