Bug #2548
closed
Usals don't work properly anymore
Added by Richard Bolster over 10 years ago.
Updated over 10 years ago.
Found in version:
3.9.2218
Description
My system Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-40-generic x86_64) and 1 TBS 6922SE (rotor) and 1 TBS 6981 (fixed dish) has now problem that usals don't work anymore. I use version 3.9.2218 from repositories. In version 3.9.2178 everything seemed to be working fine, except some tuning problems (stays in testing status quite often at only rotor (not fixed dish). Disappears after new mux scan).
Did a --trace linuxdvb,diseqc with version 3.9.2218 and with 3.9.1567. Result added in logfiles.
In v1567 rotor movement is working fine. What I noticed:
1567
sirius 4.8E failed
-9.07
hotbird 13.0E scan completed
-25.72
astra 28.2E scan completed
-0,06
sirius 4.8E scan completed
2218
sirius 4.8E failed
-4.65
astra 28.2E failed
already positioned to 4.8E !!
sirius 4.8E failed
0.67
hotbird 13.0E failed
-4.65
astra 28.2E failed
searching through the file on "clockwise" give different positioning results?!
what else could I output? Apologize because I am quite new in this :-)
With regards, richard
Files
Please, could you log directly to a file (do not use syslog) - use --logfile (or short -l) option.. I think that some lines are missing..
I used the following command: sudo tvheadend --trace linuxdvb,diseqc --logfile /home/richard/tvh_logfiles/tvh_2218.log
Which lines suppose to be missing?
These logs are maybe more sequential. Both started with dish pointed at sirius 4.8E and mux scan are successful. Next mux scan at hotbird 13.0E shows at v1567 -9.07 clockwise and at v2218 0.67 counter clockwise.
These logs are fine. Random lines were missing (I think that syslog filtered them).
Could you try latest v3.9-2232-g39d985b and upload the log for it, too ? You may give the look to the USALS input values.
Tried v3.9.2232 unsuccessfully. In logfile can see that site latitude and longitude are printed now. Can see the difference in usals "input values" as "waiting time to finish usals".
Started with dish pointed already at 4.8E so first scan was successful.
Does these values match your settings in webui ?
rotor USALS site lat 52.9500N site lon 4.7500E sat lon 4.8E zero 0.0W
Jaroslav Kysela wrote:
Does these values match your settings in webui ?
[...]
Yes they do match Jaroslav, but in webgui only with two decimal digits.
Could you try the latestv3.9-2234-gad16b3d ? I changed the USALS formula to be similar like in Enigma2.
Tried v3.9.2234 but not working. Actually have to reset the motor as it reached its hardware limits, hopefully it's broken because I never reached that position. It's still dark outside so can't reset it/move it manually.
Don't bother part of the game and shouldn't do it at midnight ;-)
Added the logfiles and you will see exceptional rotation.
Certain advanced settings I don't understand as I haven't seen them in any box before: checkbox "longitude direction west" and "altitude (meters)"
Azimuth is shown correct:
- diseqc: rotor angle azimuth 179.9373 elevation 29.5445
- diseqc: rotor USALS goto 4.8E (motor 179.0 counter-clockwise)
- diseqc: rotor angle azimuth 169.6971 elevation 29.0625
- diseqc: rotor USALS goto 13.0E (motor 89.0 counter-clockwise)
- diseqc: rotor angle azimuth 151.4598 elevation 25.7864
- diseqc: rotor USALS goto 28.2E (motor 77.0 clockwise)
- diseqc: rotor angle azimuth 151.4598 elevation 25.7864
- diseqc: rotor USALS goto 28.2E (motor 77.0 clockwise)
- diseqc: rotor angle azimuth 179.9373 elevation 29.5445
- diseqc: rotor USALS goto 4.8E (motor 179.0 counter-clockwise)
From my site Sirius 4.8E is actually 0 at the rotor (dishpointer.com motorized SG2100)
Forgot to add that in log from v3.9.1567 this went correct with:
- diseqc: rotor USALS goto 4.8E (motor -0.06 clockwise)
- diseqc: rotor USALS goto 13.0E (motor -9.07 clockwise)
- diseqc: rotor USALS goto 28.2E (motor -25.72 clockwise)
- diseqc: rotor USALS goto 4.8E (motor -0.06 clockwise)
Rotor still alive. Managed to scan and watch everything again with v3.9.1567.
Can still test :-)
Oops. Sorry. Forgot some old code. Could you try v3.9-2237-g388f57e ?
Am impressed, you fixed it Jaroslav :-)
Thank you very much!!
First times it gave at Sirius 4.8E - scan no data, failed. That was because the dish was probably pointed at Hotbird 13.0. When I started a scan at Hotbird 13.0 it went well and after it all others.
Also could tune with vlc to different channels on different satellites. Will test this later on because somehow I could not watch BVN at Hotbird though it had a lock. Next try with xbmc/kodi client.
I don't know why the first movement fails. There is 10 seconds delay after rotor USALS goto 4.8E (motor 0.1 clockwise). The 10 seconds value is your "Max Rotor Movement (seconds)" settings.
- Status changed from New to Fixed
Closing. The USALS angle calculation should be definitely fixed in v3.9-2274-g932ade3 .
Also available in: Atom
PDF
Updated by 
Updated by