Pull out then re-insert.!?

[MortUK]

Hi all,

I have 2xFloppyDVT Cable tuners, 2xIcecrypt Cam with the Joker 79 firmware and Windows Media Centre.

Everything has been working fantastically for a week or two until one of the tuners decided last night that it didn't want to unscramble channels any more.. After a quick pull out of the cam then plug in again everything worked fine.

Does anyone know what causes this.? It's just going to be a bit of a pain if it happens again and I miss recordings..

Mort.

[Confused Stu]

Does it happen on particular channels, or random ones?

I had that problem on about 15 channels (always the same ones) that required a pull out/push back or a reboot to get it unscrambling again. I even went as far as to have a batch file that stopped the FireDTV service, then restarted it as that fixed it as well. Finally, on the advice of someone else on another forum, I reflashed my CAMs with 0.80 Joker. My unscrambling problem is now fixed on those 15 channels - but I now have no video on 6 channels! Strangely, they were ones that worked fine with Joker 0.79, but I chose to stick with 0.80 as at least no rebooting is required after I hit a non-working channel.

[MortUK]

I had none of that.. All of my channels worked, there were no freezes or anything like that, just got the message, "This channel is Scrambled, unable to view" on All of the encrypted channels, the free ones were fine. I took out the cam, re-inserted and everything was fine again.. No rebooting needed...

It's just a bit of a pain if it's gonna happen regularly.. I'll bare the Joker 80 firmware in mind.. I'm a bit reluctant to mess too much with it as it was working so well up until last night.. and it's only once in a week so far..

Do you know the best way to flash the Icecrypt with the Joker 80 if i need to.? Can it be done with just a funcard..? I don't have a CAS3 at the moment...

[Confused Stu]

That sounds like a different problem then mate - mine happened EVERY time I tuned to one of those particular channels. Hopefully yours will just have been a one-off and never happen again.

No idea how to flash a CAM without a CAS3, I'm afraid mate. By the sound of it though, you shouldn't need to worry. (fingers crossed)

[Cafe.Rcaer]

Check what firemware you have on the FDTV, and try upgrading. Some people have had problems with high firmwares, but you can downgrade them afterwards if you need to.

[MortUK]

Originally Posted by Cafe.Rcaer

Check what firemware you have on the FDTV, and try upgrading. Some people have had problems with high firmwares, but you can downgrade them afterwards if you need to.

Ah, I think that may be it.... I'd forgotten that I'd updated the FW on the first FloppyDTV that I bought when it arrived but not on the 2nd as I bought it a week later..

Although I'm not sure exactly which one has which.. I have a sneaky suspicion that it's the one with the old FW that went wrong.... I't hasn't happened since so I'll leave it alone until it happens again.

[Cafe.Rcaer]

You can see the firmware in the FDTV Support tool - there are two different HW versions, though, with two different FW versions (I have one of each).

It's all on their site, just get the right one!

[TogaForComfort]

I have exaclty the same issue. It has been suggested to me to try upgrading to Joker 0.80 but I have not had a chance to look into how this is done.

Out of curiosity, My DTV Info is:
Hardware revision 01.26.02 and firmware 2.4.0 build 51440
could you post what you are running?
I have not updated the card at all.

i have been running the card for about 6 months with no problem. I have had this issue for about a month.
I have built a dedicated TV server for media portal and since moving the card to this machine the issue does not occur as often.

[Cafe.Rcaer]

FireDTV / FloppyDTV devices:
-------------------------------------------------------------------------------
devices found: 2
Status for device 1
Model : FireDTV C/CI
GUID : 0x0012870036001E87
HW Ver.: 01.36.02
FW Ver.: 2.4.0 Build 51440
Driver : 5.0M (5290-1000)
Frontend Status:
Power Supply: 0.24V
1394 Bus: 11.40V
Frequency.: 762992 kHz, Sig.Str.: 0%, BER: 16160
Locked : NO
CAM Module: Module
Status for device 2
Model : FireDTV C/CI
GUID : 0x0012870036000A0C
HW Ver.: 01.36.01
FW Ver.: 1.4.0 Build 52030
Driver : 5.0M (5290-1000)
Frontend Status:
Power Supply: 0.24V
1394 Bus: 11.40V
Frequency.: 698992 kHz, Sig.Str.: 100%, BER: 0
Locked : YES
CAM Module: Module

The other thing I remember is that one of the firewire ports on one of the FDTVs stopped working, I seem to remember it was the old one of the two. I swapped the lead to the other port and it's been fine since. D-E did offer to swap it, I just never bothered.

[MortUK]

Both my H/W versions are 01.26.02

I had one running the 2.4.0 FW and one on the 2.4.4 FW.

I'm pretty sure it was the one running on 2.4.0 that went wrong.. I'm running with them both on 2.4.4 now so i'll see what happens, fingers crossed.

I had a look through the FireDTV forums and people appeared to be having problems with the 2.4.3 FW which has now been taken down..

Status for device 1
Model : FloppyDTV C/CI
GUID : 0x0012872602010B1C
HW Ver.: 01.26.02
FW Ver.: 2.4.4 Build 61030
Driver : 5.0M (5290-1000) x64

Frontend Status:
Frequency.: 394992 kHz, Sig.Str.: 0%, BER: 16160
Locked : NO

CAM Module: Module

Status for device 2
Model : FloppyDTV C/CI
GUID : 0x0012872602010B06
HW Ver.: 01.26.02
FW Ver.: 2.4.4 Build 61030
Driver : 5.0M (5290-1000) x64

Frontend Status:
Frequency.: 370992 kHz, Sig.Str.: 100%, BER: 0
Locked : YES

CAM Module: Module