Investigate lost power or range
Compare hill pulls, acceleration, and supported voltage behavior with the same vehicle's healthy baseline to help guide the next check.
Prototype in active development
Know what changed before you buy parts.
Use BuggyDoc while your vehicle is running well to establish its own known-good performance baseline. If power, range, or reliability changes later, compare new drive data with the same vehicle's healthy history instead of relying on factory defaults, memory, or guesswork.
Bring hard evidence to the shop and spend less time trying to reproduce a vague or intermittent complaint.
Working prototype demonstrated on a Curtis 1268. Public sales have not opened.
Record known-good
performance
performance
Compare the same
vehicle later
vehicle later
See what meaningfully
changed
changed
Bring evidence
before buying parts
before buying parts
Why collect data before there is a problem?
A healthy vehicle gives you the reference you will need later.
Most diagnostics begin after performance has already deteriorated. BuggyDoc takes a different approach: record a repeatable drive while this exact vehicle is operating well, then compare later tests with its own known-good history.
Record known good
Capture a healthy drive under normal load and repeatable conditions
Repeat later
Run a similar test if range, power, response, or reliability changes
Compare and share
Review supported differences and bring specific evidence to the shop
Planned comparison workflow: BuggyDoc is being developed as decision support, not automatic diagnosis. Comparisons will show only changes supported by collected data and work best when route, load, battery charge, and conditions are kept similar.
What the controller already knows
Useful data is already passing through your vehicle.
Most electric-vehicle motor controllers are already sophisticated devices. They monitor information such as accelerator position, motor current, controller temperature, voltage, and faults, then use those readings moment by moment to manage power and help keep the drive system operating properly.
What is often missing is an easy way to keep that information and compare it over time. BuggyDoc is being developed to continuously capture supported controller readings during a drive, connect them with how the vehicle was moving, and build a baseline of healthy performance.
If power, range, or reliability changes later, a new drive can be compared with that baseline. Instead of starting with a guess, you or your repair shop can see what changed and make a better-informed next check.
Capture intermittent problems
Preserve the conditions around a cutout, hesitation, or weak pull, then contrast that event with sessions recorded when the vehicle behaved normally.
Spot a worsening trend
Repeat the same simple test over time. If the same job begins to require more electrical effort than the healthy baseline, the change can help focus the next inspection.
Images are concept visualizations. Hardware appearance, connectors, supported vehicles, and app screens may change during development.
A practical workflow
Start with a healthy drive. Keep evidence for later.
Connect while the vehicle is performing well, capture its normal behavior, and keep that session. If a problem develops later, repeat the test and bring the differences to your own troubleshooting or a repair professional.
Connect while it is healthy
Attach a purpose-built harness to a supported controller, without changing its settings.
HARNESS DESIGNS IN DEVELOPMENTRecord normal performance
Capture supported live values under repeatable, real-world conditions while the vehicle is running well.
LIVE VALUES PROVEN ON 1268Compare and share
Review a drive, compare it with earlier tests, and send useful evidence to a technician or shop.
LOGGING WORKFLOW IN DEVELOPMENTIllustrated workflow
Test under the conditions the vehicle actually sees.
Connect near the controller, record a safe known-good drive, and repeat it later if performance changes instead of trying to recreate everything on a workbench.
Illustrative concepts only. Connection method, harness routing, mounting, screens, and equipment compatibility are not finalized.
● Working prototype
Curtis 1268
- Prototype communication demonstrated
- Multiple live values identified and displayed
- Validation will document exact controller suffixes and vehicle combinations
◒ Next validation target
Curtis 1266 / 1266A / 1266R
- Strongest next target for the golf-cart audience
- Also used in small utility and light road vehicles
- Bench and vehicle validation is the next step
◇ Second planned target
Curtis 1243GEN2
- Expands testing toward small industrial and material-handling vehicles
- Planned after the 1266-family validation
- Successful validation would broaden coverage across more equipment types
◇ Additional candidate
Curtis 1244-5651
- Promising candidate for the compatibility roadmap
- Documentation review and test-hardware sourcing are the next steps
- Offers another path toward broader controller and vehicle coverage
Useful evidence
Look for what changed when performance changed.
The Curtis 1268 prototype has displayed several values in real time. You do not need to interpret them like an engineer: BuggyDoc is being designed to connect the readings with what the vehicle was doing and highlight changes worth investigating. Availability varies by exact controller and firmware.
- Accelerator input — what were you asking the vehicle to do?
- Controller supply voltage — did it stay steady when the problem happened?
- Motor field current — how much electrical effort was being used under load?
- Controller output — how did the controller respond?
- Planned session comparison — is the pattern changing or getting worse?
LIVE TELEMETRY● CONNECTED
THROTTLE
72%
LOGIC VOLTAGE
49.6 V
FIELD CURRENT
18.2 A
ARMATURE PWM
64%
FIELD PWM
CONCEPTUAL UI · SAMPLE PROTOTYPE VALUES
38%
Planned guided performance check
Same route. Same prompts. Better comparisons.
You do not need a broken vehicle to learn something useful. BuggyDoc is being designed to learn how your vehicle normally performs, recognize meaningful changes later, and—when enough matching data is available—add context from similar vehicles.
Flat pull and coast
On a clear, level route, accelerate firmly to a chosen speed, release the pedal, and coast. Capture controller response alongside acceleration and coast-down behavior.
GUIDED TEST CONCEPTUphill pull
Repeat the same safe climb, direction, payload, and starting conditions. Compare how quickly the vehicle accelerates and which supported controller values change under load.
GUIDED TEST CONCEPTDownhill coast
Enter the same descent at a safe, repeatable speed, release the pedal, and compare deceleration with supported regenerative-braking and controller data.
GUIDED TEST CONCEPT◒ Planned vehicle profile
Show BuggyDoc what you have
- Add basic vehicle details and photos of the battery pack, motor, controller, and drivetrain
- Record modifications, recent service, and normal working conditions
- Use that profile to keep comparisons relevant to your vehicle and its category
◒ Your normal baseline
Learn how your vehicle normally performs
- Repeat a few simple tests while the vehicle is running well
- Compare acceleration, hill performance, coasting, and vibration over time
- Keep the route, load, battery charge, and weather similar when practical
◇ Changes worth checking
Know where to look next
- Weaker acceleration and a larger voltage drop may suggest checking the battery or its connections
- More electrical effort for the same drive may suggest checking brakes, bearings, tires, load, or the drivetrain
- A new vibration may suggest inspecting tires, wheels, mounts, the motor, or the drivetrain
Important: These comparisons are planned decision support, not an automatic diagnosis. Tests should only be performed in a safe, permitted area, without handling a phone while driving, and within the vehicle manufacturer's operating limits.
Honest progress
What's real. What's next.
BuggyDoc is early. Here is the line between demonstrated work and the roadmap.
● Working prototype
Demonstrated today
- Read-only communication with a Curtis 1268
- Live values during controller operation
- Throttle, logic voltage, field current, and PWM readouts
- Six-axis motion sensor hardware onboard
◒ In development
Being built now
- Phone view for test drives
- Full-session controller and motion recording
- Event markers for the moment a symptom occurs
- Vehicle-specific baseline comparisons
- Shareable logs and summaries
◇ Being evaluated
Research track
- Guided flat, uphill, and downhill checks
- Warnings for meaningful performance trends
- Additional controller families
- Configuration backup and experimental programming
- Shop and fleet comparisons
Help steer the build
Which problems should it help solve first?
Tap a reaction on any capability. Anonymous votes help prioritize the work that would be most useful during a real diagnosis.
Check it while it is happening
See supported controller values on a nearby phone while the symptom is present.
Build a known-good history
Record healthy drives now so later changes can be compared with the same vehicle.
Share useful evidence
Send a session to a technician, shop, vendor, or knowledgeable friend for a closer look.
Put faults in context
Review supported fault and status information alongside what the vehicle was doing.
Test without a laptop
Watch the most useful values during a drive or service test from a phone.
Keep an eye on performance
Use an optional mounted display to watch key values during normal operation.
Preserve known-good settings
Read and retain supported settings before service or component changes.
Make supported adjustments
Experimentally change approved parameters only where it can be done safely.
Find vehicles worth inspecting
Compare repeatable tests across multiple vehicles and flag meaningful changes for follow-up.
Product research
What would make troubleshooting easier?
Choose the capabilities you would actually use when testing a vehicle. This is research—not an order or reservation.
Price research
Where does it make sense?
These ranges test product-market fit. They are not offers, preorder prices, or commitments.
Four-minute research survey
Tell us what a useful vehicle history would include.
Whether your vehicle is healthy or already has a problem, your experience can help shape useful baselines, repeatable comparisons, and evidence that supports real repairs.
- No email required
- No purchase commitment
- Only submitted answers are saved
Beta recruitment
Help establish what healthy looks like.
We need known-good vehicles as much as problem vehicles. Healthy sessions establish the individual reference needed to recognize meaningful changes later. We are recruiting Curtis 1268 owners first, plus 1266-family, 1243GEN2, and 1244-5651 owners for planned compatibility work.
Contributor discount: Complete agreed beta tests and share usable controller and motion data to receive up to 25% off your first BuggyDoc order when the product becomes available. Selection is not guaranteed, exact discounts will be confirmed before testing, and applying is not a purchase commitment.
Straight answers
Frequently asked.
Can I buy BuggyDoc now?
No. BuggyDoc is in development and is not taking orders or preorders. The site is gathering feedback and recruiting potential beta testers.
Which controllers are supported?
Prototype communication has been demonstrated with a Curtis 1268. The Curtis 1266 / 1266A / 1266R family is the next planned validation target, followed by the Curtis 1243GEN2. The Curtis 1244-5651 is an additional evaluation candidate. None of these target models are currently supported, and compatibility will only be claimed after testing.
Is there a discount for contributing test data?
Yes. Selected participants who complete agreed beta tests and share usable controller and motion data will receive a contributor discount of up to 25% off their first BuggyDoc order when sales open. The exact discount will be confirmed before testing.
Will BuggyDoc tell me exactly which part has failed?
No. BuggyDoc is intended to show observable controller and motion data plus changes worth investigating, not automatically condemn a battery, controller, motor, or mechanical component. The goal is better evidence for the next test and less replacement by guesswork.
Can it program my controller?
Not as a promised feature. Two-way configuration and programming are experimental research areas and would only be enabled for models and parameters that can be supported safely.
Will I need a permanent display?
The primary concept uses a phone over Bluetooth. A compact permanent OLED/dashboard is also being evaluated based on interest.
Follow the build
Get meaningful updates, not noise.
Hear about prototype milestones, compatibility testing, and beta openings.