On February 3, 2022, the following 2 CubeSats will be deployed from “Kibo” Japanese Experiment Module.
Light-1
A collaboration initiative of the UAE Space Agency (UAESA), Bahrain’s National Space Science Agency (NSSA), Khalifa University of Science and Technology, and New York University - Abu Dhabi (NYUAD).
Both satellites are now available for scheduling in Network and also have been scheduled for the first hours after deployment using current ISS TLE set.
The new TLE set for GT-1 by @EelkeVisser, a little improved than the one above by taking into consideration LIGHT-1 observations, is now added in DB and Network containing the temporary NORAD ID we use in DB:
I’m slightly confused by the ‘NOTES’ section below the GT-1 uplink instructions. So, our uplinks SHOULD, or SHOULD NOT be a valid AX.25 packet w/ ‘To’ & ‘From’ addressing?
Or, to be accepted by the satellite, should our uplink ONLY include the raw bytes to fit the expected pattern of " KK4UVG DE Operator-Callsign Operator Grid-Square K "
## Notes
1. All Messages sent to GT-1 must be sent using 9600 baud, G3RUH AX.25 wrapping a. GT-1 Does not Conform to the APRS Standards
2. GT-1 uses the callsign 'KK4UVG'
Will certainly try on the next pass to my SW also, but that’s not very high in my sky either. But that’s the nice thing about orbits; in a few days I’ll get some higher passes.
The objects are still too close to identify, but judging from their position relatively to ISS position it looks like GT-1 is OBJECT TH (51510) and LIGHT-1 is OBJECT TG(51509).
EDIT: The above sets are now used for both satellites to follow in DB and Network.
… and please note that I an NOT transmitting that last ''0d" character - I can only assume that EasyTerm is somehow appending that. It doesn’t show up in my string as handled by UZ7HO HS_Soundmodem (audio interface to my radio). I wonder if that trailing “0d” is a deal breaker? Instead of EasyTerm I can manually create the appropriate packet & make sure it ends with the “4b” (K) character…
After some initial diagnosis, we have found the problem that has prevented uplink to the spacecraft. GT-1 has an OpenLST based radio that it uses for RX and TX. The OpenLST is unique for the fact that it expects an Open LST specific preamble for any messages that it receives, something that is automatically added if two OpenLST radios are communicating with each other. During testing of GT-1, the team primarily used a Open LST to model our groundstation radio instead of an SDR. Because of this, we never had any issues with transmitting or receiving data with GT-1.
The GT-1 team is currently in the process of creating and testing a flowgraph that accounts for the added OpenLST data and successfully transmits and receives with our GT-1 testbed. Once we have finished testing and development of this flowgraph, we will release it to the community so that any operators can use it with GT-1.
