GLONASS-M

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
GLONASS-M[1]
Designer ISS Reshetnev
Country of origin Russia
Operator JSC «Navigation-Information Systems»
Applications Navigation
Specifications
Bus 3-Axis stabilized Uragan-M[2]
Constellation GLONASS
Design life 7 years[1]
Launch mass 1,415 kg (3,120 lb)[1]
Power 1250 W[1]
Batteries NiH2[3]
Equipment 3 Cs clocks[3]
FDMA signals: L1OF, L1SF, L2OF and L2SF
Space Laser Ranging[3]
Regime MEO
Production
Built 61[1][4]
Launched 45
Operational 27
Retired 12
Lost 6
Maiden launch 1 December 2001
Last launch 29 May 2016
Last retirement 13 April 2015
Related spacecraft
Derived from GLONASS
← GLONASS GLONASS-K1 →

GLONASS-M (Russian: ГЛОНАСС-М), also known as Uragan-M (Russian: Ураган-М) (GRAU Index 11F654M and manufacturing code 14F113) are the second generation of Uragan satellite design used as part of the Russian GLONASS radio-based satellite navigation system. Developed by ISS Reshetnev (Reshetnev Information Satellite Systems), it had its debut launch in 2003, and is in the process of being phased out. Its production is expected to finish in 2015 and as of July, 2015, its last launch is expected in late 2017. It is an evolution of the previous Uragan (GRAU Index 11F654) second-generation satellites, improving accuracy, increasing power, extending the design life and adding the FDMA L2OF open signal.

Design

It used a 3-axis stabilized pressurized bus with two solar panels, a propulsion module and a payload module.[5] At 1,415 kilograms (3,120 lb) these are just 2 kg (4.4 lb) heavier than the previous generation, but have 25% more power 1250 W, 230% more design life (7 years), an additional signal (L2OF) and generally improved accuracy.[1] It uses an on-board computer based on a Russian microprocessor using the VAX 11/750 instruction set (the Angstrem K1839 (Russian Wikipedia)).[6]

The Uragan-M are usually launched in trios, and due to the close distance, the radios of the thee would interfere with each other, meaning that the ground segment can only command one satellite at a time. Setting sun pointing attitude for power and then Earth pointing attitude for communications for a single unit takes about 5 hours. Since the radio contact window with ground control is between 4 to 6 hours, ground control can not control all spacecrafts in a single pass. The on-board computer in the Uragan-M can put the spacecraft in sun pointing mode autonomously, and does many of the start up processes so the ground segment can take control and process the Earth pointing mode.[7]

The payload consists of L-Band navigation signals in 25 channels separated by 0.5625 MHz intervals in 2 frequency bands: 1602.5625 - 1615.5 MHz and 1240 - 1260 MHz. EIRP 25 to 27 dBW. Right hand circular polarized.[8] It transmits the FDMA signals L1OF, L1SF, L2OF and L2SF, with the open L2OF being new to the Uragan series. It uses 3 Cs clocks with a clock stability of 1x10−13 (an 5x improvement over the 5x10−13 clock stability of the previous generation Uragan).[3]

In 2011 ISS Reshetnev announced plans to include the new CDMA signal L3OC, first introduced on Glonass-K series, on Glonass-M satellites flown from 2014; these plans did not materialize.

History

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: GLONASS

The first generation Uragan spacecraft were created under ban of foreign radiation-hardened components and thus had been an inferior product with just 3 years of expected design life.[9] Given the realized average life was just 22 months, and the fleet should have 24 spacecraft, it was necessary to launch more than 7 spacecraft per year to keep the fleet in good health.[10] To this end, the Uragan-M was designed, with an increased design life of 7 years, thanks to the availability of ITAR controlled parts.[11][12][13]

On December 1, 2001, a prototype might have been launched. Kosmos 2382 is identified by some sources as a Uragan-M, but the official documentation generally lists 2003 as the launch date of the first Uragan-M satellite.[1][3][14][15] On December 10, 2003, the first operational Uragan-M was launched by a Proton-K / Briz-M from Baikonur along two Uragan Block IIv satellites. On December 26, 2004 the second operational Uragan-M was launched by a Proton-K
DM-2, also along two Uragan Block IIv satellites. And on December 25, 2005, two Uragan-M were launched along the last Uragan Block IIv satellites.[14][15]

On December 25, 2006 launched the first trio of only Uragan-M. Two launches by late 2007 meant that six additional Uragan-M were added to the fleet. And another six were successfully launched in 2008. On September 12, 2008 Prime Minister Vladimir Putin signed RF Government Resolution on increasing GLONASS Program financing by 67 billion rubles.[14][15] 2009 saw the launch of a single trio of Uragan-M, and with nine spacecraft planned for 2010, full service availability was expected. Regrettably, the third launch, on 5 December 2010, ended in failure, leaving no on-orbit spares.[16]

