I’ll add the file to the remote package.
This is for the vfd, not remote.
1 Like
I know. I have it seen included in some other packages like for the remote of the TaNiX TX3 and TX5, and found it a good idea. I grandfathered it in.
1 Like
Hi there!
I know this question is a long shot, but I believe you can help me.
I have an X96 air p2 and the vfd works fine, but I find it small and too blue.
Do you know if I could replace the Vfd/Lcd or even use a graphical display to indicate more info, even the actually playing content’s name, etc?
So tldr: Can I replace the vfd on the x96 air p2, and if so, which are compatible? Thanks 
i am not afraid of soldering of course!
Technically it’s possible. Practically I can’t recommend anybody to do it.
Depending on the internal structure of the device, you would have to de-solder the display controller and the display itself, and then solder in the connections for your replacement display.
You can replace it with an I2C SSD1306\9 or SH1106 OLED display, a HD44780 alphanumeric display (with I2C backpack). It’s possible to use an SPI display, but only if it requires at most 3 control pins, as that’s all that you have available.
Hi All
I have a A95x Max v.81 box… display works but showing only time or boot… is that all it can show under CoreElec …
Kind regards…
Did you read the first post in this very topic? If not, then I suggest that you do.
Yes i did… and display does work with time and boot… But no wifi or other symbols…
i did copy a file for this from an other tread… and that made it work with time and boot… otherwise it was only boot… ))
Just wonder if more option could be activated…
Regards…
Reread step 4.
Wonderfull It Works …!! Thank you very much…
1 Like
Is there a way you could share your working program?
Hello,
I have this box. https://www.aliexpress.com/item/1005001335327312.html
dmesg:
CoreELEC:~ # dmesg | grep Open
[ 0.389633@1] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 21.261363@3] OpenVFD: Version: V1.3.0
[ 21.261384@3] OpenVFD: vfd_gpio_clk: #0 = 0x00; #1 = 0x41; #2 = 0x00;
[ 21.261390@3] OpenVFD: vfd_gpio_dat: #0 = 0x00; #1 = 0x40; #2 = 0x00;
[ 21.261395@3] OpenVFD: vfd_gpio_stb: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.261401@3] OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.261406@3] OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.261411@3] OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.261416@3] OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.261513@3] OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00;
[ 21.261521@3] OpenVFD: vfd_chars: #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[ 21.261529@3] OpenVFD: vfd_dot_bits: #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x05; #5 = 0x04; #6 = 0x06;
[ 21.261535@3] OpenVFD: vfd_display_type: #0 = 0x03; #1 = 0x00; #2 = 0x00; #3 = 0x03;
[ 21.261541@3] OpenVFD: Detected gpio chips: ao-bank, banks.
[ 21.261547@3] OpenVFD: “banks” chip found. base = 155, pin count = 101, pin = 65, offset = 220
[ 21.261551@3] OpenVFD: “banks” chip found. base = 155, pin count = 101, pin = 64, offset = 219
[ 21.261555@3] OpenVFD: Skipping vfd_gpio_stb evaluation (0xFF)
[ 21.261558@3] OpenVFD: Skipping vfd_gpio0 evaluation (0xFF)
[ 21.261562@3] OpenVFD: Skipping vfd_gpio1 evaluation (0xFF)
[ 21.261565@3] OpenVFD: Skipping vfd_gpio2 evaluation (0xFF)
[ 21.261567@3] OpenVFD: Skipping vfd_gpio3 evaluation (0xFF)
[ 21.266081@3] OpenVFD: Select FD650 controller
[ 21.266167@3] OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups off)
[ 28.852961@3] OpenVFD: Select FD650 controller
can anyone help me to make it work?
Thanks.
device starts with ki plus dtb
Sadly, there’s no info on what type of vfd driver, nor how it’s connected internally.
Maybe the original Android DTB would help, but I wouldn’t count on it too much.
Ok, try this one:
ki-plus-vfd.conf (1.2 KB)
If it doesn’t work, try to swap the 69/70 values around in vfd_gpio_clk/vfd_gpio_dat
I tried 69/70 and swap them to 70/69, but no luck. The display is off.
dmesg:
CoreELEC:~ # dmesg | grep Open
[ 0.390294@1] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 21.269646@2] OpenVFD: Version: V1.3.0
[ 21.269663@2] OpenVFD: vfd_gpio_clk: #0 = 0x00; #1 = 0x46; #2 = 0x00;
[ 21.269668@2] OpenVFD: vfd_gpio_dat: #0 = 0x00; #1 = 0x45; #2 = 0x00;
[ 21.269674@2] OpenVFD: vfd_gpio_stb: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.269679@2] OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.269684@2] OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.269689@2] OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.269694@2] OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
[ 21.269698@2] OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00;
[ 21.269705@2] OpenVFD: vfd_chars: #0 = 0x02; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04;
[ 21.269712@2] OpenVFD: vfd_dot_bits: #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[ 21.269718@2] OpenVFD: vfd_display_type: #0 = 0x04; #1 = 0x00; #2 = 0x00; #3 = 0x03;
[ 21.269724@2] OpenVFD: Detected gpio chips: ao-bank, banks.
[ 21.269730@2] OpenVFD: “banks” chip found. base = 155, pin count = 101, pin = 70, offset = 225
[ 21.269735@2] OpenVFD: “banks” chip found. base = 155, pin count = 101, pin = 69, offset = 224
[ 21.269738@2] OpenVFD: Skipping vfd_gpio_stb evaluation (0xFF)
[ 21.269741@2] OpenVFD: Skipping vfd_gpio0 evaluation (0xFF)
[ 21.269744@2] OpenVFD: Skipping vfd_gpio1 evaluation (0xFF)
[ 21.269748@2] OpenVFD: Skipping vfd_gpio2 evaluation (0xFF)
[ 21.269750@2] OpenVFD: Skipping vfd_gpio3 evaluation (0xFF)
[ 21.272268@2] OpenVFD: Select FD650 controller
[ 21.272347@2] OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups off)
[ 28.508009@2] OpenVFD: Select FD650 controller
The DTB file you attached doesn’t seem to be an actual DTB file but something else.
I can’t decompile it.
I performed the command: dd if=/dev/dtb | gzip > /storage/downloads/dtb.img.gz
from CE
Maybe it is the DTB, but the first part of it is corrupted or missing.
Can you try to run this command from android? I’m not sure that would work, though.
Edit: I went over another VFD part I found in the DTB, and the pin numbers seem to be correct. Another possible issue is that the controller may not be FD650.