Replies: 2 comments
-
Seeing little of your code i will only be able to ask questions. Does your chip have the ldac pin ? You said ending the app effects the output. If u used the ldac and drove it high and did not drive low after sending the i2c data AND was configured to go low when the app exists, you could see this behavior |
Beta Was this translation helpful? Give feedback.
-
Good question about the ldac pin, I have to check the HW/schematics when I'm back in the office. Here the code and pom.xml snippets:
|
Beta Was this translation helpful? Give feedback.
-
Hi all,
I have following raspbian installed on my compute module 3:
with java:
with javafx:
with pigpio:
In my I2cController class I create my device (which should control the light intensity of some LEDs):
And upon user interaction on the screen, I try to write to my device:
GPIOS work, bu nothing on I2C happens.
Only when I close my application the light settings change.
It seems there is some kind of flush missing, or clock issue. any suggestions?
Slave address is 0x10
Light register is 0x30 or 0x31
tests with i2c-tools work:
i2cset -y 1 0x10 0x30 0xA0 0x00 i
its done with maven:
Beta Was this translation helpful? Give feedback.
All reactions