Simeon Simeonov wrote:
> Hi Manu,
> 
> I am attaching two gzipped logs. They are supposed to tune to the same 
> frequency using the tip
> of Mantis tree. The difference between the two are that in the GOOD log no 
> repeat command is used
> and in the BAD log one repeat for the switch is issued. The initial position 
> of my rotor is about 20 deg
> east from the target rotor position. 
> Using the tunning without the repeats the rotor goes all the way through and 
> tunes successfully - GOOD log.
> When repeat command is included in the diseqc sequence the rotor goes about 
> 10 degrees to the west and stops as if it has reached the desired position.  
> The BAD log corresponds to that.
> When I tried to move to any other rotor stored position I find that that all 
> of the memorized in the rotor positions are shifted. My guess is that for 
> some reason the rotor stops, stores current position as the target one and 
> then
> re-calculates all of them. But I do not see anything like that in the log 
> file. The only thing I see is that
> after the third byte  in the  diseqc  repeat command fifo  get  full  and  
> sending  the  next  byte  has  to
> wait for one cycle.
> The  same  sequences  work  just  fine  with  my  102g  card  and the v4l 
> drivers.

Can you please try to get the DiSEqC strings that you are sending
(from the application) in these 2 cases ?

* Without repeat
* With repeat

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Reply via email to