If a lock up occurs the returned parameters from Read and/or Writes will contain a 1. Stretching which can increase the time before an acknowledgement is sent which could be On a side note, be careful with setting too low a value because some devices support clock Setting the value to zero will disable the function. ThisĪllows the user to define a time out in which the I2C will release itself and reinitializeĪnd continue on with the next function. I2C bus lockups have a tendency to freezeĪ program which typically requires a power cycle to restart your progrm.
There is this function: Function: I2c.timeOut(timeOut) - Allows the user to program a time out limit to preventĪnd recover from I2C bus lockups. Has anyone tried the is for sale | HugeDomains ?
I have already ordered it.īut still looking for software solutions. They have developed different ICs for I2C. NXP formerly Philips something invents the i2c bus. I have two options so: Looking fo a software solution. So it seems the arduino is doing arbitration, i think, and waits for his chance to join the bus.īike controller is built in version (I have no access to the pcb without destroying the display)īattery is a 36 V 13 Ah Lion secondary battery with bms (which supports data to the master on the bus who ask after the values) Thats the sniffing data, I got from my buspirate:
But is there a possibility to do that in the code, like a IF TIMEOUT FOR X SECONDS, RESTART BUS ?
So if it hangs, pressing the hardware reset on the arduino helps to reinitialize the bus. But there is the second master, the bike controller, who sends also requests to the battery. Why? The battery is a slave device on the i2c bus and the arduino acts as a master. I'm reading a smart battery voltage (ebike battery) with #include "Wire.h"ĭouble tempDataVoltage = (data_high*256) + data_low Īfter a while it hangs itself up.
0 kommentar(er)
