Date: Tue, 05 Sep 2000 09:00:01 +0200 From: mike.rupprecht@t-online.de (Mike Rupprecht) To: Mineo Wakita [je9pel@jamsat.or.jp] Cc: amsat-bb@amsat.org Subject: [amsat-bb:34502] Re: OPAL Beacon Hi Mineo, Beacon 1 send an AX.25 packet frame containing OPAL's current time stamp and a 2 bit summary of OPAl's health. These 2 bits are defined as : 00 = all systems working nominal 01 = voltage to high 10 = temperature to high 01 = voltage to low See also : http://ssdl.stanford.edu/opal/Operations/beacon.html 73, Mike DL1LSZ ------------------------------------------------ Name : Mike Rupprecht, DL1LSZ, AMSAT-DL #9502099 Mail : mail@mike-rupprecht.de URL : http://www.mike-rupprecht.de QTH : Hoechst, GERMANY, Loc.: JN49LS ------------------------------------------------ Mineo Wakita schrieb: > > Today Sep 4, I received some digital beacons from OO-38(OPAL). > She transmitted them every one minute with the weak signals. > 437.100MHz(+/- doppler), 9600bps_FSK, KISS_mode > Does someone know what this numerical sequence mean ? > > KF6RFX>CQ (03 Sep 2000 23:13:28 UTC) [UI R]:OPAL 18:6998020925 [01] > KF6RFX>CQ (03 Sep 2000 23:16:28 UTC) [UI R]:OPAL 18:6998020925 [01] > KF6RFX>CQ (04 Sep 2000 00:50:28 UTC) [UI R]:OPAL 18:7220873266 [01] > KF6RFX>CQ (04 Sep 2000 00:51:28 UTC) [UI R]:OPAL 18:7220873266 [01] > > ---------------------------------------------- > Name : JE9PEL/Mineo Wakita, Member of JAMSAT > Mail : je9pel@jamsat.or.jp > URL : http://www.ne.jp/asahi/hamradio/je9pel/ > QTH : Yokohama Japan, GL:PM95TJ > Date : Sep 4, 2000 > ---------------------------------------------- ==== From: "Jay, kf6rmg" [kf6rmg@hotmail.com] To: amsat-bb@amsat.org Subject: [amsat-bb:34503] Re: OPAL Beacon Date: Tue, 05 Sep 2000 00:48:40 PDT Are you sure that [01] means voltage too high? According to the beacon log at http://ssdl.stanford.edu/opal/Operations/opal/index.html the beacon has reported [01] for most of its lifetime and has never reported [00]. 73, Jay, KF6RMG P.S. OPAL telemetry logs are available at the above website, but there is no new info there after late May. ==== [Reference] http://ssdl.stanford.edu/opal/Operations/beacon.html > Opal Beacon Summary > > Opal broadcasts two beacons. Both > are at 437.100 MHz. > > * Beacon 1 - An AX.25 packet > beacon containing Opal's > current time stamp and a 2 bit > summary of Opal's health. > Example beacon: > > OPAL 0:0009948696 [01] > > "0:0009948696" is the time > stamp. It is the number of > clock ticks since last hard CPU > reset onboard Opal. The number > of seconds can be calculated > by: > > seconds = (number of > ticks> / ( 4096 ) > > The two bit beacon "[01]" is a > summary of health. The states > correspond to: > > 00 - > 01 - > 10 - > 11 - > > * Beacon 2 - A continuous wave > pulse that encodes the two bit > beacon. More to follow (when > we're not exhausted!). Check > out the paper that was written > on it: Development of a > Satellite Beacon Receiving > Station ==== Date: Wed, 13 Sep 2000 07:03:24 +0200 From: mike.rupprecht@t-online.de (Mike Rupprecht) To: Mineo Wakita [je9pel@jamsat.or.jp] Cc: amsat-bb@amsat.org, jwc@stanford.edu, btwiggs@leland.stanford.edu Subject: [amsat-bb:34748] Re: OPAL Beacon Hi Mineo, Yes, the description of the 2 bits is right. The time stamp changes only every pass: 05.09.2000 0535 UTC OPAL 18:1445291277 [01] 05.09.2000 0715 UTC OPAL 18:1668142770 [01] 05.09.2000 0854 UTC OPAL 18:1991000565 [01] To the time stamp I have the following acceptance, but I'm not sure: OPAL 18:1991000565 [01] XX:XXZZZZZZZZ Z : The difference is average 22855000 ticks. These are about 5580 seconds (22855000 / 4096) -> 93 minutes. Is this the period of opal? 73, Mike ------------------------------------------------ Name : Mike Rupprecht, DL1LSZ, AMSAT-DL #9502099 Mail : mail@mike-rupprecht.de URL : http://www.qsl.net/dl1lsz QTH : Hoechst, GERMANY, Loc.: JN49LS ------------------------------------------------ Mineo Wakita schrieb: > > I received again some digital beacons from OO-38(OPAL). > She transmitted them every 10 seconds with 437.100MHz > (+/- doppler), and 9600bps_FSK. Time is UTC: > > KF6RFX>CQ [11 Sep 2000 23:50:00] [UI R]:OPAL 19:2888678815 [01] > KF6RFX>CQ [11 Sep 2000 23:50:10] [UI C]:OPAL 19:2888678815 [01] > KF6RFX>CQ [11 Sep 2000 23:50:20] [UI R]:OPAL 19:2888678815 [01] > KF6RFX>CQ [11 Sep 2000 23:50:30] [UI R]:OPAL 19:2888678815 [01] > KF6RFX>CQ [11 Sep 2000 23:50:40] [UI R]:OPAL 19:2888678815 [01] > > In the URL, http://ssdl.stanford.edu/opal/Operations/beacon.html > > 'Opal Beacon Summary' say : > > Beacon 1 - An AX.25 packet beacon containing Opal's current > > time stamp and a 2 bit summary of Opal's health. > > Example beacon: OPAL 0:0009948696 [01] > > > > "0:0009948696" is the time stamp. It is the number of clock > > ticks since last hard CPU reset onboard Opal. The number of > > seconds can be calculated by: > > > > seconds = (number of ticks> / ( 4096 ) > > Q1. I don't know why the above today's data doesn't change. > Q2. Do the next two bit health states beacon are right ? > > > 00 = all systems working nominal > > 01 = voltage to high > > 10 = temperature to high > > 11 = voltage to low > > ---------------------------------------------- > Name : JE9PEL/Mineo Wakita, Member of JAMSAT > Mail : je9pel@jamsat.or.jp > URL : http://www.ne.jp/asahi/hamradio/je9pel/ > QTH : Yokohama Japan, GL:PM95TJ > Date : Sep 12, 2000 > ----------------------------------------------