LASARSAT
1 98797U 24358.12569444 .00000000 00000-0 37435-2 0 04
2 98797 45.0011 352.2343 0005149 109.2259 353.7958 15.17854396 01
4 Likes
Looks quite nice. I was working with NAV beacon from LASARSAT data today as time permitted.
Here is a very quick comparison to orbit prediction based on this latest TLE of yours. Admittedly the comparison is done using time of packet from database and not true GPS time from the beacon. But, I would rather share partial data than not.
In the coming days around Christmas, better results will be hopefully shared.
Latitude and longitude errors seem to be relatively good though.
5 Likes
Does anyone know if the UHF Digipeater on LASARsat is enabled for general use?
If so, what settings should be used (To:, From:, Via:)?
9600 baud, same as the downlink?
Thanks!
1 Like
Click on the link “Digipeater Dashboard” in the panel next to the panel “Digipeated Message from”.
The digipeater is always on.
The destination callsign is arbitrary.
3 Likes
Great - thanks!
I’ll give it a try.
1 Like
You must have the magic touch… no luck here w/ 50 watts on a 56° pass.
Will keep trying!
2 Likes
Upgraded my TX power to 80w via an external 70cm RF amp but still no luck - this time on a pass that reached 53° max EL. So, even though I can decode my uplinks just fine doing in-house ‘live’ over-the-air testing, it seems that LASARsat is not interested.
Could you share your hardware & software setup for those uplinks that are being digipeated? Any info about settings might be helpful, too.
Thanks!
Very helpful - thanks!
I have been using the high-speed version of UZ7HO-SoundModem for 9600 RX/TX with my TM-V71A. I’ll give Direwolf a try with your settings. (and of course I have the TM-V71A data speed set to ‘9600’ and am using the DATA port as the connection to my computer)
As for the radio itself, are you using the ‘FM’ or ‘FM-narrow’ setting?
My RX is via the SDR dongle and Gqrx.
So, the setting FM or FM-narrow on the FT-847 has no influence on it.
I’m also using the DATA port but leaving the PKT RATE (DAT.SPD on your TM-V71A) at 1200.
As I can see from the manual, the TM-V71A has no CAT control.
Remember, it’s UHF, there is more doppler to correct.
And perhaps the 1 kHz steps are too big for LASARsat and CroCube.
Very interesting - thank you! I’ll experiment w/ that Data Speed setting on the radio.
I am stepping through -5- memory channels w/ appropriate doppler adjustments both up & down.
On odd situation when testing in-house over-the-air w/ Direwolf (as opposed to UZ7HO_HS-SoundModem) is that with Direwolf, it seems that I have to TX multiple times in quick succession to get a decode on my RX SDR (running direwolf). With the UZ7HO_HS-SoundModem, I get a clean decode on every single packet. I’ll have to experiment further w/ that today to see what setting in Direwolf might be causing that behavior.
1 Like
Sorry to be off-topic for the entire Bandwagon-2 deployment, but for anyone else who finds these posts and has any issue with having to transmit multiple times to get decoded, I traced the issue with my hardware / software (TM-V71A, Direwolf) to the TXTAIL parameter. Too short, and it apparently corrupts the payload somehow. I increased the value to “20” and now my test receiver decodes my transmissions first-time / every-time!
This is in reference to transmitting 9k6 packets to LASARsat in an attempt to relay through the digipeater on 436.925 MHz.
5 Likes
Hey, do you know if the satellite identification process of satellites on this launch is ongoing? I don’t see any updates on Celestrak and in space-track I see launch 2024-246 and 248. But not this one, 247.
I am not aware of communication with satellite teams about this either.
Usually it takes some time (few days to few weeks depending on the load) for multiple satellite launches to get TLE. Also in this launch there is the secrecy due to the military payload, so we may see longer delay, even no TLE at all. Until then we will continue to track the satellites we can receive.
2 Likes
An improvement on LASARSat TLE, not fully accurate but better than the current one:
LASARSAT
1 98797U 24361.40000000 .00000000 00000-0 37435-2 0 07
2 98797 45.0011 334.8616 0005149 109.2259 264.4136 15.17187952 03
5 Likes
DJIBUTI-1B update:
DJIBUTI-1B
1 98729U 24361.60000000 .00000000 00000-0 43247-2 0 02
2 98729 45.0018 333.3935 0003705 4.7833 50.3795 15.19804809 08
CTC-0 has not received the last ~24h.
1 Like
TLE update for LASARSat by @somecheese:
LASARSAT
1 98797U 24362.50000000 .00000000 00000-0 37435-2 0 09
2 98797 45.0011 325.1552 0005149 109.2259 165.3084 15.17187952 06
2 Likes
One TLE update for DJIBUTI-1B:
DJIBUTI-1B
1 98729U 24363.20000000 .00000000 00000-0 43247-2 0 00
2 98729 45.0018 325.6026 0003705 64.0988 111.9931 15.19562102 06
1 Like
And one TLE for CroCube:
CROCUBE
1 98799U 24363.20000000 .00000000 00000-0 41141-2 0 08
2 98799 45.0011 317.3887 0004896 125.6016 18.5594 15.18157716 04
Unfortunately still no reception from CTC-0, last heard since 2024-12-25 07:15 UTC.
1 Like
FYI, I continue to try the LASARsat 9k6 uplink on every pass, but so far you are still the only one able to reach it. By any chance could you make an audio recording of an uplink packet transmitted from your station? (via an SDR app capable of outputing & recording 15k audio bandwidth, of course)
Thanks!
1 Like