I2C commands for display control

[kolle87]

Hey there!
I'm digging through this forum since hours, but not really found what I need

OK, basically I'm curios if there is a list of I2C commands for the display.

As far as I could find out, it's possible to connect the display by the side pins to the header of the pi (gnd, 5v, sda, scl). Address of display is 0x45.
To control the backlight the command to use is 0x86 followed by a u8 for brightness.

What else is possible by I2C? I would need to switch the display on and off.
Either only the backlight, better the whole display.

Ah, I read that when I start the communication with via the I2C the touch is not working proper anymore since the display assumes to communicate exclusively via that bus... can somebody confirm that?

Thanks allot for your help

PS:
I have seen the use of "/sys/class/backlight/rpi_backlight/brightnes" and some other files. But I'm using Windows IoT with C#.

[DougieLawson]

OK, basically I'm curios if there is a list of I2C commands for the display.

So you're running an official display on a Win10 IoT system. You're probably one of a small handful of folks doing that anywhere in the world.

Have you asked the same question on https://social.msdn.microsoft.com/forum ... WindowsIoT

[kolle87]

That was fast

It's the 7" Touch Display with board version 1.1

Do you have the dimming working or more?
I was wondering if the I2C is needed at all, guess there is a driver in windows OS which might has flags to control.

[DougieLawson]

That was fast

It's the 7" Touch Display with board version 1.1

Do you have the dimming working or more?
I was wondering if the I2C is needed at all, guess there is a driver in windows OS which might has flags to control.

It all works brilliantly for me using Raspbian. I have no desire to run Win10Iot on any of my 2B or 3B raspberries.

[kolle87]

Hmm... I would unlikely give up windows just because of the display

anyhow, thanks for the Win IoT forum link

[alphanumeric]

The I2C wires are only needed if you have the display connected to an A or B. I think the way it works is A+, B+, 2, and 3 all use i2c0 for configuring the display and touchscreen via the CSI port. I2c1 is still available for other uses. A and B need to use the other i2c bus for the display via the additional wires.

I didn't use any of the jumper wires with my display. Power comes in via the Micro USB power port. CSI cable goes to my Pi 3B.

[kolle87]

The I2C wires are only needed if you have the display connected to an A or B. I think the way it works is A+, B+, 2, and 3 all use i2c0 for configuring the display and touchscreen via the CSI port. I2c1 is still available for other uses. A and B need to use the other i2c bus for the display via the additional wires.

I didn't use any of the jumper wires with my display. Power comes in via the Micro USB power port. CSI cable goes to my Pi 3B.

Ok, cool - no additional wires

so every thing is set, just the commands are not documented

[alphanumeric]

The I2C wires are only needed if you have the display connected to an A or B. I think the way it works is A+, B+, 2, and 3 all use i2c0 for configuring the display and touchscreen via the CSI port. I2c1 is still available for other uses. A and B need to use the other i2c bus for the display via the additional wires.

I didn't use any of the jumper wires with my display. Power comes in via the Micro USB power port. CSI cable goes to my Pi 3B.

Ok, cool - no additional wires

so every thing is set, just the commands are not documented

Commands for what? Backlight DIM, and screen blank are handled by the OS, as far as I know? Touch screen function too. In Raspbian they are. I've only briefly used Windows 10 IoT and found it very lacking in what you can do. For me it is anyway, I don't have the skills to do much of anything with it. And its pretty well useless right out of the box. I'm scratching my head as to how they can even call it Windows? It doesn't look like any version of Windows I've ever seen or used. No browser, no Start Menu, no GUI really. No support for the touch screen in 10 IoT? I only ever used it with my TV for a monitor.

Now if Microsoft would port 10 Mobile to run on the Pi I'd be all over it. I don't see that ever happing though. =(

[kolle87]

The I2C wires are only needed if you have the display connected to an A or B. I think the way it works is A+, B+, 2, and 3 all use i2c0 for configuring the display and touchscreen via the CSI port. I2c1 is still available for other uses. A and B need to use the other i2c bus for the display via the additional wires.

I didn't use any of the jumper wires with my display. Power comes in via the Micro USB power port. CSI cable goes to my Pi 3B.

Ok, cool - no additional wires

so every thing is set, just the commands are not documented

Commands for what? Backlight DIM, and screen blank are handled by the OS, as far as I know? Touch screen function too. In Raspbian they are. I've only briefly used Windows 10 IoT and found it very lacking in what you can do. For me it is anyway, I don't have the skills to do much of anything with it. And its pretty well useless right out of the box. I'm scratching my head as to how they can even call it Windows? It doesn't look like any version of Windows I've ever seen or used. No browser, no Start Menu, no GUI really. No support for the touch screen in 10 IoT? I only ever used it with my TV for a monitor.

Now if Microsoft would port 10 Mobile to run on the Pi I'd be all over it. I don't see that ever happing though. =(

Ok, looks like you don't like it - I do

The windows IoT is actually just the "core". You can program different apps remotely from a windows PC where you can debug and emulate your program. These apps are so called UWA what means universal windows app, which makes them run on my pc, mobile, tablet and raspi without any change.
Sorry, just a small explanation

Back to the commands, it is possible to control the display e.g. dimming via the i2c. so since there is a command for this, I was curious if there are more.

[DougieLawson]

Have you asked the same question on https://social.msdn.microsoft.com/forum ... WindowsIoT

[alphanumeric]

I know what it is, I researched it after giving it a look see. I'm a Microsoft MVP. It just doesn't do it for me is all. Not my personal cup of tea. I'm not a programmer.
You won't get a whole lot of help with it here either. I'm not going to go into why, just that they will send you to the official Microsoft Forum.

[kolle87]

Just posted there a few minutes ago.
Thanks for the link