Limeux transmitting station

The Limeux transmitting station (50°00′44″N 1°49′49″E) is a facility for FM radio and television transmissions located near Abbeville, Somme, France. It has a 203-metre (666 ft) tall guyed mast for FM radio and analogue and digital television services. It is the tallest built structure in the Somme.

Analogue services

FM radio
Radio name Frequency Power
France Musique 89.8 MHz 2,5 kW
France Inter 93.1 MHz 2,5 kW
France Culture 97.4 MHz 2,5 kW
France Bleu Picardie 100.6 MHz 5 kW

Digital switchover planned date on Abbeville-Limeux TV mast : February 1, 2011.

Analogue TV SECAM with NICAM Subcarrier
Channel Name UHF Channel Power Notes
TF1 63H 380 kW
France 2 57H 380 kW will be used for digital broadcasting when DSO completed
France 3 Picardie 60H 380 kW
Canal+ not transmitted N/A This Pay TV was received from Bouvigny TV mast (in analogue) (Switched off on 14/04/10). It is now only available using DTT on Limeux
France 5/Arte 45H 80 kW
M6 42H 80 kW

Digital services

Frequencies from July, 3rd 2012

Télévision Numérique Terrestre the French version of Freeview (UK)
Multiplex Name UHF Channel Nominal power Operator Transmitting standard
Multiplex R1 (GR1) 57H 80 kW TDF DVB-T
Multiplex R2 (NTN) 25H 80 kW TDF DVB-T
Multiplex R3 (CNH) 28H 80 kW TDF DVB-T
Multiplex R4 (Multi4) 55H 80 kW TDF DVB-T
Multiplex R5 (GR5 - TNT HD) 58H 80 kW from October 30, 2008 OneCast (TF1 Subsidiary) DVB-T
Multiplex R6 (SMR6) 39H 80 kW Towercast (NRJ Group) DVB-T
gollark: No, it does.
gollark: - PotatOS uses a single global process manager instance for nested potatOS instances. The ID is incremented by 1 each time a new process starts.- But each nested instance runs its own set of processes, because I never made them not do that and because without *some* of them things would break.- PotatOS has a "fast reboot" feature where, if you reboot in the sandbox, instead of *actually* rebooting the computer it just reinitializes the sandbox a bit.- For various reasons (resource exhaustion I think, mostly), if you nest it, stuff crashes a lot. This might end up causing some of the nested instances to reboot.- When they reboot, some of their processes many stay online because I never added sufficient protections against that because it never really came up.- The slowness is because each event goes to about 200 processes which then maybe do things.
gollark: WRONG!
gollark: It doesn't reuse already allocated IDs.
gollark: Don't read too much into that.

References

    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.