AutoGen X Pro Manual

Clear, Practical Guide For Owners, Dealers, And Admins

This manual explains how to set up, claim, connect, monitor, and operate an AutoGen X Pro controller. It uses plain language first, so you understand what the system does before worrying about technical terms. Where needed, a small technical reference is included at the end for support and advanced operators.

Start Here API Docs
For End Users Create an account, claim your controller, connect it to Wi-Fi, and monitor or control it remotely.
For Dealers Hold controllers as inventory, test them safely, unclaim before sale, and keep devices visible under your dealer account.
For Admins Assign dealers, reassign ownership, manage firmware, and recover devices when credentials or QR labels need rotation.
How X Pro Works The controller uses an internal state machine. That means it makes decisions in steps, not as a single on/off action.

First-Time Setup

A new controller normally goes through four steps: create an account, claim the device with its QR code, connect the controller to Wi-Fi, and then open the dashboard to monitor it.

1. Create an account
Create your account in the mobile app or web dashboard. Use the same account you want to use for daily monitoring.
2. Claim the controller
Scan the QR code attached to the controller or provided with the installation package.
3. Connect to Wi-Fi
If the controller is not already online, use the in-app BLE Wi-Fi setup tool to send your network name and password.
4. Open dashboard
Choose the controller in the app or web dashboard and review live values, control status, and settings.
The QR code is the ownership credential for the controller. If the controller is already claimed, the same QR code should not allow another user to take over ownership unless the device has first been unclaimed or intentionally rekeyed.

Claim Your Device

In the mobile app, go to Devices and use the QR scanner. The app reads the controller ID and claim code, then asks you to choose a device name and confirm your account password before the claim is completed.

What the user sees

You scan the QR, enter a name such as Home Generator, and confirm with your password.

What happens in the background

The backend ties the controller to your account so it appears in your devices list and dashboard views.

Important claim rule

A claimed controller belongs to the current claimant until it is unclaimed. If the QR label has been exposed and should no longer be trusted, the correct action is to rekey the device and issue a new QR label.

Connect To Wi-Fi

AutoGen X Pro supports Bluetooth Low Energy setup for Wi-Fi onboarding. In the mobile app, open BLE WiFi Setup, scan for the controller, select it, type your Wi-Fi network name and password, and tap Send Credentials.

Controller BLE name

The controller advertises a BLE name like AutoGen-XPro-123ABC. The suffix helps identify the correct device nearby.

Status button

After sending credentials, use Status to confirm whether the controller has connected and received an IP address.

If setup fails

Keep the controller in BLE setup range, verify the Wi-Fi password, and retry before assuming a controller fault.

The BLE tool is for onboarding and recovery. Day-to-day monitoring happens over Wi-Fi and cloud connection, not over BLE.

Mobile App Guide

Main sections in the app

Devices

Shows your claimed controllers. This is also where the QR-claim flow begins.

Dashboard

Shows live values, runtime information, and the main start / stop / reset button.

BLE WiFi Setup

Used only when the controller needs Wi-Fi credentials or local recovery.

BLE Connection

Advanced local Bluetooth command session for direct testing and diagnostics.

WiFi Connection

Direct IP-based local view for controller settings and local firmware update workflows.

OTA / Update

Used when an authorized user performs a local firmware upload to the controller.

Start button behavior in the app

The main control button changes based on controller condition. In standby it shows Start Generator. While the generator is running it changes to Stop Generator. If the controller is in a fault condition, it changes to Reset Generator.

Web Dashboard Guide

The web dashboard is the broader management view. It is typically used by admins and dealers, but users can also monitor their devices there when ownership data is correct.

What users do here

Monitor live values, start or stop the generator when allowed, review runtime, and adjust normal settings if their access level allows it.

What dealers and admins do here

Manage inventory, assign dealers, trigger firmware actions, view fleet-level data, and unclaim devices when preparing them for resale.

Important dashboard actions

Start / Stop / Reset
Direct operational controls. The controller still decides whether the requested action is valid for its current state.
1h / 2h / 3h timer
Sets a runtime limit. The selected time is applied once the generator is truly in a running state.
Firmware Update / Force OTA
Checks for or forces a firmware update depending on the action selected.
Hours Reset
Clears accumulated runtime on the controller. Use intentionally only.
Add Runtime
Adds historical runtime manually if service records need to be corrected.

What You See On Screen

The dashboard is designed around a small number of values that matter during real operation.

