On raspbmc: diseqc setup failed -1
Added by grant ed over 10 years ago
Hi there, tvheadend novice here.
The background for my setup is:
- Country: UK
- System: Raspberry pi running raspbmc 3.10.24
- DVB input: PCTV 460e DVB-S2 USB stick (external power source, not using usb hub)
- Satellite: Astra 28.2 - confirmed working when using using bundled PCTV software on a separate Windows box
I'm borrowing one of the two LNB feeds going into my usual PVR box, to try out some HTS.
I've installed tvheadend, and can see the UI on port 9981. (Process is running as user "pi", who is in the video group.)
The adapter is correctly listed under Configuration -> DVB Inputs -> TV Adapters (name "NXP TDA10071")
I've setup a single Satellite config using Port 0, with LNB type "Standard".
(The PVR box claims the LNB type is Standard, and the PCTV bundled software claims the port is "DiSEqC A | 1", which I assume means port 0 for tvheadend satconf.)
I've added the muxes using "Add DVB by Network location...", choosing Astra_28_2E, which gives me 88 muxes.
However, during the initial scans, no services are detected; every attempted initial scan gives errors like:
Feb 18 22:56:23.002 dvb: diseqc setup failed -1 Feb 18 22:56:23.002 dvb: "/dev/dvb/adapter0" tuning via s2api to "12,596,000 kHz Vertical (Initial)" (2596000, 27500000 Baud, 2/3, SYS_DVBS, QPSK) for Initial autoscan Feb 18 22:56:23.004 dvb: "/dev/dvb/adapter0" tuning to "12,596,000 kHz Vertical (Initial)" -- Front configuration failed -- Invalid argument, frequency: 2596000
Any pointers you can offer me on how to fix this are much appreciated.
~granted
Replies (2)
RE: On raspbmc: diseqc setup failed -1 - Added by Prof Yaffle over 10 years ago
What version of tvheadend are you running? I've used that stick on my (non-Pi) 'buntu server under 3.2.x-3.5.x and now 3.9.x with no trouble at all. Default satconf works fine: I've a direct LNB connection and am only targetting a single satellite (also Astra 28.2E, for UK Freesat), so no diseqc required.
Interesting that it seems that the 12,596,000 is being turned into 2596000 by my reading of those messages. Not sure if it's not just a coincidence, but other logs I've seen don't have the frequency (good or bad) as the first field.
RE: On raspbmc: diseqc setup failed -1 - Added by Prof Yaffle over 10 years ago
Old, but it concluded that you should add one mux manually, let tvheadend discover the others, and delete any it finds that are obviously duff and which cause things to get stuck on the way.