Project

General

Profile

TVheadend + HDhomerun + Ziggo new problem.

Added by John Pollaert almost 10 years ago

Hello,
This week Ziggo has made serveral changes in their dvb-c network. I needed to do a new scan to find the new channels.
But now I can't get it working anymore.
To scan for channels, I need to manually set the first Mux.:
Frequency 474000000
Symbol rate 6875000
Qam 64
This works, and the HDhomerun starts with scanning, and finds all other muxes. But the 474 mux is the only which is giving me an OK. All other muxes are giving a FAIL.
This is from the log:

2015-01-26 22:25:49.000 [   INFO] mpegts: 698.75MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #1 (192.168.0.144)
2015-01-26 22:25:49.000 [   INFO] tvhdhomerun: tuning to auto:698750000
2015-01-26 22:25:49.013 [   INFO] subscription: 042B: "scan" subscribing to mux, weight: 2, adapter: "HDHomeRun DVB-C Tuner #1 (192.168.0.144)", network: "Ziggo", mux: "698.75MHz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>" 
2015-01-26 22:25:49.013 [   INFO] mpegts: 388MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #0 (192.168.0.144)
2015-01-26 22:25:49.013 [   INFO] tvhdhomerun: tuning to auto:388000000
2015-01-26 22:25:49.026 [   INFO] subscription: 042C: "scan" subscribing to mux, weight: 2, adapter: "HDHomeRun DVB-C Tuner #0 (192.168.0.144)", network: "Ziggo", mux: "388MHz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>" 
2015-01-26 22:25:49.026 [   INFO] mpegts: 396MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #2 (192.168.0.144)
2015-01-26 22:25:49.026 [   INFO] tvhdhomerun: tuning to auto:396000000
2015-01-26 22:25:49.039 [   INFO] subscription: 042D: "scan" subscribing to mux, weight: 2, adapter: "HDHomeRun DVB-C Tuner #2 (192.168.0.144)", network: "Ziggo", mux: "396MHz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>" 
2015-01-26 22:25:49.039 [   INFO] mpegts: 546.75MHz in Ziggo - tuning on HDHomeRun DVB-C Tuner #3 (192.168.0.144)
2015-01-26 22:25:49.039 [   INFO] tvhdhomerun: tuning to auto:546750000
2015-01-26 22:25:49.051 [   INFO] subscription: 042E: "scan" subscribing to mux, weight: 2, adapter: "HDHomeRun DVB-C Tuner #3 (192.168.0.144)", network: "Ziggo", mux: "546.75MHz", hostname: "<N/A>", username: "<N/A>", client: "<N/A>" 
2015-01-26 22:26:04.004 [   INFO] mpegts: 546.75MHz in Ziggo - scan no data, failed
2015-01-26 22:26:04.004 [   INFO] subscription: 042E: "scan" unsubscribing
2015-01-26 22:26:04.005 [   INFO] mpegts: 396MHz in Ziggo - scan no data, failed
2015-01-26 22:26:04.005 [   INFO] subscription: 042D: "scan" unsubscribing
2015-01-26 22:26:04.006 [   INFO] mpegts: 388MHz in Ziggo - scan no data, failed
2015-01-26 22:26:04.006 [   INFO] subscription: 042C: "scan" unsubscribing
2015-01-26 22:26:04.006 [   INFO] mpegts: 698.75MHz in Ziggo - scan no data, failed
2015-01-26 22:26:04.007 [   INFO] subscription: 042B: "scan" unsubscribing

When I use the HDhomerun to scan directly, then I can find and play all FTC channels. But TVheadend doesn't. I have already upgraded the firmware of the HDhomerun, upgraded TVheadend to the lates version, and even tried a complete new installation. But still the same.
What can be the problem here??


Replies (2)

RE: TVheadend + HDhomerun + Ziggo new problem. - Added by Richard Snepvangers almost 10 years ago

Hi John,

After the Ziggo changes yesterday I also have issue's, but all Muxes are found. Did you set the original network ID to 5555?

All my channels are found, but can only view the channels on the initial mux (474.000). I made a seperate post for this.

Greetings Richard Snepvangers

RE: TVheadend + HDhomerun + Ziggo new problem. - Added by J Elz almost 10 years ago

John, please see https://tvheadend.org/boards/5/topics/15154?r=15218 for correcting the issue. The problem is most likely you have not set the new modulation to a symbolrate of 6900 on the HDHomerun. The topic I linked to shows you the commands to do that in Linux. Alternatively, if you use the HDHomerun Setup utility in Windows goto the DVBC tab and set:

QAM256 6900
QAM256 6875
QAM64 6875

The new muxes use a symbolrate of 6900 instead of 6875; which needs to be set in the HDHomerun configuration tool in order to work properly.

    (1-2/2)