Motor in the Traccar catalogue is a vendor protocol name on TCP 5202, not a synonym for immobilizer “motor cut.” MotorProtocol builds a TCP line pipeline (LineBasedFrameDecoder + StringDecoder) and leaves command registration empty — so field truth lives in the vendor SMS/PC sheet, while the open MotorProtocolDecoder only proves the wire path.
How installers get burned
Silkscreens say “Motor” while the SMS card still shows GT06 SERVER, / TIMER, examples. GT06 wants binary 0x78 0x78 on 5023. Motor wants its own line frames on 5202. Guessing from the brand sticker alone creates silent ports.
What “good” looks like
After APN is live, the unit should emit line frames that MotorProtocolDecoder accepts. Keep a short ASCII/hex sample; it is the fastest way to prove Motor versus a mislabeled Concox clone.
Catalogue stance
positions_only. Useful for decoder identification during BYOD review, not a Traxelio full-provisioning claim.