Magnetically Encoded SMSMB Servo - Memory Table¶
For SMSMB series servos, which use the standard MODBUS-RTU protocol. MODBUS holding registers are 16-bit and two-byte fields are transmitted with the high byte first; "Address (PLC)" is the corresponding MODBUS holding-register address (4xxxx).
1 Servo Communication Protocol¶
Servos use the standard MODBUS-RTU protocol. Factory serial defaults: baud rate 115200, 8 data bits, no parity, 1 stop bit; configurable baud rate range 4800~256Kbps, default communication address (station number) 1.
For the frame layout and function codes, see MODBUS-RTU Protocol.
2 Servo Memory Table Definition¶
2.1 Version Information¶
| Address (DEC) | Address (HEX) | Address (PLC) | Function | Bytes | Initial value | Access | Range | Unit | Description |
|---|---|---|---|---|---|---|---|---|---|
| 0 | 0x0 | 40001 | Firmware version | 2 | – | R | – | – | |
| 1 | 0x1 | 40002 | Servo version | 2 | – | R | – | – | |
| 2 | 0x2 | 40003 | Firmware release date (year) | 2 | – | R | – | – | |
| 3 | 0x3 | 40004 | Firmware release date (month) | 2 | – | R | – | – |
2.2 EEPROM Configuration¶
2.3 SRAM Control¶
2.4 SRAM Feedback¶
2.5 Factory Parameters¶
3 Special Byte Explanation¶
3.1 Servo Phase¶
Bit (weight): Description
- BIT0 (1): Drive direction phase; (0) forward, (1) reverse
- BIT1 (2): Driver bridge mode; (0) brushless, (1) brushed, takes effect after reboot
- BIT2 (4): Torque auto switch; (0) auto-on, (1) command-on, firmware >= 20.9
- BIT3 (8): Automatic status reset; (0) auto reset, (1) command reset, firmware >= 20.9
- BIT4 (16): Angle feedback mode; (0) single-turn angle feedback, (1) full-angle feedback
- BIT5 (32): ----
- BIT6 (64): PWM frequency, (0) 24kHz, (1) 16kHz
- BIT7 (128): Position feedback direction phase, (0) forward, (1) reverse
Note
If multiple bits are set at the same time, the phase value is the sum of the bit values. Example: with an original phase value of 0, if the servo runs in reverse, the phase value is 128+1=129;
3.2 Servo Status¶
Servo status: 0 means normal, 1 means abnormal
Bit (weight): Description
- BIT0 (1): Voltage status
- BIT1 (2): Magnetic encoder status
- BIT2 (4): Temperature status
- BIT3 (8): Current status
- BIT4 (16): Torque status: 0 means torque off, 1 means torque on
- BIT5 (32): Load status
Note
If multiple statuses occur at the same time, the status value is the sum of the bit values. Example: over-voltage/under-voltage together with servo overheating gives a status value of 4+1=5;
3.3 Protection Switch¶
Unload condition: 0 means off, 1 means on
Bit (weight): Description
- BIT0 (1): Voltage protection
- BIT1 (2): Magnetic encoder protection
- BIT2 (4): Overheat protection
- BIT3 (8): Overcurrent protection
- BIT4 (16): ----
- BIT5 (32): Load overload
Note
If multiple bits are set at the same time, the unload condition value is the sum of the bit values. Example: with voltage protection and overheat protection enabled together, the unload condition value is 4+1=5;
3.4 LED Alarm Condition¶
LED alarm condition: 0 means off, 1 means on
Bit (weight): Description
- BIT0 (1): Voltage alarm
- BIT1 (2): Magnetic encoder alarm
- BIT2 (4): Overheat alarm
- BIT3 (8): Overcurrent alarm
- BIT4 (16): ----
- BIT5 (32): Load overload alarm
Note
If multiple bits are set at the same time, the LED alarm condition value is the sum of the bit values. Example: with the voltage alarm and the overheat alarm enabled together, the alarm condition value is 4+1=5;
3.5 Fault Reset¶
Fault reset: 0 means invalid, 1 means reset
Bit (weight): Description
- BIT0 (1): Reset overload fault; with auto-reset enabled, reversing the goal and closing the torque switch can reset the fault
- BIT1 (2): Reset overcurrent fault; with auto-reset enabled, reversing the goal and closing the torque switch can reset the fault
- BIT2 (4): Centre setting, the current position is set to the 2048 centre
- BIT3 (8): ----
- BIT4 (16): ----
- BIT5 (32): Reset over-voltage/under-voltage; once the voltage returns to normal, write 32 to reset the over-voltage/under-voltage status; with auto-reset enabled, the fault resets automatically once the voltage returns to normal
- BIT6 (64): Reset overheat status; once the temperature returns to normal, write 64 to reset the overheat status; with auto-reset enabled, the fault resets automatically once the temperature returns to normal
- BIT7 (128): Reset magnetic encoder status; once the magnetic encoder is connected normally, write 128 to reset the magnetic encoder status; with auto-reset enabled, the fault resets automatically once the magnetic encoder is connected normally
Note
If multiple bits are set at the same time, the values of reset-overload-fault and reset-overcurrent-fault are summed. Example: resetting the overload fault together with the overcurrent fault gives a reset value of 1+2=3;
Do not reuse addresses across families
Other series may use the same address with a different meaning: address 16 is maximum torque in HLS but operating mode in this series; address 20 is LED alarm condition in HLS but velocity loop P coefficient in this series. Return to Bus Protocol and select the matching memory table.
4 Common Workflows¶
- Scope: once the connection is up, day-to-day work on the servo comes down to reading and writing a handful of registers, and this section collects the common ones by task; how to build the instruction frames is out of scope here — see MODBUS-RTU Protocol.
- Numbering and function codes: all numbers below refer to the "Address (DEC)" column of this table, while PLC programming software uses the "Address (PLC)" column; read with function code 03 and write a single register with 06; two-byte fields are high byte first, and the CRC16 is low byte first.
- Online check: this protocol has no PING instruction, so check whether a slave is online with "read register 0 (firmware version) and expect an answer".
4.0 Before You Start¶
- EEPROM area (2.2, 10~21): write 133 Lock flag = 0 before changing anything, and write 1 back afterwards, otherwise the value is not saved. Measured: with the lock flag at 1 a write is still accepted and takes effect immediately, but it does not survive power-off; enabling (129 Torque switch) does not affect saving.
- SRAM area (2.3, 128~134): write directly, effective immediately, lost at power-off — good for trial writes; 133 Lock flag itself lives here, so writing it needs no unlock.
- 0~3 in 2.1 and 256~263 in 2.4 are read-only; reading them does not change the servo state.
- The 2.5 factory-parameter area (384~406) has "Default" access: measured — it can be changed by first writing 128 to 133 Lock flag to release the factory-parameter write lock, then writing 1 back when done; the value persists across power-off, see 4.6 for the steps.
- Position registers in this series count in "minimum resolution angle": by default (403 Angle resolution = 1) a full turn is 4096 counts and each count is 0.0879° (360° ÷ 4096) — that is the "count" used below; with 403 set to K one count becomes K × 0.0879°. Positions are signed: write a negative goal in two's complement and the sign decides the direction — this table has no direction bit.
4.1 Getting the Servo Moving¶
Goal: turn the output shaft through a small angle for the first time.
| Step | Action | Register | Value / example |
|---|---|---|---|
| 1 | Read the present position, call it P | 257 Present position | read-only, e.g. 2048 |
| 2 | Drop the torque limit to 30% | 132 Torque limit | 300 (0.1%; the power-on default comes from 404 = 1000) |
| 3 | Set the running speed | 131 Running speed | 100 (100 × 0.732 RPM ≈ 73 RPM) |
| 4 | Turn the torque output on | 129 Torque switch | 1 |
| 5 | Write the goal position | 128 Goal position | P + 200 (about 17.6°) |
Turning by angle
128 Goal position takes an absolute position, so "turn 90°" first needs a reference point. One count is 0.0879°, and 90° is exactly 1024 counts.
| Desired result | How to work it out | Worked example |
|---|---|---|
| Turn another 90° from the present position (recommended) | read 257 Present position as P, goal = P ± (90° ÷ 0.0879°) | P ± 1024 |
| Turn 90° from the start of the travel | goal = 90° ÷ 0.0879° | 1024 (when 13 = 0) |
- Try P + 1024 first; if it turns the wrong way, use P − 1024. Which side adds depends on how the horn is mounted.
- If the result is negative, just write the negative number (e.g. −1024): this table has no direction bit and the sign of the goal sets the direction.
- The goal must stay within 13 Minimum angle limit / 14 Maximum angle limit (see 4.3).
Notes:
- 132 Torque limit is in SRAM: effective immediately, lost at power-off, and re-loaded from 404 Torque limit default value at power-on, so 132 is the easy one to change for a trial; to make it stick, change 404 instead (2.5 factory parameter, so write 128 to 133 Lock flag first to unlock).
- 131 Running speed and 130 Acceleration are also in SRAM and are loaded at power-on from 406 Speed default value / 405 Acceleration default value; writing 0 to 130 means the servo accelerates at its maximum acceleration.
- Changing the 132 torque limit also affects the rotation speed: the lower the limit, the lower the maximum no-load speed, proportionally.
Check: while moving, 262 Moving flag is 1 and returns to 0 on arrival; 257 Present position should then equal the goal (the boundary value if clamped by the travel range).
4.2 Midpoint Calibration¶
Goal: make goal position 2048 correspond to the pose in which the horn is mounted square. The magnetic encoder zero is fixed to the factory shaft angle, and mounting a horn usually introduces an offset — this step puts the zero back where it belongs.
Register: 134 Fault reset (write 4, i.e. BIT2 centre setting).
Steps:
- First turn the output shaft by hand to the pose in which the horn should sit square (you can take the horn off, calibrate, then refit it).
- Write 134 Fault reset = 4: the servo then treats the present position as 2048 (half a turn) and the computed offset is stored automatically in 15 Position calibration (EEPROM, so it persists; measured: no unlock of 133 is needed) — no manual edit required.
Notes:
- The shaft should be unloaded and still during calibration; every execution turns "wherever it is now" into 2048, so repeating it accumulates offset.
- After calibration the whole 0~4095 zero point shifts: position readings taken before are invalid. If the travel limits are still the factory 0 / 4095 (full turn), they still cover a full turn after the shift and need no change; if you set a custom range, the values in 13 Minimum angle limit / 14 Maximum angle limit now refer to the shifted physical angle and must be set again against the new zero (see 4.3).
- After a power cycle, read 257 Present position again to confirm the calibration held.
Check: after writing, 257 Present position should read 2048; then write 128 Goal position = 2048 and the shaft should not move at all.
4.3 Setting the Travel Range¶
Goal: limit how far the output shaft may turn.
Registers: 13 Minimum angle limit and 14 Maximum angle limit, in minimum resolution angle (0.0879°); both are in the EEPROM area (2.2), so unlock 133 Lock flag before writing.
Steps:
- Convert the boundaries you want into counts (angle ÷ 0.0879°, see "Turning by angle" in 4.1).
- Write 13 and 14; 13 must be smaller than 14; write 133 Lock flag = 0 first and set it back to 1 afterwards.
Notes:
- Factory defaults are 13 = 0 and 14 = 4095, i.e. a full turn.
- Setting both 13 and 14 to 0 enters multi-turn absolute position control (both rows note "0 in multi-turn absolute position control"), which is no longer bound to a single turn, and the ±32767 of 128 Goal position covers about ±8 turns; treat this mechanism as measured-only. To return to normal mode, write both limits again (unlock 133 Lock flag first). The number of turns also depends on 403 Angle resolution in 2.5 (see its row).
- The limits only constrain goal position commands; an external force can still push the shaft past them.
Check: first set 14 Maximum angle limit to 2048 (EEPROM, so unlock first), then write 128 Goal position = 3000; the shaft should stop at 2048 counts and go no further.
4.4 Changing the ID¶
Goal: change the slave address of the servo; do this before building a multi-servo bus.
Registers: 10 ID, 133 Lock flag.
Pitfalls:
- Only write it when this is the only servo on the bus; with several servos, power them one at a time.
- Writing through the broadcast address (0) changes every slave on the bus at once, and slaves do not answer a broadcast frame — do not wait for a reply.
- ID range 1~247; never duplicate an ID on the same bus.
- After a successful write the servo answers on the new ID at once and no longer answers on the old one; the re-lock and any status read afterwards must use the new ID in the slave-address byte — sending with the old ID only times out.
Steps: confirm this is the only servo on the bus → write 133 = 0 → write 10 = new ID → using the new ID write 133 = 1.
Check: reading 10 ID (or register 0, the firmware version) with the new ID should answer, and the old ID should not.
4.5 Changing the Baud Rate¶
Goal: change the communication baud rate to match the host. Factory default is 115200 (gear 2).
Registers: 11 Baud rate, 133 Lock flag; for several servos you can set 12 Return delay as well.
Pitfalls:
- What you write is the gear number 0~9, not the baud rate itself (2=115200, 1=128000, 0=256000 … full mapping in row 11 of the 2.2 table).
- The current connection drops the moment the write succeeds: the servo switches to the new gear at once and stops answering on the old rate, so reconnect at the new rate (change the rate and reopen the port in your serial tool, or reinitialise the UART on the host) before sending anything else — the re-lock included; with a wrong gear you can only retry gear by gear.
- The host and every slave on the bus must use the same gear; a mixed bus does not communicate.
- 12 Return delay (0~500 μs, factory 500) is not a second ID: with several servos on one bus it staggers their reply slots per slave; it is in the EEPROM as well, so the unlock procedure is the same.
Steps: unlock as described in 4.0 Before You Start → write 11 = new gear (the connection drops here) → reconnect at the new rate → write 133 = 1.
Check: reconnect at the new rate and read register 0 (firmware version); an answer is all you need. For lost connections see Troubleshooting.
4.6 Configuring Protection¶
Goal: set temperature, voltage, current and overload protection so a stall does not damage the servo.
Registers:
| Role | Register | Notes |
|---|---|---|
| Temperature threshold | 395 Maximum temperature limit | °C; crossing it sets BIT2 of 256 |
| Voltage threshold | 396 Maximum input voltage / 397 Minimum input voltage | 0.1 V; 397 set to 40 means 4.0 V (set it for your supply voltage) |
| Current threshold | 398 Overload current / 399 Overcurrent protection time | 398 is 6.5 mA per count (0~511), 399 is 1 ms per count (0~5000) |
| Whether to unload the output | 393 Protection switch | bit-wise enable of voltage, magnetic encoder, overheat, overcurrent and load, with bit definitions in 3.3 Protection Switch |
| Whether to flash the LED | 394 LED alarm condition | a separate channel; it flashes only on models with an LED, bit definitions in 3.4 LED Alarm Condition |
| Overload torque drop | 401 Overload torque / 402 Overload protection time / 400 Protection torque | once the load exceeds 401 (800 = 80%) for the time in 402, the output torque drops to the protection torque in 400 (e.g. 200 = 20%) |
All of the above are in the 2.5 factory-parameter area with "Default" access: measured — to write them, first write 128 to 133 Lock flag to release the factory-parameter write lock, then write 1 back when done; the value persists across power-off.
Key points:
- Temperature, voltage and current protection need both conditions to fire: the matching bit of 393 Protection switch set to 1 (that item enabled) plus the measured value crossing the threshold in 395~397 or 398 → that protection acts (unloads the output); with the bit at 0 it never acts.
- Overload is a separate chain: once the load exceeds 401 Overload torque for 402 Overload protection time, the output torque drops to 400 Protection torque; whether the output is also unloaded is decided by BIT5 (load overload) of 393.
- 256 Servo status reflects the detection layer: the bit is set as soon as the threshold is crossed, whether or not 393 is enabled; 394 LED alarm condition is another independent channel — an alarm and an unload never substitute for each other.
- BIT1 (magnetic encoder protection) of 393 has no threshold register: it fires when the sensor itself reports an error and does not depend on the values in 395~398.
- 395~398 are thresholds, not switches: writing 0 to one of them does not disable that protection.
Check: confirm the matching bit of 393 is set to 1, then cross a threshold on purpose (or stall the servo) and read 256: the matching bit turns 1 and the output follows the protection; both return to 0 once the condition clears.
4.7 Reading Status to Troubleshoot¶
Goal: locate a problem with read-only registers when the servo misbehaves.
Registers: 256 Servo status, 257 Present position, 258 Present speed, 259 Output PWM, 260 Present voltage, 261 Present temperature, 262 Moving flag, 263 Present current; all read-only, reading them at will does not affect the servo.
Order to check:
- Read 256 Servo status: if it is not 0, decode it bit by bit with 3.2 Servo Status (1 = voltage, 2 = magnetic encoder, 4 = temperature, 8 = current, 16 = torque status, 32 = load); note that BIT4 (16) set to 1 means the torque is on as normal, not an error.
- Read 260 Present voltage / 261 Present temperature: compare them with the thresholds set in 396 / 397 / 395.
- Read 263 Present current: multiply by 6.5 mA and see how close it is to the threshold in 398 Overload current.
- Read 257 / 258 / 262: compare the present position with the goal position and check the moving flag to see whether the command was executed.
- Once you have located the fault, reset it with 134 Fault reset, but its bit numbers differ from those of 256 (BIT0 overload, BIT1 overcurrent, BIT2 centre, BIT5 over/under-voltage, BIT6 overheat, BIT7 magnetic encoder), see 3.5 Fault Reset.
Source Definition¶
- This series uses standard MODBUS-RTU and has no dedicated SDK class; any Modbus master or debugging tool can read the table on this page
- The official Arduino library (
FTServo_Arduino) does not cover this series; register meanings follow the table on this page