New TLE for AmicalSat by @pierros using @cgbsat’s sattools
AMICALSAT 2
1 99836U 20253.25000000 .00000000 00000-0 50000-4 0 06
2 99836 97.4424 326.1556 0000240 80.5969 326.6795 15.10185622 07
4 Likes
New TLE for Amicalsat based on two passes from station 977
1 99836U 20254.46180556 .00000000 00000-0 50000-4 0 05
2 99836 97.4424 327.5404 0000240 80.6989 70.2299 15.10399348 00
# 20200910.39-20200910.46, 37 measurements, 0.047 kHz rms
2 Likes
Two important updates.
- The unknown satellite, was the ION cubesat carrier.
- AmicalSat has changed its transmission interval so now it is easier to catch more than one transmissions in one pass
Nothing new on the TLE side, except the new AmicalSat TLE that you can check above.
2 Likes
Could you please change the TLE for TTU100 for the following one:
1 74005U 20061 20247.15007234 .00012616 00000-0 70000-4 0 00002
2 74005 097.5174 320.2827 0001428 234.5934 154.3000 15.10898652000008
I believe it would be a slightly better fit for the time being.
Thanks to @cgbsat for the script which allowed me to further check and compare the TLEs.
I’ve changed TTU100 to the above TLE.
2 Likes
New TLE for AmicalSat by @pierros using @cgbsat’s sattools
1 99836U 20254.92159350 .00000000 00000-0 50000-4 0 04
2 99836 97.4424 327.9873 0000180 40.8112 86.9629 15.10400370 02
2 Likes
Compare with the CSpOC TLEs for VV16 that have just been released.
0 TBA - TO BE ASSIGNED
1 46287U 20061R 20255.49438382 .00000506 00000-0 35089-4 0 9991
2 46287 97.5193 328.4728 0002458 12.9372 347.1920 15.09934471 1246
This TLE fits the AMICalSat Doppler curves best.
1 Like
As still the new objects/TLE from spacetrack are not fully assigned I think we should wait to be sure about the NORAD ID.
From my (not very accurate) calculations with ikhnos I will agree with @cgbsat and PA0DLO tweets:
So, I’ve changed satellites to follow these objects, however I’ll keep watching some of the other objects as they are close to fit satellites:
AMICALSAT: 46283,46284,46285,46286,46287(chosen to follow in Network), 46288
TRISAT: 46279, 46280(chosen to follow in Network), 46281 and 46313
The rest satellites remain as they were for now.
1 Like
I was just comparing with my various estimations. By the looks of it any of these could be: 46319, 46318, 46317, 46316, 46315, 46314. Probably 46320 is a bit too far in the front. Even though the first estimation 74003 is close-by, I believe the Bstar term is a bit too high (e.g. especially if the satellite isn’t deployed).
Perhaps it would make sense to use the TLE of 46317 for tracking? As it is in the centre of the pack and also considering the launch position, might be quite a good choice.
1 Like
Thanks, I’ve changed TLE to follow to 46317 for TTU100. Fingers crossed!
2 Likes
I think the change didn’t went through yet?
There was an issue with syncing of TLE sets, now it should be ok.
2 Likes
Hello, dear ea4bpn! Can You help to use programm upmsat2_v1_2.exe? I downloaded AWGP driver, added upmsat2_v1_2.exe program in Startup Programms, but it doesn’t work. My email gromoff.2000@yandex.ru. Thank You!
Hi
Assuming you are using MSwindows, I think the best way to use a soundcard modem is with the application soundmodem by http://uz7.ho.ua/packetradio.htm Before start the tlm decoding program, check the soundmodem is working right with a local ax.25 station around your location.
Next you need to start the telemetry decoder program. And that is all.
Because the doppler shift is very fast, you will need a tracking program to compensate it. Remember the UPMSat-2 is transmitting FSK: your receiver should be in USB mode and the ax.25 within the marks of your soundmodem waterfall.
Hope this helps.
73, Rafael
EA4BPN
Identified and changed their temporary id:
UPMSat-2: 46276 (OBJECT E)
TRISAT: 46280 (OBJECT J)
ION-MK01: 46274 (OBJECT C) NOTE: it has stopped transmitting since 2020-09-11 probably due to the publicity of their amateur radio frequency violation.
Not fully identified:
AmicalSat: 46287(chosen to follow in Network), 46288
TTU100: Unfortunately not heard at all, for now we are using 46317 for its observations
2 Likes
AmicalSat is now identified as 46287 on both Network and DB.
1 Like
Hello everyone! Have everyone got TLE UPMSat-2? This TLE is right? Thanks!
1 99999U 20999C 20247.10526620 .00000038 00000-0 12762-4 0 18
2 99999 97.4580 310.2540 0014300 070.7990 076.3347 15.15988174 992
Hi,
UPMSat-2 has been identified and its NORAD ID is 46276, so you can find the latest TLE at sites like celestrak.
The TLE you provided seems to follow UPMSat-2 but not fit its signal. Check the images bellow of observation 2850196, red line shows the expected line that signal should follow:
| TLE 46276 | Custom TLE |
|---|---|
Who can give a .wav record of AmicalSat? I`m want to check decoder. Thanks!