Communication Interface
Reserved real hardware integration layer: Serial / BLE / MQTT link configuration, frame parsing, and real-time streaming. Currently driven by simulated data sources; simply switch the data source upon actual hardware connection.
USB Serial Direct Connection
idleThe list below shows serial devices automatically detected by your browser. Click "Connect" on the corresponding device to connect directly (no need to open the configuration dialog). If no devices appear, click "Scan for New Serial Ports" and select your USB-to-serial adapter from the browser prompt. For privacy reasons, the browser only returns the USB VID/PID, not the system-assigned COM port number. Please refer to the COM port number shown in the browser permission prompt.
No authorized serial devices detected.
No authorized serial ports found: Click "Identify New Serial Port" and select the USB-to-Serial device from the browser prompt. After authorization, the device will automatically appear in the list above.
Security ContextHTTPS / Security
Browser SupportWeb Serial is available
Serial port authorized0
Link StatusNot connected
Data received0 bytes / 0 frames
Recently reportedNone
Try opening0 times
Baud rate115200· 8N1
Recent Connection Logs (Success / Failure / Disconnected)
No connection history yet: Click "Connect" or "Identify New Serial Port and Connect" above. Recent connections and their timestamps will appear pinned here to help troubleshoot device issues.
Link Configuration
linkSimulation Source
Built-in dataset · DST · 2 s
Link not established
Report interval 2 s
AA55 | LEN | CMD | PAYLOAD | CRC16 (Compatible with Modbus RTU 0x04)
Waiting for device report
Link not established
Note: The host PC uses a unified data model where simulated source fields match real hardware field names and semantics. Upon connecting to a real BMS, only the data source needs to be switched; no frontend changes are required.
Communication Protocol Specification
AA55Frame Structure
AA 55 | LEN | CMD | PAYLOAD | CRC16_LO CRC16_HIValidation AlgorithmCRC16/MODBUS (poly 0xA001); crc16("123456789")=0x4B37; Payload big-endian, CRC little-endian
Link ModeBLE FFE0/FFE1/FFE2 · MQTT broker.chenpower.cn:8883 chenpower/bms/{sn}/{data|alarm|cmd}· USB 115200-8N1
Timing ParametersHost polling every 2 s · Response ≤100 ms · Timeout 10 s · Archive every 15 frame
Command Code
| Command Prompt | Command Code |
|---|---|
| 0x31 | 0x31 Real-time Telemetry (V / I / T / SOC / SOH / R₀ / Cycles) |
| 0x32 | 0x32 Capacity / SOH Calibration Report |
| 0x10 | 0x10 Parameter Settings |
| 0x1 | 0x81 Alert Reporting |
| 0x0 | 0x80 ACK |
This host PC shares the same frame format and field definitions with the Mini Program, mobile app, and lower-level device; fields with the same name across all three endpoints have identical meanings.
Real-time Telemetry (Live Link Parsing)
waitingReal device not connected yet: After selecting a USB serial or Bluetooth link and completing authorization, this section will display real-time BMS data including voltage, current, temperature, SOC, SOH, and cell information.
The actual test data uses the same frame parsing engine as the "Battery Analysis" page (AA5 + CRC6 / Modbus RTU), with identical field names and meanings. The parsed results are exported to the graduation project summary via the "Records → Report" workflow on this page.
Frame Parsing (Real-time CRC16 Validation)
Link Status: SIM · idleWaiting for link establishment: Select USB serial, Bluetooth, or analog source to begin receiving raw frames.