Technical Details for Reinstatement

0439-EX-CN-2017 Text Documents

Aerospace Corporation, THE

2017-06-10ELS_193393

THE RF TECHNICAL DETAILS IN THIS LICENSE REINSTATEMENT ARE IDENTICAL TO THOSE IN THE GRANT 0454-EX-RR-2015 [Call Sign: wf9xvn], EXHIBITS INFORMATION: 0423-EX-ST-2012 AeroCube-4 test. The purpose of the operation is to conduct research regarding the space application of microelectronic technologies. The operation includes a demonstration of principles of the physics of the low-earth-orbit space environment and its effects on microelectronics. Three AeroCube-4 satellites comprise this flight to study the physics of formation flying. The AeroCube-4 is a PICOSAT class satellite, weighs less than 1.3 KG and is 4x4x4 inches in dimension (see “satellite design” Exhibit). Launched on NROL-36, September 13, 2012. The orbit is 490 x 778 km with 66 degree inclination. Orbital debris analysis predicts a lifetime between 12.3 and 21.2 years (see “orbit lifetime” Exhibit). The AeroCube-4 satellite has two radios for redundancy. The first is the “tried- and-true” Freewave Technologies, Inc. FGRM radio inside which outputs 2 Watts. It has a fixed frequency (i.e. not hopping or spread spectrum) at 914.7 MHz (see “Freewave bandwidth” Exhibit) so that the ground station can quickly link up with the satellite rather than waiting for the hopping sequence to sync up. The second radio is called the AdvRadio that is built by The Aerospace Corporation around a Texas Instruments CC1101 transceiver chip. It also operates at a fixed 914.7 MHz frequency (see “AdvRadio bandwidth” Exhibit) and outputs 1.5W. The satellite chooses which radio to use - both are not used at the same time. Both radios attach to separate omni-directional patch antennas on the AeroCube-4. We have the pattern calculated and tested but use -10dB as the gain for 90% of the sphere area (see “satellite antenna pattern” Exhibit). Upon the AeroCube-4 satellite ejection, it was powered-on. However the radio is in receive-mode only. As the satellite flies over a ground station, the station will be continuously beaconing upwards towards the satellite. When the satellite radio hears the beacon, along with the proper serial number code, it will respond and a link will be established. At that point, the ground station will ask the satellite for whatever information it wants typically state of health log files, images from the cameras or other onboard telemetry. The satellite will respond by down-loading the requested information. When the link is lost due to the satellite passing out of view while the satellite was transmitting, the satellite will try 256 times to complete the last packet transmitted. If each packet is 72 bytes long and the radio data rate is 38.4 Kbaud, then it will try for only a couple of seconds before the 256 attempts are exceeded. At that point the satellite will go back into a passive receive mode again and again wait for the next beacon from a ground station with the correct serial number. We would like to use two types of ground stations to communicate with the AeroCube-4 satellite. The first is a fixed 16” dish antenna at The Aerospace Corporation in El Segundo, CA, near LAX airport. It has 30 dB gains, 5 deg beam width and also would use a 2W Freewave FGRM radio or an AdvRadio on the feed horn. The second ground station is a portable 2-meter diameter dish. This has 22 dB gain, a 10 deg beam width and would use a Freewave FGRM radio or an AdvRadio with the output passed through a 9 W amplifier. This portable station we would like to use somewhere that is RF quiet and also advantageously located for maximum satellite coverage. A typical satellite pass is 5 minutes long, twice per day - so the system spends a lot of time not in use. We requesting approval for the same remote locations already approved in STA 0153-EXST-2013.

We are currently requesting an reinstatement to STA 0454-EX-RR-2015 because the AeroCube-4 satellites are still performing well and the science is very good. We predict that their usefulness will last an additional 12 months.


Document Created: 2017-06-10 09:24:49
Document Modified: 2017-06-10 09:24:49
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC