FireDTV Diseqc Problem

[yeoda]

Hi

Heading back to GBPVR due to the recent addition of CI support.

Glad to say the CI support works with my FireDTV satellite.

However, diseqc doesn't work correctly.

Using the diseqc options when selecting the capture source channels are found and can be successfully mapped. However, when trying to view live TV no signal is found from one of the LNB's.

Interestingly, if I change the BDA.INI FireDTV entry for SUPPORTS_BDA_DISEQC from 2 to 1, live TV will select the other LNB.

Any help in getting diseqc to work would be appreciated, as GBPVR with CI support would be the perfect solution.

yeoda

[dennit]

Glad to say the CI support works with my FireDTV satellite.
However, diseqc doesn't work correctly.

DiSEqC worked well for me with my Twinhan card, but it did require some setup. As background: GBPVR must tell your card to send the diseqc commands. There is no universal BDA command set for this, but sub supports certain cards. Different manufacturers use different commands for different cards. The Twinhan could respond to three different sets of DiSEqC commands, and sub provided a config.xml setting for each. I found that some worked better than others. Some put the commands it sent into the log - you may want to check the logs.

Assuming that you have set GBPVR to send the right DiSEqC commands, they still have to be created by your card, pass through any switches and be understood by your LNBF. Does your card work to send DiSEqC commands with other software?

[yeoda]

Yes, the card works fine with other software.

What logs should I check and what should I be looking for?

[dennit]

Yes, the card works fine with other software.

What logs should I check and what should I be looking for?

Open up the logs directory, tune a channel, shut down GBPVR and sort by date. See what's at the end of any logs that changed. I don't know if there's anything in the logs that will help you, but I found it useful to compare what GBPVR was sending to what worked when sending raw commands from other software.

[yeoda]

Thanks

I have taken a look at the logs. I managed to locate the DiSEqC commands, however, I am finding it difficult to identify which command was sent for the specific LNBs.

Is there any way of manually altering the sent DiSEqC commands so that I can establish which one works. The only one that works when watching live tv is for setting (LNB) 1. I just find it strange that all the DiSEqC commands work when channel mapping.

Thanks

[dennit]

I am finding it difficult to identify which command was sent for the specific LNBs.

Is there any way of manually altering the sent DiSEqC commands so that I can establish which one works. The only one that works when watching live tv is for setting (LNB) 1. I just find it strange that all the DiSEqC commands work when channel mapping.

I can't help much with the FireDTV card.

I found similar issues, however, with the Twinhan. Settings that worked during scanning, didn't always work properly for tuning. In addition to software issues, there were hardware issues. I found that I needed to provide more power to the card for scanning, so I had to hook up an auxiliary power source to my DiSEqC switch. Later, I ended up modifying the card to accept an auxiliary power supply.

For me, there was lots of trial and error. I used the information from the logs (about DiSEqC commands sent), and compared it to information about raw DiSEqC commands from the DiSEqC standards literature and tests with other DVB-S software before finally getting it all to work well. AFAIK, there is no raw/manual setting for DiSEqC commands to send. The Twinhan, however, had several config settings that changed what DiSEqC commands were sent, even though there was no direct control (beyond the config settings). I don't know if the FireDTV card has anything similar.

You haven't said much about what type of LNBF you are using, whether you have a DiSEqC switch or if it's built into the LNBF, or if you are using a tone switch. Sometimes, changing those is an alternative to getting the diSEqC running. Also, some DiSEqC switches are notoriously intermittent.

[yeoda]

Thanks for your assistance, it's really appreciated.

I'm using a DiSEqC switch (Global 4 way DiSEqC switch).

It has been working flawlessly with other DVB-S software (I'm not sure if I'm permitted to mention the other software). But, the Popcorn hour interface of GBPVR is second to none.

I think I will need to look again at the logs and establish the raw DiSEqC commands sent through GBPVR and how these compare with other software and DiSEqC standards.

I can see a couple of late nights ahead!