Presently, the device address (0x23/0x5C) have to be known/set with the constructor, ie. before the setup() call. This pretty much means that it must be hard-coded in the program.
If the same software is to be used on (slightly) different hardware configurations, then it might be convenient that the address can be set during the setup() phase - presumably after an i2c-scan or whatever, where the available addresses can be probed.
As it is now, I must create two instances of the object, as per eg:
Dear Wizards/@claws,
Presently, the device address (0x23/0x5C) have to be known/set with the constructor, ie. before the setup() call. This pretty much means that it must be hard-coded in the program.
If the same software is to be used on (slightly) different hardware configurations, then it might be convenient that the address can be set during the setup() phase - presumably after an i2c-scan or whatever, where the available addresses can be probed.
As it is now, I must create two instances of the object, as per eg:
Thanks for a good library. /Bjarne