Thanks,
However, I'm not sure what I'm supposed to do? Some of those commands are to initialise and format the drive, which I could probably do from the menu. It looks like the box is trying to boot from the HDD, can this be inhibited?n this be inhibited?So it looks like it is trying to boot from the internal HDD, can this be inhibited?
Well this is all rather strange.
The box is working fine but if I force recovery mode from the remote or reflash a recovery, it locks up again until I power down and disconnect the internal drive, then it works fine but its hardly ideal! So the root cause of the problem must be the internal drive - is it trying to boot from there?
I have two more of these boxes, one with an identical Samsung 500Gb internal drive and the other with a much smaller udb drive - neither exhibit this issue when going through either recovery process. However this particular box is one of the earlier one's and I seem to remember the Open PLi team provided me with a script to get the drive mounted correctly. The main issue was that the drive wouldn't go to sleep, which was explained to me as a box hardware issue, the script was a workaround. Its worked fine ever since, but I vaguely remember the mount didn't look quite right to me.
Is there a way of checking what is causing this issue?
Thanks
I've worked it out!!
I disconnected the internal Hard drive and it went straight into recovery mode with the boot menu. Successfully flashed Open PLi from the online menu. Hope it still works when the drive is re-connected!
Thanks all.
Thanks,
It doesn't work and just sits at the Open ATV Splash screen with the display showing 'boot'.
I'd already tried that particular recovery, albeit with a different date. I used the 128mb as I don't have a 256, nor am I likely to get hold of one nowadays.
Not looking good is it?
Looks bricked.
Five USB sticks, 128mb, 2 x 2Gb, 8 Gb, 32Gb kingston low level formatted with HDDLLF and prepared with BOOTICE. Various recovery flashes tried from Open PLi 7.3 - 8.0, OpenVix, Open ATV 6.2, 6,2. All show the same behaviour in that the box goes from boot, into flash, wait a couple of minutes whilst the usb light flashes, then the box goes into boot mode. When it boots the splash screen has updated to show whatever recovery has been flashed and then stops at that point - the recovery menu with the bbot menu options never appears. If I power down and force recovery mode via remote I also just get the splash screen (Hisilicon or Open ATV) and no bootmenu. I'm not convinced its a usb issue as the splash screen is being updated and I used one of the 2GB drives to reflash a H9.2H SE only last week.
I think this box was on Open PLi either 7.0 or 7.1, and I was wondering whether I needed an older recovery file, but unfortunately I can't find anything that old. The other two combo's I have updated successfully but I'm pretty sure they were on later versions of Open PLi.
Thanks
Thanks,
The boot menu still will not appear. The USB contains the unzipped openatv 6.2 recovery and the openatv 6.2.zip. The box goes through boot / flash / boot and it does appear to read the usb okay. Is it flashing anything, who knows? I just get the Openatv splash screen with no boot menu?
Apart from the usb being formatted to FAT32, is there anything else to look out for in terms of allocation unit size or partition settings? I've read that the formatting is more important than the actual make of disk.
Been doing this stuff for many years and I've never seen a box as fussy. Can these be flashed via a network cable?
Morning,
My H9Combo was on Open PLi 7.0 and I tried to do a software update from the online menu, it didn't reboot and worst still is that I've lost recovery mode and do not get the boot menu.
I have tried to reflash about 7 different types of recovery images, none of which have worked, the closest I have is that the 'Open ATV' splash screen now appears. I have tried with 4 different usb sticks, 128mb, 2 X 2gb and 8gb, all formatted using the HPUSBDisk tool. Everytime it just sits there with the splash screen and 'boot' desplayed on the screen. Recovery mode does not bring up the boot menu and I really don't know where to turn now. Any help would be appreciated.
Thanks
Received the letter last week. I've only been a customer for just under three years so my original setup was with a hardware paired HD+ Box (Amstrad), I then cancelled my HD subs and purchased an old Thompson HD box and repaired to that. Earlier this year I cancelled completely but went back to them after being offered a deal. However the card wasn't clearing in my VU+ so I tried to re-pair with a pace SD box which still didn't help, it only cleared after moving to OSCAM. I assume that currently on their system I only appear to have an SD box even though the other HD boxes have both been registered at various points in time. Sounds like I'm going to end up with a third HD box that I'm not going to use?
In terms of setting up a multi room using one of their boxes, I've been considering splitting the HDMI output and buying a DVB-T2 modulator and distributing the signal around the house, whilst using a mobile phone as the remote. I think you may also be able to achieve this using an Extrend 10000 which has an HDMI input but both of these are quite expensive solutions. I've also been looking at setting up Sky Go on an Android TV device in the second room but I've yet to see a working example so far.
Installed the OScam 11245 ipk for Open Pli and the basic 0963 configuration files as posted by Master G (thanks) and the local card began clearing straight away. I then translated the c and f lines from the cccam.cfg into corresponding readers (c lines) and users (f lines) and established the connections, for the readers it seems to me that the cccam version number is not necessary? Also nor is the card ID - would this limit what the server would share? The main problem now is that I can only decode the 0963 package, I assume this is because service files in the configuration files only listed 0963 services?
I've been reading these threads with interest and have a couple of questions. It seems that the way forward at the moment is to run OSCam as a standalone cam then configure it as a server using the CCCam protocol with clients being assigned user accounts. Does this mean that a version of CCCam also needs to be installed onto the box? If so does it need to be a specific version? I understood CCCam 2.3.0 supports dual tuners whereas 2.1.3 does not? Is that an issue for this setup whereby OSCam as acting as the Cam - does OScam support the decoding of two channels (dual tuner) from a single card?
Thanks
VU+ Duo Open PLi with CCCAM 2.3.0
I cancelled a few weeks ago and then rejoined last week after being offered a deal, I only have the Sports SD package. After the call to reconnect me I monitored to CCcam info pages until I saw an emm to re-activate the card and I'm pretty sure it was clearing Sports 1-5. However as the week has gone it seems that only Sports 4 and 5 are clearing? I have the box key in CCcam.cfg which WAS working, updated CCcam.channelinfo and CCcam.prio files and re-paired the card via their website (it warns that it could take 2 hours). Since then I've had a number of emm's from my DM800SE to the VU which I would of expected to have confirmed the pairing but it still isn't clearing Sports 1-3, so they have changed something at their end.
I used to use an OSCAM/CCcam combination a few years ago but changed to CCam 2.3.0 because it didn't seem to be able to decode two channels at the same time (dual tuner), also I remember a problem with the boxkey in OSCam, although I am willing to be corrected? It would be nice to see if anyone has a workaround for this which will clear these channels on a multiple tuner receiver.
Thanks
which is why many of us use Smargo's. , please elaborate ?
It supports the lower 3.3v power supply for card readers. Some receivers can only support a card reader power supply of 5v and there was a theory that this could potentially cook some cards.
Is it OK to put an 0963 card into the internal reader of a VU+ Duo2? There was a potential overheating issue due to the voltage, which is why many of us use Smargo's. I must admit that I've had another 0963 in a DM800SE for over a year now and that seems fine?
OK, we are half way there, its now decoding the non-premium channels. Do you think this is a boxkey issue or possibly a service file issue. Also the generated smargo line doesn't work and doesn't look quite right:-
SERIAL READER : /dev/usb/tts/0 smartreader+
I was expecting (VU+ Duo2 with latest Vix):-
SERIAL READER : /dev/ttyUSB0 smartreader+
Do we still need to run these 0963's in smargo's or will it be ok in the internal reader? Also what frequency should they be set to?
Are you saying CCCam doesn't support emm blocking, I'd be a little happier being able to block them.
- - - Updated - - -
Yeh, serial reader needs to be "SERIAL READER : /dev/ttyUSB0 smartreader+", I think this is image related rather than box. Boxkey was incorrect and has now been fixed so all working now. I can confirm this fixes being able to view an encrypted channel whilst recording another. I also have the blocker set to "has blocker(s): Shared Group enabled", shame I can't block unknown's. Hopefully this will still update the card? Thanks again Master G.
The oscam & CCcam 2.3.0 combo is used to read TNT sat card, it`s not suitable for running a server..
OK thanks, sorry for being a pest but do you have a link to the latest cccam.cfg for a 0963 card which allows U emm but blocks S/G/UNKNOWN emm's? Also do I now need a boxkey when using CCCam alone, its years since I've used it stanalone and assumed it was a dead duck now!
Only CCcam 2.1.3 and below will work along side oscam as cardreader.. All other versions show the card as HOP10, not local.. CCcam will then try from your peers first instead of your card..
You would be better ditching the separate CCcam configuration and go oscam only or just CCcam 2.3.0.. If you need help with that let us know buddy..
Hi Master G, you've confused me a little there as I'm trying to fix this on a VU+ running Open Vix and downladed "enigma2-plugin-cams-oscam-svn9842-cccam-2.3.0_openvix_all.ipk" - a file which I belive you posted?
http://linuxsat-support.com/showthread.php?t=1689&page=4
I also downloaded "enigma2-plugin-cams-oscam-svn9842-cccam-2.1.3_openvix_all.ipk" which works fine, so I assumed the other file should work. It certainly infers that it should work otherwise why build a file using incompatible CAMs?
Anyway if straight CCCam is the way to go then so be it. The reason for using OSCAM is that it auto updates 0963 well and you can block specific types of emm.
Bit stumped here.
I've been using various versions of OSCAM as a server with a CCCam client for many years but can only get older versions of CCCam to clear channels. Are there any differences in the configuration requirements for the two versions. I've successfully had OSCAM to CCCam 2.13 running with a 0936 card amongst others in DM500's, DM800's, DM800SE's, VU+ Duo2 with various Open PLi and Open Vix images and both with internal and external card readers. As soon as I change one variable - the version of CCCam - it won't clear channels, despite OSCAM showing entitlements and CCCam successfully connecting. The only reason for me to consider 2.3.0 after all these years is that I've read that for a dual tuner setup, the only way I can record one encrypted channel whilst watching another is to use v2.3.0??
What I am missing, does CCCam v2.3.0 need additional setup information?
DM800SE with RTL2832U / E4000 tuner combo working fine now. No go with the R820T yet and no luck at all with any of the sticks with a DM800.
Also off topic....
Has anyone wondered why the oscam devs have shown zero interest in this issue ???
They are not prepared to flog a dead horse perhaps? If you actually have a read of their problem report board and refer back to when this system was rolled out in Italy, it was reported as a problem to the OSCAM team. They investigated and found that the problem was due to the pairing system and not the CAM software, they closed the problem on the grounds that it could not be fixed until somebody provided them with the pairing algorithm. Which all seems above board and fair enough to me.
Also off topic....
Don't all rush to the phone and cancel your hd subs when the last hd channels go black.
Either cancel it now or wait a few weeks after they are gone and say you cant afford it.
Er, what difference will that make?
