From 459c221dab7b033df0127604d74b5348fc774a1b Mon Sep 17 00:00:00 2001
From: MeatPi Electronics <94690098+meatpiHQ@users.noreply.github.com>
Date: Tue, 22 Oct 2024 01:58:29 +1100
Subject: [PATCH] Update 3.New_Vehicle_Profiles.md

---
 docs/content/0.Config/6.Automate/3.New_Vehicle_Profiles.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/content/0.Config/6.Automate/3.New_Vehicle_Profiles.md b/docs/content/0.Config/6.Automate/3.New_Vehicle_Profiles.md
index 542d5f1..b84b514 100644
--- a/docs/content/0.Config/6.Automate/3.New_Vehicle_Profiles.md
+++ b/docs/content/0.Config/6.Automate/3.New_Vehicle_Profiles.md
@@ -1,3 +1,7 @@
+---
+title: New Vehicle Profiles
+---
+
 # How to Create a New Vehicle Profile
 
 A vehicle profile is a JSON file that tells WiCAN how to communicate with the vehicle. It uses the ELM327 protocol instead of sending raw CAN frames, making it as user-friendly as possible. ELM327 is an AT command-based protocol used by all OBD apps and software. This is also important for creating a profile since most EVs have non-standard PIDs to request data, such as EV battery state of health and other vehicle-specific parameters. These PIDs are not publicly available; however, apps like Car Scanner and Torque have a huge database of these PIDs.