SAFIR-M (Rubin-2) decoded
(25 Dec 2002) SAFIR-M Page From SAFIR-M Web Page
(26 Dec 2002) Oliver Amend SAFIR-M Status per 26.12.2002
(28 Dec 2002) Mineo Wakita SAFIR-M (Rubin-2) decoded
(28 Dec 2002) Mineo Wakita SAFIR-M telemetry decoded
(31 Dec 2002) A Thomas Decoding SAFIR-1 from TRACE ON
( 2 Jan 2003) Masahiro Arai Re: Decoding SAFIR-1 from TRACE ON
( 9 Jan 2003) Mineo Wakita Informations about SAFIR-M
(10 Jan 2003) Oliver Amend AO-49 / Invitation to Participation in Uplink test
(11 Jan 2003) Oliver Amend Re: AO-49 / Invitation to Participation in Uplink test
(12 Jan 2003) Mineo Wakita Intervals of SAFIR-M beacon
(13 Jan 2003) Don Woodward RUBIN-2 INFO packets captured and translated...
(13 Jan 2003) Mineo Wakita Re: RUBIN-2 INFO packets captured and translated...
(14 Jan 2003) Oliver Amend AO-49 / Any signals observed on 13th?
(16 Jan 2003) Mineo Wakita Received many digital signals on 16 Jan
(26 Jan 2003) Mineo Wakita Analysis of the telemetry
( 6 Feb 2003) Oliver Amend AW: saphir-m AO49 not heard???
--------
Subject: SAFIR-M (Rubin-2) decoded
From: Mineo Wakita
Date: Thu, 28 Dec 2002 22:45:56 +0900
To: amsat-bb@amsat.org
I decoded the digital signals from SAFIR-M (Rubin-2)
using PAYLOAD-A keps with 145.825MHz 9600bps, FSK, mode KISS
as follows. (21228saf.kss, 998 bytes)
http://www.ne.jp/asahi/hamradio/je9pel/21228saf.zip
Decoded by Exterm at 07:35-07:44 UTC, 28 Dec 2002
> 0000006@006880244@00
Decoded by WiSP and Kiss2asc at 09:12-09:26 UTC, 28 Dec 2002
(Replaced the escape sequences by dots)
> fm DP0AIS to INFO via .x"(.-4 ).060:-2 :9.902-4 7.2[82-9 4627:.-9
> #$).& 47.791-4 :.77.1-7 ctl I30^ pid 72
> d nf Rtbhn,2
> fm DP0AIS to DATA0 via .x*268 !7092. ......-12* !.*268 $#.68-13
> ......-12* !.*...-9 +76:.. ctl I10^ pid 32
> ,20V.T.4,4Vnlt: 4,48V.T.@jjt: 04,6V.Bht,Drrnr: 000.
> fm DP0AIS to DATA1 via .x....-8 .."...-1 .....!-8 ..*268 $#.68-13
> ......-12* !.*...-9 +76:.. ctl I10^ pid 32
> fm DP0AIS to MH0 via .x&$.)-9 )$....-6 47..60-12 ..921.-12 [[[[[.
> -8 ...... ......-12 ...[[[-12 ctl I34+ pid 78
> ,00 ,020 ,020 4860.xxxxxx,00 ,020 ,020 4860.xxxxxx,00 ,020 ,020
> 4860.xxxxxx,00 ,020 ,020 4860.xxxxxx,00 ,020 ,020 4860.xxxxxx,00 ,
> 020 ,020 4860.xxxxxx,00 ,020 ,020 4860.
> fm DP0AIS to MH1 via .x&$.)-9 )$....-6 47..60-12 ..921.-12 [[[[[.-8
> ...... ......-12 ...[[[-12 ctl I34+ pid 78
> ,00 ,020 ,020 4860.xxxxxx,00 ,020 ,020 4860.xxxxxx,00 ,020 ,020
> 4860.xxxxxx,00 ,020 ,020 4860.xxxxxx,00 ,020 ,020 4860.xxxxxx,00 ,
> 020 ,020 4860.xxxxxx,00 ,020 ,020 4860.
bottom top
Cf.1
From SAFIR-M Web Page
http://hft.fh-pforzheim.de/download/aatis/
SAFIR-M frequencies and modes:
Downlink 145,825 MHz 9600 Bd MSK G3RUH
Uplink 435,275 MHz 1200 Bd AFSK Bell 202
The payload operates only when the solar collector generates power,
i.e. when the satellite is in the sunshine.
Operational data on the downlink is transmitted in UI frames
(unnumbered information) according to AX.25 standard. User data on
uplink and downlink may consist of arbitrary HDLC frames.
Each valid HDLC frame detected on the uplink triggers a downlink
transmission of the last 4 kByte of received user data. In addition,
the last 512 kByte of received user data is stored and can be recalled
by the satellite command station.
A failure in the processor hardware causes an erroneous transmission
of operational data. Bit 0 is set permanently low in both header and
body of the frame. Subsequent processing like stuffing, CRC and
scrambling is done correctly so that valid HDLC frames are generated.
Nevertheless most AX.25 monitoring systems do not display these frames.
The failure may be repaired in future. User data should remain
uninfluenced by the failure and should be repeated correctly.
We encourage you to monitor the downlink frequency with an FM receiver
and a PC sound device connected directly to its discriminator output,
or a 9k6 TNC in KISS mode logging the raw KISS stream. You may send
received bursts to DG6BCE@aatis.de.
New: Tom HB9JNX wrote a command line tool to decode the defective
beacon frames. It works with a TNC-2 in KISS mode. See link in the
'Tools' section.
Thank you for your support!
bottom top
Cf.2
Subject: [amsat-bb:64683] SAFIR-M Status per 26.12.2002
From: Oliver Amend
Date: Thu, 26 Dec 2002 13:27:55 +0100
To: amsat-bb@amsat.org
The analysis of a recorded WAV file of a pass over Germany
from 24.12.2002, 05:38 - 05:40 UTC shows unexpected effects:
a) The TX clock rate of the SAFIR-M 9k6 modem seems to have
9844 Baud instead of expected 9600 Baud. A receive of
frames may be still possible with high RX fieldstrength
so that the DPLL of the ground equipment can lock within
its tolerance range.
b) Additional it seems that the data line for bit 0 to the
external memory of the PIC is stucked to "0", so that the
parts of the transmitted MH frames could be damaged. CRC,
NRZI, stuffing and scrambling are done correctly from the
faulty data source.
These effects will be analysed within the next passes.
For further examination, Martin DG8UAU has written a small
software "SAFIR-M Decoder" (28kB) to allow a decoding of the
received DATA0 frames. It is available on the SAFIR-M Homepage
http://amend.gmxhome.de in the section Aktuelles.
The news information are also available there from now on as
english translation...
73 de Oliver, DG6BCE
SAFIR-M Homepage: http://amend.gmxhome.de
Mail pse to : DG6BCE@aatis.de
bottom top
Cf.3
I, JE9PEL, decoded SAFIR-M telemetry by using two programs
'Hex Editor' and 'SAFIR-M Decorder' as follows.
These programs are available at the bottom of this page.
[09:12-09:26 UTC, 28 Dec 2002]
+++++++++++++++++++++++++++++++++++++++
SAFIR-M Telemetrie (DP0AIS)
Raw Data: 0000006D006B82244B00
Temperature Board: 54.5 C
Temperature PA: 53.5 C
Voltage [Accu]: 13.0 Volt
Voltage [5.5V]: 5.48 Volt
Voltage [3.3V]: 3.31 Volt
Biterror: 00 Errors
+++++++++++++++++++++++++++++++++++++++
bottom top
Cf.4
Subject: [amsat-bb:64797] Re: Decoding SAFIR-1 from TRACE ON
From: Masahiro Arai
Date: Thu, 02 Jan 2003 01:29:26 +0900
To: A Thomas
CC: amsat-bb
SAFIR-M is transmitting only even numbers due to bit0=0 problem now.
This means SAFIR-M may transmit incorrect data. Non hex code character
should change. If you find '@'(=40hex) in the telemetory, you must
change '@' to 'A'(=41hex).
The correct telemetry on Andy, G0SFJ's trace file at 1859utc 31/12/02
is 000000A0008D8A244B00. Another odd numbers may be in the telemetry.
The accident error is +1.
trace data (hex) 30 30 30 30 30 30 40 30 30 30 38 44 38 40 32 34 34 42 30 30
ascii 0 0 0 0 0 0 @ 0 0 0 8 D 8 @ 2 4 4 B 0 0
correct data (hex) 30 30 30 30 30 30 41 30 30 30 38 44 38 41 32 34 34 42 30 30
^^ ^^
corecct ascii 0 0 0 0 0 0 A 0 0 0 8 D 8 A 2 4 4 B 0 0
^ ^
Here is the table ascii/hex data.
ascii hex data
0 30 may 31(=1)
1 31 *
2 32 may 33(=3)
3 33 *
4 34 may 35(=5)
5 35 *
6 36 may 37(=7)
7 37 *
8 38 may 39(=9)
9 39 *
A 41 *
B 42 may 43(=C)
C 43 *
D 44 may 45(=E)
E 45 *
F 46
@ 40 change 41(=A)
*: not seen in telemetry (trace file)
I don't know why non hex characters (v,*) are in 1829utc 30/12/02
telemtry, 0000008v008*88244b00.
73, JN1GKZ Masa
jn1gkz@jamsat.or.jp http://www.ne.jp/asahi/m-arai/gkz/
bottom top
(Original Message)
> Subject: [amsat-bb:64787] Decoding SAFIR-1 from TRACE ON
> From: A Thomas
> Date: Tue, 31 Dec 2002 19:22:50 -0500
> amsat-bb
>
> i thought that those of you who can only receive frames using TRACE ON
> might like to see how I have managed to decode the telemetry packet from
> the raw hex received:
>
> How to decode data frames from safir-1
>
> 1. Look for the hex sequence starting
>
> 88 82 a8 82 62
>
> i.e. D = 88 hex to dec /2
> A = 82 hex to dec /2
> T = a8 hex to dec /2
> A = 82 hex to dec /2
> 1 = 62 hex to dec /2
>
> Convert these hex to decimal, divide by 2 and enter as ascii.
> These correspond in decimal to the ascii codes for DATA1
>
> 2. Locate the last 21 hex items. Discard the last one and take the
> immediate preceding 20. ( at the moment) these start with 30 six times ie
> 30 30 30 30 30 30
>
> 3. using Win calculator, enter one by oneall the 20 hex codes into the
> calculator and check the decimal box: this returns 20 decimal ascii codes.
> Enter each one into Word by pressing left-ALT then the ascii using Numeric
> keypad then release ALT.
>
> 4. Copy the exact stream including punctuation (20 items) into the Safir-1
> decode program.
>
> This method has produced the following:
>
> Heard at 1829utc 30/12/02:
>
> SAFIR-M Telemetrie (DP0AIS)
> Raw Data: 0000008v008*88244b00
> Temperature Board: 4.0 C
> Temperature PA: 4.0 C
> Voltage [Accu]: 13.6 Volt
> Voltage [5.5V]: 5.48 Volt
> Voltage [3.3V]: 3.31 Volt
> Biterror: 00 Errors
>
> Heard at 1859utc 31/12/02:
>
> SAFIR-M Telemetrie (DP0AIS)
> Raw Data: 000000 0008d8 244b00
> Temperature Board: 0.0 C
> Temperature PA: 70.5 C
> Voltage [Accu]: 00.8 Volt
> Voltage [5.5V]: 5.48 Volt
> Voltage [3.3V]: 3.31 Volt
> Biterror: 00 Errors
>
> 73 de andy G0SFJ
bottom top
Cf.5
Informations about SAFIR-M and actual operational information
and 'SAFIR-M Decorder' are published of the following sites:
SAFIR-M Homepage : http://amend.gmxhome.de
SAFIR-M Operational: http://hft.fh-pforzheim.de/ao49/
Received at 06:50 UTC, 9 Jan 2003:
0000008@008680244B00
0000008A008680244B00
^
+++++++++++++++++++++++++++++++++++++++
SAFIR-M Telemetrie (DP0AIS)
Raw Data: 0000008A008680244B00
Temperature Board: 69.0 C
Temperature PA: 67.0 C
Voltage [Accu]: 12.8 Volt
Voltage [5.5V]: 5.48 Volt
Voltage [3.3V]: 3.31 Volt
Biterror: 00 Errors
+++++++++++++++++++++++++++++++++++++++
Received at 07:35 UTC, 28 Dec 2002:
0000006@006880244@00
0000006A006880244A00
^ ^
+++++++++++++++++++++++++++++++++++++++
SAFIR-M Telemetrie (DP0AIS)
Raw Data: 0000006A006880244A00
Temperature Board: 53.0 C
Temperature PA: 52.0 C
Voltage [Accu]: 12.8 Volt
Voltage [5.5V]: 5.48 Volt
Voltage [3.3V]: 3.30 Volt
Biterror: 00 Errors
+++++++++++++++++++++++++++++++++++++++
SAFIR-M Decorder: ttp://hft.fh-pforzheim.de/ao49/
Hex Editor : http://www.hhdsoftware.com/hexeditor.html
For more info. : http://www.ne.jp/asahi/hamradio/je9pel/safir-m2.htm
Zip file : http://www.ne.jp/asahi/hamradio/je9pel/30109a49.zip
bottom top
Cf.6
Subject: AO-49 / Invitation to Participation in Uplink test
From: Oliver Amend
Date: Fri, 10 Jan 2003 17:58:06 +0100
The team of SAFIR-M (AATiS OSCAR-49) invites you to
participate in a test of the uplink conditions for AO-49 SAFIR-M.
To get more information about the behaviour of AO-49 SAFIR-M
we kindly ask for tests with different uplink powers. By the
use of the onbord implemented MH0 and MH1 reports of the SAFIR-M
a test result is also direct available for the user.
At the moment, there is still one known problem in the down-
linked data of the messages (bit0 is fixed to "0"). A SW upload
for correction is planned but will still need some time of
preparation.
The SAFIR-M digipeating functionality is not affected by this
fault and can be monitored with every 2m 9k6 equipment!
Details about possibilities to receive and even decode the
data are discribed at the following links:
http://hft.fh-pforzheim.de/ao49/
http://www.ne.jp/asahi/hamradio/je9pel/safir-m2.htm
The onbord implemented MH0 and MH1 list (normaly) looks
as follows:
[001: DP0AIS > MH0 UI^]
MH/RSSI min max sec
DG6BCE-00 -070 -070 0006
DG6BCE-04 -070 -070 0023
DG6BCE-03 -070 -070 0052
DG6BCE-03 -070 -070 0076
DG6BCE-02 -120 -117 0109
DG6BCE-01 -120 -117 0133
DG6BCE-01 -120 -117 0155
xxxxxx-00 -120 -120 1121
[001: DP0AIS > MH1 UI^]
MH/RSSI min max sec
xxxxxx-00 -120 -120 1121
xxxxxx-00 -120 -120 1121
xxxxxx-00 -120 -120 1121
xxxxxx-00 -120 -120 1121
xxxxxx-00 -120 -120 1121
xxxxxx-00 -120 -120 1121
xxxxxx-00 -120 -120 1121
xxxxxx-00 -120 -120 1121
Description:
The used Call and SSID of the last 2 x 8 received messages are
displayed with the related min and max RX power within this
message in dBm and the elapsed time in seconds.
Note: Only messages with destination "DP0AIS" wil be listed
here.
This feature was implemented to allow a simple check of the
used ground station equipment and shall allow a couple of
more experiments...
The uplink equipment could be quite simple: even a transmitter for
435,275 MHz, up to 30 W of TX-power, antenna, 1k2 AFSK modem/TNC.
To verify this functionality, we request the usage of SAFIR-M
digipeating function
* with different uplink power
* with / without correction of the doppler shift
And reports, containing
* day / Time in UTC
* station location
* rig description (antennas, powers, gains/losses)
* used uplink power
* used Uplink-QRG
It is helpful to include some of these information in the
transmitted data packet as showed in the example:
DK2SM>DP0AIS: JO42rl 80W 430269 kHz
DK2SM>DP0AIS: JO42rl 25W 430279 kHz
The actual TLEs are available on the CELESTRAK database under
TLE-NEW and "RUBIN 2" with the NORAD #27605.
We kindly request to provide us with monitored SAFIR-M
beacon messages and reports of uplink experiments so that
we can analyse this feature.
For any questions please do not hesitate to contact us.
Please address any reports to DG6BCE@aatis.de
tnx & 73 de Oliver, DG6BCE
--------------------------------------------------------------------------
Mailto: DG6BCE@aatis.de
AATiS-Homepage: http://www.aatis.de
SAFIR-M homepage: http://amend.gmxhome.de
SAFIR-M Operational: http://hft.fh-pforzheim.de/ao49/
Mineo Wakita / JE9PEL: http://www.ne.jp/asahi/hamradio/je9pel/safir-m2.htm
--------------------------------------------------------------------------
bottom top
Cf.7
Subject: AW: Re: AO-49 / Invitation to Participation in Uplink test
From: Oliver Amend
Date: Sat, 11 Jan 2003 11:53:34 +0100, 11 Jan 2003 19:53:34 JST
To: "Mineo Wakita" [ei7m-wkt@asahi-net.or.jp]
Dear Mineo,
Sat, 11 Jan 2003 19:33:01 +0900 wrote:
> I translated this message from English into Japanese
> and posted it to JAMSAT-BB and my Web-Page.
Thanks for this service !
> Question 1, Uplink 435.275 MHz 1200 Bd AFSK ?
> Downlink 145.825 MHz 9600 Bd MSK ?
> (+/- doppler)
Correct. For downlink the so-called "G3RUH-TNCs"
can be used. Henning DF9IC has developped some
years ago a modified & enhanced version, which is
also well known here in Europe as G3RUH/DF9IC-TNC,
but fully compatible.
This technologie was the base for the communication
design of SAFIR-M and Thomas HB9JNX is also active
since years in the "german-based" radio amateur
community for digital communications development
in the BAYCOM-team. He has programmed the EPLD
in VHDL which is responsible for the digipeating
feature.
> Question 2, Can we send any data to AO-49 ?
> Is Digipeat Callsign 'DP0AIS' ?
Any AX.25-confom UI telegram with proper HDLC frameing
can be sent to SAFIR-M, even SABM and DISC.
Any Source- or Destination Call can be used.
Its a very stupid or simple digipeater...
In the message body, any binaries or texts as f.e.
APRS strings or messages can be included.
73 de Oliver, DG6BCE
bottom top
Cf.8
I observed the intervals of SAFIR-M beacon.
These were every approximately 55 seconds.
Jan 12, 2002
UTC Hex Editor
------------- --------------------
04:49:20 AOS
04:50:15 ---
04:51:10 ---
04:52:05 ---
04:53:00 Decoded 0000008800848B244B00
04:53:55 ---
04:54:50 Decoded 0000008800848@244B00
04:55:45 Decoded 0000008800848@244@00
04:56:40 ---
04:57:35 ---
04:58:30 ---
04:59:25 ---
05:00:20 ---
05:01:15 LOS
By Safir-M_Decoder:
SAFIR-M Telemetrie (DP0AIS)
Raw Data: 0000008800848B244B00
Temperature Board: 68.0C
Temperature PA: 66.0C
Voltage [Accu]: 13.9 Volt
Voltage [5.5V]: 5.48 Volt
Voltage [3.3V]: 3.31 Volt
Biterror: 00 Errors
Subject: Re: [AATiS-Sat] WG: [amsat-bb] AO-49 status Jan 12
Date: Sun, 12 Jan 2003 16:36:06 EST
From: DF9IC
Hello Mineo,
please add the text of the DATA0 beacon to your report. Because of
the well known failure it is not possible to evaluate the telemetry
alone from the binary data sent to DATA1.
The real temperature was not 66 and 68 C but 74-74.5 and 76-76,5 C.
This comes from the unkown bit0. Example:
b0=?
0000_0088_00848B244B00 68
0000_0089_00848B244B00 68.5
0000_0098_00848B244B00 76
0000_0099_00848B244B00 76.5
Best Regards
Henning DF9IC
bottom top
Cf.9
Subject: RUBIN-2 INFO packets captured and translated...
From: Don Woodward
Date: Sun, 12 Jan 2003 16:36:07 -0500
To: Amsat Bulletin Board
RUBIN-2
2110 UTC on 12 January 2003
Captured by: KD4APP - Don Woodward
First line as captured - second line translated with bit corrected.
DP0@HR .l.tdtr r.dhn dxpdrhldnt R@FHR,L hn nrbht nn bn.rd nf Rtbhn,2
DP0AIS amateur radio experiment SAFIR-M in orbit on board of Rubin-2
RAW data from TNC with TRACE ON below.
000: 929C8C9E 4040E088 A0608292 A66002F0 INFO pDP0AIS0.x ....@@...`...`..
010: 44503040 48522060 6C607464 74722072 "(. $).060:2:9.9 DP0@HR `l`tdtr r
020: 6064686E 20647870 6472686C 646E7420 0247.2<8294627:. `dhn dxpdrhldnt
030: 52404648 522C4C20 686E206E 72626874 ) #$).&.47.7914: R@FHR,L hn nrbht
040: 206E6E20 626E6072 64206E66 20527462 .77.17092.73.):1 nn bn`rd nf Rtb
050: 686E2C32 47.. hn,2
000: 929C8C9E 4040E088 A0608292 A66002F0 INFO pDP0AIS0.x ....@@...`...`..
010: 44503040 48522060 6C607464 74722072 "(. $).060:2:9.9 DP0@HR `l`tdtr r
020: 6064686E 20647870 6472686C 646E7420 0247.2<8294627:. `dhn dxpdrhldnt
030: 52404648 522C4C20 686E206E 72626874 ) #$).&.47.7914: R@FHR,L hn nrbht
040: 206E6E20 626E6072 64206E66 20527462 .77.17092.73.):1 nn bn`rd nf Rtb
050: 686E2C32 47.. hn,2
Don Woodward
KD4APP
AMSAT 33535
http://kd4app.webhop.org
bottom top
Cf.10
You wrote at 16:36:07 -0500, 12 Jan 2003.
> RUBIN-2
> 2110 UTC on 12 January 2003
> Captured by: KD4APP - Don Woodward
>
> First line as captured - second line translated with bit corrected.
>
> DP0@HR .l.tdtr r.dhn dxpdrhldnt R@FHR,L hn nrbht nn bn.rd nf Rtbhn,2
> DP0AIS amateur radio experiment SAFIR-M in orbit on board of Rubin-2
I, JE9PEL, also captured the same message from Rubin-2, not telemetry.
http://www.ne.jp/asahi/hamradio/je9pel/30113a49.zip
She were transmitting these messages every 2 or 3 seconds.
I also think so that the tranlation of the strings are as above.
RUBIN-2
0355 UTC on 13 January 2003
Captured by: JE9PEL - Mineo Wakita
> DP0@HR .l.tdtr r.dhn dxpdrhldnt R@FHR,L hn nrbht nn bn.rd nf Rtbhn,2
> DP0AIS amateur radio experiment SAFIR-M in orbit on board of Rubin-2
I thought a tranlation table as below.
Are these quite sure ?
A ... A 41 ... 41
B ... B or C 42 ... 42 or 43
C ... C 43 ... 43
D ... D or E 44 ... 44 or 45
E ... E 45 ... 45
F ... F or G 46 ... 46 or 47
G ... G 47 ... 47
H ... H or I 48 ... 48 or 49
I ... I 49 ... 49
J ... J or K 4A ... 4A or 4B
K ... K 4B ... 4B
L ... L or M 4C ... 4C or 4D
M ... M 4D ... 4D
N ... N or O 4E ... 4E or 4F
O ... O 4F ... 4F
P ... P or Q 50 ... 50 or 51
Q ... Q 51 ... 51
R ... R or S 52 ... 52 or 53
S ... S 53 ... 53
T ... T or U 54 ... 54 or 55
U ... U 55 ... 55
V ... V or W 56 ... 56 or 57
W ... W 57 ... 57
X ... X or Y 58 ... 58 or 59
Y ... Y 59 ... 59
Z ... Z or [ 5A ... 5A or 5B
@ ... A 40 ... 41
... a 60 ... 61
, ... - 2C ... 2D
bottom top
Cf.11
Subject: AO-49 / Any signals observed on 13th?
From: Oliver Amend
Date: Tue, 14 Jan 2003 11:01:29 +0100
Dear AO-49 users and observers,
we detected yesterday over AO-49's passes over Europe that only
one INFO UI frame at 13:34 UTC (13.01.2003) was sent.
Any other activities noticed anywhere?
Probably the satellite has turned in a position that the solar
panel is not yet proper directed to the sun and therefor is
not switched on.
This may fit to the other observed effect on the path of
12th, 19:47UTC, where a lot of INFO frames without expected
DATA0 and DATA1 frames were observed, shortly before entering
into eclipse.
>From the SAFIR-M design point of view it is correct that after
being switched on, SAFIR-M sends first the beacon signal
(INFO, DATA0, DATA1, MH0, MH1).
Toggeling between On and Off within few seconds may also cause
this effect, that only INFO messages are sent...
Any reports about SAFIR-M activities are appreciated,
please direct the to DG6BCE@aatis.de.
73 de Oliver, DG6BCE
RUBIN 2
1 27605U 02058A 03013.21756886 .00000835 00000-0 15505-3 0 283
2 27605 64.5539 307.6211 0031016 126.4289 233.9678 14.71367927 3465
Mailto: DG6BCE@aatis.de
AATiS-Homepage: http://www.aatis.de
SAFIR-M homepage: http://amend.gmxhome.de
SAFIR-M Operational: http://hft.fh-pforzheim.de/ao49/
Mineo Wakita JE9PEL: http://www.ne.jp/asahi/hamradio/je9pel/safir-m2.htm
Cf.12
I received today, 05:06 - 05:18 UTC, 16 Jan 2003
with WiSP many digital signals from AO-49
including the data of "INFO, DATA0, DATA1, MH0, MH1".
2003-01-16-05.KSS 5837 bytes
30116a49.zip 449 bytes
Please see the zipped files in the future at the bottom
of this page below, because I put it when I can receive
the telemetry from AO-49 at the weekends after this.
bottom top
Cf.13
I received today, 01:35 - 01:49 UTC, 26 Jan 2003
with WiSP a few digital signals from AO-49
including the data of "INFO, DATA0, DATA1, MH0, MH1".
By WiSP,
> 2003-01-26-01.KSS 2034 bytes
> http://www.ne.jp/asahi/hamradio/je9pel/30126a49.zip
By KISS2ASC,
> fm DP0AIS to MH0 via .....
> fm DP0AIS to MH1 via .....
> fm DP0AIS to INFO via .....
> fm DP0AIS to DATA0 via .....
> fm DP0AIS to DATA1 via .....
By Safir-M_Decoder,
> SAFIR-M Telemetrie (DP0AIS)
> Raw Data: 0000008D008B8B244B00
> Temperature Board: 70.5 C
> Temperature PA: 69.5 C
> Voltage [Accu]: 13.9 Volt
> Voltage [5.5V]: 5.48 Volt
> Voltage [3.3V]: 3.31 Volt
> Biterror: 00 Errors
By Hex Editor, [Ascii] [Translated]
> 44 50 30 40 48 52 20 60 6c 60 : DP0@HR `l` : DP0AIS ama
> 74 64 74 72 20 72 60 64 68 6e : tdtr r`dhn : teur radio
> 20 64 78 70 64 72 68 6c 64 6e : dxpdrhldn : experimen
> 74 20 52 40 46 48 52 2c 4c 20 : t R@FHR,L : t SAFIR-M
> 68 6e 20 6e 72 62 68 74 20 6e : hn nrbht n : in orbit o
> 6e 20 62 6e 60 72 64 20 6e 66 : n bn`rd nf : n board of
> 20 52 74 62 68 6e 2c 32 c0 c0 : Rtbhn,2 : Rubin-2
> 00 88 82 a8 82 60 40 e0 88 a0 : `@ : aA
> 60 82 92 a6 60 02 f0 54 64 6c : Tdl : Tem
> 70 20 42 6e 60 72 64 3a 20 20 : p Bn`rd: : p Board;
> 2a 36 38 2c 30 f8 42 0c 54 64 : *68,0 B Td : +68,0 C Te
> 6c 70 20 48 46 2c 40 6c 70 3a : lp HF,@lp: : mp IF-Amp;
> 20 2a 36 36 2c 34 f8 42 0c 54 : *66,4 B T : +66,4 C T
> 2e 32 2c 32 56 6e 6c 74 3a 20 : .2,2Vnlt: : /2,2Volt;
> 20 20 32 2c 32 30 56 0c 54 2e : 2,20V T. : 2,20V T/
> 34 2c 34 56 6e 6c 74 3a 20 20 : 4,4Vnlt: : 4,4Volt;
> 20 34 2c 34 38 56 0c 54 2e 40 : 4,48V T.@ : 4,48V T/A
> 6a 6a 74 3a 20 20 20 20 20 20 : jjt: : ccu;
> 30 34 2c 30 56 0c 42 68 74 2c : 04,0V Bht, : 04,0V Bit-
> 44 72 72 6e 72 3a 20 20 20 30 : Drrnr: : Error: 0
bottom top
Cf.14
Subject: [amsat-bb:65903] AW: saphir-m AO49 not heard???
From: "Oliver Amend"
Date: Thu, 6 Feb 2003 13:28:37 +0100
To: amsat-bb@amsat.org
> Hi All
> I have not heard AO49 since Saturday 1st Feb ,is it still operational?
>
you are right. At the moment, AO-49 can't be used.
I have placed on the SAFIR-M homepage http://amend.gmxhome.de
under "Aktuelles" the following note:
(...)
No transmissions detected since 1st of February 2003!
Due to its orbit, SAFIR-M will be until 13th of february in a
phase without eclipses. At 30th of January 2003, a continuous
on/off-switching with lots of INFO messages but no DATA messages
have been recorded.
Since 1th of February, no transmissions could be detected until now.
(...)
It seems that the solar panel orientation is not pointing towards
the sun but this will last only for some days.
We are now waiting every day for a detectable signal from SAFIR-M
and this will be announced on the a.m. site.
We don't expect a grave system failure...
Any reports are welcome.
73 de Oliver DG6BCE
Mailto: DG6BCE@aatis.de
AATiS-Homepage: http://www.aatis.de
SAFIR-M Homepage: http://amend.gmxhome.de
SAFIR-M Operational: http://hft.fh-pforzheim.de/ao49/
Mineo Wakita / JE9PEL: http://www.ne.jp/asahi/hamradio/je9pel/safir-m2.htm
top
Reference URL
http://amend.gmxhome.de
http://hft.fh-pforzheim.de/ao49/
http://www.hhdsoftware.com/hexeditor.html
http://www.ne.jp/asahi/hamradio/je9pel/tlmformt.pdf
http://www.ne.jp/asahi/hamradio/je9pel/21228saf.gif
KISS Data by WiSP
21228saf.zip 09:12 UTC 28 Dec 2002
30109a49.zip 06:50 UTC 9 Jan 2003
30112a49.zip 04:53 UTC 12 Jan 2003
30113a49.zip 03:55 UTC 13 Jan 2003
30119a49.zip 03:12 UTC 19 Jan 2003
30120a49.zip 03:41 UTC 20 Jan 2003
30126a49.zip 01:35 UTC 26 Jan 2003
Back to Top
Back to Home Page