begin does not set values on subsequent calls about ina HOT 7 CLOSED

I am using an ESP8266. It seems to me that the EEPROM will be used. Am I confused?

If it is being used, what prevents another library from using the same address space in the EEPROM?

from ina.

I will look into the first issue, but changing the functionality of the begin() call in the manner you suggest is not possible, as it would break existing code.

To address the second question - there is nothing to prevent another library or the programmer from using the same address space. The library allows the EEPROM to be relocated, but there is no mechanism to prevent any other code from accessing the same locations.

from ina.

I don't see the point of using the EEPROM. I just need to store the maxamps and ohms for my devices and do so whenever the user changes them. The other values that the INA lib uses are all derived at run time and thus don't need to be EEPROMed.

I modified my instance to not use the EEPROM, instead using the array. I also sized the array to my max number of devices.

I suggest that there be a version of begin that takes a pointer to a array of inaEE and max size parameter, and returns the # of devices. And add a setXXX function to set each devices' maxamps and ohms.

These changes will not affect any existing code that depends on the begin(x,y) version. Note that nobody is using the begin(x,y,z) version, because it does not work.

from ina.

Also the code that mods _DeviceCount back to 0 when more devices are found than there is space makes no sense (See: // start again at 0 if overflow). Change that to a simple _DeviceCount++; and it will work fine.

from ina.

would be a good option to release a 2.0 version with optional parameter to use EEPROM or not. I could test it with ESP32. I got a little confused about the EEPROM at the beginning too

from ina.

Sorry for taking so long to address this issue. I will look into making the use of EEPROM for storing the memory structure optional - but I'll open up a separate issue for that

from ina.

Fixed as of v1.0.13

from ina.