yavdr(0.2) rotor plugin

  • Yep - my rotor.conf is as follows:


    Code
    S5.0E = 2
    S7.0E = 3
    S9.0E = 4
    S10.0E = 5
    S13.0E = 6
    S16.0E = 7
    S19.2E = 8
    S23.5E = 9
    S1.0W = 1


    My diseqc.conf (which is for a 4-way diseqc switch with my rotor on the first port)



    I'm not sure how you should adapt that if you are just directly connected to your rotor.

  • Zitat

    Originally posted by Wilb
    I'm not sure how you should adapt that if you are just directly connected to your rotor.


    Thx 4 posting. If anyone has an example on how it should look when the rotor is directly connected i would appriciate it :)


    Can you directly select the desired position in the rotor menu ?


    Greetings,
    MrNike

    Hardware: Zotac ION F, Cine S2 V5.4 DVB-S2, 1.5TB HD, 2 GB Ram
    Software: Ubuntu Precise
    64bit, yavdr:vdr-unstable ppa, xbmc
    www.coinflip.de

  • Yes - it is still only showing a position number, no description of the satellite like in previous versions so not quite as functional - but it works so that is the main thing!


    Maybe you don't actually need a diseqc.conf at all for a single rotor - or if it insists on having something configured then try modifying mine anyway. S28.2E is the one which is connected to port 2 so just ignore that.

  • thank to Wild


    at least the rotor is operating well now. now we need to look for a way to display the satellite name instead of the position.

    yaVDR 0.5/softhddevice, Asus P5N7A-VM, DDBridge + 2x DuoFlex C/T

  • Zitat

    Originally posted by marabout
    thank to Wild


    at least the rotor is operating well now. now we need to look for a way to display the satellite name instead of the position.


    I stell dont have working rotor.
    I have rotor conected direcly to my pc card.


    Can you send me your diseqc.conf if you have the same setup at your home?

  • this is all I have in my diseqc.conf


    Code
    S19.2E  11700 V  9750  t v
    S19.2E  99999 V 10600  t v
    S19.2E  11700 H  9750  t V
    S19.2E  99999 H 10600  t V


    and rotor 0.1.4 mh 1.2 is working for all positions. I had problems with original rotor 0.1.5 and vdr 1.7.15, but this version is working fine (if you use goto position and not gotox).
    you have to create rotor.conf in plugins rootfolder yourself.

  • I found the bug :D
    Reason is that enum Values of eSourceType have changed


    Code
    Line 95 in rotor.c:
    -    if ((source->Code() & 0xC000) != 0x8000)
    +         if (!cSource::IsSat(source->Code()))


    and you will get all Satellite Names in Rotor Plugin again. Perhaps also GotoX could work again.

  • this should be enough to reactivate GotoX:

    Code
    Line 93 in diseqc.c:
    -    if ((Source & 0xC000) != 0x8000))
    +         if (!cSource::IsSat(Source)


    still untested and I will take no responsibility.

  • Zitat

    Originally posted by newsy
    here's the patch I promised providing GotoX and satnames support again.


    First gotox patch was not enough because rotor positions were stored differently (1 bit for pos/neg, 10 bit for position, now it's a signed 2 byte number)


    Thanks mate ... working again on my vdr (yavdr rep: vdr-testing) with ubuntu 10.04. I downloaded the sources and patched the plugin. Then compiled a new .deb, istalled it and the plugin is working perfectly again :)


    If anyone need the .deb file for ubuntu lucid 64bit i can post it here.


    Greetings,
    MrNike

    Hardware: Zotac ION F, Cine S2 V5.4 DVB-S2, 1.5TB HD, 2 GB Ram
    Software: Ubuntu Precise
    64bit, yavdr:vdr-unstable ppa, xbmc
    www.coinflip.de

  • Zitat

    Originally posted by newsy
    here's the patch I promised providing GotoX and satnames support again.


    First gotox patch was not enough because rotor positions were stored differently (1 bit for pos/neg, 10 bit for position, now it's a signed 2 byte number)


    how to build that rotor plugin for yavdr to be in .deb format and do i need to patch vdr with gotox patch?

  • Zitat

    Originally posted by Lazocar
    how to build that rotor plugin for yavdr to be in .deb format and do i need to patch vdr with gotox patch?


    With Ubuntu 10.04 64bit:
    1) get sources: 'apt-get sources vdr-plugin-rotor'
    2) change to sources dir, copy patch to that dir (/var/lib/vdr/vdr-plugin-rotor-0.1.5/)
    3) patch sources: 'patch -p1 -i rotor-0.1.4mh-v1.2_satnames_gotox.diff'
    4) compile sources: 'dpkg-buildpackage -rfakeroot -us -uc -b'
    5) install deb: 'dpkg -i ../vdr-plugin-rotor_0.1.5-15yavdr1_amd64.deb'


    Be sure to use the right filenames depending on your system.


    Only problem i have is that is that when i start 'apt-get upgrade' the system wants to install the remore remote plugin from the ppa. Needed to ignore my that version.


    Cheers,
    MrNike

    Hardware: Zotac ION F, Cine S2 V5.4 DVB-S2, 1.5TB HD, 2 GB Ram
    Software: Ubuntu Precise
    64bit, yavdr:vdr-unstable ppa, xbmc
    www.coinflip.de


  • Thanks MrNike for detail of building package and i have sucesfuly build 0.1.5 and 0.1.4 rotor plugin and as i see it thay bouth have name of satelite besides position numbers.
    My problem remains the same the rotor dish dont move.
    I't youstu move with yavdr 0.1.1 and vdr 1.7.10 but now when i tray tu install yavdr 0.1.1 and rotor plugin it wont move i start to thing it is something with my rotor dish.
    Does anywhone know some rotor program for linux that i can test my motor insted of instaling windows(i hate windows and always loking for the drivers :P)


    Thanks!

  • I finally figure out what was my problem with rotor not moving so tu share with you all.
    Thank you Wilb for kaffeine it's a nice program however it didnt work with it so i decide to put the windows xp and altdvb a try.
    Sadly the motor didnt work with it so it isnt the vdr problem it is the rotors.
    I did manage to set the rotor moving by making the "hardware reset".


    Now the motor is working fine in windows and it is moving in vdr however when i try to do anything with rotor plugin it just crash vdr and restart it again.


    Does somebody have crashing vdr with rotor plugin and is it posible to vdr send raw diseqc commands to rotor and how??

  • Zitat

    Originally posted by Lazocar
    Does somebody have crashing vdr with rotor plugin and is it posible to vdr send raw diseqc commands to rotor and how??


    Zitat

    Nov 3 17:23:05 Isomaniac kernel: [ 1578.308165] Rotor-Plugin[4429]: segfault at 10 ip 00007f5acf850ad9 sp 00007f5aa87ef820 error 4 in libfribidi.so.0.3.1[7f5acf84d000+15000]


    Also having some trouble since yavdr-testing updated to 1.7.16. With 1.7.15 everything worked nice. Now it crashes when i try to select another satellite.


    Greetings,
    MrNike

    Hardware: Zotac ION F, Cine S2 V5.4 DVB-S2, 1.5TB HD, 2 GB Ram
    Software: Ubuntu Precise
    64bit, yavdr:vdr-unstable ppa, xbmc
    www.coinflip.de

  • here is my output from /var/log/syslog


    Code
    kernel: [  123.859375] Rotor-Plugin[1986]: segfault at 8 ip 0036ae91 sp a7ad8df0 error 4 in libfribidi.so.0.3.1[369000+14000]


    any help with this or just give us old repository with vdr 1.7.15

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!