The satellite is available for scheduling. I’ve already scheduled for the first 4 hours after launch.
As there is an issue in the way that radio of SatNOGS Client works(@PE0SAT can give more details on the issue), I’ve created an extra transmitter for the FSK transmission, only to use with SatNOGS. On my scheduling I shared the observations on both FSK transmitters that are in DB.
To station owners, have in mind that the TLE we have are preliminary and could be affected by the launch time and change a lot when the satellite is deployed, so avoid scheduling too far in the future until we have something more stable.
I’ve just checked the documentation of the transmissions:
This entire transmission takes 15 seconds to happen and there will be 45 seconds in receive
mode, so there will be one transmission loop every minute.
Which means 1min interval that fits the received signals in the observations I linked on my previous post. Also it looks like that these were the first signals that the satellite sent as the expected deployed time was at 4:03 and the first received signal was at ~4:15 UTC.
AzaadiSAT-2’s orbit will be low for some stations, but here is a clean LoRa decode by N6RFM way up in the U.S. New England region. So, the satellite’s downlink is covering a nice big area.
Given that the used observations were taken from Australian stations, this is not very accurate over the rest of the world but still better than the preliminary ones.
And one more FSK decode uploaded at 0949utc (got -6- LoRa decodes on this pass; was very pleased with that. No luck uploading messages yet, but of course I’ll keep trying)
Not sure if I understand, but maybe this will help.
All downlink beacons are a sequence of LoRa, FSK, & CW.
You have the ability to UPLOAD messages to the mailbox slots - LoRa only.
The contents of mailbox slot #00 is included in the downlink beacon rotation.
You can transmit a different command up to the satellite to request the message from any mailbox slot. When you make the request, you specify the mailbox slot #, the satellite TX power, and whether the downlink of that message should be over LoRa or FSK.
I’m signing off for now but if that is not helpful, please let me know.
Hi folks - this is Brian Waldon with Antaris. I am operating the JANUS-1 spacecraft.
Just a note that we have seen some odd behavior in the catalog IDs assigned to the objects associated with the SSLV-D2 launch. Two oddities we observed in the last 24hrs:
A new object has taken the place of 55563 - this is likely the actual track of AzaadiSat-2. Anyone tracking 55563 up until this moment would have been tracking significantly ahead of AzaadiSat-2’s actual location.
The object that had been tracked as 55563 up until the event describe in item 1 above has been now assumed the identity of 55564.
If anyone here was tracking AzaadiSat-2 using the 55564 catalog identifier, you will now need to use 55563.
Data from space-track/celestrack as of 2023-02-16T17:57:00Z:
Indeed it seems that there was a change in the latest TLE sets for this launch by space-track.org, as it is visible in the diagram below generated by @cgbsat:
On the above diagram we can see that there are several sudden changes.
OBJECT C (55564), with green, look like that the last two days got closer to the OBJECT B (55563). The question is if this change has actually been done or it was an error fix.
In the first case of the actual change, then there isn’t any doubt that OBJECT B (55563) is AzaadiSat-2 as can be seen in the evidence of this identification post:
In the second case that the change happened due to an error on calculations/tracking, then OBJECT C (55564) is also a good candidate, with OBJECT C (55563), for being AzaadiSAT-2. Unfortunately the last days we haven’t any observed transmission by AzaadiSAT-2 to confirm which of the two is the one that describes the Doppler curve.
@bcwaldon if you can share some more info about JANUS-1 spacecraft transmissions, like the ones @K4KDR ask for, we may be able to help on confirming identification of JANUS-1 and find out what’s going on.
@dl7ndr added EOS-07 in DB as recently it has been spotted to perform APRS transmissions, it should be APRSDP-BTN, an APRS-DP payload from Bhutan, coordinated by IARU. I’ve added the related transmitter and scheduled a couple of observations to verify it.
