Hi all,
I recently got a stone-aged Digibit R1 to replace an even older PCI-E card. My
satellite antenna points at Astra S19.2E and Hotbird S13E, 2 Dual LNBs in Quad
configuration. However, the Digibit device seems not to find anything on S13E.
Not sure if I need DiSeQC with SATIP but I set:
in sources.conf
S19.2E 1 Astra 1KR/1L/1M/2C
S19.2E 2 Astra 1KR/1L/1M/2C
S13E 3 Eutelsat Hot Bird 13B/13C/13D
S13E 4 Eutelsat Hot Bird 13B/13C/13D
and in diseqc.conf
1 2:
S19.2E 11700 V 9750 …
[View More]t v W15 [E0 10 38 F0] W15 A W15 t
S19.2E 99999 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T
S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t
S19.2E 99999 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T
3 4:
S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t
S13.0E 99999 V 10600 t v W15 [E0 10 38 F5] W15 B W15 T
S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t
S13.0E 99999 H 10600 t V W15 [E0 10 38 F7] W15 B W15 T
This has worked with a DD Cine S2 V6.5 PCI-E card earlier.
conf.d/50-satip.conf goes like,
[satip]
-d 4
# -s 192.168.20.4|DVBS2-4:S19.2E,S13E|DIGIBIT
in order to detect 4 tuners. The -s line is apparently not needed and the
params are autodetected. syslog says,
Sep 17 19:21:12 seneca vdr: [5163] SATIP discover thread started (pid=5159, tid=5163, prio=high)
Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=0 DeviceNumber=0 [device 0]
Sep 17 19:21:12 seneca vdr: [5164] SATIP#0 tuner thread started (pid=5159, tid=5164, prio=high)
Sep 17 19:21:12 seneca vdr: [5159] new device number 2 (card index 2)
Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=1 DeviceNumber=1 [device 1]
Sep 17 19:21:12 seneca vdr: [5166] device 1 section handler thread started (pid=5159, tid=5166, prio=low)
Sep 17 19:21:12 seneca vdr: [5165] SATIP#0 section handler thread started (pid=5159, tid=5165, prio=high)
Sep 17 19:21:12 seneca vdr: [5167] SATIP#1 tuner thread started (pid=5159, tid=5167, prio=high)
Sep 17 19:21:12 seneca vdr: [5159] new device number 3 (card index 3)
Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=2 DeviceNumber=2 [device 2]
Sep 17 19:21:12 seneca vdr: [5170] SATIP#2 tuner thread started (pid=5159, tid=5170, prio=high)
Sep 17 19:21:12 seneca vdr: [5159] new device number 4 (card index 4)
Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=3 DeviceNumber=3 [device 3]
Sep 17 19:21:12 seneca vdr: [5173] SATIP#3 tuner thread started (pid=5159, tid=5173, prio=high)
Sep 17 19:21:12 seneca vdr: [5169] device 2 section handler thread started (pid=5159, tid=5169, prio=low)
Sep 17 19:21:12 seneca vdr: [5174] SATIP#3 section handler thread started (pid=5159, tid=5174, prio=high)
Sep 17 19:21:12 seneca vdr: [5171] SATIP#2 section handler thread started (pid=5159, tid=5171, prio=high)
Sep 17 19:21:12 seneca vdr: [5172] device 3 section handler thread started (pid=5159, tid=5172, prio=low)
Sep 17 19:21:12 seneca vdr: [5175] device 4 section handler thread started (pid=5159, tid=5175, prio=low)
... other stuff
Sep 17 19:21:12 seneca vdr: [5168] SATIP#1 section handler thread started (pid=5159, tid=5168, prio=high)
Sep 17 19:21:13 seneca vdr: [5163] SATIP: Adding server '192.168.20.4|DVBS2-4|DIGIBIT-002F2A:SAT>IP' Bind: default Filters: none CI: no Quirks: SessionId,ForcePilot
However, when I set UpdateChannels = 5 to run channel full scan, all I get on devices 2 and 3 is
Sep 17 19:22:34 seneca vdr: [5170] SATIP-ERROR: Tuning timeout - retuning [device 2]
Sep 17 19:22:34 seneca vdr: [5173] SATIP-ERROR: Tuning timeout - retuning [device 3]
over and over. What am I missing?
TIA!
Ciao,
hm
[View Less]
*** CALL FOR STUDENT VOLUNTEERS - MUM 2023***
*Application Deadline: 15th of September 2023*
* We apologize if you receive multiple copies of this CfP *
*For the online version of this Call, please visit:
https://mum-conf.org/2023/index.php?web=svs*
* MUM 2023, the 22nd International Conference on Mobile and Ubiquitous
Multimedia | Vienna, Austria, December 3-6, 2023 *
We are thrilled to announce the upcoming 22nd International Conference on
Mobile and Ubiquitous Multimedia (MUM 2023) to …
[View More]be held from December 3rd to
6th in the enchanting city of Vienna, Austria. We would like to invite
passionate and dedicated students to join us as volunteers. This is an
exceptional opportunity for you to gain valuable hands -on experience,
expand your network, and contribute to the success of an international
conference.
*Responsibilities of Student Volunteers*
- Assisting with registration and check-in processes
- Guiding attendees and providing information about the conference venue
and schedule
- Assisting speakers and presenters during sessions
- Supporting the organizing committee with various administrative tasks
- Helping with the setup and management of conference equipment and
facilities
- Assisting with social events and networking activities
- Social media support
*Benefits of Volunteering*
- Free registration - Access to all conference sessions and workshops
during your volunteer shifts
- A goodie bag, t-shirt and a certificate of appreciation for your
valuable contribution
- Networking opportunities with renowned researchers and industry
professionals
- Recognition on the conference website and in the official program
- An opportunity to showcase your organizational and communication
skills
*Requirements*
- Must be a currently enrolled student
- Strong communication and interpersonal skills
- Reliable and responsible with a professional attitude
If you are enthusiastic about MUM 2023 and would like to be a part of the
conference, we encourage you to apply as a student volunteer. To submit
your application here <https://forms.gle/2q7A7DRPkkk5fpcVA> (
https://docs.google.com/forms/d/e/1FAIpQLSesAxVcvUUKRi-7cFqCS7CiXEUI2V7HZ4p…
).
The deadline for applications is *Sept 15th, 2023*. Selected volunteers
will be notified by email no later than *Sept 29th, 2023*. We look forward
to receiving your applications and welcoming you to Vienna for a memorable
conference experience!
*Student Volunteers Chair*
Ambika Shahu,TU Wien
All questions about the student volunteer program should be emailed to:
sv2023(a)mum-conf.org
[View Less]