Full Freeview on the Winter Hill (Bolton, England) transmitter
Google Streetview | Google map | Bing map | Google Earth | 53.625,-2.516 or 53°37'30"N 2°30'56"W | BL6 6SL |
The symbol shows the location of the Winter Hill (Bolton, England) transmitter which serves 2,690,000 homes. The bright green areas shown where the signal from this transmitter is strong, dark green areas are poorer signals. Those parts shown in yellow may have interference on the same frequency from other masts.
_______
Digital television services are broadcast on a multiplexes (or Mux) where many stations occupy a single broadcast frequency, as shown below.
64QAM 8K 3/4 27.1Mb/s DVB-T MPEG2
DTG-12 QSPK 8K 3/4 8.0Mb/s DVB-T MPEG2
DTG-2 16QAM 2K 3/4 18.1Mb/s DVB-T MPEG2
H/V: aerial position (horizontal or vertical)
Which Freeview channels does the Winter Hill transmitter broadcast?
If you have any kind of Freeview fault, follow this Freeview reset procedure first.Digital television services are broadcast on a multiplexes (or Mux) where many stations occupy a single broadcast frequency, as shown below.
64QAM 8K 3/4 27.1Mb/s DVB-T MPEG2
DTG-12 QSPK 8K 3/4 8.0Mb/s DVB-T MPEG2
DTG-2 16QAM 2K 3/4 18.1Mb/s DVB-T MPEG2
H/V: aerial position (horizontal or vertical)
Which BBC and ITV regional news can I watch from the Winter Hill transmitter?

BBC North West Tonight 3.1m homes 11.8%
from Salford M50 2QH, 22km southeast (139°)
to BBC North West region - 92 masts.

