[sparks7162] Problem with vfd in some Amiko Alien2

[itsmearron]

On HDMU13155 issue on vfd displaying time+"boot" on new spark's vfd was still not solved... See 1st post in this thread to find why

OK. ... I don't quite understand it say that it is not supported in and enigma 2 image? But with AopenTV image, the VFD works fine.?

[miciomax]

OK. ... I don't quite understand it say that it is not supported in and enigma 2 image? But with AopenTV image, the VFD works fine.?

My reply was not for your question, but for who replied to you that this is an old post. Yes. It's an old post for an issue not solved. And in 1st post they can find a way to try to solve it.

openATV work with new alien vfd. They spent 1 week to let it work.

[zdzislaw22]

@Audioniek:
It's super easy.
In GIT you have 2 versions of driver:
aotom - works with both
aotom_spark - works with "old" vfd only.

[miciomax]

Hello everybody,

everyone is talking about a "new" VFD in the Spark receivers, but nobody has revealed so far what is new about it, or how to identify the new VFD. I am willing to test/modify the aotom VFD driver if needed, but need a way to identify the "new" VFD version from the old one. If new pertains to the displaytype DVFD, the code for that has been in aotom for quite some time now. The two Spark 7162 receivers I have access to both have the VFD displaytype and work absolutely OK.

Regards,

Audioniek.

I don't know if this pic can help. Up new vfd, down old vfd.
I can say that one friend has compiled module aotom.ko with oSaiYa's commit in kernel 215 and sustituting it in HDMU13155 /lib/modules works fine in eachone vfd.

Thanks.

[Audioniek]

Thank you, miciomax!

This is exactly what I was looking for. The "new" VFD has dot matrix characters instead of 14 segment digits, so it is the DVFD displaytype. Will need another Spark 7162 receiver for testing now...

Regards,

Audioniek.