And I would say that in our received data we see satellite battery doesn’t have enough energy so being off in some territory can be happened
Unfortunately due to the generic parameters about the transmitter I can not confirm any of the information you ask for these observations.
I’m going to change the transmitter parameters in SatNOGS DB, so the new observations will be able to track better the satellite and may confirm the signals.
RS50S on 437.100 about 8 minutes earlier than TLE from 5th 04:51.
2024-11-08 20:45:08 UTC
82 98 98 40 40 40 E0 A4 A6 6A 60 A6 40 61 03 F0 52 53 35 30 53 20 53 3D 34 38 35 31 20 55 31 3D 33 2E 38 32 20 55 32 3D 33 2E 38 32 20 54 31 3D 32 34 2E 31 36 20 4D 78 3D 32 39 2E 38 32 37 31 37 33 20 4D 79 3D 2D 32 31 2E 33 30 35 31 32 34 20 4D 7A 3D 2D 38 39 2E 34 38 31 35 32 32 20 56 78 3D 30 2E 30 30 30 30 30 30 20 56 79 3D 30 2E 30 30 30 30 30 30 20 56 7A 3D 30 2E 30 30 30 30 30 30 20 54 69 6D 65 3D 33 30 38 39 32 32 30 30 34
RS50S S=4851 U1=3.82 U2=3.82 T1=24.16 Mx=29.827173 My=-21.305124 Mz=-89.481522 Vx=0.000000 Vy=0.000000 Vz=0.000000 Time=308922004
.
2024-11-08 20:46:40 UTC
82 98 98 40 40 40 E0 A4 A6 6A 60 A6 40 61 03 F0 52 53 35 30 53 20 53 3D 34 38 35 32 20 55 31 3D 33 2E 38 32 20 55 32 3D 33 2E 38 32 20 54 31 3D 32 33 2E 38 36 20 4D 78 3D 31 2E 31 32 31 33 32 32 20 4D 79 3D 2D 31 34 2E 31 32 38 36 36 31 20 4D 7A 3D 2D 35 39 2E 38 37 38 36 31 33 20 56 78 3D 30 2E 30 30 30 30 30 30 20 56 79 3D 30 2E 30 30 30 30 30 30 20 56 7A 3D 30 2E 30 30 30 30 30 30 20 54 69 6D 65 3D 33 30 38 39 36 37 31 35 35
RS50S S=4852 U1=3.82 U2=3.82 T1=23.86 Mx=1.121322 My=-14.128661 Mz=-59.878613 Vx=0.000000 Vy=0.000000 Vz=0.000000 Time=308967155
.
2024-11-08 20:47:26 UTC
82 98 98 40 40 40 E0 A4 A6 6A 60 A6 40 61 03 F0 52 53 35 30 53 20 53 3D 34 38 35 33 20 55 31 3D 33 2E 38 31 20 55 32 3D 33 2E 38 32 20 54 31 3D 32 32 2E 39 37 20 4D 78 3D 36 31 2E 32 32 34 31 39 37 20 4D 79 3D 2D 31 2E 35 36 39 38 35 31 20 4D 7A 3D 38 2E 37 34 36 33 31 34 20 56 78 3D 30 2E 30 30 30 30 30 30 20 56 79 3D 30 2E 30 30 30 30 30 30 20 56 7A 3D 30 2E 30 30 30 30 30 30 20 54 69 6D 65 3D 33 30 39 30 35 36 31 39 38
RS50S S=4853 U1=3.81 U2=3.82 T1=22.97 Mx=61.224197 My=-1.569851 Mz=8.746314 Vx=0.000000 Vy=0.000000 Vz=0.000000 Time=309056198
.
2024-11-08 20:45:16 UTC
@dl7ndr Thanks for the information.
I went over my strf files and created the following updated TLE
MORDOVIA-IOT
1 98785U 24313.92400463 .00000000 00000-0 50000-4 0 00
2 98785 97.4000 178.7253 0014167 173.4581 274.4147 15.24664711 06
It needed several attempts for me to get the websocket
of the proxy_mmt_gui running.
Now, also my callsign is on RS64S’s contributors list with currently 136 received frames from two observations.
TLE sets by @PE0SAT for ZIMSAT-2 and RUZAEVKA-390:
ZIMSAT-2
1 98777U 24310.14664352 .00000000 00000-0 50000-4 0 01
2 98777 97.4000 174.6627 0016235 86.9300 165.7900 15.25312984 04
RUZAEVKA-390
1 99194U 24313.92792825 .00000000 00000-0 50000-4 0 01
2 99194 97.4000 178.8092 0016734 76.4569 33.1708 15.24414870 05
There is a slight chance that the TLE should be vice versa, please let us know if worked for you!
also, considering the satellite state vector from seperation moment, the real TLE is proabably as followed:
KOSAR1
1 99999U 98067A 24310.14432870 .00005246 00000-0 21060-3 0 0006
2 99999 97.3828 174.9565 0007069 236.8580 003.0943 15.25009610000014
tracking this pass would help a lot. tnx.
@fredy this is our transmitter spectrum mask as we seen modulation is 2FSK and center frequency equal to 436.75 MHz. can you share your carrier spectrum mask?
Again two Europe passes, I am sorry to say there are no clear signals or to weak to detect.
(update 09:33, this time with the correct freq, sorry for the confusion)
First pass started at 05:45 UTC and the second at 07:16 UTC
This spectrum shows all possible signal between 04:30 and 08:30 UTC with a center freq of 436.750 and a bw of 100 Khz
There are only already cataloged satellites.
technically, the different flowgraphs we use have varying filter bw, some has it fixed like the FM flowgraphs that we use when we’re not sure of the transmitter mode. the FSK has it’s width set based on the baudrate.
this filtered bw is fed to the demodulator and also the audio recording.
the waterfall is running on a wider bw than the recorded audio as we want to see a bigger slice of the spectrum for mismatching doppler etc.
in this case, sharing a FFT spectrum over time is more helpful, as this can be matched to the waterfalls in the observations.
if you can share either IQ or FM/FSK demodulated signals from the transmitter, it might be possible to match it by ear if it has a peculiar sound to it. or to generate FFT spectrum to be compared with the observations that we run.
Updated TLE sets for 3 more satellites:
TUSUR GO
1 98788U 24314.20000000 .00000000 00000-0 50000-4 0 08
2 98788 97.4000 174.1104 0012126 120.2730 15.6400 15.23901209 05
SIT-HSE
1 98774U 24314.10000000 .00000000 00000-0 29546-3 0 02
2 98774 97.4000 178.8583 0012824 89.7672 241.0540 15.24127533 02
SIT-2086
1 98773U 24314.10000000 .00000000 00000-0 50000-4 0 01
2 98773 97.4000 178.8742 0016163 73.5149 258.7748 15.24302220 01
sites.txt (9.8 KB)
sit2086_314_v1.dat (1.4 KB)
sithse_314_v1.dat (1.6 KB)
tusur_314_v1.dat (325 Bytes)
Updated TLE for SamSat-Ionosphere:
SamSat-Ionosphere
1 98786U 24314.25181294 .00000000 00000-0 00000-0 0 00007
2 98786 097.4022 178.5232 0040238 250.7439 170.9816 15.22804544000006
@fredy
Hi
We agree totally your technical interpretation.
For more clearance we can send you three below informations:
1-transmitter spectrum mask on carrier frequency in pnj or jpeg format.
2-iq file of our propagated signal.
3-even our decoder structure that shows our data.
We would like to arrange a technical meeting with you so that we can talk about how it works and the transmitter data interval scenario in more detail.
As I mentioned before, due to the satellite unstable power condition, it may was off during the pass.
In addition to that, do you think our TLE may be very different from real orbit? Since the signal has been frequently seen from satnogs stations?
We have seen TLE that where 8 minutes of and that specific satellite was also 7 KHz lower in frequency.
With that in mind, we will not find KOSAR by running automated obs, we first need to find the signal with the help of manual observations and or with software like STRF.
I am currently monitoring every 48 hours the whole spectrum between 400 - 404 and 434 - 438 MHz
17G ./402/2024-11-09T01:45:01+00:00
17G ./436/2024-11-09T01:45:01+00:00
52G ./402/2024-11-03T01:00:01+00:00
52G ./402/2024-11-05T01:15:01+00:00
52G ./402/2024-11-07T01:30:01+00:00
52G ./436/2024-11-03T01:00:01+00:00
52G ./436/2024-11-05T01:15:01+00:00
52G ./436/2024-11-07T01:30:01+00:00
This is what I have so far.
Just to be clear on this, still the good observations are not 100% sure. I mean these are the best candidates we have, but it could be something different than kosar.
We will keep monitoring the frequency in Network, and in more generic scans like the ones @PE0SAT described and if we see something let you know.
Some updates
RTU MIREA1
1 98894U 24313.86700000 .00000000 00000-0 50000-4 0 04
2 98894 97.4000 172.7132 0012212 41.0769 68.5791 15.20985231 00
Colibri-S
1 98794U 24314.76000000 .00000000 00000-0 50000-4 0 06
2 98794 97.4000 179.2709 0007877 197.6187 148.4517 15.25669108 05
Horizon
1 98793U 24312.81000000 .00000000 00000-0 50000-4 0 09
2 98793 97.4000 176.3227 0009285 268.8013 184.7277 15.19529351 05
TUSUR GO
1 98788U 24314.78000000 .00000000 00000-0 50000-4 0 01
2 98788 97.4000 181.8104 0012126 219.7730 212.3400 15.23901209 00
VIZARD-ion
1 98789U 24314.84525463 .00000000 00000-0 50000-4 0 04
2 98789 97.4000 178.9015 0002766 263.0012 189.1762 15.24799255 02
Fellow Hams, unfortunately my equipment especially the omnidirectional ham radio antenna is not really helpful for capturing cubesat signals.
Anyway on Nov. 9th at 22:14 UTC I captured this fragment of an SSTV image on 437.050 MHz in Robot-36.
Could someone please confirm if this was received from ZIMSAT-2 and how the complete image should have looked alike.
Thank you and regards.
73, Martin DL5BK
Perhaps this is the image you received: