|
two-way satellite broadband |
|||||||||||||||||||||||
Opensky Transponder ChangeOn the 28th of February 2005, Opensky moved transponder on eBird at 33 deg East. What to Do?
Using Opensky 1.6 on eBird on 33 deg East - Auto UpdatedNetwork sent out an automatic update over the air for a few days prior to the change. If you had your Opensky Client running during that time, you should be OK and not even notice a change has occurred. Using Opensky 1.6 on eBird on 33 deg East - Not Auto UpdatedIf you have already installed Opensky Client
If you are about to install Opensky Client 1.6
Note: OSControl and OSWizard will identify the transponder as a1 (the old name) instead of the new name of b2. This is expected behaviour. The Opensky system has "renamed" the new transponder internally as a1 in order to avoid database problems. This means that Opensky (and OSControl and OSWizard) "think" that the transponder is called a1 when in reality it is Eutelsat's transponder b2. Using BSM2 on 33 deg EastThe procedure for the BSM2 is given on page 13 of the Manual: about the Advanced Settings page. You only need to change the:
Then click "Commit Settings". The satellite will change to "Unkown" (sic) but this is OK. Do not reset the satellite to eBird-a1 as this will put back the old settings. Using Manual Tuning on 33 deg EastYou need to retune your receive device with the following parameters:
Please see your device documentation for details. Using any method on 7 deg EastThere is no change to the service on W3A at 7 degrees East. Problems?notify us via this link or call the helpline. NoteAll our users should already be using Opensky Client 1.6. If not, you should upgrade asap. You can download OS Client 1.6 for 33E here or ask us for a CD. |
|||||||||||||||||||||||
|
©2008 BeyonDSL.net Ltd |
|