...
- FlatSat will be accessed remotely (can start this asap in Fall)
- FlatSat uses CSP client, every subsystem has CSP address (access thru ethernet)
- Payload controller fully accessible with reconfiguration of processing chain, data levels and command & control
- Full subsystem capability (baseline)
- ADCS
- Magnetometers
- IMUs
- 5x sun-sensors
- Star-tracker
- Reaction wheels
- Magnetorquers
- Solar Panels
- EPS
- Flight Computer
- Payload controller
- S-band radio
- UHF radio
- ADCS
- Use Flatsat subsystems on our own premise at some point, install dummy masses to simulate the satellite (for example for ADCS testing) – dummy-EM
- May test the imaging of HSI remotely through TCP/IP or Ethernet
- I.e. test image capturing and storage à remote à transmit the downlink capability à then validate the images back at NTNU
- UHF capability also to be tested – downlink TM, uplink TT&C
- We don’t buy a standard engineering model (flatsat instead as well as flight model)
- Integration of payload will happen under supervision of NA technical representatives
- Transport the FM to Trondheim, will be sent to launcher from Trondheim
- Only minimum environmental testing necessary: shake & bake (vibrations)
- Radiation test is not necessary
- Certainly may delay the timeline and introduce unknown costs
- If FM breaks or something goes wrong, consider it as an expensive EM
- How to test the ADCS? In Helmholtz coils, sun-sensor with FM?
- We verification and validation of our/NA’s controller algorithm
- Shall use FFI, NTNU facilities etc. for environmental tests
- Use clean room at NTNU for integration
...