PART3 » History » Version 46

« Previous - Version 46/83 (diff) - Next » - Current version
JANVIER, Thibault, 03/23/2016 08:32 AM


PART 5 : Implementation and results.

.......................


1 - Starting point.

a - Receiver scheme and milestones.

.......

b - Quid about LabVIEW.

.......

Input : GPS signal of sampling frequency 38.192 MHz at intermediate frequency 9.55 MHz from CD [1] under GNSS_signal_records/GPSdata-DiscreteComponents-fs38_192-if9_55.bin

c - Local C/A code generation.

The files involved are :
- CA_Code.vi
- CA_generatorG1.vi
- CA_generatorG2.vi


2 - Acquisition.

See the UML Diagram of Section 2 under : Acquisition.PNG

The files involved are :
- Main_Acquisition.vi : SnapAcquisition.PNG
- Acquisition_subVI.vi : SnapAcquisitionSub.png
- CA_Code.vi

Justification acquisition method in terms of accuracy and time execution
Justification of the step of 500Hz
Methods to avoid the data bit transition while running acquisition
Frequency refine is needed for the PLL of the tracking to converge
Definition of the threshold and how it is implemented

.......

...........


3 - Tracking.

Justification of the DLL discriminator
Correction of the blocksize to read as a function of the doppler shift

See the UML Diagram of Section 2 under : Track.PNG

The files involved are :
- Main_Carrier_Tracking.vi : SnapTracking.png
- CalcLoopCoeff.vi : SnapCalcLoopCoeff.PNG

.......

...........


4 - Navigation Data decoding.

See the UML Diagram of Section 4 under : NavigationData.PNG.

a - Delimiting subframes.

The files involved are :
- FindPreamble.vi
- TestFindPreamble.vi : SnapTestFindPreamble.PNG
- GenerateFrame.vi
- ParityCheck.vi : SnapParityCheck.png

Figure 5. : Cross-correlation between navigation frame and local preamble. Figure 5. : Subframes with index of delimitation.

b- Decoding ephemeris and information within the frame.

The files involved are :
- Ephemeris.vi
- BinaryArrayToDecimal.vi : SnapBinaryArrayToDecimal.PNG
- twosComp2dec.vi : SnapTwosComp2dec.PNG
- ParityCheck.vi_ : SnapParityCheck.png
- TestEphemeris.vi


5 - Elementary blocks for localization.

See the UML Diagram of Section 5 under : Localization.PNG

a - Satellite position.

The files involved are :
- SatellitePosition.vi
- TestSatellitePosition.vi : SnapTest_satellite_position.PNG
- Check_time.vi : SnapCheckTime.PNG


Figure 5. : Interface with ephemeris as input and illustration of the satellite position.

b - Pseudoranges.

The file involved is :
PseudorangesComputation.vi

c - Least Square solution for position determination.

The files involved are :
- LeastSquarePosition.vi
- SatelliteRotationECEF.vi : SnapSatelliteRotationECEF.PNG
- toTopocentric.vi : SnaptoTopocentric.png
- CartesianToGeodetic.vi : SnapCartesianToGeodetic.png
- TroposphericCorrection.vi

6 - Receiver position computation.

See the UML Diagram of Section 6 under : Receiver.PNG

The files involved are :
- ComputeReceiverPosition.vi
- NavigationProcess.vi
- CartesianToGeodeticForUTM.vi : SnapCartesianToGeodeticForUTM.png
- CartesianToUTM.vi

7 - Complete UML Diagram of the receiver.

The UML diagram with real size is available under : UMLDiagram.png

Here is a small overview of the structure :


References :
[1] K. Borre, D. M. Akos, N. Bertelsen, P. Rinder, S. H. Jensen, A software-defined GPS and GALILEO receiver