forked from SEAME-pt/SEAME-Course-24-25
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
96 additions
and
26 deletions.
There are no files selected for viewing
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# Hardware - Glossary | ||
|
||
## Cooling Solutions | ||
**Cooling Solutions**: Hardware such as heatsinks or fans used to dissipate heat from the Raspberry Pi and other components, ensuring reliable operation under high loads or in warm environments. | ||
|
||
## Enclosures | ||
**Enclosures**: Protective housings used to shield hardware components such as the Raspberry Pi and CAN transceivers from physical damage, dust, and moisture. | ||
|
||
## GPIO (General-Purpose Input/Output) | ||
**GPIO**: Physical pins on the Raspberry Pi used for interfacing with external devices. These pins can be programmed to send or receive digital signals. | ||
|
||
## LCD Display | ||
**LCD (Liquid Crystal Display)**: A type of screen that uses liquid crystals to display data. It is commonly used in instrument clusters for clear, low-power visual outputs. | ||
|
||
## Mounting Hardware | ||
**Mounting Hardware**: Physical components such as brackets, enclosures, or stands used to securely attach the display and Raspberry Pi within the PiRacer vehicle. | ||
|
||
## OLED Display | ||
**OLED (Organic Light-Emitting Diode)**: A display technology that offers high contrast and brightness. OLEDs are often chosen for their superior visibility and thinner design compared to LCDs. | ||
|
||
## PiRacer | ||
**PiRacer**: A miniature car platform equipped with a CAN bus system, used as the testing and development vehicle for this project. | ||
|
||
## Power Supply | ||
**Power Supply**: The source of electrical power for the system. In automotive contexts, this often refers to the vehicle's 12V electrical system, which is regulated down to 5V for components like the Raspberry Pi. | ||
|
||
## Speed Sensor | ||
**Speed Sensor**: A hardware component that measures the vehicle's speed, typically by detecting the rotation of wheels or the drivetrain. It transmits this data to the Raspberry Pi via the CAN bus. | ||
|
||
## Voltage Regulator | ||
**Voltage Regulator**: A device that converts and stabilizes electrical power. In this project, a 12V to 5V regulator is used to ensure that the Raspberry Pi operates safely within its voltage requirements. | ||
|
||
## Wiring Harness | ||
**Wiring Harness**: A bundle of wires and connectors used to integrate various hardware components, such as the speed sensor, voltage regulator, and Raspberry Pi. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Networking and Communication - Glossary | ||
|
||
## CAN Bus | ||
**Controller Area Network (CAN)**: A robust communication protocol designed to enable real-time data exchange between microcontrollers and embedded devices within a vehicle. It operates without the need for a central computer and is essential for transmitting data such as speed, engine performance, and diagnostics. | ||
|
||
## Interoperability | ||
**Interoperability**: The ability of different systems, devices, or protocols to work together seamlessly. In the context of the PiRacer, it ensures smooth communication between hardware components like the speed sensor, Raspberry Pi, and the CAN bus. | ||
|
||
## MCP2515 | ||
**MCP2515**: A standalone CAN controller that interfaces microcontrollers (or Raspberry Pi) with the CAN bus. It processes CAN messages and interacts with the TJA1050 transceiver to send and receive data. | ||
|
||
## Network Latency | ||
**Network Latency**: The time delay between sending a message and receiving a response. Low latency is critical for real-time communication in vehicle systems to ensure timely data processing and decision-making. | ||
|
||
## OBD-II | ||
**OBD-II (On-Board Diagnostics II)**: A standardized vehicle diagnostic interface that allows external devices to access real-time data and diagnostic information from the vehicle's systems. An OBD-II cable connects the Raspberry Pi to the CAN bus. | ||
|
||
## Over-the-Air Updates (OTA) | ||
**Over-the-Air Updates (OTA)**: A method of updating software on a device remotely via a network connection, without requiring physical access. This feature is increasingly common in modern vehicles and IoT systems. | ||
|
||
## Real-Time Data | ||
**Real-Time Data**: Information that is collected, processed, and transmitted with minimal delay, allowing the system to respond to changes instantaneously. In the PiRacer project, this involves displaying live speed data from the sensor. | ||
|
||
## TJA1050 | ||
**TJA1050**: A high-speed CAN transceiver used alongside the MCP2515. It converts the CAN protocol signals to a form that the Raspberry Pi or microcontroller can understand. | ||
|
||
## Vehicle-to-Everything (V2X) | ||
**Vehicle-to-Everything (V2X)**: Communication technology that enables vehicles to exchange information with infrastructure, other vehicles, and even pedestrians. It enhances safety and efficiency in smart transportation systems. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# Software - Glossary | ||
|
||
## CAN Protocol Library | ||
**CAN Protocol Library**: A software library that abstracts the complexity of communicating with the CAN bus, providing an interface for sending and receiving messages. | ||
|
||
## Cross-compilation | ||
**Cross-compilation**: is a process of creating executable code for a platform other than the one on which the compiler is running. The platform difference might be a different OS or a different architecture. | ||
|
||
## Data Binding | ||
**Data Binding**: A technique in software development where the UI elements are automatically updated when the underlying data changes. It is often used in modern GUIs to simplify synchronization between data and views. | ||
|
||
## Error Handling | ||
**Error Handling**: Techniques and practices for managing and responding to errors in the software to ensure stability and reliability. In this project, it includes handling invalid CAN messages or sensor disconnections. | ||
|
||
## Event Loop | ||
**Event Loop**: A control flow structure in Qt that continuously checks for user interactions, system events, or data updates and processes them in real-time. | ||
|
||
## JSON Parsing | ||
**JSON Parsing**: The process of decoding JSON (JavaScript Object Notation) data into a format that the application can process. It is used for configuration files or to exchange data between systems. | ||
|
||
## Logging | ||
**Logging**: The practice of recording application activity and system events for debugging and performance monitoring. Logs can help identify issues during development and runtime. | ||
|
||
## QML (Qt Modeling Language) | ||
**QML**: A declarative language in the Qt framework used to design and implement user interfaces with a focus on simplicity and visual richness. | ||
|
||
## Signal-Slot Mechanism | ||
**Signal-Slot Mechanism**: A core concept in the Qt framework that enables communication between different parts of the application. It allows objects to send signals and other objects to respond to them. | ||
|
||
## Threading | ||
**Threading**: A programming technique that allows multiple tasks to run concurrently within the same application. For example, separate threads may handle CAN communication and GUI rendering. | ||
|
||
## User Interface (UI) Design | ||
**UI Design**: The process of creating layouts and interactive elements for the instrument cluster application to ensure usability and visual appeal. |
This file was deleted.
Oops, something went wrong.