SUNMOD Configuration Tool Documentation

Use a supported browser over HTTPS, connect the module before pressing Connect, and allow the browser to access the selected port. Close terminal programs or other applications that may already have the port open.

The browser or platform does not expose the required Web Serial API, or the page is not in a secure context. On desktop systems, use a current Chrome or Edge browser. On Android, use Chrome 148 or later.

Web Serial is not supported in:

• Safari on macOS;
• Firefox;
• Safari, Chrome, Edge, Firefox, and other browsers on iPhone or iPad; and
• older browser versions that do not provide Web Serial.

For Android USB connections, the phone or tablet must support USB host/OTG operation and the connected USB-to-UART bridge.

iOS and iPadOS browsers do not currently expose the Web Serial interface required to connect directly to this module.

The SUNMOD module exposes UART rather than USB, so the browser lists the connected USB-to-UART bridge. Check module and bridge power, cross-connect TX and RX, share ground, and use a 3.3 V/5 V-compatible logic-level UART interface. Never connect true RS-232 signal levels directly. Also check the USB cable and physical connection; some USB cables provide power but do not carry data.

The EVK uses a Silicon Labs CP2102C USB-to-UART bridge and is normally detected by current Windows and macOS systems without manually installing a separate driver. If no serial device appears, disconnect and reconnect the EVK, try another data-capable USB cable and USB port, install available operating-system updates, restart the browser or computer, and contact Behvolt if it remains unavailable.

No. The USB connection provides the communication interface but does not power the EVK or SUNMOD module. Connect a suitable power source to the BAT+ and BAT−/GND inputs. This input powers the SUNMOD module and its microcontroller so the device can operate and respond to commands.

Yes. Route the module's UART through a compatible USB-to-UART bridge on the host board and ensure the operating system exposes it as a serial device. If the board has no onboard USB-to-UART bridge, connect an external converter based on an FT232-family device, Silicon Labs CP2102C, or an equivalent compatible bridge. Cross TX and RX, share ground, and use only 3.3 V/5 V-compatible UART logic levels—not true RS-232 levels.

Another application may own the port, the selected port may be incorrect, or the device may not be replying with the expected SUNMOD protocol. SUNMOD03PUxx communicates at 9600 baud with 8 data bits, no parity, and 1 stop bit (9600 8-N-1); the app applies these settings automatically. Disconnect, verify the hardware and UART path, and try again.

The module accepts only the command that requests Manual/Config Mode while operating automatically. Enter Manual/Config Mode before reading status, changing settings, or controlling outputs.

Firmware-upgrade capability depends on the selected SUNMOD module. Some models support firmware upgrades through their serial interface, while others do not. When a selected module and its firmware support this function, the Configuration Tool can provide the applicable upgrade controls. For unsupported modules, the firmware-upgrade card is not displayed.

SUNMOD03PU does not support firmware upgrades over UART. For information about other available firmware-update methods, contact Behvolt.

Yes, provided the device is in Manual/Config Mode and the requested output command is otherwise permitted. The application places serial transactions in a queue and sends only one command at a time. If Auto Polling is reading a value when you select an output control, your command may wait briefly for the active transaction to finish and is then sent in sequence. This prevents commands generated by the web application from colliding on the serial interface.

Keep other serial-terminal or test software disconnected from the same port, because the application cannot coordinate traffic sent independently by another program. An acknowledged command also does not override device faults, protective inputs, or configured voltage limits that may prevent the physical output from turning on.

An accepted command confirms that the module acknowledged the command; it does not confirm the physical electrical state of the output. Make sure the module is in Manual/Config Mode, then use Read All or Auto Polling in the System Status card to inspect Device Faults Status and Digital Inputs Status.

• Check for an active LOAD or CHARGE hardware or software fault.
• For LOAD, check S3 (ForceLoadOff). An active S3 input prevents LOAD from turning on.
• For CHARGE, check SEN. When the physical SEN pin is LOW, the module sets the SEN fault bit and can force CHARGE off. This may be caused by an external logic-low signal or by a connected NTC temperature sensor: as the sensed temperature rises, the NTC resistance decreases and can pull SEN LOW. When you poll Device Faults Status in the System Status card, SEN may consequently display Fault (High). This indicates that the physical SEN input is LOW and CHARGE is inhibited from turning on.
• Check other protective input states and configured voltage limits relevant to the requested output.
• When using a SUNMODP0xEVK, verify the EVK jumper positions and connections.
• On customer hardware, measure or otherwise verify the physical logic levels at the relevant module input pins and check the surrounding wiring.

If the blocking status is unclear or returns after being cleared, refer to the product documentation or contact Behvolt with a saved status snapshot and communication log.

E is an explicit error reply generated by the module when it cannot complete a command or provide the requested result. One example is an internal ADC or voltage-reference failure that prevents the module from obtaining a valid battery or panel voltage measurement. In that case, commands such as RBV or RPV may return E instead of a voltage value. Other commands or internal error conditions may also produce this reply.

