Hundred1906
Member
I think i2c slave mode data exchange on a 20x2 conflicts with readtemp. Does anyone know is that correct?
My 20x2 program regularly does a readtemp. Asynchronously it may also receive a message from an i2c master and sometimes the i2c message is reported by the master as 'failed'. This failure does not happen if I disable the readtemp instruction.
I see from the Manual 2 (page 267) that interrupts can conflict with 1-wire operations but I have no interrupts specifically enabled. Otherwise I believe the documentation is silent on possible conflicts?
Aside from the documentation and assuming the source of the conflict is as I describe, is there a way around this? The cause of the difficulty is that the i2c master (a Raspberry-Pi) needs to send out a one time urgent message just prior to its own shutdown - when there is little guaranteed time for protracted negotiation.
My 20x2 program regularly does a readtemp. Asynchronously it may also receive a message from an i2c master and sometimes the i2c message is reported by the master as 'failed'. This failure does not happen if I disable the readtemp instruction.
I see from the Manual 2 (page 267) that interrupts can conflict with 1-wire operations but I have no interrupts specifically enabled. Otherwise I believe the documentation is silent on possible conflicts?
Aside from the documentation and assuming the source of the conflict is as I describe, is there a way around this? The cause of the difficulty is that the i2c master (a Raspberry-Pi) needs to send out a one time urgent message just prior to its own shutdown - when there is little guaranteed time for protracted negotiation.