Arcbound FieldThe EVSE DirectorySubscribe
← Learn

Primer 06 · ~6 minFree

How to use The EVSE Directory

Search, brands, free samples, guides, and when Solo unlocks the full corpus.

Arcbound Field (The EVSE Directory) is a fault and procedure encyclopedia for EVSE and site-stack gear—not vehicle OBD, not OEM manual dumps, not a forum (yet). This primer is the map.

Surfaces

Go hereWhen
LearnYou need curriculum before a deep guide
GuidesProtocol / site field manuals (many free)
DatabaseSearch fault codes, tags, brands
BrandsOEM ownership notes + fault index
CategoriesEquipment layer (modem, cooling, LMS…)
HelpCurated FAQ
RequestMissing code / new entry ask
PricingFounding / Solo / Pro / Team

Free vs Solo vs Pro

  • Free: Learn primers, free guides, ~80 sample fault procedures (full body), brand hubs, help FAQ.
  • Solo: Full published corpus + weekly updates (/whats-new).
  • Pro: Print sheets, direct Q&A (/qa), early-access codes.
  • Team: Seats + API for shops.

Samples are the SEO and trust funnel—not a teaser wall of one sentence.

Search tips

  1. Start with the exact HMI/OCPP string or OEM code.
  2. If unknown, search the symptom (isolation, heartbeat, GFCI).
  3. Filter by brand when the vendor string names one.
  4. Open related guides linked on the entry.
  5. Confirm one gun vs site before following HV steps.
  1. EVSE levels and tickets
  2. Reading StatusNotification
  3. OCPP Faulted triage
  4. One free protocol sample that matches today’s ticket
  5. Subscribe to Solo when you need the OEM-deep packs daily
  1. Brand hub for the OEM on site
  2. Exact code in database
  3. Free CCS/NACS/cooling/payment guide when the branch is protocol
  4. /request if the code is missing — do not invent from memory

Field action

Bookmark theevsedirectory.com/guides/ocpp-faulted-triage and theevsedirectory.com/learn. Add the PWA on your phone for weak-signal pads.

Confirmations and provenance

Entries show verified dates and confirmation counts. When a fix matches the field, use the confirm control (signed-in) so the next tech sees signal—not vibes.

Offline / PWA

Install the site as an app on your phone. Weak-signal pads are exactly when you need the OCPP map and a sample procedure without waiting on LTE.

What we will not become

  • Vehicle OBD / dealer scan-tool replacement
  • Unlicensed reproduction of OEM service manuals
  • Unmoderated public wiki

Those boundaries keep the corpus trustworthy. Community discussion is a later wave after Learn/guides earn traffic—use Help and Request today.

Founding and Solo

If free samples already save you truck rolls, founding locks price for early supporters: pricing. Solo is for techs who live in OEM-deep packs daily.

Share with your shop

Point apprentices at Learn in order. Point leads at brand hubs and exact codes. Same site; different entry ramps.

Worked example: apprentice onboarding week

Day 1–2: Learn primers 01–03. Day 3: free OCPP + CCS guides. Day 4: shadow a ticket using database search. Day 5: submit one /request for a missing code they saw. That is a one-stop curriculum without a forum.

Worked example: lead tech

Brand hub → exact code → print sheet (Pro) → confirm fix. Use Help FAQ only when the branch is unfamiliar.

Categories worth browsing

Enriched intros exist for DCFC, modem, payment, liquid cooling, and power/LMS under Categories. Use them when the ticket is layer-shaped rather than OEM-shaped.

Search operators that help

Exact model strings beat brand alone. Include OCPP errorCode text in quotes when the CSMS shows it. If search returns only gated Solo rows, open the free sample siblings in the same family—often the branch is identical and the OEM packing differs.

Free vs Solo without resentment

Free content is the curriculum and the SEO surface. Solo is the deep OEM pack and early-access rows. Use free to decide the branch; buy Solo when you need the exact menu path on the cabinet you own. That is the intended funnel, not a tease.

When to use Field Help vs Pro Q&A

Help FAQ answers patterned questions with links. /request is for missing codes. /qa is for Pro+ subscribers who need a human on a live sticky ticket. Do not paste customer PII into public request forms.

Field action checklist (directory)

  1. Start at Learn if the branch is unfamiliar.
  2. Search exact code/model; open free samples before Solo.
  3. Use brand hubs for OEM packing; categories for layer faults.
  4. Submit /request for gaps; use /qa only on Pro+ sticky tickets.
  5. Keep customer PII out of public forms and exports.

One-stop map

Learn primers → free guides → free samples → Solo packs → /request or Pro Q&A. That order keeps beginners and experts in the same hub without a forum this wave.