Changes between Version 31 and Version 32 of NDF
- Timestamp:
- Nov 2, 2018, 9:03:15 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NDF
v31 v32 38 38 || Signal Type || || uint5 || 5 || Signal type specification, index from MSM signal mask bit field (0..31, see DF395) || 39 39 || Epoch Time || || uint30 || 30 || Epoch time, specific for the satellite system always 30 bits (see table below) || 40 || Continuous Tracking || || bit(1) || 1 || Tracking this satellite frame data was contin ous (1 = continous, 0 not continuos or unset) ||40 || Continuous Tracking || || bit(1) || 1 || Tracking this satellite frame data was continuous (1 = continuous, 0 not continuous or unset) || 41 41 || Frame Data Size (N) || || uint12 || 12 || Number of bits to follow || 42 42 || Frame Data || || || N || Bit data from satellite (see data section below) || … … 87 87 Data senders need to decide whether data with bad checksum is transferred or not. While generally data with a bad checksum may be discarded, in disturbed environments even such data may be useful, in particular when parts of the message are common to multiple satellites, or when a portion of the data is already known. 88 88 89 Implementers can freely choose how to group data into a single message. Possibilities (used by proprietary formats already) include: 90 - One Frame per message (easy, but bandwidth wasting) 91 - Time based per satellite system (all simultaneous transmissions of a single satellite system in one block until maximum block size reached) 92 - ... 93 89 94 = NDF as ephemeris transport = 90 95