Electric Start vs Remote Start vs ATS Auto Start: A Buyer's Guide

Electric start does not mean automatic backup. Before comparing offers, identify who sends the start request, how it reaches the generator, and what the quoted equipment does next. An automatic transfer switch (ATS) adds a separate question: who controls the transfer of the load?

Use the Start-Mode Trigger and Interface Proof Matrix below to compare those functions for the exact quoted build. The matrix is a purchasing aid, not a wiring or installation guide. It does not confirm any start feature on a BEAR model.

Identify who or what initiates the start request

Start with who makes the start decision. These four arrangements require different evidence:

Manual means a person makes the start decision. Electric describes the starting mechanism. A key or pushbutton at the generator can therefore provide electric start without remote or automatic control.

Remote means the user or sending device is away from the generator control. The quote must still say whether the link is wired or wireless and whether a person or a controller sends the request.

Automatic means control logic makes the start decision. Name the device that senses the condition and sends the request. Then record what the generator is documented to do in response.

Compare functions, not feature labels

Two offers labelled “remote start” may cover different work. One may include a wireless receiver; another may provide only an input for a third-party wired command. An ATS-issued request is a third possible arrangement.

The matrix below separates the trigger, command path, response, load transfer, required options and proof. Keep unknown fields open. A previous order or another controller's manual cannot fill a gap in the current quote.

Trace the command path and stop at the documented response

Name both ends of the command path before accepting a start claim. For local electric start, record the quoted panel and onboard control. For wireless start, list the supplied fob or app, receiver and any gateway.

Wired and ATS-commanded start need the external sending device and the generator-side input. For ATS start, also name the device that senses the condition and decides to send the request.

Shorthand is not an interface specification. Labels such as “two-wire,” “dry contact,” “remote input,” “AMF,” or “ATS-ready” do not establish compatibility. The exact drawing and controller records must define the contact form, signal voltage, terminals and common/reference, powered or unpowered behavior, and maintained or momentary action. Keep the sequence review with those documents and the qualified project reviewer.

Next, record what happens after the request reaches the generator. Use the offered build's documents to answer:

• Does the record show that the request was recognized?
• Which controller mode or prerequisite must already be present?
• What does the exact document say about initiating and ending the start request?
• Which running, available, alarm, or other indication is included, if any?
• Who owns stop, cooldown, reset, and return-to-ready behavior?
• Which functions, accessories, states, or failure responses are explicitly excluded or still open?

Do not invent controller settings to close an open field. Crank attempts, delays, warm-up, cooldown and fault behavior must come from the files for the offered build.

Separate engine start, generator availability, and load transfer

A running engine does not prove load transfer. It also does not show that the generator met the project's conditions for use or that the ATS chose the correct source. Record those results separately.

Use separate matrix fields for:

• start request: who or what initiates it;
• generator response: what the exact set/controller is documented to do;
• availability decision: which condition and owner determine that the source may be used;
• transfer decision: which equipment senses sources and commands switching;
• power transfer: which equipment connects and disconnects the load;
• standby outcome: which broader project evidence establishes the agreed system result.

A standby review extends beyond the start command. It may include sensing and transfer equipment, battery charging, control power, fuel and site conditions. Protection, interlocks, installation, commissioning and maintenance also need named owners; do not assume one supplier covers them all.

For portable-generator safety, see OSHA's Using Portable Generators Safely and Grounding Requirements for Portable Generators. The OSHA electrical page provides wider safety guidance. These sources do not specify an ATS design or the start mode for this project. Installation, grounding, connection and transfer decisions require applicable instructions and qualified parties.

Build the Start-Mode Trigger and Interface Proof Matrix

Create one row per exact quoted generator, controller, panel, and accessory arrangement. Do not combine family variants under a shared feature icon.

The matrix identifies the quoted functions and who supplies them. Detailed signals, control power, inputs and outputs, alarms, interlocks and witnessed interface tests belong in the project technical review. Do not mistake a completed commercial comparison for that approval.

Use the generator documents-before-order checklist to keep the quotation, option list, panel/controller record, applicable files, and change history aligned. A later controller, receiver, module, firmware, setting, or accessory change reopens every matrix row that depended on it.