On October 2, 2011, the first launch of single Uragan-M satellite was performed by a Soyuz-2.1b/Fregat-M which put Kosmos 2474 on orbit from the Plesetsk Cosmodrome. Another Proton-M launched trio and an additional Soyuz-2.1b/Fregat-M launch put the fleet at full operative capacity with 24 healthy satellites.[17] On April 26, 2013 a Soyuz successfully orbited Kosmos 2485, but the Proton-M mission failed spectacularly taking with it a trio of Uragan-M.[18] During 2014, two satellites were launched by Soyuz in March and June.

On a May 28, 2014 interview, Nikolay Testoyedov — president of ISS Reshetnev — stated that production of GLONASS-M would end in 2015, with GLONASS-K being exclusively produced after that final batch.[19] In a December 14, 2014 interview with GPS World, he stated that while the original idea was to have just two GLONASS-K1 prototypes to be followed by the GLONASS-K2 production, the Western sanctions limited the supply of radiation resistant electronics. And thus, they had decided to launch an additional nine GLONASS-K1 as fleet replacement while they finished the GLONASS-K2 design.[20] In a May, 2015 presentation, Mr. Testoyedov expected the last GLONASS-M to fly in late 2017.[21] On July 30, 2015, ISS Reshetnev announced that it had completed the last GLONASS-M (N° 61) spacecraft and it was putting it in storage waiting for launch, along an additional eight already built satellites.[4][22]

Uragan-M launches

Statistics

Ordered Manufactured Launched Operational Not in service Retired Launch failures Remarks
61 61 45 24 3 12 6 Launches continuing

