You found a real inconsistency in the LRF1500H manual, and your arithmetic is right. The frame is 5 bytes: header 5C, three distance bytes (little-endian, in centimetres), checksum. The out-of-range value is 16777215 cm (0xFFFFFF).
The manual's rule is "from byte 2 to byte 4, invert the sum". For the printed example distance bytes 02 11 03 that gives 0x02 + 0x11 + 0x03 = 0x16, inverted 0xE9, but the example frame prints EC. EC is what the 2-byte checksum of the other H modules gives for 02 11, so the example looks like it was copied from them and not recalculated. Datasheet inconsistent; ERDI confirms the checksum scope in writing, and the safe approach until then is to validate on your own capture.
Decode in a way that tolerates this:
def decode_1500h(f): # f = 5 bytes
if len(f) != 5 or f[0] != 0x5C:
return None
raw = f[1] | (f[2] << 8) | (f[3] << 16)
ok = (~(f[1] + f[2] + f[3]) & 0xFF) == f[4]
if not ok:
return None # log it, count it
return None if raw == 0xFFFFFF else raw / 100.0 # metres
Worked frame by the manual's rule: 12345 cm is 0x003039, bytes 39 30 00, checksum ~(0x39 + 0x30 + 0x00) = ~0x69 = 0x96, so 5C 39 30 00 96. The distance in your example frame is 0x031102 = 200962 cm, which is the manual's own number and is beyond the 1,500 m range, so it is a format sample and not a realistic reading.
Other LRF1500H facts: 0.05-1,500 m at 90 % reflectivity (0.05-300 m at 10 %), 9-36 V DC supply, 1 kHz or 50 Hz chosen automatically by echo strength, 460800 baud default, repeatability +/-5 cm below 10 m. The datasheet does not specify the signal level of TX and RX; it lists only the supply range, so ask us before connecting a 3.3 V host. Please send a raw capture of 20 frames if your unit shows a different checksum than the rule predicts.
Sources:
ERDI Verified Answer — checked against the datasheet by ERDI Engineering.