If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor
EGNOS Receivers: Difference between revisions
mNo edit summary |
Gema.Cueto (talk | contribs) No edit summary |
||
| (32 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
{{Article Infobox2 | {{Article Infobox2 | ||
|Category=EGNOS | |Category=EGNOS | ||
| | |Editors=GMV | ||
|Level=Basic | |Level=Basic | ||
|YearOfPublication=2011 | |YearOfPublication=2011 | ||
|Logo=GMV | |Logo=GMV | ||
|Title={{PAGENAME}} | |||
}} | }} | ||
To receive EGNOS signals an EGNOS compatible receiver is required There are many receivers | To receive EGNOS signals an EGNOS compatible receiver is required. There are many receivers available on the market from a variety of manufacturers. Serving as an augmentation, or overlay, to a global navigation satellite system (GNSS) message, the European Geostationary Navigation Overlay Service (EGNOS) improves the accuracy and reliability of GNSS positioning information, and provides a crucial integrity message regarding the continuity and availability of the signal. Because of this accuracy and reliability, EGNOS has proven essential for a range of applications across numerous market segments, as can be seen in the reference link. <ref name=" GSA EGNOS applications>[https://www.gsa.europa.eu/egnos/applications GSA EGNOS Applications ]</ref> | ||
An EGNOS receiver is like a | An EGNOS receiver is like a GNSS receiver but with special software inside that allows the receiver to lock onto the code used by the EGNOS satellites and apply the EGNOS corrections to the GNSS signals. Apart from this, an EGNOS receiver is just like a GNSS receiver. This means that it can pick up GNSS signals as well. An EGNOS receiver is the same size as a GNSS receiver and uses the same type of antenna. The next EGNOS generation (EGNOS V3) is going to include a multi frequency and multi constellation configuration (GPS and Galileo) and is currently being assessed with the objective to have them operational by 2025. | ||
==Receiver types== | ==Receiver types== | ||
[[File:receiver_test.jpg | EGNOS receiver used for test and validation purposes. | 350px|thumb|right]] | [[File:receiver_test.jpg | EGNOS receiver used for test and validation purposes. | 350px|thumb|right]] | ||
EGNOS | The selection of the EGNOS receiver to use will depend on the specific application, the functionalities needed, and the integration constraints. In particular, it is necessary to check whether the receiver processes EGNOS correctly, and if its interfaces allow the application to retrieve the required data. | ||
EGNOS-enabled | There are different technologies to use as basis upon which design an EGNOS-enabled receiver, namely, chipsets, hybrid components and auxiliary cards: | ||
* | * Chipsets: the EGNOS solution is embedded in one or two components that are installed in a circuit board. Special care is to be put with the RF interface. This solution is the least expensive. | ||
* Hybrid | * Hybrid components: a single component includes RF functions and data processing. With a cost higher than the chipset solution, the integration is simpler. | ||
* Auxiliary | * Auxiliary cards (piggybacks): all the RF and processing functions are included in a single card designed to be attached to the main board. Although this is the highest cost solution, is also the best one for embedded applications. | ||
==Communications protocols== | ==Communications protocols== | ||
Receiver manufacturers tend to provide output data in a combination of proprietary and standardized open formats, the most common of which include [[Interfaces and Protocols| NMEA, RTCM, NTRIP, SiSNET and RINEX]]. | |||
==Manufacturer’s specifications== | ==Manufacturer’s specifications== | ||
[[File:egnos_receiver.jpg | EGNOS Receiver market. |200px|thumb| | [[File:egnos_receiver.jpg | EGNOS Receiver market. |200px|thumb|right]] | ||
As EGNOS is [[SBAS Interoperability|interoperable]] with other SBAS, those receivers implementing the SBAS standards will take benefit of it. In practice, many receivers indicate its compatibility with SBAS with the tags "WAAS Capable" or "WAAS Enabled", after the [[WAAS General Introduction|first operational SBAS]], deployed by the US government. "WAAS Capable" usually means that the SBAS functions are switched off in the default receiver configuration; the user would have to turn them on at least once. On the contrary, "WAAS Enabled" usually indicates that the SBAS features are set in the initial configuration. | |||
==Safety-of-Life and Open Service Receivers== | |||
For the Safety-of-Life (SoL) service,<ref name="EGNOS SoL SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/documents/egnos_sol_sdd_in_force.pdf EGNOS Safety of Life Service Definition Document]</ref> the EGNOS user equipment shall be compliant (certified) against several standards. For instance, civil aviation SBAS equipment shall demonstrate (see [[SBAS Standards|SBAS standards]]): | |||
* Full compliance to RTCA SBAS MOPS DO-229 (airborne equipment). | |||
* Full compliance to the RTCA SBAS MOPS 228 and 301 (antenna requirements). | |||
* Compliance to RTCA TSO (C190, C145b, C146b) for SBAS equipment or equivalent European TSO. There is an additional TSO linked to the GNSS Antenna (TSO-C190). | |||
* Compatibility to other avionics equipment, in particular Flight Management Systems (FMS). | |||
The SoL civil aviation certified equipment is in the highest rank with respect its cost. There exist a large number of certified receivers manufacturers worldwide both in the US (GARMIN, Honeywell, Rockwell Collins, General Avionics, etc) and in Europe (see complete list in EASA homepage<ref>[https://www.easa.europa.eu/download/etso/etsoa.pdf List of ETSO Authorisations (European Aviation Safety Agency)]</ref>). | |||
The Open Service (OS)<ref name="EGNOS OS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/documents/egnos_os_sdd_in_force.pdf EGNOS Open Service Definition Document]</ref> targets low cost, general purpose GNSS equipment that uses the SBAS SIS to provide the user with an enhanced accuracy performance in comparison with the one provided by a standalone GPS device. In comparison with the certification requirements of the user equipment above, user equipment is not necessarily compliant with the RTCA MOPS DO 229 processing rules, but might only make use of the processing algorithms that render the accuracy corrections provided by the SBAS SIS. | |||
Helios<ref name=" Helios Home Site">[http://www.askhelios.com/ Helios Home Site ]</ref> produced a list of receivers compatible with EGNOS as part of a market study completed in 2008 on behalf of the GSA. | |||
The survey divided the receivers into several categories, depending on the level of processing of the SBAS information: | |||
*Category 1: Full use of SBAS corrections. | |||
*Category 2: Capability of receiving the signal from the SBAS satellites. | |||
*Category 3: The receiver is known to be SBAS compatible, but the receiver does not make use of this ability and does not process the augmentation data. Products in this category would require a more extensive receiver firmware upgrade to make use of SBAS. | |||
*Category 4: Receivers for which the SBAS capability of the device/chipset is unknown. | |||
In any case, it should be noted that this classification is not aligned with the equipment operational classes defined in the MOPS RTCA DO 229. | |||
==Notes== | ==Notes== | ||
Updated information regarding EGNOS implementation in market products can be found in the Market reports<ref name=" GSA Market Reports">[https://www.gsa.europa.eu/market/market-report GSA Market Reports ]</ref> or in the User Technology Reports <ref name=" GSA User Technology Reports">[https://www.gsa.europa.eu/european-gnss/gnss-market/gnss-user-technology-report GSA User Technology Reports ]</ref> published regularly by GSA. | |||
<references group="footnotes"/> | <references group="footnotes"/> | ||
==References== | ==References== | ||
<references/> | <references/> | ||
[[Category:EGNOS | [[Category:EGNOS]] | ||
[[Category:EGNOS User Segment]] | |||
[[Category:EGNOS User Segment | |||
Latest revision as of 09:42, 28 February 2019
| EGNOS | |
|---|---|
| Title | EGNOS Receivers |
| Edited by | GMV |
| Level | Basic |
| Year of Publication | 2011 |
To receive EGNOS signals an EGNOS compatible receiver is required. There are many receivers available on the market from a variety of manufacturers. Serving as an augmentation, or overlay, to a global navigation satellite system (GNSS) message, the European Geostationary Navigation Overlay Service (EGNOS) improves the accuracy and reliability of GNSS positioning information, and provides a crucial integrity message regarding the continuity and availability of the signal. Because of this accuracy and reliability, EGNOS has proven essential for a range of applications across numerous market segments, as can be seen in the reference link. [1]
An EGNOS receiver is like a GNSS receiver but with special software inside that allows the receiver to lock onto the code used by the EGNOS satellites and apply the EGNOS corrections to the GNSS signals. Apart from this, an EGNOS receiver is just like a GNSS receiver. This means that it can pick up GNSS signals as well. An EGNOS receiver is the same size as a GNSS receiver and uses the same type of antenna. The next EGNOS generation (EGNOS V3) is going to include a multi frequency and multi constellation configuration (GPS and Galileo) and is currently being assessed with the objective to have them operational by 2025.
Receiver types
The selection of the EGNOS receiver to use will depend on the specific application, the functionalities needed, and the integration constraints. In particular, it is necessary to check whether the receiver processes EGNOS correctly, and if its interfaces allow the application to retrieve the required data.
There are different technologies to use as basis upon which design an EGNOS-enabled receiver, namely, chipsets, hybrid components and auxiliary cards:
- Chipsets: the EGNOS solution is embedded in one or two components that are installed in a circuit board. Special care is to be put with the RF interface. This solution is the least expensive.
- Hybrid components: a single component includes RF functions and data processing. With a cost higher than the chipset solution, the integration is simpler.
- Auxiliary cards (piggybacks): all the RF and processing functions are included in a single card designed to be attached to the main board. Although this is the highest cost solution, is also the best one for embedded applications.
Communications protocols
Receiver manufacturers tend to provide output data in a combination of proprietary and standardized open formats, the most common of which include NMEA, RTCM, NTRIP, SiSNET and RINEX.
Manufacturer’s specifications
As EGNOS is interoperable with other SBAS, those receivers implementing the SBAS standards will take benefit of it. In practice, many receivers indicate its compatibility with SBAS with the tags "WAAS Capable" or "WAAS Enabled", after the first operational SBAS, deployed by the US government. "WAAS Capable" usually means that the SBAS functions are switched off in the default receiver configuration; the user would have to turn them on at least once. On the contrary, "WAAS Enabled" usually indicates that the SBAS features are set in the initial configuration.
Safety-of-Life and Open Service Receivers
For the Safety-of-Life (SoL) service,[2] the EGNOS user equipment shall be compliant (certified) against several standards. For instance, civil aviation SBAS equipment shall demonstrate (see SBAS standards):
- Full compliance to RTCA SBAS MOPS DO-229 (airborne equipment).
- Full compliance to the RTCA SBAS MOPS 228 and 301 (antenna requirements).
- Compliance to RTCA TSO (C190, C145b, C146b) for SBAS equipment or equivalent European TSO. There is an additional TSO linked to the GNSS Antenna (TSO-C190).
- Compatibility to other avionics equipment, in particular Flight Management Systems (FMS).
The SoL civil aviation certified equipment is in the highest rank with respect its cost. There exist a large number of certified receivers manufacturers worldwide both in the US (GARMIN, Honeywell, Rockwell Collins, General Avionics, etc) and in Europe (see complete list in EASA homepage[3]).
The Open Service (OS)[4] targets low cost, general purpose GNSS equipment that uses the SBAS SIS to provide the user with an enhanced accuracy performance in comparison with the one provided by a standalone GPS device. In comparison with the certification requirements of the user equipment above, user equipment is not necessarily compliant with the RTCA MOPS DO 229 processing rules, but might only make use of the processing algorithms that render the accuracy corrections provided by the SBAS SIS.
Helios[5] produced a list of receivers compatible with EGNOS as part of a market study completed in 2008 on behalf of the GSA. The survey divided the receivers into several categories, depending on the level of processing of the SBAS information:
- Category 1: Full use of SBAS corrections.
- Category 2: Capability of receiving the signal from the SBAS satellites.
- Category 3: The receiver is known to be SBAS compatible, but the receiver does not make use of this ability and does not process the augmentation data. Products in this category would require a more extensive receiver firmware upgrade to make use of SBAS.
- Category 4: Receivers for which the SBAS capability of the device/chipset is unknown.
In any case, it should be noted that this classification is not aligned with the equipment operational classes defined in the MOPS RTCA DO 229.
Notes
Updated information regarding EGNOS implementation in market products can be found in the Market reports[6] or in the User Technology Reports [7] published regularly by GSA.