Forums

I have just installed your new image for the Vu+ Ultimo. I was using OpenPLi on my previous Vu+ Duo and ET9000 for more than a year now, so I was happy to see that you now also have an image for the Ultimo.

However, there's one major disadvantage: I can't seem to find any way to configure the nice front display, which was the main reason why I got myself the Ultimo. In the VTI image there is a selection of several skins for the front display, also there are channel picons on their feed which are displayed on the front display.

Are you planning to implement something similar? Basically, all that I would need in addition to what the display already displays with your image are the channel picons.

TIA!

From what I've seen the patches from VU+ regarding the VFD were not complete and didn't build, so we left them out for now. It is something VU+ has to fix.

Honestly I'm not even sure if this is something they care about at all. Because the original Vu+ image for the Ultimo also does not contain any VFD customization capabilities. So I'm afraid that these capabilities in the VTI image are some homework of the VTI coders. If that would be the case, would that mean that it would never be possible to have any VFD customizations in PLi image?

you can try copy the files skin_vfd* to /usr/share/enigma2

Are there sources available from VTI?

i try, but now flashing. works the remotecontrol from Duo also ?

i try, but now flashing. works the remotecontrol from Duo also ?

Yes, if you set the R/C code of the Ultimo to "1".

thx. i will try.
and Display works well. try this. fonts should be in /usr/share/fonts, rollercahr /xxx/components/renderer

piconlcd i try, but i need the link for the folder

i try, but now flashing. works the remotecontrol from Duo also ?

Yes, if you set the R/C code of the Ultimo to "1".

where? by plugin?

Hi,

try this one, and create Subfolder ..SystemPlugins/RemoteControlCode

thx!!

@kaneguru:

You seem to be on the right track. Using your files, I was able to get an alternative front display setup, but it only showed the same informations than I got with OpenPLi per default (which is channel name, progress bar for current show, current time), just with a different layout (everything's bigger).

What I would liked to have is the display informations that I can see with VTI image and "VTI 1" as display config. On VTI you can choose from 5 different layouts for the display, VTI 1, VTI 2, VTI 3, VU+ 1 and VU+ 2 (and "none"). There is a .xml for each of these layouts in /usr/share/enigma2, the one I would like to have is skin_vfd_vti_I.xml. So what I did was to take this xml from the VTI image, put it on PLi image and rename it to skin_display.xml. In addition, I took the following files/folders from the VTI image because they are obviously needed:

/usr/share/enigma2/piconlcd/*.*
/usr/share/enigma2/vfd_icons/*.*
/usr/share/fonts/analog.ttf

Also there seem to be some additional render modules required, so in addition to RollerChartLCD which you provided, I also took the following renderers from VTI image:

FixedLabel
Label
Picon
Pixmap
Progress
RollerCharLCDLong

Some of them are already there in PLi image but with different filesize.

To my surprise it perfectly works. I now have exactly the same VFD layout as with the VTI image "VTI 1" layout.

OK, there's one little issue I've encountered. When I switch to a channel where the name of the show is too long for the display so that it gets scrolled once, I get a GS. I can get rid of the error by deleting RollerCharLCDLong.pyo to end the boot loop, and then by editing skin_display.xml and change all occurances of "RollerCharLCDLong" to "RollerCharLCD". Unfortunately, when this renderer is used and a show title is being scrolled, this looks somewhat ugly.

The GS refers to a problem with a key called "vfd_scroll_speed". I tested with config.pyo from VTI image but same problem. I remember that in VTI image there is a config option for the VFD scroll speed, so maybe this somehow sets the key that is missing here.

For now I can live with using the RollerCharLCD renderer instead of the ...Long version, but it would be great to fix this somehow. Any suggestions would be highly appretiated.

Here's the relevant part of the crashlog:

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/Renderer/RollerCharLCDLong.py", line 56, in moveTimerTextRun
  File "/usr/lib/enigma2/python/Components/config.py", line 1577, in __getattr__
KeyError: 'vfd_scroll_speed'
(PyObject_CallObject(<bound method RollerCharLCDLong.moveTimerTextRun of <Components.Renderer.RollerCharLCDLong.RollerCharLCDLong object at 0x1618510>>,()) failed)

did you see the LCD Picon also on the display?

Yes, the picons work perfectly fine. But as said above only after using the required files from the VTI image. With your mod it does of course not display any picons.

Hi,

simply ask the Guys to share their code.

I don't really think that is an option.

Besides, it wouldn't help me anyway because I'm not a programmer.

Hi,

but contributing code would help to support the opensource community in here. if is'nt not an option, that's said, when they are not following the opensource spirit.
Edited by daddelfalk, 2 January 2012 - 10:38.

Well... I cannot really comment on that, but I always had the feeling that the VTI team is not really into sharing their stuff, which is unfortunately true for other teams as well nowadays...

Anyway, I was hoping that based on the description I gave someone might be able to help...

Yes, the picons work perfectly fine. But as said above only after using the required files from the VTI image. With your mod it does of course not display any picons.

i cant believe it. on vti this works perfectly with my mod.
i will try it with the files from vti.