[mythtv-users] Any experience with Unicable under MythTV ?
warpme at o2.pl
Sat Jul 7 18:07:06 UTC 2012
On 7/7/12 11:48 AM, Karl Dietz wrote:
> On 07.07.2012 11:18, Warpme wrote:
>> Now I get running BE & have probably issue with configuration.
>> I configured 2 SCR tuners:
>> 1. Id=0, carrier=1210
>> 2. Id=1, carrier=1420
>> Log below shows probably that after trying to tune to given mplex I'm
>> receiving wrong mplex as TID/NID/SID are wrong...
>> Any clue where error is ?
>> 2012-06-23 22:13:20.491790 I DiSEqCDevTree: SCR: Tuning to 12322000kHz,
>> HiBand, H using UB=0, FREQ=1210MHz, POS=A
>> 2012-06-23 22:13:22.970863 I
>> DTVSM(/dev/dvb/adapter0/frontend0)::HandleSDT(): networkID = 318
>> orig_net_id = 318 transportID = 8100 orig_transport_id = 8400
> > 2012-06-23 22:13:29.984283 I
> > DTVSM(/dev/dvb/adapter0/frontend0)::HandleSDT(): networkID = 113
> > orig_net_id = 318 transportID = 13200 orig_transport_id = 8400
> Looks like you get the same (ONID 113/0x85, formerly Beta Research/Sky
> /Premiere) transponder no matter what channel you actually tune to.
> One issue might be that some systems count the SCR address as 0-7 and
> others as 1-8. Maybe you are tuning a different carrier frequency then
> the one you wanted to tune.
> mythtv-users mailing list
> mythtv-users at mythtv.org
Thx for this hint !
I overlook this scanning logs.
It looks like mapping ID->CarrierFreq isn't monotonic for my converter
By try&error (with converter connected to single tuner) I was able to
1210MHz require ID=3
1420MHz require ID=1
But for 1680MHz & 2040MHz I wasn't able to find working ID :-(
Unicable patch has ID limit set to 7
Maybe for 1680 & 2040 required ID is higher than 7 ?
What You think ?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 83 bytes
Desc: not available
More information about the mythtv-users