Pytes BMS Client Software Guide

Pytes BMS Client is a desktop application (executable bms_hmi.exe) for monitoring batteries, viewing parameters and history, backing up configuration, debugging, and updating firmware on Pytes batteries — connecting over RS232 or Bluetooth, with no need for HyperTerminal or third-party tools. This chapter is the full per-page operating guide based on User Manual V1.0 (2026-05-15): from how to connect, through the six function pages, to scripts/CSV and the firmware update procedure. The field diagnostic command set (info, pwr, bat, datalist…) lives in 03-08; this chapter focuses on the software itself.

For: operation and maintenance technicians using the monitoring software, support staff collecting logs and history, technicians updating Pytes battery firmware.

Quick summary

The software has six pages along the left menu, running in sequence from monitoring to upgrading: HOME → BATTERY INFORMATION → HISTORY → CONFIG → DEBUG → UPDATE. Daily use only needs HOME (monitoring) and HISTORY (downloading history when a fault is reported); CONFIG backs up configuration; DEBUG and UPDATE are risky technical tasks.

Three operating-safety points to remember. One, select RS232 or Bluetooth before clicking Connect — None will not connect. Two, set a minimum delay of 2000 ms in scripts so commands transmit/receive completely. Three, never cut power or unplug the cable while upgrading or running a script.

System requirements and launch

Open the software folder, find bms_hmi.exe and click to launch. The window is a fixed 1870 × 1000, with the maximize button disabled. Layout: function menu on the left, content area in the middle, local computer date/time at the bottom (not BMS time).

Connection and communication

On the HOME page, the communication-mode dropdown has three choices: None, RS232, Bluetooth. You must pick RS232 or Bluetooth before clicking Connect; None will not connect and the software prompts you.

• RS232 (serial port): click Connect, then under “Serial Port” select the Port and Baud rate matching the BMS and confirm. The RS232 console cable goes into the battery console port, USB end into the laptop.
• Bluetooth: click Connect, then under “Bluetooth Device” select the device as prompted and complete the connection.

Once connected, the button becomes Disconnect — click to disconnect (both RS232 and Bluetooth). If a “Connection Error” warning appears: check for port occupancy, wrong baud rate, the cable, Bluetooth distance/pairing; close other programs using the serial port and retry.

The six function pages

HOME — monitoring, curves, time sync

Shows system-level data: total voltage, total current, SOC (dial changes color by level: 0–20% red, 20–90% yellow-green, above 90% green), SOH, number of online batteries, system status and fault messages, BMS system time. When connected and on HOME, data refreshes about every 2 seconds.

Curves: select SOC, VOLT, CURR, TEMP to toggle the matching line (SOC by default, multiple allowed, up to 4 lines at once, each axis colored like its line). Scroll the timeline below to view recent trends in ~12-hour windows; hovering the graph shows a tooltip with all four values.

Time sync: right-click the BMS system-time area → choose Auto Sync Time (use the computer’s time) or Manual Sync Time (enter in the dialog). A device must be connected.

Extended info (MORE): click the button on the home page to open the “MORE” window — view system SOH, recommended charge/discharge voltage/current, system temperature, etc.

BATTERY INFORMATION — pack and per-cell parameters

Use the pack selector to switch the battery being viewed (the dropdown lists the IDs of connected batteries). View voltage, current, temperature, SOC, SOH, status, and version of each pack. The cell area supports four display modes for the 16 cells:

• Table: voltage/temperature table of the 16 cells — highest in red, lowest in blue; click “details” to jump to that cell’s curve.
• Single: temperature/voltage trend curve of one selected cell (the cell selector appears only in the Single window).
• Curve: voltage and temperature curves of all cells on one chart.
• Delta: variation of voltage/temperature difference over time — used to assess cell balance.

HISTORY — events and history

Two modes via the EVENT and HISTORY buttons: “Events” shows how many events are stored in the BMS, “History” shows how many history records.

• Range: the Start/End boxes give the record sequence numbers to read. Leaving Start empty = read from the first record; leaving End empty or entering -1 = read to the end. If End is not greater than Start, the software reports invalid parameters and refuses to send the command.
• Buttons: HISTORY/EVENT read and display each type; REFRESH refreshes and stops reading; CONTINUE immediately reads the next batch (default 50 records/batch, 2-second interval); DOWNLOAD saves the current window data to an .xlsx file.
• Table: double-click a row to view a single event’s detail. Left-click the “Events” column header to filter by event type. The downloaded file includes all filtered data with each entry’s detail.

CONFIG — configuration backup

The table shows the current BMS configuration. Use the download button to save the parameter table locally as a backup (path and format per the save dialog).

DEBUG — terminal, scripts, log/CSV, upgrade

Terminal: send text commands and view the raw response — for experienced personnel only. Type a command then Enter or click Send; use the up/down arrow keys to recall previous commands; Ctrl + ”+”/”-” to zoom the display font.

Shortcut buttons and scripts: right-click the area between the send box and the display box to add shortcut buttons (send a stored command in one click) and scripts (run multiple commands sequentially). Scripts are JSON, can be created/edited/deleted and exported/imported as local files; a script can be packaged as a button on the main interface. In the script editor: Add command adds a command, Delay is the wait after sending a command — recommended minimum 2000 ms for complete transmission/reception; loop count = -1 means infinite looping until manually stopped; loop interval is the time between two runs. While a script runs, you cannot switch pages, click other buttons, or type commands — click Stop to halt.

Log and CSV: click Start Log to save printed output to a log file (.txt), Stop Log to stop. Append the csv suffix to a command (e.g. pwr csv) to save output to CSV; subsequent csv commands append to the same file; csv new opens a new CSV file. Difference: csv on a single command saves raw unprocessed data, while csv in a script processes it so each loop fits in one row — convenient for later analysis.

Upgrade within DEBUG: entering a trigger word identical to the Upgrade page switches the software to the same upgrade procedure as UPDATE (same risks). Enter the upgrade command, enter the password to put the battery into the upgrade-waiting state, then click “Update File” to select the file; the display shows file-transfer progress.

UPDATE — firmware and bootloader update

Updates firmware and bootloader (uboot); some models support wake-up before upgrading. Click the upgrade button → password verification dialog → enter the correct password → select the firmware file; the white area continuously prints progress information to follow.

Version-confirmation mechanism after completion: for uboot upgrades no version check is done; for others, after completion the software compares the current version with the upgrade file version — if they differ it indicates an upgrade error, but the BMS side has actually upgraded successfully. On success, a completion message appears.

On upgrade failure: record the full message; do not repeatedly power-cycle; retry or roll back under technical-support guidance.

Relation to field diagnosis

When a customer or dealer reports a fault, the three most important things to collect are the output of info, datalist event 0 and datalist history 0 (run in DEBUG → Terminal after login debug). Alternative if you prefer no commands: go to the HISTORY → DOWNLOAD tab to download the full history (.xlsx). For the diagnostic command set and full command table, see 03-08.