ITV Granada Reports 3.1m homes 11.6%
from Salford M50 2EQ, 22km southeast (139°)
to ITV Granada region - 80 masts.
How will the Winter Hill (Bolton, England) transmission frequencies change over time?
1956-80s | 1984-97 | 1997-98 | 1998-2009 | 2009-13 | 2013-18 | 2013-17 | 20 Feb 2020 | ||
VHF | C/D E | C/D E | C/D E | C/D E | C/D E T | W T | W T | ||
C9 | ITVwaves | ||||||||
C12 | BBCtvwaves | ||||||||
C24 | _local | ||||||||
C29 | SDN | ||||||||
C31 | com7 | com7 | |||||||
C32 | BBCA | ||||||||
C34 | D3+4 | ||||||||
C35 | BBCB | ||||||||
C37 | com8 | com8 | |||||||
C40 | LOCAL2 | ||||||||
C48 | C5waves | C5waves | |||||||
C49tv_off | ArqA | ArqA | |||||||
C50tv_off | BBCA | BBCA | |||||||
C54tv_off | -BBCB | -BBCB | -BBCB | ||||||
C55tv_off | BBC1waves | BBC1waves | BBC1waves | ArqB | ArqB | ArqB | com7tv_off | ||
C56tv_off | _local | _local | _local | LPR | |||||
C57tv_off | GIM | GIM | GIM | GIM | |||||
C58tv_off | SDN | SDN | SDN | ||||||
C59tv_off | ITVwaves | ITVwaves | ITVwaves | D3+4 | D3+4 | D3+4 | |||
C61 | ArqA | ||||||||
C62 | BBC2waves | BBC2waves | BBC2waves | BBCA | |||||
C65 | C4waves | C4waves | C4waves |
tv_off Being removed from Freeview (for 5G use) after November 2020 / June 2022 - more
Table shows multiplexes names see this article;
green background for transmission frequencies
Notes: + and - denote 166kHz offset; aerial group are shown as A B C/D E K W T
waves denotes analogue; digital switchover was 4 Nov 09 and 2 Dec 09.
How do the old analogue and currrent digital signal levels compare?
Analogue 1-4 | 500kW | |
SDN, ARQA, ARQB, BBCA, D3+4, BBCB | (-7dB) 100kW | |
com7 | (-12.9dB) 25.7kW | |
com8 | (-13.4dB) 22.6kW | |
Analogue 5 | (-16dB) 12.5kW | |
Mux 1*, Mux 2*, Mux A*, Mux B*, Mux C*, Mux D* | (-17dB) 10kW | |
LL | (-24dB) 2kW | |
GIM, LM, LPR | (-27dB) 1000W |
Local transmitter maps
Winter Hill Freeview Winter Hill DAB Winter Hill TV region BBC North West GranadaWhich companies have run the Channel 3 services in the Winter Hill transmitter area
|
|
Wednesday, 20 June 2018
S
StevensOnln18:22 PM
Andy: If other multiplexes are indicating maximum signal then the tuner may be being overloaded by too much signal (it's effectively being deafened). Try fitting an attenuator to reduce the signal strength. Also, check for any loose or damaged cables or connections.
link to this comment |
Sunday, 24 June 2018
J
js8:51 AM
Invalid Codes in the Freeview EIT:
What I'm talking about here is the EIT text - the titles and descriptions of events.
There are two processing paths for the Freeview EIT.
The EIT text off DVB-T2 multiplexes is entirely Huffman coded.
The EIT text off DVB-T multiplexes is only Huffman coded for services on DVB-T2 multiplexes.
Thus a DVB-T only device will not normally encounter Huffman coded text.
Generic DVB-T2 receivers are not able to decode the Huffman coded text and will typically display gibberish - what their users often describe as Chinese.
The BBC is responsible for Huffman coding the EIT text, the objective being the ability to dictate DRM implementation requirements to manufacturers in exchange for the Huffman decode tables.
Thus the recordings made on Freeview HD certified devices are encrypted to disk and only playable on the device that they were made on.
Now that's out of the way, let's get back to the errors in the EIT text.
By observation, it has become evident that the invalid codes are the Least Significant Bytes of a group of Unicode punctuation characters.
The invalid codes seen so far are:
0x10 = LSB of Unicode Character 'HYPHEN' (U+2010)
0x13 = LSB of Unicode Character 'EN DASH' (U+2013)
0x14 = LSB of Unicode Character 'EM DASH' (U+2014)
0x18 = LSB of Unicode Character 'LEFT SINGLE QUOTATION MARK' (U+2018)
0x19 = LSB of Unicode Character 'RIGHT SINGLE QUOTATION MARK' (U+2019)
0x1C = LSB of Unicode Character 'LEFT DOUBLE QUOTATION MARK' (U+201C)
0x1D = LSB of Unicode Character 'RIGHT DOUBLE QUOTATION MARK' (U+201D)
The Current State:
The Freeview EIT stream, together with the NIT, SDT and TDT/TOT streams, were recorded for 360 seconds off BBC A and BBC B multiplexes.
The overall EIT cycle time is 300 seconds so recording for 360 seconds ensures all events are captured.
The file off BBC A was 33.4 MB.
The file off BBC B was 19.0 MB.
The BBC B file was much smaller because of the Huffman coding - a lossless compression.
Only the EIT text from events from services carried on DVB-T2 multiplexes is Huffman coded in the EIT off BBC A.
The files were processed by my EIT program which produced xmltv output files:
North West_BBC A__2018 06 23 041950.xml - 31.2 MB and North West_BBC B__2018 06 23 042617.xml - 31.0 MB.
Upon loading these files, the xmltv viewer app, TVGuide, reported:
"Loaded 33518 in 7.015625 seconds, spanning 23/6/2018 to 01/07/2018" for North West_BBC A__2018 06 23 041950.xml
and
"Loaded 33518 in 7.609375 seconds, spanning 23/6/2018 to 01/07/2018" for North West_BBC B__2018 06 23 042617.xml
The files thus contained the same number, 33518, of events.
My EIT program has a subroutine which substitutes meaningful strings for the invalid codes:
Private Sub fixbadcode(b As Byte, s As String)
Select Case b
Case &H10 'Unicode Character 'HYPHEN' (U+2010)
s = s + "{-}"
Case &H13 'Unicode Character 'EN DASH' (U+2013)
s = s + "{-}"
Case &H14 'Unicode Character 'EM DASH' (U+2014)
s = s + "{-}"
Case &H18 ''LEFT SINGLE QUOTATION MARK' (U+2018)
s = s + "{L'}"
Case &H19 ''RIGHT SINGLE QUOTATION MARK' (U+2019)
s = s + "{R'}"
Case &H1C 'Unicode Character 'LEFT DOUBLE QUOTATION MARK' (U+201C)
s = s + "{L''}"
Case &H1D 'Unicode Character 'RIGHT DOUBLE QUOTATION MARK' (U+201D)
s = s + "{R''}"
Case Else
Stop
s = s + "[0x" + hexbyte(b) + "]"
End Select
End Sub
So, for example, invalid code 0x19 is replaced by {R'} signifying 'RIGHT SINGLE QUOTATION MARK'.
The curly brackets that enclose the strings are not found in normal EIT text and are used to search for and locate the invalid codes in the output file.
TVGuide has the useful ability to count and display events based on text in event descriptions.
I have defined a "highlighter" in TVGuide as "{ in Description".
Thus upon loading North West_BBC A__2018 06 23 041950.xml, TVGuide shows "{ in Description(710)", indicating there are 710 events that contain invalid codes in the EIT captured off BBC A.
Clicking on the highlighter displays those events.
Upon loading North West_BBC B__2018 06 23 042617.xml, TVGuide shows "{ in Description(17)", indicating there are 17 events that contain invalid codes in the EIT captured off BBC B.
Looking at those events showed they were all off services carried on DVB-T2 multiplexes.
TVGuide also has the ability to restrict its display to categories, for example Sport or Movies.
In my EIT program, I created a "DVB-T2" category to restrict display to events on services carried on DVB-T2 multiplexes.
Upon loading North West_BBC A__2018 06 23 041950.xml and selecting the "DVB-T2" category and clicking the "highlighter" "{ in Description(710)", the same 17 events as those off BBC B were displayed.
So when the invalid codes originate in events from services carried on DVB-T2 multiplexes, they are the same whether the EIT is captured from BBC A or BBC B.
What happened to all the rest? There are 710 events containing invalid codes in the EIT off BBC A - but a mere 17 in the EIT off BBC B.
The invalid codes have simply been omitted in EIT text off BBC B.
This solution causes grammatical errors such as thats in place of that's and cant for can't.
I give a single example to illustrate here:
This event has an invalid code in its title:
Channel 5 HD, Mon 25 Jun 04:00 - 04:45: Now That{R'}s Funny
This error is present regardless of EIT origin and Huffman coded because it is off a service carried on a DVB-T2 multiplex.
The SD version of the event off the Huffman coded BBC B EIT:
Channel 5, Mon 25 Jun 04:00 - 04:45: Now Thats Funny
The invalid code for the intended apostrophe has been omitted, rendering a grammatically incorrect "thats".
The SD version of the event off the non-Huffman coded BBC A EIT:
Channel 5, Mon 25 Jun 04:00 - 04:45: Now That{R'}s Funny
The invalid code for the intended apostrophe is present.
link to this comment |
Sunday, 1 July 2018
M
Mark Jolly3:36 PM
I have just moved to the. Bromley Cross area of Bolton BL79NY and am in line of sight of the transmitter at Winter Hill. The house does not currently have an aerial. Can you suggest a suitable aerial for my area. Regards Mark
link to this comment |
MikeP
5:11 PM
5:11 PM
Mark Jolly:
As you are just 6 km away frok the transmitter at Winter Hill, you only need a small aerial fitted, which could be in a loft or external. You need to avoid having too much signal so a high gain aerial is not needed, but it is best to have a directional aerial to avoid external interference, hence having a small aerial fitted. Note that there is no such thing as a 'digital' aerial (that's a ploy to increase the costs) as the aerial does not care how the signals are modulated on the carrier.
You should aim to have between 60% and 85% signal strength on all multipexes available. Put your post code into the Digital UK Coverage Checker at Digital UK - Coverage checker and it will tell you the channels currently being used.
link to this comment |
Monday, 2 July 2018
M
michael3:39 PM
Rather than the above unrelated garbage, it would be timely and helpful to have
updated information on the situation of the Winter Hill with approaching moor fires.
link to this comment |
MikeP
4:25 PM
4:25 PM
Michael:
According to Digital UK, the Winter Hill transmitter is operating normally and is unaffected by the nearby moorland fires.
link to this comment |
Tuesday, 3 July 2018
C
Chris.SE4:28 AM
michael:
The "unrelated garbage" is SPAM and only the site owner might be able to do something about blocking it or removing it.
link to this comment |
C
Chris.SE4:55 AM
js:
As I have said before, I would try talking directly to Arqiva who should have the technical knowledge to address your issues. Failing that you could try and talk to BBC engineering who might be able to help or point you in the right direction.
If there is any chance that you could receive signals from another transmitter (even perhaps if only when there is a lift on - variable at present) and see if you get the same problems. If not, this does suggest that it's an issue at Winter Hill, but I really am surprised that others aren't posting here with similar issues. There is some posts on DigitalSpy which might suggest a transmitter issue.
link to this comment |
A
Andy blair5:14 PM
I weak signal on UHV channel 31 that has BBC rd 2-6 and now 80s
From winter hill
link to this comment |
Wednesday, 4 July 2018
J
js1:26 PM
Andy blair: Yes, com8, uhf31, is about 7 or 8 dB down on its normal level - not usable for me.
link to this comment |
Select more comments
Your comment please