Digger Posted April 7, 2005 Posted April 7, 2005 (edited) Diseqc1.2 is the one thing I miss with DVBViewer. OK I know there is a problem that the Technisat drivers do not accept Diseqc2 commands, and maybe the relationship with Technisat makes it difficult to use the pached versions that are out there because of DvbViewerTE. So this is probably as much a Technisat problem as a DVBViewer problem. I can say that with Diseqc2, DVBViewer would be the only SkyStar2 program on my PC. Have I missed something here? Edit for 1.2!!!!! Edited April 7, 2005 by Digger Quote
Derrick Posted April 7, 2005 Posted April 7, 2005 >Have I missed something here? ..yes you have (it could be a simple 1 -> diseqc 1.2) diseqc 2.x is not possible. It's not a software but a hardware question. 2.x allows 2way communication but there is no receiver for this on the card. Quote
Digger Posted April 7, 2005 Author Posted April 7, 2005 Yes you're right 1.2, with the ability to send lots of satellite positions to a disecq positioner ~50 satellites. Quote
Derrick Posted April 7, 2005 Posted April 7, 2005 this feature won't be supported by the DVBViewer. The current for the motor could fry your card Quote
Digger Posted April 7, 2005 Author Posted April 7, 2005 AFAIK there is no extra current in Disecq 1.2 compared to Disecq 1.0, it's simply a different message format. I've had 1.2 working happily with ProgDVB, MyTheatre and DVBDream but would infinitely prefer to use DVBViewer. What's actually needed is for the viewer program to send the right disecq 1.2 command for each satellite based on a table that defines a value of 0-99 for each sat. It's up to the positioner to interpret the code and work the motor, not the viewer program. or the sat card. The unfortunate thing is that the Technisat drivers block anything but Disecq 1.0 commands but there are patched versions to get around this. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.