Posts by The Coolest

ErsFreezy

Yes, VFD support is only built into Leia builds.

It's possible to make it work on LE8 builds, but it requires a bit of work and I don't provide support for it.

Look at this post.

This is LibreELEC forums, not CoreELEC forums.

The DTBs from CE may not be compatible with LE.

No, it is not.

Ah, well, obviously you can't get HDR with a S905.

HDR should work if you play a HDR video.

Quote from jxt

Pls, share a script

I modified the Confluence skin, not the default Estuary skin. To apply a change, a resolution or refresh rate change is required.

It's not an issue if you have refresh rate matching turned on.

In file 'IncludesHomeMenuItems.xml'

<include name="HomeSubMenuMovies">
.
.
.
        <control type="button" id="90168">
            <include>ButtonHomeSubCommonValues</include>
            <label>8-Bit output</label>
            <onclick>RunScript("/storage/downloads/rec709.py")</onclick>
        </control>
        <control type="button" id="90169">
            <include>ButtonHomeSubCommonValues</include>
            <label>10-Bit output</label>
            <onclick>RunScript("/storage/downloads/bt2020.py")</onclick>
        </control>

rec709.py:

import subprocess
log = open("/storage/downloads/rec709-err.log", "w")
subprocess.call(["echo '444,8bit' > /sys/class/amhdmitx/amhdmitx0/attr"], shell=True, stderr=log)
log.close()

bt2020.py:

import subprocess
log = open("/storage/downloads/bt2020-err.log", "w")
subprocess.call(["echo '444,10bit' > /sys/class/amhdmitx/amhdmitx0/attr"], shell=True, stderr=log)
log.close()

I don't support other builds, and I don't know which version of the driver AlexELEC uses. vfd.conf support requires a relatively new driver version, currently only available on latest builds of LibreELEC and CoreELEC.

Your best bet is to probably ask Alex to add support for this into their own device trees.

Great!

Advanced configuration is only really needed to figure out the correct configuration for the display if it isn't working right.

Since the Vorke Z6 has a known configuration already, you don't need the advanced settings at all.

Quote from MunkeyBalls

In case you missed it, I managed to retrieve the original android dtb by booting from android and running terminal emulator and have my last post with the correct file.

The box and DTB look identical to the Vorke Z6. Get the vorke-z6-vfd.conf file from here, place it in /storage/.config and rename the file to 'vfd.conf', then reboot the box.

paulopais CoreELEC

paulopais Maybe, see this post. But I'm not providing any active support for it.

Quote from paulopais

I use these files .. i tried install manually and "install addon by zip file".. some idea?

I forgot to mention that you need to be running CoreELEC or Adam's later LE builds.

If you already are then you're not using the correct DTB.

Quote from paulopais

Sorry, someone can help me? my display tanix tx3 it´s always "boot" i already copy the vfd file and install addon, nothing works

You have to make sure that you're using the correct DTB.

Use the DTB from the "device_trees" on the root of the SD card.

johnzhang Update the DTB to one from the device_trees folder on the SD.

estimadarocha

Get a RF remote instead.

PDXUser Not in the current version. But there won't be any AM/PM indicator on the display (not that it's really necessary, just saying).

I'll look into adding that capability in the next (or after the next) release.

Just thought I'd bring this thread out of the depth with a little update.

In the next release of CE, a new and practically rewritten from scratch vfd driver will be included.

This time there's support for more controllers and communication protocols.

It will add support for HD47780 LCD driver, so users who have boards such as KVIM2 or LePotato will be able to hook up a LCD to their device and get it to display a clock, and more information in the future.

This is a gallery of my modded box powering a 20x4 character display

https://imgur.com/a/yzo9j

Jenica13 Nope, the DTB was fine, I confirmed with the one from the firmware.

I have seen several boxes now that use the same method to drive the display.

The driver is baked into the kernel, and the pin configurations are hard-coded, so there's no way to get that information without some extensive reverse engineering.