Excellent news! I am sure the entire rotor vdr community will be very glad to hear that!
At the moment I use diseqc.conf with goto position commands for each sat position to move the dish With rotor-ng does diseqc use have to be switched off in vdr and the plugin takes care of everything or does it parse diseqc.conf?
Message: 1 Date: Mon, 21 Mar 2011 23:15:11 +0000 From: Morfstamorfsta@gmail.com Subject: Re: [vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin] To: VDR Mailing Listvdr@linuxtv.org Message-ID: AANLkTimUPe+jotg9J9V3pN5QG4iOJVG9_v8-m0Zest7h@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1
On Sun, Mar 20, 2011 at 10:08 PM, Timothy D. Lenztlenz@vorgon.com wrote:
I only have a Nexus-s for sat card and right now my rotor alignment is all screwed up. Relays went bad and had to replace them. I left the rotor elevation setting untouched but now it over shoots more and more the farther it goes as if the elevation is wrong. Haven't had time to look into it.
Well, it seems I found the problem. The HAUPPAUGE NOVA-S2-HD card (HVR4000 lite / CX24116 frontend) won't lock onto DVB-S2 channels with FEC_AUTO or ROLLOFF_AUTO set. So, I modified the plugin to allow selectable values for FEC and ROLLOFF and now it works fine. I can now lock and scan DVB-S and DVB-S2 channels (QPSK and 8PSK) directly from the plugin menu and move the dish to find and store satellites with diseqc and signal strength meter. Ideal for feedhunting now!
When I get a bit more time I'll tidy up the plugin and release it as it should now act as a pretty good satellite channel scanner irrespective of whether you have a rotor within VDR. I haven't tested the entire satellite transponder scanning functionality yet for DVB-S/S2, that will be the next task but hopefully it won't need many changes.
On Tue, Mar 22, 2011 at 12:05 PM, Arturo Martinez martinez@embl.de wrote:
Excellent news! I am sure the entire rotor vdr community will be very glad to hear that! At the moment I use diseqc.conf with goto position commands for each sat position to move the dish With rotor-ng does diseqc use have to be switched off in vdr and the plugin takes care of everything or does it parse diseqc.conf?
VDR Diseqc settings are off in my configuration.
Similarly to the rotor and actuator plugins there is a file in the plugin directory that stores the disecq postion number for every satellite: -
S3.0E 31 S4.0E 30 S4.8E 15 S7.0E 14 S9.0E 29 S10.0E 13 S13.0E 12 S16.0E 11 S19.2E 10
At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface.
I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called "Dish" or something similar.
Still left to do: -
1) Remove or fix some actuator specific interface buttons that are not too relevant or don't work 2) Fix enabling and clearing of limits as this doesn't work with my VBOX, I can't clear the limits via the plugin once they are set 3) Look at "recalc" and see how that can be implemented within rotor-ng 4) Remove old unused code that is related to actuator use 5) Update documentation etc 6) Find somewhere to host it - vdrprojects? 7) Implement GOTOX (though I don't use it so not sure how it would be tested. Might need a volunteer to do this by looking at the GOTOX patches for rotor and implementing them on rotor-ng).
Thanks
On Tue, Mar 22, 2011 at 5:41 AM, Morfsta morfsta@gmail.com wrote:
At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface.
I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called "Dish" or something similar.
I don't use a actuator/rotor myself but I know people who do and are really looking forward to your plugin. I think a good stable 'vdr-movedish' plugin has been needed for quite some time. It almost seems like a plugin you'd expect to come with vanilla VDR since it provides such a basic function.
Anyways, thanks for your work.
maybe once it's cleaned up and fully functional, in can be intigrated with vdr.
On 3/22/2011 8:49 AM, VDR User wrote:
On Tue, Mar 22, 2011 at 5:41 AM, Morfstamorfsta@gmail.com wrote:
At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface.
I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called "Dish" or something similar.
I don't use a actuator/rotor myself but I know people who do and are really looking forward to your plugin. I think a good stable 'vdr-movedish' plugin has been needed for quite some time. It almost seems like a plugin you'd expect to come with vanilla VDR since it provides such a basic function.
Anyways, thanks for your work.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
I get smoe of the terms confused. gotox is where you tell it the sat postion such as 97w and it goes there as vs telling it to go to a stored location? If that is the case, then gotox is needed as a way to get the rotor to a location.
Also, VDR Diseqc should be on to use rotor as well as switches. I use both rotor and switches.
On 3/22/2011 5:41 AM, Morfsta wrote:
On Tue, Mar 22, 2011 at 12:05 PM, Arturo Martinezmartinez@embl.de wrote:
Excellent news! I am sure the entire rotor vdr community will be very glad to hear that! At the moment I use diseqc.conf with goto position commands for each sat position to move the dish With rotor-ng does diseqc use have to be switched off in vdr and the plugin takes care of everything or does it parse diseqc.conf?
VDR Diseqc settings are off in my configuration.
Similarly to the rotor and actuator plugins there is a file in the plugin directory that stores the disecq postion number for every satellite: -
S3.0E 31 S4.0E 30 S4.8E 15 S7.0E 14 S9.0E 29 S10.0E 13 S13.0E 12 S16.0E 11 S19.2E 10
At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface.
I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called "Dish" or something similar.
Still left to do: -
- Remove or fix some actuator specific interface buttons that are not
too relevant or don't work 2) Fix enabling and clearing of limits as this doesn't work with my VBOX, I can't clear the limits via the plugin once they are set 3) Look at "recalc" and see how that can be implemented within rotor-ng 4) Remove old unused code that is related to actuator use 5) Update documentation etc 6) Find somewhere to host it - vdrprojects? 7) Implement GOTOX (though I don't use it so not sure how it would be tested. Might need a volunteer to do this by looking at the GOTOX patches for rotor and implementing them on rotor-ng).
Thanks
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-
Arturo Martinez -
Morfsta -
Timothy D. Lenz -
VDR User