VU+ Zero 4K Receiver.

[el bandido]

I would not suggest using multiboot until you understand the basics of the enigma2 operating system. Get the box and get it running using a simple image such as OpenPLi or SatDreamGr. Then add other features, or other tuners such as ATSC.

[eastof111]

Good point, just go at your own pace.

[el bandido]

The OpenPLi Wiki has a lot of useful information.

[Only registered and activated users can see links. ]

[zonetech1961]

My Receiver is suppose to be here this week, fingers crossed
I've downloaded about 5 images to play with, do they come with N.A. satellites on the image
or would I need to telnet with FileZilla

[el bandido]

Most enigma2 images have about every satellite in the arc by default, so you should be OK.

[zonetech1961]

It made it today, I put the newest openpli image on it
I didn't see any NA sats, I just messing around with it anyway. I picked a 10 east sat cband
got the blindscan plugin downloaded and tried a few scans.
I didn't see any dvb-s2x , transponders logged , I don't think anyway
I was hoping for one dvb-s2x channel anyway.
blindscan is fairly fast.
I'm going to try some more images when time allows

[el bandido]

Very Good Start!
openpli-6.2-release-vuzero4k-20180827_usb.zip Has satellites from 1.9 East to 177 West. Other unmodified OpenPli images should have these satellites too.
Blindscanning DVB-S2X transponders will cause the receiver to crash because DVB-S2X is not defined. This is easy to fix or keep from happening, but the blindscan plugins have not been updated because no one has had any trouble. There should be a couple of DVB-S2X transponders on 87 West C band. You might try blindscanning that satellite and see what happens. I do not know of any DVB-S2X transponder that has channels, and is visible in North America.

[zonetech1961]

I tried few different images, blind scan crashed on 2 different ones, cant remember now which ones now
Openpli and Openspa did not crash, still didn't see any dvb-s2x tps, unless they are scanning in as dvb or dvbs2
the couple of s2x tps, you mention do they log as dvb-s2x

[el bandido]

To be clear, A crash in enigma2 will result in a green screen with information in it about why the system crashed. This green screen will be displayed for a few seconds, then the receive will reboot. A crash log will be stored in the system files (/tmp) or on the receiver's hard drive.

The receiver will crash if a DVB-S2X is logged in blindscan because (A) DVB-S2X is Not defined, (B) DVB-S2X FEC's are not defined, and possibly (C) roll off values will be different. The only exception to this is the Vu+ images such as BlackHole.
I have modified the blindscan plugin so it will not crash on DVB-S2X transponders, but this modded plugin has to be manually installed. 87 West C band has a couple of DVB-S2X data transponders on it, and these are the only S2X transponders I have found.

[Megatron817]

OpenPli 6.2 release Is very stable.I have never seen a green screen crash with blind scan.I only have KU band fixed dishes.The only green screen crash I have seen was when checking out different modified skins that were not totally compatible and had problems.