loguey Posted June 16, 2016 Share Posted June 16, 2016 I'm puzzled, I have successfully set up a TVHeadend server which is a SAT>IP server. I'm using the most recent transponders .ini file for Astra 28.2 but can only successfully scan some of the transponders. It would seem that I can only scan 8PSK and not QPSK transponders. When using Transedit I get an error message "The server cannot provide the requested transponder"when I scan QPSK transponders. When using DVBViewer the channel scan skips the QPSK transponders and does not return an error message. What steps should I take to ensure DVBViewer can see all transponders? The specific transponder I want to scan is 12266H. This transponder exists on my TVHeadend configuration and all details appear to match DVBViewer's transponder ini file. Moreover if I use Kodi's TVHeadend client I can scan all Astra 2 transponders successfully. I've attached my support.zip file, any advice you can offer would be appreciated.support.zip Quote Link to comment
Griga Posted June 17, 2016 Share Posted June 17, 2016 I'm using the most recent transponders .ini file for Astra 28.2 Obtained from where? Please attach it here. Usually Sat>IP servers can't handle parameters that are set to "auto", e.g. Modulation or FEC. Quote Link to comment
loguey Posted June 19, 2016 Author Share Posted June 19, 2016 I'm using the most recent Astra 2 .ini file downloaded from the King of sat website. I'm travelling at the moment so will attach the ini file to a post when I'm home tonight. Quote Link to comment
loguey Posted June 19, 2016 Author Share Posted June 19, 2016 Hopefully this works, attached via Dropbox. 0282.ini Quote Link to comment
Griga Posted June 19, 2016 Share Posted June 19, 2016 Well, the transponder list looks ok, except 10744 H that is wrongly flagged as DVB-S. It must be DVB-S2 8PSK FEC 2/3 SR 23000. Apart from that I can see no reason for a Sat>IP server to complain about the parameters. "The server cannot provide the requested transponder" means that TransEdit gets an error message as response. Are only DVB-S transponders affected (all QPSK) or only DVB-S2 QPSK transponders like 11719 H or both? I've used your transponder list for a full scan with my old Hauppauge Nova S2 HD that is very picky about parameters. Settings -> Scanner -> Mark transponders without signal with [X] was ticked, so you can see which transponders I can't receive (those with [X] in the description column, e.g. the Africa beam transponders). Here is the result 0282.ini 10744 H and some DVB S2 Pilot Symbol parameters are corrected (TransEdit does it automatically if a Hauppauge Nova S2 is used). Maybe you can use the option mentioned above for providing a transponder list that shows what you can't receive. 1 Quote Link to comment
Cjay Posted June 20, 2016 Share Posted June 20, 2016 @loguey Just as a matter of interest which Sat>IP server are you using? I have a Triax TSS400 and it will not scan with any degree of reliability, often returning completely erroneous data - a bit as if data from the other tuners (TSS400 has 4) is being blended in to the scan results! Chris Quote Link to comment
loguey Posted June 20, 2016 Author Share Posted June 20, 2016 It's a homebrew server. I've got a Hauppauge Nova S2 card installed in a PC running Ubuntu 14.04 and TVHeadend. TVHeadend is configured to run SAT>IP. The Hauppauge card is connected to my UK Sky dish. Using Kodi as a client I can play all the FTA channels off the server but I particularly want to use DVBViewer as it's a far superior product. I've had some unrelated power supply problems on the PC that is my usual DVBViewer client so will install DVBViewer and Transedit Beta on a laptop tonight and try and get that to work. I'll post an update late tonight. Quote Link to comment
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.