RS300 I2C Commands Skill

Format RS300 I2C command packets to an 18-byte structure by applying little-endian encoding for multi-byte parameters and verifying the complete sequence against the CSV reference. This enforces correct packet construction and prevents protocol integration errors.

Use dynamic CRC-16-CCITT calculations when I2C command parameters change frequently, and rely on hardcoded CRC lookups for static, fixed-payload commands. The Skill provides guidance on selecting the correct CRC handling method to ensure protocol validation accuracy.

Encode multi-byte parameters in RS300 I2C commands using little-endian byte ordering. The Skill provides specific encoding rules and examples for commands with two or more parameter bytes, ensuring the 18-byte packet structure is maintained correctly.

Yes, the RS300 I2C command framework cross-checks every command against the Mini2_I2C_full_commands.csv reference. This CSV-grounded validation covers 20+ commands to ensure packet formatting accuracy and reduce driver development errors.

Common mistakes when building RS300 I2C command packets include incorrect little-endian multi-byte encoding, misapplied CRC-16-CCITT handling, and violating the 18-byte packet structure. The Skill documents these error patterns and provides correct usage guidelines for prevention.