Tool/software:
The protector NACKs, always, the very first I2C command it receives, after it has been powered for the first time. The NACK behavior is consistent, whether the command is a Write or a Read. If the protector remains powered and the software restarted, the same sequence of I2C commands does not result in a NACK.
The first I2C command I send is a Read of register 0x62, the alarm register. However, the protector also NACKs a read of register 0. The protector also NACKs a write command.
After the first command, all following commands succeed and do not NACK.
I've attached an image of the very first I2C command after the protector has been powered.
