Enhanced Position Location Reporting System

The Enhanced Position Location Reporting System (EPLRS) is a secure, jam-resistant, computer-controlled communications network that distributes near real-time tactical information, generally integrated into radio sets, and coordinated by a Network Control Station.[1] It is primarily used for data distribution, position location, and reporting. It enhances command and control of tactical units by providing commanders with the location of friendly units.[2] It was first fielded by the US Army in 1987.[3]

EPLRS is a Time Division Multiple Access System that uses a frequency hopping, spread spectrum waveform in the UHF band.[4] It incorporates the Thornton family of COMSEC devices, and has the capability for Over the Air Rekeying (OTAR). EPLRS uses the Army Data Distribution System version of the X.25 CCITT and IEEE 802.3 protocols to interface with Army Tactical Command and Control System (ATCCS).

Situation Awareness Data Link (SADL),[5] installed on USAF F-16 and A-10 fighters, coordinates with EPLRS for ground support missions.[6]

Network Control Station

Each network is controlled by a Network Control Station (NCS), AN/TSQ-158. These have gone through several iterations.

First Gen

Second Gen

Third Gen

Downsized version to fit in HMMWV, first fielded in 1991. Dimensions: 8.5'x7'x6', 4000 lbs

  • 1 AN/UYK-44(V) Enhanced Processor (EP) computer

Fourth Gen

The AN/TSQ-158(V)4 is produced by Raytheon. Housed in a HMMWV replacing the AN/UYK-44 computer with a Toughbook laptop computer. Data is displayed through the FBCB2 platform.

Sources

gollark: Too bad, I read 100000 words or more today for no apparent reason and so you should obviously read my dubiously useful OIRâ„¢ information.
gollark: It really shouldn't be, but the entire subsystem crashes mysteriously sometimes for no reason.
gollark: Unfortunately, as I said, this is horribly broken for no debuggable reason. Fun!
gollark: This meant it could now do websockets, which would in theory allow greater interactivity and such, but which are currently just used to ship song data more efficiently.
gollark: Interestingly enough, some weeks ago the Random Stuff API was rewritten to use asyncio instead of the horrible gevent bodge it used to use for much of its history.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.