Posts by cardomons

If your using oscam, you can modify the oscam.dvbapi to have a single line so it will force dead cards to wake up

P: 0963:000000 1

ps. I would avoid putting it in the original box

Happy days reinstalled dreamplex with the latest enigma2-plugin-extensions-dreamplex_2.0-rc.11_all.ipk from the download section in linuxsat and the stop button is now working

I had a similar problem on Vu+Duo but I had updated using the update on the box, since then I reflashed the box (Apollo.029) now and everything almost works fine, except for the stop button when playing a movie

So just updated my Vu+Duo to the latest VIX image Apollo build 29 and installed dreamplex from the plugins and unable to stop any movies with the stop button, all the other buttons work except the stop button. Have to fast forward using the number buttons and let the film stop when it comes to the end - doh!

If anyone is interested in running this on the amiko alien 2 box running hyperion v3, I have just managed to get this working. After installing the dreamplex ipk listed in the thread, (or the one listed on the box downloads) the app complains about the curl library not being installed, I managed to hunt it down to http://opkg.familienforum.biz/…m7162/curl_7.29.0_sh4.ipk copied the ipk to the /tmp folder and ran opkg install curl_7.29.0_sh4.ipk

trying to run curl it complains about missing ssl lib so also installed the openssl from the same place http://opkg.familienforum.biz/…openssl_1.0.1e-29_sh4.ipk

I used to use Project Valerie to play movies on a Vu+ Duo box but found if the computer went into sleep mode the vix image would hang while it tries to locate the connection, using dreamplex I am able to play the movies on any box now that I have moved my movies to the router. I can also share the movies with family and friends, unfortunately movie playing is a bit hit and miss on the latest zues image and find I have to reboot the duo 1st before playing a movie but this I suspect is more to do with the latest round of changes in the VIX image and less to do with dreamplex

Typical post a comment and mgcam behaves itself, I realised the ccam was still on autostart, removed it from autostart and no black screens for 3 days now, maybe worth checking you don't have ccam on auto start interferring with the mgcam!

I too have problems with running mgcam 1.38 (installed through tspanel) going to sleep on the Vu+Duo, black screen, having to restart the cam normally does the trick but sometimes I do have to reboot the box.

I had this 6 months back and decided to switch to Black Hole 1.7.6. rarely had a problem on BH, however, personally I prefer the VIX layout more user friendly, the epg I find is better for me and feels faster switching channels, playing movies from the HDD or an external HDD has a better interface, sorry black hole ;-( . The configs I am using on the VIX image are exactly the same as I used on the BH, as I backed them up before loading the new VIX image and I have the same glitch as you have.

I tried different firmware, same thing, but managed to connect using newcamd client to a (random ;-) ) newcamd server (still missing *** Atlantic+1), but all the other channels were working so tried using 202e newcamd client with my Oscam server, added a cardclient.conf in /var/tuxbox/config with

newcamd:{oscam-serverip}:{port}:1/0963/0000:{user}:{pwd}:0102030405060708091011121314

even though I could see the user connecting it would never clear any scrambled channel and would keep showing an anonymous user connecting and then disconnect, along with the connected user, so eventually I installed CCcam on the Vu+Duo added the cccam on a different port to the newcamd and hey presto it worked, (still no *** Atlantic+1) but all the other channels were fine.

Has anyone else managed to get the newcamd client connect to an Oscam server, I read a comment on a forum somewhere that the newcamd protocol was broken in Oscam, but MGCam works just not that well on the 202e

Normally oscam is the server used for sharing the card to other users, so you would need both Oscam + MgCam installed, how do you rate the box, from a users point of view, e.g. 7 day epg ease of use, does it freeze/crash, missing channels and have you tried the recording functions?
Regards

Thanks - Maybe it's the firmware upgrade, can anyone suggest an older version of the firmware for this receiver, preferably with a working channel list?

Hi,

I'm using an Ariva 202e in the bedroom to connect to my Vu+Duo downstairs with MGCAM, some channels work and some are scrambled, e.g. *** Atlantic works, but *** Atlantic+1 is scrambled. Using Oscam as the server I can see the user connected but the logs report its accessing the cache, if anyone has any ideas, it would be much appreciated?

All channels work on the Vu+Duo and another ***Box F3 in another bedroom, both are using MGCAM

I have re-scanned numerous occasions doing blind scan on Astra 28.2E and Hotbird 28.5E

snippet of the OSCAM log for the Ariva 202e user...

channel switched to *** Atlantic

r reader: slot0 ecm: FC4E real time: 430 ms
r start client thread action 24
c data from add_job action=24
r ending thread
c ecm answer from reader slot0 for ecm FC4E rc=0
c ncd_send_dcw: er->msgid=7, cl_msgid=7, 80
c send 31 bytes to client
...
...
c User1 (0963&000000/1268/5F:FC4E): found (433 ms) by slot0 (2 of 2)
c cw:
...
c ending thread

s start client thread action 23
c data from add_job action=23
c nmr(): len=2, errno=0
c received 97 bytes from client

Channel switched to *** Atlantic+1

c ncd_process_ecm: er->msgid=8, cl_msgid=8, 80
c trying user 'User1' filter 0963:000000
c 0963:000000 allowed by user 'User1' filter 0963:000000
c trying server filter 0963:000000
c 0963:000000 allowed by server filter 0963:000000
c ncd_send_dcw: er->msgid=8, cl_msgid=8, 80
c send 31 bytes to client
...
...
c User1 (0963&000000/1268/5F:FC4E): cache1 (0 ms) by slot0 (2 of 2)
c cw:
...
c ending thread

Thanks and regards

I have had an F3 for a couple of months now, the kids don't like the EPG and the USB recording is somewhat limited in that it keeps reporting the device is too slow. Also, when the network is unattached and the box is switched on from cold the load sequence gets to 93 stays there for a few minutes and then displays E0001. This maybe firmware related rather than box related., but eventually the box kicks into life if the server is reachable.

I have also been messing around with an Ariva 202e, the latest firmware version works for awhile then the box reports the dreaded 'ASH' on switch on, RS232 NULL modem cable and a reload of factory firmware brings the box back to life, also struggling with channels not clearing, with either NEWCAMD and MGCAMD, did have it working for awhile but just stopped.

IMO I do like the F3, both HD and SD picture qualities are better than the 202e and the F3 worked straight out of the box for me, using a Vu+Duo with OSCAM+MGCAM as the server/client