docs: remove vehicle-specific Xterra branding
This commit is contained in:
@@ -4,7 +4,7 @@ Overland Controller is a local-first vehicle power and monitoring system designe
|
|||||||
|
|
||||||
Current target vehicle:
|
Current target vehicle:
|
||||||
|
|
||||||
Nissan Xterra
|
overland vehicle
|
||||||
|
|
||||||
The firmware itself is intended to stay vehicle-agnostic.
|
The firmware itself is intended to stay vehicle-agnostic.
|
||||||
|
|
||||||
|
|||||||
+1
-1
@@ -880,7 +880,7 @@ Updates the AP SSID/password and restarts the access point.
|
|||||||
Example request:
|
Example request:
|
||||||
|
|
||||||
{
|
{
|
||||||
"ssid": "Xterra-Camp",
|
"ssid": "Overland-Controller",
|
||||||
"password": "new-secure-password"
|
"password": "new-secure-password"
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
# Architecture
|
# Architecture
|
||||||
|
|
||||||
Overland Controller is a distributed monitoring and control platform for the Nissan Xterra and future mobile power systems.
|
Overland Controller is a distributed monitoring and control platform for mobile power systems and overland vehicles.
|
||||||
|
|
||||||
Core principle:
|
Core principle:
|
||||||
|
|
||||||
|
|||||||
@@ -1,4 +1,4 @@
|
|||||||
# Xterra Overland Dashboard - Codex Handoff
|
# Overland Controller - Codex Handoff
|
||||||
|
|
||||||
## Repository
|
## Repository
|
||||||
|
|
||||||
@@ -27,7 +27,7 @@ Before making any code changes:
|
|||||||
|
|
||||||
# Project Overview
|
# Project Overview
|
||||||
|
|
||||||
The project is an overland vehicle monitoring and control system for a Nissan Xterra.
|
The project is an overland vehicle monitoring and control system for a overland vehicle.
|
||||||
|
|
||||||
Architecture:
|
Architecture:
|
||||||
|
|
||||||
|
|||||||
@@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
## Purpose
|
## Purpose
|
||||||
|
|
||||||
The Raspberry Pi Pico 2 W dashboard is the primary user interface for the Xterra Overland Power & Monitoring Dashboard.
|
The Raspberry Pi Pico 2 W dashboard is the primary user interface for the Overland Controller dashboard.
|
||||||
|
|
||||||
Its responsibilities are:
|
Its responsibilities are:
|
||||||
|
|
||||||
|
|||||||
@@ -4,7 +4,7 @@
|
|||||||
|
|
||||||
The first hardware version will use UART over CAT5 between the Pico dashboard and the ESP32 controller.
|
The first hardware version will use UART over CAT5 between the Pico dashboard and the ESP32 controller.
|
||||||
|
|
||||||
UART is simpler than RS-485 and should be reliable for the short cable run inside the Xterra.
|
UART is simpler than RS-485 and should be reliable for the short cable run inside the vehicle.
|
||||||
|
|
||||||
RS-485 remains a future fallback if testing reveals communication issues.
|
RS-485 remains a future fallback if testing reveals communication issues.
|
||||||
|
|
||||||
|
|||||||
@@ -233,7 +233,7 @@ input{width:100%;border:1px solid var(--line);border-radius:12px;padding:12px;ba
|
|||||||
<div class="list">
|
<div class="list">
|
||||||
<div class="row"><span class="muted">Current AP</span><span class="v" id="apCurrentSsid">--</span></div>
|
<div class="row"><span class="muted">Current AP</span><span class="v" id="apCurrentSsid">--</span></div>
|
||||||
<div class="row"><span class="muted">Security</span><span class="v" id="apSecurity">--</span></div>
|
<div class="row"><span class="muted">Security</span><span class="v" id="apSecurity">--</span></div>
|
||||||
<input id="apSsidInput" placeholder="AP SSID, example: Xterra-Camp">
|
<input id="apSsidInput" placeholder="AP SSID, example: Overland-Controller">
|
||||||
<div class="inputHelp">SSID must be 1-32 characters.</div>
|
<div class="inputHelp">SSID must be 1-32 characters.</div>
|
||||||
<input id="apPasswordInput" placeholder="New AP password" type="password">
|
<input id="apPasswordInput" placeholder="New AP password" type="password">
|
||||||
<div class="inputHelp">Password must be 8-63 characters. The current password is never displayed.</div>
|
<div class="inputHelp">Password must be 8-63 characters. The current password is never displayed.</div>
|
||||||
|
|||||||
@@ -1,7 +1,7 @@
|
|||||||
<!DOCTYPE html>
|
<!DOCTYPE html>
|
||||||
<html>
|
<html>
|
||||||
<head>
|
<head>
|
||||||
<title>Xterra Dashboard Simulator</title>
|
<title>Overland Controller Simulator</title>
|
||||||
<link rel="stylesheet" href="/static/style.css">
|
<link rel="stylesheet" href="/static/style.css">
|
||||||
</head>
|
</head>
|
||||||
<body>
|
<body>
|
||||||
@@ -23,7 +23,7 @@
|
|||||||
|
|
||||||
<main>
|
<main>
|
||||||
<header>
|
<header>
|
||||||
<h1>Xterra Dashboard</h1>
|
<h1>Overland Controller</h1>
|
||||||
<div id="statusLine">UART: -- | WiFi: --</div>
|
<div id="statusLine">UART: -- | WiFi: --</div>
|
||||||
</header>
|
</header>
|
||||||
|
|
||||||
|
|||||||
@@ -11,7 +11,7 @@ void setup() {
|
|||||||
Serial.print("Target: ");
|
Serial.print("Target: ");
|
||||||
Serial.println(TARGET_ADDRESS);
|
Serial.println(TARGET_ADDRESS);
|
||||||
|
|
||||||
NimBLEDevice::init("XterraESP32");
|
NimBLEDevice::init("OverlandController");
|
||||||
NimBLEDevice::setPower(ESP_PWR_LVL_P9);
|
NimBLEDevice::setPower(ESP_PWR_LVL_P9);
|
||||||
|
|
||||||
NimBLEAddress address(std::string(TARGET_ADDRESS), BLE_ADDR_PUBLIC);
|
NimBLEAddress address(std::string(TARGET_ADDRESS), BLE_ADDR_PUBLIC);
|
||||||
|
|||||||
@@ -44,7 +44,7 @@ void setup() {
|
|||||||
Serial.print("Target: ");
|
Serial.print("Target: ");
|
||||||
Serial.println(TARGET_ADDRESS);
|
Serial.println(TARGET_ADDRESS);
|
||||||
|
|
||||||
NimBLEDevice::init("XterraESP32");
|
NimBLEDevice::init("OverlandController");
|
||||||
NimBLEDevice::setPower(ESP_PWR_LVL_P9);
|
NimBLEDevice::setPower(ESP_PWR_LVL_P9);
|
||||||
|
|
||||||
NimBLEAddress address(std::string(TARGET_ADDRESS), BLE_ADDR_PUBLIC);
|
NimBLEAddress address(std::string(TARGET_ADDRESS), BLE_ADDR_PUBLIC);
|
||||||
|
|||||||
Reference in New Issue
Block a user