Battery Voltage
The live battery-bank voltage being monitored by the controller. This is the key value for voltage-based automatic start and stop.
Generator Status
Shows whether the controller believes the generator is stopped, starting, running, pausing, or in error.
Current
Live current reading reported by the controller for system monitoring.
Temperature
Live temperature used both for visibility and for temperature-based control logic.
Accumulated Runtime
Total recorded runtime over the life of the controller, unless manually reset.
Last Runtime
The duration of the most recent run or the current run session if the engine is still running.

How Start And Stop Work

AutoGen X Pro does not simply switch the generator on and off instantly. When a start command is accepted, it enters a start sequence and waits for proof that the generator is actually running. If that proof is not detected, the controller retries. If repeated attempts fail, the controller enters an error state to avoid false operation.

Start accepted

Usually only when the controller is in standby or an equivalent ready state.

Stop accepted

Used to return the controller to stop. If the controller is already in an error state, reset is usually the correct action instead.

If the start button appears to do nothing, the issue is often not the button itself. The controller may simply be in a state where start is intentionally blocked.

Automatic Start And Stop

Voltage-based automatic start

The most common automatic start method is battery voltage. If the battery bank falls below the configured Start Voltage, the controller begins its automatic start sequence.

Voltage-based automatic stop

While the generator is running, if the battery bank rises above the configured Stop Voltage, the controller stops the generator because charging has reached the configured stop condition.

2-wire start mode

Some installations use a 2-wire external start input instead of relying only on battery-voltage behavior. In that mode, the controller starts when the external start condition is present and stops when that condition is removed long enough for the controller to confirm it safely.

Temperature-based behavior

High temperature start threshold

If temperature rises above the configured upper threshold while the controller is waiting, the generator can be started automatically.

Low temperature shutdown threshold

If temperature drops below the configured lower threshold while the generator is running, the controller can shut the system down.

Why Error States Happen

Error states are protective. The controller enters them when it cannot safely confirm normal operation.

Failed start attempts

The controller tried to start the generator several times but never received a valid running confirmation.

Run confirmation lost

The controller expected the generator to be running, but the run-detection signal no longer matched that expectation.

Conflicting input conditions

The controller detected a condition that makes continued running unsafe or invalid for the current mode.

If the generator is already running and a bad condition appears, the controller may not continue “just because it is already on”. That would be unsafe. Instead, it may stop or enter an error state so the system can be checked and reset properly.

Timers And Runtime

Run limit timers

The 1-hour, 2-hour, and 3-hour options do not stop the generator immediately. They arm a run limit. Once the generator is truly in a running state, the selected timer starts counting down. When it expires, the controller issues a stop command.

Accumulated Runtime

Total operating time recorded by the controller over its life, unless hours are reset manually.

Last Runtime

The duration of the most recent run cycle, or the current cycle while the generator is still running.

Hours reset

Hours reset clears the controller’s total runtime record. This is usually a service or maintenance action, not a normal user action.

Add runtime

Add runtime is used when service records need correction. It allows runtime to be added manually rather than overwritten.

Dealer And Admin Workflow

Dealer inventory

Dealers should continue to see controllers assigned to them even after those controllers are unclaimed and ready for sale. That visibility comes from dealer assignment, not from temporary claim state.

Admin assigns dealer

An admin assigns the device to a dealer account. This is what makes the controller part of that dealer’s inventory.

Dealer may test-claim

A dealer can claim a device temporarily for testing, then unclaim it before handing it to the customer.

Customer then claims

After unclaim, the customer can use the same QR code unless the device has been intentionally rekeyed.

Unclaim vs rekey

Unclaim

Use when ownership should be cleared but the same QR code should still remain valid.

Rekey

Use when the old QR must no longer work. Rekey issues a new claim credential and requires a new QR label.

Technical Reference

This section maps user-facing wording to the internal controller language used in firmware and dashboards. It is here for support staff, dealers, and admins. End users do not need to read this section to operate the product.

Start Voltage
Firmware term: BatteryBankLow
Stop Voltage
Firmware term: BatteryBankHigh
Generator Running Detection
Firmware terms: RunSignal, RunSignalSelected, running signal source selection
2-Wire External Start Input
Firmware terms: CutOffVolts, CutOffSet, 2-wire states
High Temperature Start
Firmware term: upper temperature threshold, stored in temperature_thresholdH
Low Temperature Shutdown
Firmware term: lower temperature threshold, stored in temperature_thresholdL
Accumulated Runtime
Published runtime totals from firmware runtime counters
Last Runtime
Current session or latest completed run duration