Welcome to GOFASTMOTORSPORTS.com ... ... ... Green Flag - Green Flag - Go Go Go ... ... Brought to you by Ricks Satellite - Where the Big Dish Rules!

Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
wejones

Avatar / Picture

Registered:
Posts: 5,751
Reply with quote  #1 
Hi... I started this thread so people can find it easier, even though the topic was first brought up in the "Anybody recieved theirs yet" thread.
But to repeat what the issue was that on my motorized BUD I'm using a Bullseye feed which has 2 C-band and 2 Ku LNBs.  These 4 lnbs plus a Ku LNBF which is on a fixed 1M dish aimed at AMC-21 are all on an 8 port diseqC-1.1 switch.  
   I originally had the problem that when I would scan in channels on one satellite, or even on one polarity, that it would wipe out channels that I had previously scanned in.  Hockeynut and I think others helped me get to understand that I needed to change the "LNB#" for each separate satellite/band/polarity, although at first I thought that I could get by with only 5 separate LNB#s, which is apparently wrong.
   I also had the problem that in order to do this, I needed to have a separate satellite defined for C-band-horizontal, C-band-vertical, Ku-horizontal, Ku-vertical for each satellite, which means that I can't use the pre-defined sat list, and also can't use the internet site which allows you to create custom satellite lists, since it only allows you to choose satellites once.
 
   So what I had to do was manually create my own custom satellite list by editing the original list. To do this, I first used FTP (I've used both Filezilla and the FTP function that comes with Windows) to download the satellite.xml file from the Octagon. 
   After starting either FTP program, I changed directory to the /etc/tuxbox directory, and pulled the satellite.xml file back to my computer.  Then I used wordpad in Windows to edit the file.  Basically I would find the entry for the satellite in question, then I would copy that whole section, and then paste it back in 3 more times.  Then I would edit the sat name so as to indicate C-V, C-H, Ku-V, and Ku-H, and I changed the sat positions to something like 86.9,87.0,87.1, 87.2 using SES-2 as an example, just to make sure it saw them as different satellites.
  Then I saved this file, and used FTP to load it back to the Octagon.  Actually I renamed the file to satellites1.xml before uploading it to the /etc/tuxbox directory, then connected via SSH, and saved a copy of the original satellites file before copying the new file into satellites.xml.  This probably wasn't necessary. I probably could have FTP'd the new file directly, but it was safer to do it the way I did.
   After getting the new file in there, I rebooted the Octagon, then went in and configured the new satellite files.  I first made the mistake of re-using LNB#s one each satellite, but that ended up messing up everything I had already scanned.  Finally, I realized that I needed to use a different LNB# for every different satellite, or in my case 4 separate lnb#s for each satellite.  After scanning 1 satellite for all 4 LNBs, 4 other satellites for 1 band at one polarity, and 1 Ku LNBF using voltage polarity, I think that I had used up 11 different LNB#s. 
   It took me a whole day just to get 11 LNB#s configured properly and scan in a few channels on each.  But now that I understand what is necessary, future sats won't take nearly as long. 

   Anyway, the reason for the post is that I think programming the Octagon for feeds like the Bullseye can be complicated, but it does seem to work.  If anyone else tries to do this, I can go into more detail, and if anyone sees that I didn't need to go to these lengths, please post, as it would be nice to find an easier way.

chewie

Registered:
Posts: 30
Reply with quote  #2 
Hello Wejones
Did you try downloading the satellite list from this site? it lets me download more than a few list.
http://satellites-xml.org/
Regards.
Chewie
Hockeynut

Avatar / Picture

Registered:
Posts: 9,611
Reply with quote  #3 
I took the sat farm down before the Octagon but even then when I had over 30 dish`s in the yard running to multiswitches and then to Diseqc switches it was a real job labeling this and making sure everything was in order.Using the Vu and AZMe both E2 units.

Now that I have downscaled it is a much simpler setup and Here is an ex of what I do.

Currently using only 5 inputs of the 16x1 Diseqc switches now and all receivers and computers are tied into this the same..Makes life so much easier when every device has the same setup.

So for port 1 of the Diseqc switch is connected to a 10' KTI that the AZMe pushes around.It has a Dual Cband Ortho.This is going to a 4x8 multiswitch 22Khz off.Then I have a fixed 1.2 parked at 91 going to the 22Khz on side of the multiswitch..Both of these to port 1 on the Diseqc switch.

Then for port 2 of the Diseqc switch I have another 10' KTI that the Octagon is pushing around along with another dual cband ortho.Same setup as described..going to 4x8 multiswitch 22Khz off.Then another fixed 1.2 parked at 103 going to 22Khz on..Both port 2 on the Diseqc switch.

Now this is what I do with what I described on all E2 receivers is for port 1 I label all sats as lnb1 as it is a moving dish so the same lnb,port etc never change and then for the fixed dish tied into the same multiswitch I call it lnb 11...Same thing for port 2 of the Diseqc switch.I label lnb 2 for the octagon as it has same lnb`s and for the other fixed dish coming into this same multiswitch I label that as lnb 12..

and so on and forth.It keeps things simple this way.You get the idea...It was nuts when the farm was much larger.No regrets simplifying.Hope this helps.

__________________
Dish`s--10' KTI,10' Button Hook,10' Unimesh x2.
1.2 Ch Masters parked at 91,103.
1.2 Ch Master with factory polar mount tracking from-58w-127w -Western Ku Dish.
1.2 Ch Master with factory polar mount tracking from-12.5w-81w -Eastern Ku Dish.
Positioners--Gbox,Vbox`s.
Receivers--AZMe,AZPlus,AZElite,Icecrypt S1600 HD,VU Solo2 SE,Octagon SF4008 UHD 4K,Prof 7500,TBS 6982,TBS 6902.

GOD BLESS AMERICA.
wejones

Avatar / Picture

Registered:
Posts: 5,751
Reply with quote  #4 
Quote:
Originally Posted by chewie
Hello Wejones
Did you try downloading the satellite list from this site? it lets me download more than a few list.
http://satellites-xml.org/
Regards.
Chewie

Yes, I did go to that site, however unless I didn't understand how it works (which is not unusual), it looked like they had check boxes for each sat you wanted in the list, but I didn't see a way to select the same sat 2, 3 or 4 times, and again, unless I'm missing something, I need each sat to be defined multiple times in order to get both C and Ku and Hor and Ver of each.
   That site looks like it could help trim the list down to only the sats I can see, but I'd still have to manually edit the list by creating multiple copies of each sat.
    Hope I'm wrong
wejones

Avatar / Picture

Registered:
Posts: 5,751
Reply with quote  #5 

Quote:
Originally Posted by Hockeynut
.......

Now this is what I do with what I described on all E2 receivers is for port 1 I label all sats as lnb1 as it is a moving dish so the same lnb,port etc never change and then for the fixed dish tied into the same multiswitch I call it lnb 11...Same thing for port 2 of the Diseqc switch.I label lnb 2 for the octagon as it has same lnb`s and for the other fixed dish coming into this same multiswitch I label that as lnb 12..

and so on and forth.It keeps things simple this way.You get the idea...It was nuts when the farm was much larger.No regrets simplifying.Hope this helps.


Well, now I'm confused again.  This is what I thought you were saying in previous messages, and I THOUGHT it was working for a while, ie I think that I defined G-13-C-V (for NASA), Anik-F1r-C-V (for CTV), and G-19-C-V (for Azteca), all using the LNB-1 designation, each of which refer to diseqC-1.1 port 2 on my switch.  This SEEMED to work, and I was intending to use LNB-2 , referring to all sats using the C band Horizontal port 1 on my switch.  On those 3 sats, I didn't yet configure horizontal or Ku band.
   However then I went on to SES2, where I wanted to receive LPB on Ku-H, and CNN on Ku-v, and Luken on C-band-V, in case AP is ever fta, C-band-H.   So I saved LPB using LNB-3 and switch port 3, and defined the horizontal C-band side using LNB-2, switch port 1, and then went to configure C-band-V again using LNB-1, switch port 2 like I had done on G-13, F1r, and G-19. And at that point, everything went berserk.  The sat lists on all the C-band sats I had configured were now all grayed out, but I could still play LPB on Ku-H, and I could still receive AMC-21 which I had on a fixed dish assigned on LNB-5 with voltage switched polarity.  
   I thought that I had somehow made a mistake, perhaps using one of the LNB-configurations for two different switches, so I went through all the configurations to check, and after going through all of them, and re-saving them, I then lost AMC-21 ?!?!?. 
   So at that point, I then concluded (apparently wrong?) that I wasn't able to use the same LNB# on two different sats, even if they referred to the same diseqC switch position. So one by one, I went through and used a different LNB configuration for every satellite, which at this point had me up to LNB-11, even though I was only using 5 different ports on my 8 port switch. When I was all done doing that, then all the C-band sats were now working again, and I got all 4 configurations on SES-2 working, and AMC-21 was working on vertical, but for some unknown reason I lost the horizontal side of AMC-21 (grayed out).

    So now you're telling me that it should have worked the way I first tried it, ie only using LNB-1 thru 5, which will be MUCH easier to remember if nothing else. 
    Perhaps I will try to one by one, go back and change the C-band sats to LNB-1 and 2,  each time going back and checking that everything else works, etc.  

   But relative to WHY this all happened.....   I don't know, but I'm starting to think that in my first experimentation with the satellites.xml file on /share , I might have messed up the link to the file in /etc/tuxbox .   I'm going to go check the linked xml files to make sure that they are linked properly.

 Thanks.

EDIT: Just checked, and the links seem to be OK now.  It may be that previously I replaced the linked version with a non-linked version in /share, and then, after I learned that I should have edited the file in /etc/tuxbox, I then edited the version in tuxbox, which then wasn't linked to the version in /share.  However after rebooting the Octagon, I'm guessing that the file in /share was replaced with the linked version, however I had then lost the configurations I had previously done on the C-band vertical transponders, which kind of orphaned the channels I had scanned. 
    Anyway, this all seems to make sense to me now, and somehow the Octagon OS was smart enough to "fix" things after I edited the wrong file.  It will probably take me until tomorrow to get things back to where they were before I messed things up. 

wejones

Avatar / Picture

Registered:
Posts: 5,751
Reply with quote  #6 
This morning, I went back and changed the configurations of all the sat/band/pol combinations I had scanned to date so that all the LNB#s were the same as the port# on my diseqC-1.1 8 port switch, regardless of what sat.  Sure enough, this time it worked, just like hockeynut posted.
  So I guess that when it didn't work for me, it was due to my having edited the /share/satellites.xml file, which is actually normally a link to the /etc/tuxbox/satellites.xml file.  Ie I replaced a link with an actual file, so that when I later made changes to the proper file in /etc/tuxbox, the changes didn't show up in /share and /usr/share.  But after I rebooted the Octagon after later changes, my file in /share was apparently automatically replaced by a link to the /etc/tuxbox file.  So the Octagon fixed itself.  
    I'm pretty sure that if I had done something like that to my Azbox, that it would have corrupted the DVBS.dat file.

EDIT: BTW, in case anyone else tries to edit satellites.xml files via Windows Wordpad, as I did, when I eventually saved the file I had edited, I did a "save as", and chose the "Plain Text Document" option instead of in XML format. Saving this way results in a file essentially the same as the original format except that it has CR/LF instead of just LF in the original Linux file.  The Octagon isn't bothered by the extra CR.  Of course there are other text editor programs that can save in the LF format, but I used Wordpad since it is available on Windows.  Also, some other programs tried to be too smart and insert their own XML headers, while saving in plain text in Wordpad left the format as it was in the original except for the CR.

rempfer

Avatar / Picture

Registered:
Posts: 913
Reply with quote  #7 
Quote:
Originally Posted by wejones
    I'm pretty sure that if I had done something like that to my Azbox, that it would have corrupted the DVBS.dat file.
Then the AZBox to which you refer would NOT be a Me or MiniMe, correct?

I can imagine your modified satellites.xml file will be very desirable to some others of us here.  What range of satellites does it contain (I can "see" 55W to 177W at my location in western Washington).
wejones

Avatar / Picture

Registered:
Posts: 5,751
Reply with quote  #8 
Quote:
Originally Posted by rempfer
Then the AZBox to which you refer would NOT be a Me or MiniMe, correct?

I can imagine your modified satellites.xml file will be very desirable to some others of us here.  What range of satellites does it contain (I can "see" 55W to 177W at my location in western Washington).


Right, re not Me or MiniMe, I was referring to the Elite, Premium & plus.  It didn't take much to corrupt the sat databases on those. 

Re the satellites.xml file.  The one that came on my Octagon covered from -180 to +180. I've attached a copy which has been saved by Wordpad so it has CR/LF so it's easier to read with notepad.

I'm still having some problems with the edited files.  Seems like each time I add a new satellite, it changes something that then affects the ones previously saved, and it takes a bit of troubleshooting to find out what's been changed.  I'm not sure what's causing it.







 
Attached Files
txt satellites1.xml.txt (518.78 KB, 23 views)

rempfer

Avatar / Picture

Registered:
Posts: 913
Reply with quote  #9 
Thank you.  As you know, Wordpad and Notepad (which ship with Windows) both add the <CR>, which changes <LF> to <CR><LF>.  Sometimes Linux doesn't like carriage returns added to line feeds although it sounds like we may be getting away with it here.  

If you start to suspect the <CR>s as causing trouble, there's a very nice freeware alternative to Windows Notepad called Notepad++ which I've used for years.  It will preserve and display properly the formatting of text files (i.e. it won't add <CR>s to <LF>s).

Thank you for the satellites.xml file.  I have just ordered a 4-LNB setup from Rick and so the work you're doing (thanks!) with your Octagon should transport nicely over to my AZBox Me.

Much appreciated!

EDIT:

I just loaded the/your satellites.xml file in Notepad++, then used Notepad++'s replace function to remove all the <CR>s with no apparent damage to the file.  <Ctrl>-<H> will get you there and then a regular expression to replace \r with nothing will clean up the file.  Again, only useful if the <CR>s are causing problems.
majortom

Avatar / Picture

Registered:
Posts: 5,143
Reply with quote  #10 
another simple way of cleaning up files that someone created using a windows machine, is to use
the command line app 'dos2unix', or 'unix2dos' (to go back the other way).

__________________
Perfect 10 7.5' mesh Chapparal C/Ku Co-Rotor feed, Norsat 8115 CBAND, Norsat 4106A Ku Thomson Saginaw Actuator, Vbox positioner,
Home Brew Polarotor683 Servo circuit. Openbox S9, Prof7500, v4l-updatelee linux drivers installed.
ricardo's geo-orbit archive: https://web.archive.org/web/20071202191450/http://www.geo-orbit.org:80/sizepgs/tuningp2.html
AZCoder

Avatar / Picture

Registered:
Posts: 190
Reply with quote  #11 
If you want anther option, here is the URL for a free editor for windows that will allow you to save the file in PC(CR/LF), UNIX(LF), and MAC (CR)  formats. http://www.brixoft.net/prodinfo.asp?id=1

The attached satellites.xml file is the one I use in the AZBoxME.  It defines both H/V satellites for each satellite.  Four if the satellite has C/Ku.  I use a DSR-922 to drive my dish and this seems to keep things together by polarity and satellite.  I use OpenATV on the AZBoxME and it handles these definitions without any problems.  DreamBoxEdit also does not mind the multiple definitions either.

Jim

 
Attached Files
txt satellites_split_060117.xml.txt (195.43 KB, 26 views)


__________________
Laser 5500 10' mesh dish w/Chaparral CO-Rotor II.  C/Ku lnbs Norsat 3220/Norsat 1207HA.  Venture MA-810-24K 24" actuator. DSR 920, 2 DSR 922s with MapMaster Maps. AZBoxME, Wetek Play, Wetek Openelec, TBS-6902 using Win10, OTA TV antennas.

wejones

Avatar / Picture

Registered:
Posts: 5,751
Reply with quote  #12 
Quote:
Originally Posted by AZCoder
If you want anther option, here is the URL for a free editor for windows that will allow you to save the file in PC(CR/LF), UNIX(LF), and MAC (CR)  formats. http://www.brixoft.net/prodinfo.asp?id=1

The attached satellites.xml file is the one I use in the AZBoxME.  It defines both H/V satellites for each satellite.  Four if the satellite has C/Ku.  I use a DSR-922 to drive my dish and this seems to keep things together by polarity and satellite.  I use OpenATV on the AZBoxME and it handles these definitions without any problems.  DreamBoxEdit also does not mind the multiple definitions either.

Jim



Thanks for the url for editor.  I have a similar program somewhere, but couldn't find it because I didn't remember it's name.
Re your xml file, that looks to be pretty much the same thing I've been doing, except for the satellite longitudes at the end, ie which one uses the exact longitude. 
Thanks.

wejones

Avatar / Picture

Registered:
Posts: 5,751
Reply with quote  #13 
Quote:
Originally Posted by wejones

.......
I'm still having some problems with the edited files.  Seems like each time I add a new satellite, it changes something that then affects the ones previously saved, and it takes a bit of troubleshooting to find out what's been changed.  I'm not sure what's causing it.



I think I figured out what was causing problems.
I was doing pretty well editing the xml files, until I tried editing several sats in one session, and ended up with the Octagon giving me a message saying something like 'Database Corrupted, you can watch TV but you can't make any changes'  or something to that effect.  I
  It was easy to recover, but FTP'ing an older sucessful edit, but since I had edited several sats, I couldn't find the one which had the error.  Then, a bit later I ended up with that corrupted error again, so after recovering again, I decided to look more in detail at what I had done wrong. 

 I'm pretty sure now that what I had done, was to be careless when editing the name of the satellite.  For example some examples of the sat definition lines:  {text in brackets are my comments}
Code:

<sat name="133.0W C-band Galaxy 15" flags="0" position="-1331">

<sat name="127.0W C-band Galaxy 13/Horizons 1" flags="0" position="-1271">
<sat name="127.0W Ku-band Galaxy 13/Horizons 1" flags="0" position="-1270">
            {C and Ku beams on same sat}

<sat name="125.0W C-band AMC 21 &amp; Galaxy 14" flags="0" position="-1251">
<sat name="125.0W Ku-band AMC 21 &amp; Galaxy 14" flags="0" position="-1250">
            {C and Ku beams on separate satellites}

<sat name="119.0W C-band Anik F3 &amp; EchoStar 14 &amp; DirecTV 7S" flags="0" position="-1191">
<sat name="119.0W Ku-band Anik F3 &amp; EchoStar 14 &amp; DirecTV 7S" flags="0" position="-1190">
            {C and Ku on same sat and DBS-Ku beams on separate satellites}

<sat name="103.0W C-band Spaceway 1 &amp; DirecTV 10/12 &amp; SES 3" flags="0" position="-1031">
<sat name="103.0W Ku-band Spaceway 1 &amp; DirecTV 10/12 &amp; SES 3" flags="0" position="-1030">
            {C and Ku on same sat and DBS-Ku beams on separate satellites  }
<sat name="99.2W C-band Galaxy 16 &amp; Spaceway 2 &amp; DirecTV 11" flags="0" position="-993">
<sat name="99.2W Ku-band Galaxy 16 &amp; Spaceway 2 &amp; DirecTV 11" flags="0" position="-992">
            {C and Ku on same sat and DBS-Ku beams on separate satellites  }


I think that where I went wrong, was on examples like the last 3, which have the string "&amp;" in them.  I didn't have a clue what that string meant, but after some googling, I found that there are apparently some characters that have special meaning in XML documents, even when in text, and the ampersand is one of them.  Apparently the "&" is used when you want to use these characters in text, and what you do is use the & followed by the name of the special character, terminated by a semicolon.  So the "&amp;" actually just refers to & used in the text string (seems like it would have been easier to just type "and").  Ie "amp" is the name for ampersand, and the semicolon terminates the name. 
    Well, what I had done was to delete some of the unwanted sats in the name, but was careless about leaving the & or the semicolon, and this apparently messed up the XML reader in the Octagon by leaving a stray semicolon, which is apparently also considered as a special character. After I cleaned up the string for the sat names, so as not to have stray special characters, everything was OK. 
  Anyway, just wanted to warn anyone trying to edit these things by hand to be careful to avoid special characters.

On another topic, if you notice, the last item in the line is the sat position, and apparently that needs to be different for each sat definition.  In most cases, if it's a C/Ku sat, the Ku sat was given the actual longitude, and the C-band sat definition was given a position 1 tenth higher.  For example AMC-21 gets -1250 while G-14 gets 1251.  I assume this is in case USALS is being used to run a H-H motor, the Ku sat needs to be more accurate than the C-band sat.  I'm not going to use USALS, but in my case where I needed 4 sats, I used  something like 1249,1250,1251,1252 so that the numbers aren't too far from the actual 125.
   I found it odd that in the last example, ie Galaxy-16. the sat positions were 992 and 993, even though the actual position was 99.0.  I'm guessing that they took their data base from a list that listed the Ka sat at that position, which would need even more accuracy, but they deleted that, leaving the C-band position even further from the actual position, and in my case, needing 4 definitions, I would have had numbers like 994 or 995. So I moved everything down a couple tenths.




HDorBust

Avatar / Picture

Registered:
Posts: 203
Reply with quote  #14 
There are XML parsers on the Internet that will check the syntax.

If I get a chance, I may modify my own version of mstounix to include XML special character handling (mstoxml) and post it.


__________________
Receivers: Octagon SF4008 4K, Vu+ Solo 4K / LinkBox 9000i / Manhattan RS-1933 / Manhattan DJ-1997 / AZBox Premium HD+ / Pansat TC-1000HD
Dish H/W: 10 foot mesh (KTI) / 24" Venture Ball Screw 819B24CK / Chap Bullseye II  / Norsat 8115/8515 & 4106/4506A / GBOX
Old: Chap Corotor II+ / APC
rempfer

Avatar / Picture

Registered:
Posts: 913
Reply with quote  #15 
Quote:
Originally Posted by AZCoder
The attached satellites.xml file is the one I use in the AZBoxME.

Jim, thanks for the file.  I've just loaded it into my Me and am scanning in channels with my DiSEqC ports 1 thru 4 (C-H, C-V, Ku-H, Ku-V) set-up.  Beautiful job you've done on this!

Much appreciated,

Dick
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Fellow Members, your posts are welcome here! Do not worry about posting everything perfect. Different receivers and LNB's will give you different Frequencies and Symbol Rates. Some set top boxes, PCI cards and USB receivers, Do Not Require all of the same information that others may need. It is not Required to post everything that others may need to tune in a feed. It is just most important to share the find. We can always adjust the Frequency and Symbol Rates and try the various Modulations and FEC's on our own receivers until we get a lock and then give a polite reply with what works for your receiver, as that information might help others as well. We all appreciate the efforts and energy of the Posters!

Thank You for Visiting GOFASTMOTORSPORTS.com - Keep Your Eyes on the Sky and the Track!