FEP SS

1
FEP S/S
Smog - Demo
AGF-FEP Front End Processor Subsystem Technical
presentation 
2
FEP S/S

• Interface of communication with the FEP HW.
• Send and receive messages to/from the FEP HW.
• Communication with the FEP HW Scheduler.
• Ensure the persistence of scheduler for telemetry
  acquisitions.
• Downloading of FEPs treated files via ftp from
  FEP HW.

3
FEP S/S

• FEP

Socket communication
Sending commands
FEP S/S

Receiving commands
Product transfer by ftp.
4
Remote interface

• RQS remote mgr
• RQC
• MOP tm
• MOP rs
• OSC
• ASC 0 ERS_HR_fs.cfg default_rs.cfg 1117112780
  1117112840

5
FEP HW

• The software on the FEP workstation will consist
  of 4 modules
  
  
  
• Hardware (HW) interfaceretrieving the bitstream
  from the Demodulator making use of the COTS
  device driver
  
  
• Telemetry (TM) moduleframe synchronisation,
  Reed Solomon error detection and correction,
  demultiplexing the virtual channels, annotation
  with Product Confidence Data (PCD), dissemination
  or/and storage
• Monitoring and Control (MC) moduleconfiguration
  management, command/response routing, status
  gathering, scheduling
  
  
• Graphical User Interface (GUI)displaying of
  status info, commanding and configuring
  
  
  

6
Remote operation

• Request/Release Service required to do anything
• Request/Release Control
• required to have exclusive control over system.
• GUI can overrule remote control
• Monitor Status Parameters
• Get status information from individual components
  (tm, rs, dm)
• Configurations
• List configuration files, Read configuration
  file, Apply new config file
• Start/Stop individual components (tm, rs)
• Scheduling
• Open function, Add, Modify, Delete scheduling
  requests, Start scheduler

7
Presentation of the Product (Dual Mission Support)

• Both Demodulator and Test Modulator are
  predefined with the two required missions
• Both FEP and IQ controlling PCs have
  configuration options to select one of the two
  missions
• All product component interfaces are such that
  they can support the interface cabling for the
  two missions simultaneously

8
How it works (FEP)
9
FEP HW Scheduler

• Automatic scheduling for predefined missions is
  supported.
• Entries maintained in time sorted list
• A scheduling entry defines Mission configuration
  parameters for DEMOD, FrameSync and Reed-Solomon
  Functions PLUS start and stop times
• When scheduling is started, then at time of first
  schedule request the scheduled configuration is
  applied and all functions started
• When end time arrives, all functions are stopped
  and entry removed from scheduling list

10
Scheduling (active)
11
Flexibility

• Both the FEP and IQ applications are designed to
  be extra flexible through configuration
• In case other missions need to be supported then
  (using other TestMod/Demod) the FEP and IQ
  applications can simply be reconfigured to
  accomodate new mission parameters.