I2C data-address

[dotnet]

I2C data-address

[deinok]

@joperezr Yes, thanks. In my case I will add an extension method for my specific device.

[joperezr]

If by this you mean the I2c Address, then this is set in the I2cConnectionSettings.DeviceAddress. The way it works is that you would generate a I2cConnectionSettings object, and then pass that in to the constructor of the UnixI2cDevice, for example:

var settings = new I2cConnectionSettings(busId: 0, deviceAddress: 0x77);
var myI2cDevyce = new UnixI2cDevice(settings);

[deinok]

@joperezr In my case I use for now the following i2cset -y 1 0x69 0x00 0xFF && i2cset -y 1 0x69 0x01 0x00 && i2cset -y 1 0x69 0x02 0x00 for set a led to red.
As you can see, 1 is busId, 0x69 is for deviceAddress, 0x00, 0x01, 0x02 is for registers or data-address and at the end we have the RGB value.

I'm not sure, but I think that writting a byte array with the register and value works well. Could we add a method to simplificate this?

[joperezr]

reading a register from a device is not strictly standard. For example, there are some devices that in order to read register 0x00, the way you do it is that you first write 0x00 to the i2c bus chain, then you wait for one cycle, and then you read from that bus chain. There are other devices that behave different, where in order to read register 0x00, you have to first write the register you want to read with the 8-th bit flipped to 1 to the i2c bus chain and then read from it, so you would write 0x80 in order to read register 0x00. What I mean is that it wouldn't be possible to have a standard function like:

byte readRegister(byte registerAddress);
void writeRegister(byte registerAddress, byte data);

because the way to read and write registers is not standard for all devices. Today, UnixI2cDevice provides a way to Read and Write from the i2cBus chain, but each device needs to implement how reading a register is performed in that particular device (based on the device's datasheet).

Does that make sense?

[joperezr]

cool. I plan on adding some Spi and I2c device bindings as an example of the API consumption soon 😄

[deinok]

Cool. If you need it, I could give bindings for https://www.access-is.com/products/val100