Satellite rotor/motor configuration

  • Hi,


    I'm completely new to VDR, I'm about to move to OpenElec and would like to use VDR for LiveTV with my DVB-S2 card. I have a USALS rotor on my dish, and I see that VDR has motor support. I'm very much confused how to configure multiple satellites and providers, I hope you could help we with this. I see that German language support is so much better but my German is very rusty, I hope somebody can help me here in English section of the forum.


    Basically, I would need the following:


    0.8W Thor: UPC Direct, Digi (RCS)
    16E Eutelsat: MaxTV
    28.2E: SkyUK
    39E: Polaris Media


    Can you please help me with this, how can I configure VDR for these satellites and providers?


    Many thanks!

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380

  • Welcome to VDR portal!


    USALS is a special and new topic (new means new feature in VDR 2.1.x codeline) so I guess only people who have that setup running themselves are able to answer your question. Until they turn up in this thread please read the following ressources:


    http://linuxtv.org/pipermail/vdr/2013-August/027909.html
    DVBSky S960 VDR 2.1.2 USALS und DiSEqC Motor (especially this posting: DVBSky S960 VDR 2.1.2 USALS und DiSEqC Motor)
    And this posting: Grundlagen und Winkelberechnungen für H-H DiSEqC Motor Antennenanlagen


    Regards,
    hepi

  • Hi Hepi,


    thank you for your answer!
    I don't mind if I do not use USALS (DiSEqC 1.3), I'm completely fine with manually storing each position (DiSEqC 1.2 if I'm correct) for these satellite positions. I can use my STB to tune on the satellite and then store the position in the motor for each sat. I believe this should also work, and perhaps this is available already in stable VDR releases?
    AFAIK, the rotor support is already integrated into VDR and not available as a separate plugin.


    I would like to ask for some help on this, since I do not understand exactly how to configure this. I see rotor.conf file and perhaps other conf files, but based on the satellites and providers I need, I hope someone can give me a hint how to configure this?


    Your help is very much appreciated! I'm afraid my German language skills are very novice, and this is quite an advanced theme, so Google Translate is not enough.


    Many thanks!

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380

  • With the fake "position" S360E available in the VDR developer version 2.1.x it IMHO seems to be very simple to setup the disecq.conf. If you want to add channels from any new satellite positions to your channels.conf, you never have to touch the diseqc.conf again. This approach seems to be less error prone because it involves less maintainance work.

  • Thanks again!
    Well, what I need is a stable and reliable LivetTV. If latest dev version is that, I'm more then fine with it.
    However, I will use OpenElec, therefore I will be limited to the version available for OE Plugin repository. I think it is this:


    https://github.com/OpenELEC/Op…vice/multimedia/vdr-addon


    From this you will see which is the latest version of VDR used in OE.


    Anyway, I see the links you sent me, but at this stage, I even have problems how to scan for a single provider (let's say RCS Digi on 0,8W) that is, to create a channel list.
    An example for both channel list and diseqc.conf would be great, where I can see configured for the same usage as I need.


    Sorry for being so n00b.

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380

  • In yaVDR Channelpedia you can find VDR channel lists for different DVB sources. You can find channels for S28.2E in there, ready to use. (As I am the maintainer of Channelpedia, the channels for S28.2E are directly from my own VDR and are being used on a daily basis - but only FTA channels): http://channelpedia.yavdr.com/gen/DVB-S/S28.2E/


    You can copy channels from there into your channels.conf file (while VDR core is not running).


    The content of the diseqc.conf totally depends on what you want. The link in posting #4 contains a number of examples. The VDR wiki also contains some good examples for classic diseqc usage.


    It seems you still have a long way to go until you have a VDR up and running anyway? Do you already have the VDR hardware?


    Cheers,
    hepi

  • I'm doing some research, and if I got this properly, here is what I understand so far.


    I have two satellites stored in my rotor's memory.


    0,8W position 1.
    16E position 2.


    For diseqc.conf I should use the following entry:


    S360E 11700 V 9750 t V W20 P1 W20 t v
    S360E 99999 V 10600 t V W20 P1 W20 T v
    S360E 11700 H 9750 t V W20 P1 W20 t V
    S360E 99999 H 10600 t V W20 P1 W20 T V
    S360E 11700 V 9750 t V W20 P2 W20 t v
    S360E 99999 V 10600 t V W20 P2 W20 T v
    S360E 11700 H 9750 t V W20 P2 W20 t V
    S360E 99999 H 10600 t V W20 P2 W20 T V


    But how do I link the channels in channels.conf to the correct positions?

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380


  • It seems you still have a long way to go until you have a VDR up and running anyway? Do you already have the VDR hardware?


    Yes, I'm still at the beginning of my VDR project. I'm now on Win7+MediaPortal and basically everything is working perfectly on my HTPC but I just don't like Windows, so I would prefer to move to OpenElec and VDR for stable and reliable LiveTV support. But I need to understand these things first before I get into it, as it is essential for me to have this working (not to mention my wife:)).
    Your help is very much appreciated, I hope you could help me with the exact setup I need...

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380

  • There is a misunderstanding, it is simpler.


    If you decide to use VDR 2.1.x, than your diseqc.conf would only contain four lines:


    Code
    1. S360E 11700 V 9750 t V W20 P W20 t v
    2. S360E 99999 V 10600 t V W20 P W20 T v
    3. S360E 11700 H 9750 t V W20 P W20 t V
    4. S360E 99999 H 10600 t V W20 P W20 T V


    This would never change, no matter how many satellite positions you want to focus on. VDR obtains the position information from a parameter in the channel information from the channels.conf.


    Prerequisite is that you have a dish on the top of your roof so that it is free to circle by 360 degrees without hitting any walls of your house.


    Cheers,
    hepi

  • OK, then I have my diseqc.conf file.
    Well, the dish can not rotate 360 degrees, but it can 180. Anyway, I just need satellites from 0,8W up to 38E, so these are completely fine for the dish.


    About channels.conf. Here is a line for 28,2E:


    BBC One HD;BSkyB:10847:VC23M5O25P0S1:S28.2E:23000:5400=27:5402=NAR@3;5401=eng@106:5403;5404=eng:0:6941:2:2050:0


    I see that section S28.2E refers to the satellite. But where do I add my rotor positions for each satellite?

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380

  • If you want to use the rotor positions you have saved to your rotors memory, you have to do a different approach.


    The approach we just discussed doesn't need to know anything about the positions stored in your rotors memory. VDR just tells the rotor what to do via GotoX/GotoN.


    Cheers,
    hepi

  • If you want to use the rotor positions you have saved to your rotors memory, you have to do a different approach.


    The approach we just discussed doesn't need to know anything about the positions stored in your rotors memory. VDR just tells the rotor what to do via GotoX/GotoN.


    Cheers,
    hepi

    I don't mind GotoX/GotoN, as I said, it really doesn't matter to me which approach is used, what matters that it is working!


    Sorry for this, but if I use the diseqc.conf file you posted and the channels.conf, how will VDR know where to tune which channel? I think I have to add my longitude and latitude positions somewhere? Or how? What I'm missing here?

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380

  • http://en.wikipedia.org/wiki/U…Automatic_Location_System


    Yes, you need to add your long/lat data in the setup.conf of VDR.


    I already posted the link to http://linuxtv.org/pipermail/vdr/2013-August/027909.html


    where it says:


    Quote

    + The new parameters "Site latitude", "Site longitude", "Positioner speed", and
    "Positioner swing" in the "Setup/LNB" menu can be used to configure the necessary
    values for a steerable dish.


    Cheers,
    hepi

  • Hi.


    I do myself use rotor but I am using USALS, with long/lad position. It is easiest way how to use rotor, and with this VDR is working just find with SAT position you mentioned in first post, as I look them myself.


    Regards,

    The post was edited 1 time, last by crow ().

  • Remark: As I personally have never used a rotor myself my usage of the terms USALS/GotoX/GotoN/etc. might not be 100% correct. Still, the approach with four lines of S360E seems to be very clever to me, so whatever standard of the mentioned ones is compatible with the S360E approach is recommended by me. :D

  • OK, I will try USALS and see how it works.
    I still need to find out if the VDR version with OpenElec latest has USALS support or not. Perhaps you can check the link I have posted and you can tell me by the version number.
    Thanks for all your help guys, it is a great community, glad to be part of it!

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380

  • the link I have posted


    One look at the changelog file would reveal:


    4.1.6
    - update to vdr-2.1.6


    so yes you will have rotor support included in that version


    Br,
    Joe

  • Quote

    Thank you! I was confused with versions from OpenElecand other sources,
    but glad to hear that VDR 2.1.6 has USALS rotor support already!

    Server: Atom 330, 2GB RAM, 2x2TB HD, 160GB 2.5" system drive, DVBSky S960 USB DVB-S2, picoPSU 120W, Ubuntu Server Trusty, VDR 2.2.0 + Live, streamdev, epgfixer, epgsearch, restfulapi, vnsi-server
    HTPC1: ASRock 330 ION, 2GB RAM, 32GB 1,8" SSD, Chieftec IX-03B + picoPSU 90W, Kaze Slim 100mm cooler, OE 5.95.4 DualAudio Build + VDR vnsi-client
    Clients: notebook, netbook, desktop, Pi2, WP
    Harmony 515 Remote, Panasonic 42" Plasma, Sony STR-DE 585 5.1 DTS, 78 Triax + Inverto Black LNB + Powertech S380