When the order adds a supplier-configured controller, wireless receiver, remote input, ATS interface, panel label, or manual change, attach the command-path and ownership rows to the BEAR OEM and private-label project review.

Rank proof by applicability, not by technical appearance

Match the proof to the offered build first. A detailed manual may cover several variants. It is not enough if the quote omits the controller, options or assigned functions.

Use this evidence order:

1. exact quotation, BOM, option list, and controlled configuration record;
2. applicable controller, panel, receiver, gateway, or accessory document tied to that build;
3. configuration-specific technical confirmation, drawing, setting record, or witnessed result that actually exists;
4. family brochure or manual used only to identify questions and possible dependencies;
5. icons, listings, short videos, screenshots, or unsupported labels used only as weak leads.

Controller documents are product-specific. The Deep Sea Electronics remote-start input document concerns its named control module. The ComAp MRS controller page and ComAp AMF controller page describe their own products. None proves a BEAR start feature or permits assumptions about another controller.

A demonstration needs the same build identity. Record the controller, accessories, command source, initial mode and observed response. Add the date, issuer or witness, excluded transfer functions and unresolved items. Without that record, a video shows an engine starting but does not prove the quoted arrangement.

Wireless range needs its own evidence. If the supplier states a distance, ask which device was measured and under what conditions. Record obstructions, environmental limits and the link to the offered build; a range claim alone does not prove it will work at the buyer's site.

Expose readiness dependencies and failure states without designing them

The supplier must state what the start path needs to work. Use the matrix's dependency row for the battery and charger, control power, receiver or gateway, interface accessories and external command device. Add fuel preparation, required operating mode, permissives and site conditions only where the applicable documents require them.

For each item, name the supplier or project owner and mark it included, optional, excluded or open. This separates the quoted equipment from work the buyer must arrange.

Then ask what remains true when the expected path is unavailable:

• wireless command not received;
• external wired command absent, stuck, or removed;
• controller not in the required operating mode;
• starting energy or auxiliary power unavailable;
• start request recognized but the documented response not completed;
• generator starts but no availability or transfer evidence exists;
• ATS or external controller changes state without a matched generator record;
• stop, cooldown, reset, alarm, or return-to-ready ownership is undefined.

These questions do not prescribe fault logic. The exact controller and system documents define the response. Qualified project parties must review protection, interlocks, safe states and acceptance.

Evidence must cover the claimed function. A battery specification cannot prove a remote input, and a controller name cannot prove an option is enabled. Likewise, an ATS drawing alone does not show that the generator receives its command.

Require a bounded supplier return before comparison

Send the supplier your intended start mode, application and exact model request. Name the external controller or ATS if known, and attach the blank matrix. Require a completed row with file revisions, exclusions, open questions and a named action owner.

Use RETURN when a supplier field or file is missing. Use HOLD when records conflict, the two ends of the command path do not match, or the evidence belongs to another build. An undefined promise of “complete standby” also needs a hold.

Use COMPARE when the matrix lets the buyer compare the same functions and scope across offers. This is not approval of compatibility, installation, commissioning or the complete system.

Typical return or hold conditions include:

• electric start presented as automatic backup;
• a wireless fob or application presented as ATS compatibility;
• “two-wire,” “dry contact,” “AMF,” “remote,” or “ATS-ready” with no applicable identity or document;
• a consumer add-on proposed as a project interface without controlled evidence;
• a distance claim without the device, conditions, source, and offered-build link;
• a start demonstration treated as proof of source sensing or load transfer;
• missing battery, charger, control-power, receiver, stop, or cooldown ownership;
• controller/manual revision disconnected from the quotation;
• sending and receiving descriptions that conflict;
• “complete standby” without equipment boundaries and accountable parties.

For a BEAR inquiry, send Miya your start-mode request and completed matrix. Include the target market, application, electrical basis, exact generator configuration and quantity. Add the external controller or ATS identity if known, expected response, transfer responsibility and document language. BEAR must confirm the offered features and return evidence for that scope; this guide grants no model-level compatibility or standby approval.