Cute-1.7 + APD Laboratory for Space Systems

Cute-1.7 + APD Project - Amateur Radio Service -

Small Satellite Project (SSP)

Laboratory for Space Systems (LSS), Tokyo Institute of Technology

Top arrow image Cute Digipeater Service

2006/3/1 updated



*Outline of Service* *Function* *Operation mode* *How to Use* *Operaiton Schedule*


Cute Digipeater service

Cute-1.7 + APD has a digital repeater(Cute Digipeater) service mission using amateur 1200MHz band for uplink, 430MHz downlink mode. Although this mission is simple and experimentaly developed, it will be the first challenge for nano/pico satellites manufactured in a university in Japan. We sincerely welcome your advice to make it wonderful.

outline of this service

Cute Digipeater service uses amateur 1268.5MHz, GMSK, Ax.25 protocol to register your message to the satellite. When you succeed message registration, Cute-1.7 + APD will reply acknolegde imediately. This message will be sent at moderate interval when Cute-1.7 + APD is in an amateur service mission mode. Sine anyone can listern this message, international communication can be realized not only in the same sight of the satellite but also in another sight.

 

Functions of this service

Cute Digipeater service has 2 functions. One is "Multicast mode" and the other is "Uplink mode".

Operation mode of Cute-Digipeater

On nominal operation phase of Cute-1.7 + APD, FM telemetry including nominal mission data(APD sensor data, Thermal data, Gyro data, etc) are periodically downlinked according to the operation schedule. When you want to know the status of Cute Digipeater service, you should check satellite status "serviceMode" within frame 0 of CW telemetry.
Cute-1.7 + APD has only one telemetry downlink line except for CW beacon downlink line. Therefore, 430MHz FM telemetry downlink line are shared between Cute-Digipeater message downlink and another mission data downlink. Because of the above case, Cute-Digipeater service has two following operation modes.

  1. User uplink is enable under downlinking nominal mission data
  2. User uplink is enable under downlinking stored messages(Multicast mode)

The details are shown in the following table. Each number of the operation mode(I and II) corresponds to the value of "serviceMode" within CW telemetry.



How to use Cute-Digipeater service

When you want to uplink the message to Cute-1.7, you should transmit your message by UI frame packet following the above uplink message format.
Below is a example of communication with Cute-1.7.

On nominal operation, Cute-1.7 + APD periodically transmits the following FM packets in the same format as CUTE-I
  JQ1YCC>JQ1YCZ: *************Nominal TLM*********
We will take an example of the case that user uplink is enable under downlinking nominal mission data, as follows.


I. < User uplink is enable under downlinking nominal mission data >

[Check of Frame 0 of CW telemetry: serviceMode = 1]
JQ1YCC>JQ1YCZ: *************Nominal TLM********* (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: *************Nominal TLM********* (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: *************Nominal TLM********* (time interval(ex. 2sec)) -User transmit countmsg command (to acquire the number of stored messages)- JQ1YCZ>countmsg JQ1YCC>JQ1YCZ: Now 0 saved messages (time interval(ex. 2sec)) -User transmit message data- JQ1YCZ>JQ1YCZ ALL ****message data**** JQ1YCC>JQ1YCZ:JQ1YCZ ALL ****message data**** [via cute] (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: *************Nominal TLM********* (time interval(ex. 2sec)) -User transmit multicast command (to conduct multicast on purpose)- JQ1YCZ>multicast JQ1YCC>JQ1YCZ: #01 00 200602181500 JQ1YCZ ALL ****message data**** (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: *************Nominal TLM********* (time interval(ex. 2sec)) -User transmit timeplease command (to acquire onboard time)- JQ1YCZ>timeplease JQ1YCC>JQ1YCZ: Cute Onboard Time is 2007/01/11 06:30:00 (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: *************Nominal TLM********* ...

Next, we will take an example of the case that user uplink is enable under downlinking stored messages(Multicast mode), as follows.


II. < User uplink is enable under downlinking stored messages(Multicast mode) >

[Check of Frame 0 of CW telemetry: serviceMode = 2]
JQ1YCC>JQ1YCZ: #01 17 200602181500 JQ1YCZ ALL Hello, world! (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: #02 17 200602181500 JQ1YCZ ALL Hello, world2! (time interval(ex. 2sec)) -User transmit countmsg command (to acquire the number of stored messages)- JQ1YCZ>countmsg JQ1YCC>JQ1YCZ: Now 5 saved messages (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: #03 17 200602181500 JQ1YCZ ALL Hello, world3! (time interval(ex. 2sec)) -User transmit message data- JQ1YCZ>JQ1YCZ ALL ****message data**** JQ1YCC>JQ1YCZ:JQ1YCZ ALL ****message data**** [via cute] (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: #04 17 200602181500 JQ1YCZ ALL Hello, world4! (time interval(ex. 2sec)) -User transmit timeplease command (to acquire onboard time)- JQ1YCZ>timeplease JQ1YCC>JQ1YCZ: Cute Onboard Time is 2007/01/11 06:30:00 (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: #05 17 200602181500 JQ1YCZ ALL Hello, world5! (time interval(ex. 2sec)) JQ1YCC>JQ1YCZ: #06 00 200701110630 JQ1YCZ ALL ****message data**** ...

operation schedule

We are currently conducting initial checkout of the satellite. Please wait for a while.

Other Information

Because Cute-1.7 + APD has only one downlink frequency, Cute digipeater mission can not be opetated at any time. While in other missions mode, we suspend Cute digipeater service. Please check CW telemetry whether or not this Cute Digipeater accessable. CW telemetry can be listened at any time all over the world. Detailed information about CW telemetry, please see page about CW telemetry format. We also inform on operation schedule page.

Point of Contact

If you have any questions and comments about Cute-Digipeater service, please contact the following address.
POC: cute1.7_question[at]lss.mes.titech.ac.jp

Copyright ©, Tokyo Institute of Technology, All Rights Reserved.

Valid XHTML 1.1 Valid CSS! Level Double-A conformance icon, W3C-WAI Web Content Accessibility Guidelines 1.0