Hi all,
I recently added a twinhan Mantis 1034 ci card into my pc system. I purchased a purple cam and put my Austar Pay TVversion 5.3 card into it. I first used the software that came bundled with the card, Twinhan's "digitalTV."
It is very clunky software, but I could get all channels okay. I loaded ProgDBV and scanned, found all the channels with good quality signal. The thing is I'm getting a red lock icon in the bottom left hand sideof the ProgDBV dialog. I can get the free channels no problem.
I jump back into the crappy card's software player and I have unlocked channels. I have tried using this card with DNTV Live and I get the same issues as the ProgDbv software...
I interrogate the ci module and it gives me an e34 error saying the signal is scrambled..
This is definitely legit card and as I said the DigitalTV software works with it, as does the austar box. I have to be doing something fundamentally wrong here.
Anywhere I should start looking?

cheers,

I assume you have enabled the CAM interface in ProgDVB? I have no idea about what it could be in DNTV Live!, which has no specific settings for cams, it should be all automatic.

Have you tried recording with DNTV Scheduler Pro, are you able to play the recording?

Have the CAM module installed in PROGDVB. I haven't tried scheduler and it will probably do my head in to learn how to set it up.
What I have noticed is that when in ProgDvb and I had a plugin called vplug that was supplying a log file, it was showing up with Irdeto2 and videoguard\NDS in the log.
Looking on the Lyngsat page for Austar here http://www.lyngsat.com/packages/austar.html it is now noting both encryptions.

Now I could could very well be clutching at straws here, but could the videoguard\NDS encryption being filtered out of the signal via the Twinhan software and the NDS being caught up by DNTV and ProgDVB? On the scanned channel list, all of the channels are under the foxtel folders in ProgDvb..


Could there be any validity to this novice's hypothesis? It's hardly occam's razor, though. Could anyone think of a definitive way of testing this hypothesis, bearing in mind I really know nothing about decryption and satellite signalling?

cheers,

Hmm, I have no idea about all that stuff, but as far as I know you can not use certain plugins if you are using a hardware CAM. Just delete the ProgDVB folder, install the latest version of ProgDVB , no plugins and try again.

I tried ProgDvb without any plugins. I had locked channels. I then tried ProgDvb with plugins to get a log. I still had locked channels, but I had a log of sorts.


Renura, can you point me to anyone who is using the TwinHan for Austar in DNTV LIve! at all?

There are many user of DNTV Live! that use it with DVB-s cards, including to receive Austar programming, I have tested it myself in a number of locations in Australia. I am not sure what you are looking for, but if DNTV Live! see the card gets no channels when scanning with the DVB-S card, then most probably you got incorrect settings. If you get the channels, but can not play them, then it is either the CAM or the decoder used. If FTA DVB-S channels are OK, but PayTV are not, it most likely is the CAM.
If you are using a number of DVB-S applications in the same PC, I suppose you could also have a conflict of sorts, although I doubt it, as I use DVBViewer, ProgDVB, DNTV live and DigitalTV for testing, as a matter of routine.

thanks, at least I will keep trying if there are people who have actually achieved Austar via DNTV and the twinhan card.


Why I am asking is that I have Austar working perfectly with Digital TV program, yet DNTV and ProgDVB will not unscramble the signals with absolutely no changes to the setup. THis is very strange.


cheers,

renura: Have you tried recording with DNTV Scheduler Pro, are you able to play the recording?

sanquar: I haven't tried scheduler and it will probably do my head in to learn how to set it up.

sanquar: Why I am asking is that I have Austar working perfectly with Digital TV program, yet DNTV and ProgDVB will not unscramble the signals with absolutely no changes to the setup. THis is very strange.

There is a good chance that the log files produced by DNTVSchedulerPro may assist in understanding your problem.

Thanks for letting me know about the logs, Bear. I will finish set up... Any literiture on what I should look for in the logs?


Regards,

No written literiture, look in the log directory of scheduler and open the devicescan.log file after you have enabled your device from the system devices page.
In this log it should show the details of what info it was able to parse from the CAM interface & CAM card. If successful it should indicate what card info is and this should give you an idea if the interfaces are working correctly.
One advantage is that if you use the mpgmux capture type in scheduler for a recording, then if the descrambling fails then this will cause scheduler to retry multiple timers over the duration of the recording(say 15min period) and trigger the CAM to work, this may help to see if there is a intermittant CAM/Card issue involved.

BTW, It is important to ensure that you have LNB Power enabled in scheduler if your using a LNB on the dish requires it from the card. You can globally set this from the system config settings page.

Thanks, Bear. I really do apreciate this info. I will have a look at that when I get back home on the weekend.

Regards,

Attached is the log file for the capture. The capture was for fox sports 2 which I have the subscription. Capture was for 3 minutes. The actual .mpg was 2 kb in size and of course would not play.

If anyone can give me some leads on this, I thank you in advance.

cheers,

For the test you need to capture for at least 15min to get multiple retrys, zip and attach to the post the scheduler.log, capture.logs as well as the devicescan.log and channelscan.log files.

I don't see any problems in the attached capture.log that suggests that anything is amiss but without the other log files it's hard to say.

I do notice that the "f22k:1" is enabled, I suspect that you may have a tone switch involved, if not it may need to be set to 0 in the global settings.

Hi Bear, I finally got back home to try as you suggested. Attached is the log folder zipped. The scheduled recording was for 16-4-08. No luck with it recording, though. You mentioned a channelscan.log. That I don't have. I will try another rescan of the channels and post that up next.

I do notice at the start of the capture attempt, there are two lines in the capture log "win32-DLL-BDA : The registry information cannot be read." I only have rudimentry ideas of what is happening behind the scenes. If you could have a look at these logs I would be very grateful.Click to view attachment

Renura,
I am using the Azurewave PCI card with an irdeto cam and a selectv decryption card.
The system is still not working after many attempts by different technicians.
At first i could not recieve any scrambled signals even after registering the card in a setop box. I have had this card replaced and the isues have changed slightly.
This is the closest i have got to success so far. I can now play any of the scrambled channels but i get no vision (just black screen) and no sound.
However i do now get a OSD stating the channel name and sometimes the name of the show which is currently airing.
Click to view attachment

Please help this is getting very frustrating.

Thanks Heaps

Are you using the AzureWave card with the separate CI module?
If so, send back the CI module and we will check it out - we had a small batch that had the incorrect firmware on them.

Is there a way of updating the firmware or at least checking which firmware im running??
Regards

No, you need a special tool to do it

What address do i send it back to!
Ill send it by courier.
Thanks

Renura,
I have sent you the cards that are not working last week but am yet to recieve a replacement.
Could you please follow this up. Thanks

We got your card on Friday - it is only Monday! I am not sure what you expect? our suppliers RMA turn around is one month! Ours is one week, but often just a few days.