Size your test before you write to us
Data per day, average rate, on-board memory, eclipse energy and thermal cycles over the campaign from your payload profile. Same orbital mechanics as mission control; computed in the browser, nothing is sent until you attach it.
- Period
- — —
- Shadow per orbit
- — —
- β angle
- — —
- Time with a link
- — assumed; network [PENDING]
- Data per day
- — —
- Required average rate
- — platform: [PENDING]
- Memory, one orbit without link
- — platform: [PENDING]
- Average / peak consumption
- — platform: [PENDING]
- Energy per orbit
- — —
- Worst eclipse, from battery
- — platform: [PENDING]
- Thermal cycles in the campaign
- — one orbit with an eclipse = one shadow-sunlight cycle
Plain-text summary
How it is computed
- Orbit. Circular and sun-synchronous, with the inclination J2 requires at that altitude. The shadow is cylindrical and evaluated on 24 dates across the year, keeping the node time fixed: hence the range and the worst case.
- Data link. There is no ground station: data leaves through relay satellites, whose network is [PENDING]. So no link geometry is assumed: you set the time with a link, and memory is sized to hold a whole orbit without one.
- Average rate. One day's data spread over the time with a link. It is a floor: link acquisition, protocol overhead and retries push it up, and we agree the margin with you.
- Energy. Average consumption times the length of the orbit and of the worst eclipse. It does not include the efficiency of the platform's converters, which goes in the ICD.