πŸ“š
Documentation Hub
AI Tech Talk & Support Β· Last Updated: 2026-03-07
AI Tech Talk & Support Platform
Enterprise ASP.NET Core 9.0 platform providing AI-assisted technical diagnostics, hardware control, subscription management, and professional board repair services. 12-project solution with multi-domain routing and full protocol stack support.
Platform Summary
PlatformASP.NET Core 9.0
Projects12 total (10 src/ + 2 shared/)
Primary Domainaitechtalkandsupport.com
AI EngineGroq API + OLLAMA (local)
Payment GatewayPayPal (Live)
Phone+1-629-276-9373
Address2321 E. 61 Avenue, Spokane WA 99223
Build Status0 errors, 2 harmless NuGet warnings
Domain Routing
DomainRoutes ToPurpose
aitechtalkandsupport.comlanding-pro.htmlCustomer landing page
admin.aitechtalkandsupport.comadmin/server-control.htmlAdmin control center
payments.aitechtalkandsupport.compayments/admin.htmlPayments management
Project Structure
ProjectPurpose
AITechTalk.WebMain web UI, Blazor/Razor, wwwroot static files
AITechTalk.APIREST API backend, all /api/* endpoints
AITechTalk.AIEngineAI bot orchestration, 6 bots, Groq API client
AITechTalk.SerialDataProHardware/serial/PDU control, ESP32 bridge
AITechTalk.PaymentsStripe + PayPal payment processing
AITechTalk.TwilioVoice/SMS via Twilio
AITechTalk.DeviceServiceDevice management and registry
AITechTalk.WorkerBackground workers and scheduled tasks
AITechTalk.AppHostAspire orchestration host
AITechTalk.ServiceDefaultsShared service configuration
Quick Start
Get the platform running locally in minutes. Prerequisites: .NET 9 SDK, Docker (for MQTT), Groq API key, PayPal developer account.
Setup Steps
  1. Clone or open the solution: AITechTalkPlatform.sln in Visual Studio 2022 or dotnet run from the AppHost project.
  2. Copy appsettings.example.json to appsettings.Development.json and fill in your API keys.
  3. Start the MQTT broker: docker run -d -p 1883:1883 eclipse-mosquitto
  4. Build the solution to confirm 0 errors: dotnet build
  5. Run the platform: dotnet run --project src/AITechTalk.AppHost
  6. Open your browser and navigate to http://localhost:5000/landing-pro.html
Required Configuration
// appsettings.Development.json { "Groq": { "ApiKey": "gsk_your_key_here" }, "PayPal": { "ClientId": "AREQm-HY..." }, "Mqtt": { "Host": "localhost", "Port": 1883 }, "Hardware": { "SerialPort": "COM3", "BaudRate": 115200 }, "Twilio": { "AccountSid": "AC...", "AuthToken": "..." } }
Platform Architecture
The platform uses a multi-project ASP.NET Core 9.0 architecture with Aspire orchestration, subdomain routing middleware, and hardware integration via serial/ESP32 gateway.
AI Bot System
Bot NameModelSpecialty
Automotive Specialistwizardlm-uncensored:13bECU, CAN bus, OBD-II, IMMO
IoT Expertdolphin3-llama3.1:8bESP32, MQTT, sensors, firmware
HVAC Technicianhermes3:8bHVAC systems, climate control
Computer Supportllama3.2-darkGeneral hardware/software support
Electronics Propygmalion-uncensored:8bPCB, EEPROM, circuit analysis
Hardware Stack
ComponentRoleConnection
16-ch Relay Module (LOW-LEVEL TRIGGER)PDU / power distributionESP32 GPIO β†’ Relay IN pins
ATX PC Power Supply12V rail sourceGREEN→BLACK jumper, YELLOW=+12V to relay COM
KICKPI H168 (Γ—2)SBC / OLLAMA nodesCH 1-4 relay, Ethernet
BigTreeTech Pi 1.2.1IoT control nodeCH 3-4 relay, Ethernet
EAIDK310VAI inference (NPU)CH 5-6 relay, Ethernet
ESP32 Heltec HTIT-V32PDU bridge / MQTT gatewayCOM3 Β· DSD Tech SH-U09GN Β· 115200
Waveshare USB-to-AllProtocol programmerUSB Β· I2C/SPI/JTAG
AI Chat API
The AI chat endpoint routes queries to the appropriate specialist bot via Groq API. All requests must include a message and agentType.
Endpoints
MethodEndpointDescription
POST/api/ai/chatSend a message to an AI specialist bot
Request Body
// POST /api/ai/chat { "message": "What is the UDS diagnostic flow for P0300?", "agentType": "automotive", "modelId": "wizardlm-uncensored:13b" // optional }
Agent Types
automotiveAutomotive Specialist
iotIoT Expert
hvacHVAC Technician
computerComputer Support
electronicsElectronics Pro
Payments API
Payment processing via PayPal. Orders are created client-side using the PayPal SDK and confirmed server-side after capture.
Endpoints
MethodEndpointDescription
POST/api/payments/processRecord a captured PayPal payment
GET/api/payments/subscriptionsList active subscriptions
GET/api/payments/historyTransaction history
Process Payment Body
{ "orderId": "5O190127TN364715T", "serviceType": "professional", // starter|professional|board-repair "amount": 49.99, "email": "customer@email.com", "name": "John Doe", "phone": "+1-555-123-4567" }
Hardware API
Control relay channels, fan speeds, and connected devices via the PDU orchestrator service. Requests are routed through the ESP32 serial bridge.
PDU Relay Endpoints
MethodEndpointDescription
GET/api/pdu/statusAll 16 relay channel states
POST/api/pdu/channel/{n}/onTurn on relay channel N (1-16)
POST/api/pdu/channel/{n}/offTurn off relay channel N
POST/api/hardware/fansSet fan speeds (0-100%)
POST/api/hardware/fans/autoEnable auto fan control
POST/api/hardware/cyd/messageSend text to ESP32 CYD display
Relay Channel Map
Channel(s)Assignment
CH 1–4SBC Power (KICKPI H168 Γ—2, BigTreeTech Pi)
CH 5–6AI Lab Power (EAIDK310V)
CH 7–8Automotive Scanners (KTAG / KESS2)
CH 9–10I2C/SPI bus via Waveshare programmer
CH 11–12JTAG bus via Waveshare programmer
CH 13–14RF / RFID / IR modules
CH 15Chassis fans
CH 16Aux 12V rail
Tech News API
Tech news feed aggregated from RSS sources. Used in the landing page Tech News tab.
Endpoint
MethodEndpointDescription
GET/api/news?category=&page=&limit=Fetch paginated tech news articles
Query Parameters
categoryall | ai | automotive | security | hardware
pageinteger (default: 1)
limitinteger (default: 9, max: 50)
Automotive Protocols
Supported automotive communication protocols and diagnostic standards.
Supported Protocols
OBD-II
UDS (ISO 14229)
CAN bus
CAN-FD
J2534
K-Line
LIN bus
IMMO / BCM
FlexRay
DoIP (Eth)
UDS Service IDs
SIDService NameDescription
0x10Diagnostic Session ControlSwitch diagnostic session modes
0x11ECU ResetSoft/hard reset of the ECU
0x22Read Data By IdentifierRead parameter IDs (PIDs)
0x27Security AccessSeed/key authentication
0x2EWrite Data By IdentifierWrite calibration or config values
0x31Routine ControlExecute diagnostic routines
0x34Request DownloadBegin flash programming session
0x36Transfer DataTransfer firmware/calibration data
0x19Read DTC InformationRead fault codes (DTCs)
Embedded & IoT Protocols
Low-level communication protocols supported for embedded systems, IoT devices, and hardware programming.
Supported Protocols
UART
I2C
SPI
JTAG
SWD
1-Wire
RS-232
RS-485
MQTT
ESP-NOW
RFID
RF 433MHz
IR
Modbus RTU
EEPROM / Flash Operations
Read EEPROMI2C or SPI via Waveshare programmer
Write EEPROMPage-write mode with verify
Flash ProgrammingJTAG/SWD via Waveshare or J-Link
EraseSector or chip erase supported
Hardware Setup
Physical hardware setup guide for the relay PDU, ATX PSU, and SBC connections.
ATX PSU Configuration
  1. Jump the GREEN wire (PS_ON) to any BLACK wire (GND) on the ATX 24-pin connector to enable standalone operation without a motherboard.
  2. Connect YELLOW (+12V) to the relay module COM terminals. This provides the switched 12V output power.
  3. Connect BLACK (GND) from PSU to relay module GND and all device ground references.
  4. The relay module is LOW-LEVEL TRIGGER β€” the relay activates when the ESP32 GPIO goes LOW (0V). Keep this in mind when writing firmware.
  5. Connect relay NO (Normally Open) contacts to device power inputs. Devices are OFF by default (safe state).
SBC Power Connections
// Relay channel to device mapping CH1 β†’ KICKPI H168 #1 power input (+12V via relay NO) CH2 β†’ KICKPI H168 #2 power input (+12V via relay NO) CH3 β†’ BigTreeTech Pi 1.2.1 (+5V adapter via relay) CH4 β†’ BigTreeTech Pi #2 (reserved) CH5 β†’ EAIDK310V AI Lab (+12V via relay) CH6 β†’ EAIDK310V secondary rail CH7 β†’ KTAG automotive scanner CH8 β†’ KESS2 automotive programmer CH9 β†’ I2C/SPI bus power (Waveshare) CH10 β†’ SPI target device power CH11 β†’ JTAG target device power CH12 β†’ JTAG secondary CH13 β†’ RF module power CH14 β†’ RFID/IR module power CH15 β†’ Chassis fans CH16 β†’ Aux 12V rail (general purpose)
PDU Relay Control
The PDU Orchestrator service manages the 16-channel relay module through the ESP32 serial bridge. The PDUController exposes REST endpoints consumed by the admin UI.
Key Files
PDU ServiceAITechTalk.SerialDataPro/Services/PDUOrchestrator.cs
API ControllerAITechTalk.SerialDataPro/Controllers/PDUController.cs
ESP32 Firmwarefirmware/ESP32_PDU_Bridge/ESP32_PDU_Bridge.ino
Wiring Diagramdocs/ATX-PSU-RELAY-WIRING-DIAGRAM.md
Config Keyappsettings.json β†’ "Hardware"
Serial Protocol
// Command format (ASCII over UART @ 115200 baud) RELAY:ON:CH{n} // Turn on relay N (1-16) RELAY:OFF:CH{n} // Turn off relay N RELAY:STATUS // Get all 16 channel states // Response: STATUS:1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0
ESP32 Firmware
The ESP32 Heltec HTIT-V32 runs the PDU bridge firmware, listening on UART (COM3) for relay commands from the ASP.NET backend and bridging them to the 16-channel relay module via GPIO.
Setup
  1. Install Arduino IDE and add the ESP32 board manager URL: https://dl.espressif.com/dl/package_esp32_index.json
  2. Install DSD Tech SH-U09GN USB-to-TTL driver. Connect to COM3 at 115200 baud.
  3. Open firmware/ESP32_PDU_Bridge/ESP32_PDU_Bridge.ino in Arduino IDE.
  4. Select board: Heltec WiFi Kit 32 or compatible ESP32 variant.
  5. Upload the firmware. The ESP32 will begin listening on Serial at 115200 baud.
GPIO Relay Mapping
// ESP32 GPIO β†’ Relay IN pin mapping // Relay module: LOW-LEVEL TRIGGER (GPIO LOW = relay ON) GPIO 4 β†’ Relay CH1 (KICKPI #1) GPIO 5 β†’ Relay CH2 (KICKPI #2) GPIO 16 β†’ Relay CH3 (BigTreeTech #1) GPIO 17 β†’ Relay CH4 (BigTreeTech #2) GPIO 18 β†’ Relay CH5 (EAIDK #1) GPIO 19 β†’ Relay CH6 (EAIDK #2) GPIO 21 β†’ Relay CH7 (KTAG) GPIO 22 β†’ Relay CH8 (KESS2) // ... CH9-16 on GPIO 23, 25, 26, 27, 32, 33, 34, 35
Subscription Plans
Three-tier subscription model processed through PayPal. Customers subscribe via the landing page payment section.
Plan Comparison
FeatureStarter $9.99/moProfessional $49.99/moEnterprise Custom
AI Queries/Month1001,000Unlimited
AI Models Access2 modelsAll 5 modelsAll + custom
Email Supportβœ“βœ“βœ“
Priority Supportβœ—βœ“βœ“
Custom Trainingβœ—βœ“βœ“
API Accessβœ—βœ“βœ“
SLA Guaranteeβœ—βœ—βœ“
Platform Changelog
History of major platform changes, fixes, and features.
2026
2026-03-07 Feature Full enterprise UI rebuild β€” all HTML pages rebuilt to service-info.html design system (dark theme, Segoe UI, tab-based navigation)
2026-03-06 Feature PDU Orchestrator created β€” PDUOrchestrator.cs, PDUController.cs, ESP32_PDU_Bridge.ino, ATX wiring diagram
2026-03-06 Fix Complete warning cleanup β€” 186 code warnings resolved to 0 (CS8603, CS1998, CA2021, CA2022 and more)
2026-03-06 Feature AiChatEndpoints.cs created β€” /api/ai/chat endpoint wired to GroqService for real AI responses
2026-03-06 Fix Removed Flask Jinja2 template syntax from admin/dashboard.html (url_for, config.AI_MODEL, etc.)
2026-03-06 Fix Fixed index.html AI chat to route through /api/ai/chat instead of direct OLLAMA hostname
2026-03-06 Infra SubdomainRoutingMiddleware updated β€” admin subdomain now routes to admin/server-control.html
Recommended Tools & Resources
Essential open-source tools, partner services, and APIs used across the AI Tech Talk & Support platform for diagnostics, firmware development, reverse engineering, and network analysis.
Automotive & Diagnostics
Reverse Engineering & Security
Firmware & Embedded Development
Partners & Services