Changeset 433 in ntrip for trunk/BNC/bnchelp.html
- Timestamp:
- Mar 30, 2007, 4:15:12 PM (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r429 r433 50 50 Furthermore, BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. 51 51 </p> 52 <p><b> Warning</b><br>52 <p><b>Resources</b><br> 53 53 BNC needs access to the Internet with a minimum of about 2 to 6 kbits/sec per stream depending on the stream format. You need to make sure that you have always the necessary bandwidth available. BNC has the capacity to retrieve hundreds of GNSS data streams simultaneously. Please be aware that it is a powerful tool that may generate a heavy workload on the NTRIP broadcaster side depending on the number of streams it requests. We suggest to limited the number of streams where possible to avoid unnecessary workload. 54 54 </p> 55 <p> 56 Note that running BNC requires that the clock of the hosting computer is synchronized. 57 </p> 58 55 59 <p><a name="options"><h3>B - Options</h3></p> 56 60 <p>
Note:
See TracChangeset
for help on using the changeset viewer.