Retry the command and confirm that the module is correctly powered and connected. If the error persists, save the Communication Log, note which command returns E, and contact Behvolt for further investigation.

Green means the value was verified by reading it from the connected module. A typed or file-loaded value is intentionally unverified until it is written and read back or read directly from the device.

No. Both actions only stage values in the application fields. Load Settings reads a compatible file selected from your machine. Load Default Settings uses Behvolt-provided values corresponding to the applicable product datasheet. Before writing, you are responsible for confirming that every value is intended, safe, and applicable to your connected hardware and application. Then use Set individually or Set All for the chosen Battery, Panel, or Load group.

A protocol error can mean that serial data arrived when the application was not waiting for a command reply, that malformed or unexpected data arrived while a reply was expected, or that the module returned its explicit E error reply for a command. An unsupported but complete device-version reply found during connection is handled as a compatibility warning instead: its exact text remains visible beside a yellow tooltip icon, a dedicated toast and SYS entry are added, and device-operation controls are disabled. The port remains connected and Disconnect remains available so the user can disconnect it explicitly. Verify the selected port, wiring, and connected product.

Raw received bytes remain visible in RX rows. Repeated outside-response or malformed-data warnings are intentionally suppressed or summarized so heavy traffic does not create thousands of identical SYS messages and notifications. The User Guide's SYS-message table explains the individual messages.

A normal exchange generally shows a TX command followed promptly by one RX reply. After the port opens, the app requests Manual/Config Mode, identifies the firmware, and reads device values. The exact timestamps, firmware, voltages, pin states, fault states, and subsequent setting commands will vary. A healthy example can look like this:

[14:31:58.102] SYS | Port opened at 9600 8-N-1

[14:31:58.250] TX | .SM. | HEX 11 53 4D 0D
[14:31:58.276] RX | .OK. | HEX 11 4F 4B 0D

[14:31:58.281] TX | .RFV. | HEX 11 52 46 56 0D
[14:31:58.306] RX | .01F1.6. | HEX 11 30 31 46 31 2E 36 0D

[14:31:58.311] TX | .RBV. | HEX 11 52 42 56 0D
[14:31:58.336] RX | .12594. | HEX 11 31 32 35 39 34 0D

[14:31:58.341] TX | .RPV. | HEX 11 52 50 56 0D
[14:31:58.366] RX | .18420. | HEX 11 31 38 34 32 30 0D

[14:31:58.371] TX | .RSP. | HEX 11 52 53 50 0D
[14:31:58.396] RX | .7. | HEX 11 37 0D

[14:31:58.401] TX | .RFL. | HEX 11 52 46 4C 0D
[14:31:58.426] RX | .0. | HEX 11 30 0D

The dots in the text column represent the non-printable start and end framing bytes; the HEX column shows their actual values. A healthy log does not have to match these example values, but repeated timeouts, NOK replies, protocol-error SYS messages, missing replies, or unrelated bytes indicate that further checking may be required.

The browser reported that incoming data exceeded its receive capacity and some bytes may have been lost. Stop the unexpected transmission, allow automatic receiver recovery to complete, and repeat any affected operation.

Your browser could not show a file-location picker, so the app used its normal download method instead. Check the browser's Downloads list or configured download folder. Some browsers, managed devices, or protected system folders may restrict where web applications can save files. Cancelling a save dialog yourself cancels the save.

The application's original interface and documentation are written in English. You may use Google Translate or another translation feature provided by your browser to view explanatory content in many other languages. Product identifiers, UART commands, signal and fault names, pin names, measurement units, and logic states such as HIGH and LOW are intentionally protected from translation so they continue to match the module and its technical documentation. Browser-generated translations are not produced or controlled by Behvolt and may contain inaccuracies; refer to the original English text if meaning is unclear.

Behvolt does not currently provide an officially released native SUNMOD configuration application for Windows, macOS, or Linux. The browser-based SUNMOD Configuration Tool is the currently available end-user application. If your application requires native desktop software, contact Behvolt so we can review your requirements and interest.

Behvolt also provides libraries and supporting resources for system integrators and embedded-system developers who need to incorporate SUNMOD communication or configuration into their own software and test systems. Visit the SUNMOD03PU product page for currently available product resources.

Potentially, yes. Customers may need to host the application—or selected configuration and test functions—on private infrastructure or integrate them into production-line, factory-test, or quality-control systems for host boards containing SUNMOD modules.

Behvolt can review such requests and may provide technical assistance, customization, integration support, or an appropriate deployment arrangement under mutually agreed technical and commercial conditions. Availability and scope are evaluated case by case. Contact Behvolt and describe the SUNMOD product, host board, production process, required tests, expected volume, and automation goals so we can evaluate a suitable solution.

No. Device communication and exports are processed locally in your browser. Files are shared with Behvolt only if you deliberately provide them, such as during a support request.

Describe the product and firmware version, browser and operating system, steps that reproduce the issue, and any relevant status snapshot or communication log you choose to share.