You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
Make sure you are able to repro it on the latest version
Search the existing issues.
Steps to reproduce
When using the PS IOT module to communicate with the TI ADS 1115 TI ADS 1115 Documentation on the i2c bus the commands on the module are not activating the module and the conversation is not starting with the chip. I think it is because the chip is expecting a START command after the REGISTER call to initiate the conversation.
I need to change the first data bit from 133 to 132 to start a continuous conversation.
If I use the -passThru command with set the chip is returning the changed values. However a subsequent query show the same 133, 131. > Set-I2CRegister -device $device -Register 0x01 -data 132, 131 -passthru
returned:
Device Register Data
72 1 {132, 131}
But Get-I2CRegister -Device $device -register 0x01 2
returns:
Device Register Data
Prerequisites
Steps to reproduce
When using the PS IOT module to communicate with the TI ADS 1115 TI ADS 1115 Documentation on the i2c bus the commands on the module are not activating the module and the conversation is not starting with the chip. I think it is because the chip is expecting a START command after the REGISTER call to initiate the conversation.
$device = Get-i2cDevice -Id 0x48
$device Returns ID 72 & BUSID 1
Get-i2CRegister -Device $device
-Register 0x01 2Returns
Device 72, Register 1, Data 133,131.
I need to change the first data bit from 133 to 132 to start a continuous conversation.
If I use the -passThru command with set the chip is returning the changed values. However a subsequent query show the same 133, 131.
> Set-I2CRegister -device $device -Register 0x01 -data 132, 131 -passthru
returned:
Device Register Data
72 1 {132, 131}
But Get-I2CRegister -Device $device -register 0x01 2
returns:
Device Register Data
72 1 {133, 131}
Expected behavior
Actual behavior
Error details
Get-error no error is returned.
Environment data
Version
7.2.5
Visuals
na
The text was updated successfully, but these errors were encountered: