Changes between Version 31 and Version 32 of NDF

Timestamp:

Nov 2, 2018, 9:03:15 AM (5 years ago)

Author:

stoecker

Comment:

Some cleanups

NDF

@@ -38 +38 @@
 || Signal Type         || || uint5  ||  5 || Signal type specification, index from MSM signal mask bit field (0..31, see DF395) ||
 || Epoch Time          || || uint30 || 30 || Epoch time, specific for the satellite system always 30 bits (see table below) ||
-|| Continuous Tracking || || bit(1) ||  1 || Tracking this satellite frame data was continous (1 = continous, 0 not continuos or unset) ||
+|| Continuous Tracking || || bit(1) ||  1 || Tracking this satellite frame data was continuous (1 = continuous, 0 not continuous or unset) ||
 || Frame Data Size (N) || || uint12 || 12 || Number of bits to follow ||
 || 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.
 
+Implementers can freely choose how to group data into a single message. Possibilities (used by proprietary formats already) include:
+- One Frame per message (easy, but bandwidth wasting)
+- Time based per satellite system (all simultaneous transmissions of a single satellite system in one block until maximum block size reached)
+- ...
+
 = NDF as ephemeris transport =