PDA

View Full Version : problem with 16.0e


tool37
1st May, 2011, 02:43 AM
hi all, set up vu duo with black hole 151, downloaded Vhannibal E2 Motor the latest one, put them on the image and 16e was working ok, but rebooted and when i go to 16e all the channel listings are not hilighted, when i set it up in the tuner config it said 16e, but know it says 15.8, new to sky so it may be obvious to somebody, hope somebody could tell me what i did wrong, thanks
RuberDuck
1st May, 2011, 06:01 AM
looks like the new satellites.xml file is looking to 15.8 east when the satellite it self is looking to 16.0 east.

you can try generating a new satellites.xml file to see it that helps.
tool37
1st May, 2011, 12:58 PM
al sorted now, thanks for the help, can watch the match now
satmannwest
1st May, 2011, 05:48 PM
16e 15.8 both the same m8
RuberDuck
1st May, 2011, 06:33 PM
16e 15.8 both the same m8

yes i am well aware of that fact, however some bouquet packs use 16.0 as their reference and some as 15.8, these can cause all kinds of problems when transferring bouquets.
tool37
1st May, 2011, 07:47 PM
just edited the sats xml file, and changed 15.8 to 16.0, restarted and all working now
satmannwest
1st May, 2011, 09:55 PM
That was my point , then use 15.8
RuberDuck
1st May, 2011, 10:13 PM
That was my point , then use 15.8

erm that was his point, when the satellites.xml was directing the receiver to 15.8 it was not working. when he modified to look to 16.0 it worked.
satmannwest
3rd May, 2011, 07:57 PM
Then modify it back to the correct 1 as 15.8 is the correct 1 m8, . Especially with the sat being weak anyway, And it was obvious that his bouquet was wrong, Don't forget m8, load the bouquet then change your tuner configuration after. so what you trying to prove.
RuberDuck
3rd May, 2011, 08:18 PM
Then modify it back to the correct 1 as 15.8 is the correct 1 m8, . Especially with the sat being weak anyway, And it was obvious that his bouquet was wrong, Don't forget m8, load the bouquet then change your tuner configuration after. so what you trying to prove.

again that was the point. when the satellites.xml was referencing 15.8 it was not working, now he has modified it to reference 16.0 it works for him. and yes i know the correct designation of the satellite in question.