Intelligent resource base

Help Center starter guide

FAQ

Product dynamics

Scene topic

Core controller topic

Intelligent resource base

Mobile robot model

Robokit features documentation

RDSCore function document

RDS (Fleet Management System)

Roboshop Pro User Manual

Robokit API Protocol

Robot coordinate system specification

PGV QR code description

The configuration of the SRC2000 model file differs from that of the SRC800/SRC3000 model file

Zebra printer prints QR code instructions

Qr code paste requirements for navigation and secondary positioning

Specification for one dimension code of the tank

Material box DM code instructions

Ubuntu 18.04 LTS Operation Instructions

【Moxa】1131a Industrial AP

【Moxa】1137c Network client configuration

【Moxa】1137c User Manual

[Node pass] 2458-3x3-AC Industrial AP

Laser installation methods and precautions

2D laser behavior table

SICK NanoScan3 Laser sensor

Robosense Helios 16P Multiline Lidar

Pepplus Fuku R2000 laser sensor

Radium 1BS series laser sensor

Robosense 16-wire laser sensor

Robosense 32-wire laser sensor

Smart Man laser sensor

SICK LMS series laser sensors

Beiyang UAM laser sensor

Obstacle avoidance laser

Cori LS measuring laser

Blue Ocean LDS-50C-C30E

Radium 1BS2H point cloud laser

TiM310 Usage instructions

Driver behavior table

Step driver configuration of FM860

Large and medium driver

ISMC driver (Pure Hall no encoder)

SEW Driver (under test)

HLS LS driver (private version, canopen version)

Mingzhi M2DC driver (Supplier has been discontinued)

Ming Chi MDX Drive (Supplier discontinued)

Motec Driver (older PC)

Motec Driver (new upper computer)

ZLTECH-ZLAC8030L driver

Qingneng Techon drive

ZAPI driver -ACECOMBIX

Curtis Drive 1232E parameter adjustment guide

Curtis Drive F2A parameter adjustment guide

Hikang code reading camera

Pepplus Plus code reader camera

Dahua code reader camera

Grazing star code reader camera

SICK code reader camera

2D camera internal parameter calibration

Range sensor literacy

SSH-10-sensor Indicates the distance sensor

Benewake-sensor Distance sensor

Composite robot terminal device

Dahuan PGC series gripper

Kun Wei power control

SICK- Series cable encoder

kuebler cable encoder

Checklist- Battery protocol adaption

SRC-2000(S) controller battery adaptation Description

Wireless charging - Hertz

Lithium flat charging pile

Function configuration of the original handle of forklift truck

Light belt write code operation instructions

Standard IO extension

I/O sensor configuration Description

Checklist- Battery protocol adaption

First, Content Adaptation

Degree of Importance	Content	Description
Must Have	Voltage	Total Battery Voltage
	Charging Current	There are two forms of current in the protocol: Current is a signed type of data, charge is positive, discharge is negative Charge current and discharge current occupy one field each
	Discharge Current
	Residual Power	There are two forms of electricity quantity in the agreement: The battery information directly contains the remaining power information The remaining power needs to be calculated by the remaining capacity and the total capacity
	Temperature	There are two types of temperature: Cell Temperature BMS Temperature
But No	Number of Cycles
But No	Error Code

Two, Communication Interface

2.1 Controller Area Network (CAN)

2.1.1. Explanation

A CAN packet comprises of a frame ID and eight data bits. The battery information is stored within the data bits. The data bits of a CAN frame can store one or more pieces of battery information.

The packet with frame ID 0x209 contains the battery's temperature information.
The packet with frame ID 0x20A contains information about the battery's voltage, charging and discharging current, and remaining power.
The packet with frame ID 0x20B contains the number of battery cycles.

2.1.2. Requirements for CAN Battery Adaptation

The protocol includes adaptive content.
Each frame consists of 8 data bits.
A maximum of five packets contain the necessary battery information.
If the protocol is actively reported, the packet reporting period is longer than 100ms and less than 1 second.
The baud rate does not exceed 1 MB.

2.2 Serial Port

2.2.1. Interface Description

RS485-- Highly recommended
RS232-- Not recommended

2.2.2. Serial Port Battery Adaptation Requirements

The protocol includes adaptive content.
If the protocol is actively reported, the packet reporting period is between 100ms and 1 second.
Baud rate options are 9600 or 115200 (data bit: 8, stop bit: 1, no parity bit).

III. Frequently Asked Questions

Is it possible to adapt all Modbus RTU protocols?

If the provided Modbus RTU meets the adaptation requirements mentioned above, it can be adapted. However, due to the varying Modbus RTU data fields of each battery, the protocol is not universal across different batteries.