We have received ORCASAT but have in mind that it is active only over Canada.
New TLE set for ORCASAT, unfortunately due to the limited data is not very accurate:
ORCASAT
1 99232U 23003.10000000 .00000000 00000-0 00000-0 0 07
2 99232 51.6442 54.7608 0006169 65.8567 198.6413 15.50562683 01
The SPORT intended configuration at deploy was 1200 baud for the beacon. The onboard computer commands this in the radio. We have been having hardware resets of both the radio subsystem and the onboard computer since being on orbit. When the radio resets it comes back on line and defaults to 9600 baud. When the computer reboots it commands the radio to 1200 baud.
TBA(To Be Assigned) TLE sets from space-track.org:
0 TBA - TO BE ASSIGNED
1 55123U 98067UQ 23003.63333487 .00047740 00000-0 80865-3 0 9993
2 55123 51.6429 63.6040 0003157 273.6994 86.3634 15.51052568 873
0 TBA - TO BE ASSIGNED
1 55124U 98067UR 23003.65810831 .00060369 00000-0 10202-2 0 9998
2 55124 51.6453 63.4813 0002972 265.5963 231.8120 15.51017177 860
0 TBA - TO BE ASSIGNED
1 55125U 98067US 23003.63357344 .00040543 00000-0 69100-3 0 9996
2 55125 51.6429 63.6053 0003896 269.3117 90.7426 15.50949302 887
0 TBA - TO BE ASSIGNED
1 55126U 98067UT 23003.63368923 .00035150 00000-0 60181-3 0 9990
2 55126 51.6429 63.6061 0003928 268.6498 91.4041 15.50889048 888
0 TBA - TO BE ASSIGNED
1 55127U 98067UU 23003.62836962 .00374260 00000-0 53691-2 0 9998
2 55127 51.6414 63.5700 0001579 282.4679 77.6134 15.54276582 849
0 TBA - TO BE ASSIGNED
1 55128U 98067UV 23003.65902079 .00041530 00000-0 71426-3 0 9993
2 55128 51.6445 63.4855 0004828 248.9506 248.6383 15.50679744 872
0 TBA - TO BE ASSIGNED
1 55129U 98067UW 23003.44145077 .00026363 00000-0 46064-3 0 9995
2 55129 51.6427 64.5728 0002775 235.2336 124.8392 15.50470921 841
0 TBA - TO BE ASSIGNED
1 55130U 98067UX 23003.59786241 .00023350 00000-0 40927-3 0 9992
2 55130 51.6470 63.7968 0003724 221.2797 292.1437 15.50452918 811
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| AQMD-7020-9181-7420-6447 | MARIO | 55123 | - | It is well received and clear that it is this object. We are waiting for TLE set to be assigned before identifying it |
| VUIJ-4442-3257-2619-1322 | SPORT | 55129 | 55130 | Received, objects pretty close to say for sure |
| ZCND-2493-6441-2637-5373 | LORIS | 55124 | 55123-55130 | Not received yet, randomly chosen 55124 |
| LENB-9037-9456-1559-8946 | ORCASAT | 55126 | 55123-55125 | Received, not enough signals to fit better a TLE set |
| DESY-4487-8777-3725-3847 | DanteSat | 55127 | 55123-55130 | Not received yet, randomly chosen 55127 |
| NAEW-9759-0504-8538-0109 | NUTSAT | 55125 | 55124, 55126 | Received, the other objects are close but probably not the satellite |
| HICO-4044-2713-1337-0678 | PETITSAT | 55130 | 55123-55130 | Not received yet, randomly chosen 55130 |
| GSVY-0685-7956-3934-6462 | TJREVERB | 55128 | 55123-55130 | Not received yet, randomly chosen 55128 |
New TLE sets from space-track.org:
0 OBJECT UQ
1 55123U 98067UQ 23004.59974703 .00067656 00000-0 11351-2 0 9992
2 55123 51.6430 58.8087 0003001 278.7860 81.2790 15.51171177 1021
0 OBJECT UR
1 55124U 98067UR 23004.59994486 .00093942 00000-0 15671-2 0 9999
2 55124 51.6430 58.8100 0002929 275.6342 84.4313 15.51185007 1019
0 TBA - TO BE ASSIGNED
1 55125U 98067US 23004.53562475 .00056803 00000-0 95984-3 0 9994
2 55125 51.6430 59.1301 0003786 274.0027 86.0530 15.51043139 1021
0 OBJECT UT
1 55126U 98067UT 23004.60021144 .00049739 00000-0 84414-3 0 9992
2 55126 51.6431 58.8115 0003828 273.3803 86.6748 15.50977917 1030
0 TBA - TO BE ASSIGNED
1 55127U 98067UU 23004.59253830 .00590443 00000-0 79574-2 0 9993
2 55127 51.6409 58.7597 0001014 311.6408 48.4496 15.55213643 995
0 OBJECT UV
1 55128U 98067UV 23004.60105087 .00057348 00000-0 97796-3 0 9995
2 55128 51.6429 58.8169 0004811 255.1053 104.9404 15.50777088 1025
0 OBJECT UW
1 55129U 98067UW 23004.60159830 .00032781 00000-0 56903-3 0 9990
2 55129 51.6427 58.8214 0002645 241.5270 118.5453 15.50539109 1023
0 OBJECT UX
1 55130U 98067UX 23004.53721799 .00028811 00000-0 50203-3 0 9999
2 55130 51.6427 59.1414 0002689 240.4567 119.6154 15.50499079 969
With most of the TLE assigned, here are the results:
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| AQMD-7020-9181-7420-6447 | MARIO | 55123 | - | Identified, here are the ikhnos results |
| VUIJ-4442-3257-2619-1322 | SPORT | 55129 | 55130(unlikely) | Better fit of 55129 than the previous one but 55130 is still close |
| ZCND-2493-6441-2637-5373 | LORIS | 55125 | 55124(unlikely), 55126 | Probably received, chosen to follow 55125 |
| LENB-9037-9456-1559-8946 | ORCASAT | 55126 | 55124(unlikely), 55125 | Removed 55123 from the possible ones, the other ones are still close but 55126 looks like better fit |
| DESY-4487-8777-3725-3847 | DanteSat | 55127 | 55124-55130 | Not received yet, randomly chosen 55127 |
| NAEW-9759-0504-8538-0109 | NUTSAT | 55124 | - | Removed 55125 and 55126, waiting a couple of observations for definite identification |
| HICO-4044-2713-1337-0678 | PETITSAT | 55130 | 55124-55130 | Not received yet, randomly chosen 55130 |
| GSVY-0685-7956-3934-6462 | TJREVERB | 55128 | 55124-55130 | Not received yet, randomly chosen 55128 |
All the TLE sets from space-track.org are now assigned:
0 OBJECT UQ
1 55123U 98067UQ 23007.36970417 .00060250 00000-0 10002-2 0 9993
2 55123 51.6424 45.0589 0002783 292.8759 67.1936 15.51518398 1451
0 OBJECT UR
1 55124U 98067UR 23007.82058018 .00086671 00000-0 14195-2 0 9991
2 55124 51.6424 42.8207 0002597 294.0428 66.0290 15.51737918 1513
0 OBJECT US
1 55125U 98067US 23007.49911221 .00052400 00000-0 87677-3 0 9998
2 55125 51.6425 44.4230 0003550 287.1294 72.9307 15.51355276 1487
0 OBJECT UT
1 55126U 98067UT 23007.82154350 .00045975 00000-0 77298-3 0 9995
2 55126 51.6425 42.8261 0003624 287.5430 72.5164 15.51276976 1534
0 OBJECT UU
1 55127U 98067UU 23008.05828086 .00624619 00000-0 72876-2 0 9990
2 55127 51.6401 41.4079 0002176 63.5717 296.5498 15.58981898 1533
0 OBJECT UV
1 55128U 98067UV 23007.82277382 .00051803 00000-0 87464-3 0 9991
2 55128 51.6423 42.8350 0004501 268.7867 91.2607 15.51102936 1526
0 OBJECT UW
1 55129U 98067UW 23007.50173064 .00030812 00000-0 53209-3 0 9996
2 55129 51.6422 44.4408 0002482 253.0493 107.0225 15.50717402 1471
0 OBJECT UX
1 55130U 98067UX 23007.82411389 .00027034 00000-0 46863-3 0 9998
2 55130 51.6423 42.8434 0002546 253.9732 106.0977 15.50681088 1474
Here are the latest updates:
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| AQMD-7020-9181-7420-6447 | MARIO | 55123 | - | Identified, here are the ikhnos results |
| VUIJ-4442-3257-2619-1322 | SPORT | 55129 | - | Identified, here are the ikhnos results |
| ZCND-2493-6441-2637-5373 | LORIS | 55125 | 55124(unlikely), 55126 | Probably received, chosen to follow 55125 |
| LENB-9037-9456-1559-8946 | ORCASAT | 55126 | 55125(unlikely) | Removed 55124 from the possible ones |
| DESY-4487-8777-3725-3847 | DanteSat | 55127 | 55124-55128,55130 | Not received yet, randomly chosen 55127 |
| NAEW-9759-0504-8538-0109 | NUTSAT | 55124 | - | Removed 55125 and 55126, waiting a couple of observations for definite identification |
| HICO-4044-2713-1337-0678 | PETITSAT | 55130 | 55124-55128,55130 | Not received yet, randomly chosen 55130 |
| GSVY-0685-7956-3934-6462 | TJREVERB | 55128 | 55124-55128,55130 | Not received yet, randomly chosen 55128 |
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| AQMD-7020-9181-7420-6447 | MARIO | 55123 | - | Identified, here are the ikhnos results |
| VUIJ-4442-3257-2619-1322 | SPORT | 55129 | - | Identified, here are the ikhnos results |
| ZCND-2493-6441-2637-5373 | LORIS | 55125 | 55126 | Probably received, so we need more observations, removed 55124 |
| LENB-9037-9456-1559-8946 | ORCASAT | 55126 | 55125(unlikely) | Removed 55124 from the possible ones |
| DESY-4487-8777-3725-3847 | DanteSat | 55127 | 55125-55128, 55130 | Not received yet, randomly chosen 55127 |
| NAEW-9759-0504-8538-0109 | NUTSAT | 55124 | - | Identified, here are the ikhnos results |
| HICO-4044-2713-1337-0678 | PETITSAT | 55130 | 55125-55128, 55130 | Not received yet, randomly chosen 55130 |
| GSVY-0685-7956-3934-6462 | TJREVERB | 55128 | 55125-55128, 55130 | Not received yet, randomly chosen 55128 |
From https://twitter.com/ViennaHamRadio/status/1611539181280313346 it seems that TJREVERB may transmit at 144.39 MHz. I’ve added the transmitter and scheduled a couple of observations.
Also probably from someone from the team there was an update on the LORIS transmitter baudrate from 19200 to 9600. Let’s see if we are going to get anything.
Finally I was about to identify ORCASat based on SatNOGS Network - Observation 6995051. However I got a similar signal on different frequency (the one of LORIS), that matches the same object SatNOGS Network - Observation 7004278. So, I’m now wondering if the signal we recognize as ORCASat is indeed ORCASat or something else (maybe a terrestrial transmission?) and why we got similar signal at LORIS frequency. More observations have been scheduled for both to solve this mystery.
144.39 is the US APRS freq
I’m not going to keep scheduling TJREVERB, ORCASat and LORIS.
For TJREVERB we haven’t received anything since its deployment, so probably is DOA. Unless we have a request from the team or any update that proves reception, I don’t think there is any point on continue scheduling.
For LORIS and ORCASat, given that the satellites are transmitting only after command and they don’t have any beacon, I’ll wait feedback from the teams (@loris-ops and @ha6bli) on the questions asked in Observation 7014595: LORIS (99233) and in Observation 6981462: ORCASat (99232), as well as specific timestamps that they try to communicate with their satellites in order to schedule Network.
Of course station owners can keep scheduling all the three of them. 
In light of the following post, I wonder if it might be possible to schedule some additional network observations for NUTSat (436.850 1200 baud APRS)? Thanks!
https://twitter.com/EdwardChuang4/status/1619655811885854720
Body of the Twitter post:
As I know, NUTSAT is currently in low power status, so the DIGI function has not yet been activated. The control team hopes to obtain more telemetry data from regions outside Taiwan to identify the problem and find out how to resolve it. Thanks for your concern! 73 de BX1AD
It seems I created the wrong mode, sorry, for now I disabled 9k6 G3RUH AX.25 and only enabled 1k2 AFSK in the network.
There are a lot of observations of NUTSAT now, some are useful and good results, many thanks to K4KDR, PE0SAT, and SATNOGS group!
@bx1ad can you provide a link on how you can decode the data of NUTSAT?
I’ve quick searched in https://www.tasa.org.tw/inprogress.php?c=20030402&ln=en but I didn’t find anything.
This is an .exe file, so it doesn’t describe how to decode the frames. Is there are least the source code for this executable to find out how it performs the decoding?
Please share details (a link to a description would be great!).
It looks like I’ve already done a similar decoder - your OBC data is additionally encoded in something like Base64 hexadecimal!?
I’m very sorry, I’m not a member of NUTSAT control team, I just handover information here from the team, and I’ll see what else I can do.