Launch history

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: List of GLONASS satellites
Satellite Launch (UTC) Carrier rocket Launch site Satellite type Launch Block SC s/n Orbital Plane Slot Retired Remarks
Kosmos 2382 1 December 2001
18:04		 Proton-K
DM-2		 Baikonur
81/24		 M 30 711 I 5 11 January 2008 GLONASS-M satellite prototype
Kosmos 2404 10 December 2003
13:53		 Proton-K
Briz-M		 Baikonur
81/24		 M 32 701 I 6 18 June 2009 launched along 2 Uragan Block IIv (Kosmos 2402 and Kosmos 2403)
Kosmos 2413 26 December 2004
13:53		 Proton-K
DM-2		 Baikonur
200/39		 M 33 712 I 8 22 November 2012 launched along 2 Uragan Block IIv (Kosmos 2411 and Kosmos 2412)
Kosmos 2418 25 December 2005
05:07		 Proton-K
DM-2		 Baikonur
81/24		 M 34 713 III 24 18 February 2010 launched along Kosmos 2419 and Uragan Block IIv Kosmos 2417
Kosmos 2419 25 December 2005
05:07		 Proton-K
DM-2		 Baikonur
81/24		 M 34 714 III 17 24 February 2016 Reserve satellite
Kosmos 2424 25 December 2006
20:18		 Proton-K
DM-2		 Baikonur
81/24		 M 35 715 II 14 Operational
Kosmos 2425 25 December 2006
20:18		 Proton-K
DM-2		 Baikonur
81/24		 M 35 716 II 15 Operational
Kosmos 2426 25 December 2006
20:18		 Proton-K
DM-2		 Baikonur
81/24		 M 35 717 II 10 Operational
Kosmos 2431 26 October 2007
07:35		 Proton-K
DM-2		 Baikonur
81/24		 M 36 718 III 17 20 October 2011
Kosmos 2432 26 October 2007
07:35		 Proton-K
DM-2		 Baikonur
81/24		 M 36 719 III 20 Operational
Kosmos 2433 26 October 2007
07:35		 Proton-K
DM-2		 Baikonur
81/24		 M 36 720 III 19 Operational
Kosmos 2434 25 December 2007
19:32		 Proton-M
DM-2		 Baikonur
81/24		 M 37 721 II 13 Operational
Kosmos 2435 25 December 2007
19:32		 Proton-M
DM-2		 Baikonur
81/24		 M 37 722 II 14 12 October 2011
Kosmos 2436 25 December 2007
19:32		 Proton-M
DM-2		 Baikonur
81/24		 M 37 723 II 11 Operational
Kosmos 2442 25 September 2008
08:49		 Proton-M
DM-2		 Baikonur
81/24		 M 38 724 III 18 12 February 2014
Kosmos 2443 25 September 2008
08:49		 Proton-M
DM-2		 Baikonur
81/24		 M 38 725 III 21 2 August 2014 In maintenance
Kosmos 2444 25 September 2008
08:49		 Proton-M
DM-2		 Baikonur
81/24		 M 38 726 III 22 28 November 2012
Kosmos 2447 25 December 2008
10:43		 Proton-M
DM-2		 Baikonur
81/24		 M 39 727 I 3 28 November 2012
Kosmos 2448 25 December 2008
10:43		 Proton-M
DM-2		 Baikonur
81/24		 M 39 728 I 2 16 October 2013
Kosmos 2449 25 December 2008
10:43		 Proton-M
DM-2		 Baikonur
81/24		 M 39 729 I 8 9 September 2012
Kosmos 2456 14 December 2009
10:38		 Proton-M
DM-2		 Baikonur
81/24		 M 40 730 I 1 Operational
Kosmos 2457 14 December 2009
10:38		 Proton-M
DM-2		 Baikonur
81/24		 M 40 733 I 6 Operational
Kosmos 2458 14 December 2009
10:38		 Proton-M
DM-2		 Baikonur
81/24		 M 40 734 I 5 Operational
Kosmos 2459 1 March 2010
21:19		 Proton-M
DM-2		 Baikonur
81/24		 M 41 731 III 22 Operational
Kosmos 2460 1 March 2010
21:19		 Proton-M
DM-2		 Baikonur
81/24		 M 41 732 III 23 Operational
Kosmos 2461 1 March 2010
21:19		 Proton-M
DM-2		 Baikonur
81/24		 M 41 735 III 24 Operational
Kosmos 2464 2 September 2010
00:53		 Proton-M
DM-2		 Baikonur
81/24		 M 42 736 II 9 Operational
Kosmos 2465 2 September 2010
00:53		 Proton-M
DM-2		 Baikonur
81/24		 M 42 737 II 12 Operational
Kosmos 2466 2 September 2010
00:53		 Proton-M
DM-2		 Baikonur
81/24		 M 42 738 II 16 15 February 2016 In maintenance
N/A 5 December 2010
10:25		 Proton-M
DM-03		 Baikonur
81/24		 M 43 739 N/A Failed to orbit
N/A 5 December 2010
10:25		 Proton-M
DM-03		 Baikonur
81/24		 M 43 740 N/A Failed to orbit
N/A 5 December 2010
10:25		 Proton-M
DM-03		 Baikonur
81/24		 M 43 741 N/A Failed to orbit
Kosmos 2474 2 October 2011
20:15		 Soyuz-2.1b
Fregat-M		 Plesetsk
43/4		 M 45S 742 I 4 Operational
Kosmos 2475 4 November 2011
12:51		 Proton-M
Briz-M		 Baikonur
81/24		 M 44 743 I 8 Operational
Kosmos 2476 4 November 2011
12:51		 Proton-M
Briz-M		 Baikonur
81/24		 M 44 744 I 3 Operational
Kosmos 2477 4 November 2011
12:51		 Proton-M
Briz-M		 Baikonur
81/24		 M 44 745 I 7 Operational
Kosmos 2478 28 November 2011
08:25		 Soyuz-2.1b
Fregat-M		 Plesetsk
43/4		 M 46S 746 III 17 13 April 2015 Restored the system to fully operational for the first time since late 1995.
Kosmos 2485 26 April 2013
05:23		 Soyuz-2.1b
Fregat-M		 Plesetsk
43/4		 M 47S 747 I 2 Operational
N/A 2 July 2013
02:38		 Proton-M
DM-03		 Baikonur
81/24		 M 47 748 N/A Failed to orbit
N/A 2 July 2013
02:38		 Proton-M
DM-03		 Baikonur
81/24		 M 47 749 N/A Failed to orbit
N/A 2 July 2013
02:38		 Proton-M
DM-03		 Baikonur
81/24		 M 47 750 N/A Failed to orbit
Kosmos 2494 23 March 2014
22:54		 Soyuz-2.1b
Fregat-M		 Plesetsk
43/4		 M 48S 754 III 18 Operational
Kosmos 2500 14 June 2014
17:16		 Soyuz-2.1b
Fregat-M		 Plesetsk
43/4		 M 49S 755 III 21 Operational
Kosmos 2514 7 February 2016
00:21		 Soyuz-2.1b
Fregat-M		 Plesetsk
43/4		 M 50S 751 III 17 Operational
Kosmos 2516 29 May 2016
08:44		 Soyuz-2.1b
Fregat-M		 Plesetsk
43/4		 M 51S 760  ?  ?  ?

References

  1. ↑ 1.0 1.1 1.2 1.3 1.4 1.5 1.6 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 3.3 3.4 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 15.0 15.1 15.2 Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=GLONASS-M&oldid=722976329"