Thanks to Eelke and other, I have swiched the receiving side of BDSat-2 groundstation to Celestrak TLE, Norad ID 55098, I am receiving on Win PC, so for data forwarding I use Getkiss+ and it forwards data to Satnogs DB under this ID now. From this time, our packets are not occuring in the BDSat-2 Grafana. Is there anything can be done to merge those packets to BDSat-2? Thank you.
There will be a merge in the next days after the final identification.
OK, I will leave the forwarding working…
Thank you! 
Yes these are going to be also decoded after merge and added to the dashboard.
TLE sets are still 95, reminder that the total of the payloads were 114, from which initially to be deployed were 82 and from them only 78 were confirmed. Here are the latest updates:
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| DELH-6722-1461-1897-7938 | Sharjahsat-1 | - | - | Received but it doesn’t seem to be fitted on any of the published objects |
| NJFB-9884-9643-7739-4519 | BDSAT-2 | 55098 | - | Received, removed 55103 |
| NJEX-6170-8600-1975-0468 | ION SCV-008 | 55051 | - | Received - no update |
| VPUU-7194-1121-2414-5647 | ION SCV-007 | 55060 | - | Received and for now only 55060 fits, however in the last two observations with data (7066554 and 7066545) this object doesn’t seem to fit, it could be another unpublished object or maybe an older TLE used. Needs more investigation. |
| RJCF-5779-9216-5641-4111 | BRO-8 | 55011 | - | Received - no update |
| PDVW-9191-3063-9872-9368 | Vigoride-5 | 55056 | all the rest | Not (recently?) received, changed according to space-track.org |
| KCKF-9169-8304-1813-6974 | Platform-2 | 55067 | 55080, 55082(unlikely), 55083 | Not (recently?) received, not sure if the object we follow is the right until we confirm previous receptions were from the satellite |
| TVZK-1463-5590-8994-0377 | Connecta T1.2 | 55012 | - | Received - no update |
| LSZR-8461-9828-5431-6212 | Star Vibe | 55009 | all the rest | Received(?), we need to verify signals are coming from the satellite. OBJECT A(55009) is chosen based on this tweet |
| JRGY-1674-7223-5551-1972 | TAUSAT-2 | 55073 | - | Received, removed 55074, 55075 |
Given that we have at least one missing object, I think it is wise to wait a couple more days before any identification.
2 Likes
Great Information, Lets wish them best of Luck!!!
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| DELH-6722-1461-1897-7938 | Sharjahsat-1 | - | - | Received but it doesn’t seem to be fitted on any of the published objects |
| NJFB-9884-9643-7739-4519 | BDSAT-2 | 55098 | - | Received, removed 55103 |
| NJEX-6170-8600-1975-0468 | ION SCV-008 | 55051 | - | Received - no update |
| VPUU-7194-1121-2414-5647 | ION SCV-007 | 55060 | - | Received and for now only 55060 fits, however in the last two observations with data (7066554 and 7066545) this object doesn’t seem to fit, it could be another unpublished object or maybe an older TLE used. Needs more investigation. |
| RJCF-5779-9216-5641-4111 | BRO-8 | 55011 | - | Received - no update |
| PDVW-9191-3063-9872-9368 | Vigoride-5 | 55056 | all the rest | Not (recently?) received, changed according to space-track.org |
| KCKF-9169-8304-1813-6974 | Platform-2 | 55067 | 55080, 55082(unlikely), 55083 | Not (recently?) received, not sure if the object we follow is the right until we confirm previous receptions were from the satellite |
| TVZK-1463-5590-8994-0377 | Connecta T1.2 | 55012 | - | Received - no update |
| LSZR-8461-9828-5431-6212 | Star Vibe | 55009 | all the rest | Received(?), we need to verify signals are coming from the satellite. OBJECT A(55009) is chosen based on this tweet |
| JRGY-1674-7223-5551-1972 | TAUSAT-2 | 55073 | - | Received, removed 55074, 55075 |
Hi there,
I am about to build a satnogs-decoder for SharjahSat-1 and to me it looks like the telemetry description is incomplete! You’re transmitting in AX.25 and I need to deal with the whole AX.25 payload. Your description seems to start somewhere behind a header inside this payload. Could you please investigate and clarify? The ID for your General TM Packet transmission seems to be 80 - following that above mentioned document. Where can I find that ID? Is it decimal or hexadecimal?
All the best,
Patrick
1 Like
Hi,
I am Boğaç Karabulut TA1SBK. I thank you all in the name of the University of Sharjah SAASST CubeSat Lab. and Istanbul Technical University Space System Design and Testing Lab. for your interest and support. Your observations help a lot. I will try to answer some of your questions about the satellite.
We are using Norad ID 55104 and it seems ok.
CW beacon and S-Band are not active now. We will activate them in a short time and let you know.
I am sharing the recent decoder for SharjahSat TM packets. You can find a windows application as a decoder and a pdf explaining how to decode packets.
Here is an example TM packet (Hex) :
82 6C 64 AA 9E A6 E0 82 6C 60 AA 9E A6 61 03 F0 45 53 45 52 50 F6 00 00 00 00 FF 1F 33 00 02 FE 19 00 00 6E D9 D2 63 D2 05 F9 05 C3 05 3B 08 1C 02 41 08 33 0D 1B 00 09 00 3D 08 2C 0D 05 50 19 04 26 01 23 80 06 0F 77 03 17 00 06 03 5C 03 02 00 03 00 08 03 82 02 80 02 81 02 6F 03 07 00 06 03 48 00 5C 03 0A 00 11 00 17 00 07 03 0C 03 02 00 82 03 15 AC 03 64 02 58 B2 39 FA 32 1C C5 F6 87 FF C7 FF DF FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0D 10 0C 00 3F 03 00 00 E9 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 03 00 02 00 02 00 02 00 02 00 02 00 01 00 02 00 02 00 02 00 02 00 01 00 02 00 01 00 02 00 02 00 02 00 02 00 02 00 02 00 01 00 02 00 02 00 02 00 01 00 02 00 08 02 04 02 15 02 FA 01 A0 02 13 02 9C 02 9E 02 9C 02 F7 03 F5 03 F2 03 9B 02 9E 02 9E 02 9E 02 9F 02 9E 02 73 03 02 00
The message starts with call signs 82 6C 64 AA 9E A6 E0 82 6C 60 AA 9E A6 61 03 F0
Identifier for SharjahSat Messages: 45 53 45 52 for confirmation messages from satellite 52 45 53 45
Message id for General TM Packet : 50
Packet size: F6
Packet counter: 00 00 00 00
Message: FF 1F 33 00 02 …
There are some packets with Id “41”. They are usually picture packets, Raw or .jpg files. Since we are dealing with attitude control commissioning, we haven’t got a good picture to show. But I will update you in the coming days.
5 Likes
Ok, I have withdrawn my request because it was not posted properly 
Two quick questions:
- big or little endian?
- which values are signed?
Hi,
I updated the pdf for signed values. They are little endian. I will also add the multipliers for some values in a few days. Thank you!
2 Likes
Those multipliers are needed once we (or maybe you or one of your team or students) builds a dashboard! So far the decoder looks fine - there are 6 bytes left unparsed at the end! Is this expected?
For your information: GPS data, images and those 6 unparsed bytes are provided as Base64 encoded ASCII-Strings, see below:
File data_7075646_2023-01-25T20-04-25:
826c64aa9ea6e0826c60aa9ea66103f04553455241f61a0000006348061a6134c06d349a006d1400da280128a004a4a00292800a2800a4a00292800a2800a280128a0028a0028a0028a0028a0028a0028a0028a0028a0028a0028a0028a0028a0028a0028a0028a0028a00296800a280168a00296800a5a005a2800a750002968016945002d06802e1a8c9a006530d002536801b450025250014940052500149400525001494005140052500145001450014500145001450014500145001450014500145001450014500145001450014500145001450014b40094b4005140052d00145002d1400b4b40052d002d1400ea2801d494016ea33400d34c3400d349400949400945002525001450025140052
Decoded result:
❯ decode_frame Sharjahsat1 ~/Downloads/data_7075646_2023-01-25T20-04-25
{
"dest_callsign": "A62UOS",
"src_callsign": "A60UOS",
"src_ssid": 0,
"dest_ssid": 0,
"ctl": 3,
"pid": 240,
"identifier": "ESER",
"tm_id": 65,
"data_length": 246,
"packet_counter": 26,
"image_data": "Y0gGGmE0wG00mgBtFADaKAEooASkoAKSgAooAKSgApKACigAooASigAooAKKACigAooAKKACigAooAKKACigAooAKKACigAooAKKACigAooAKWgAooAWigApaACloAWigAp1AAKWgBaUUALQaALhqMmgBlMNACU2gBtFACUlABSUAFJQAUlABSUAFJQAUUAFJQAUUAFFABRQAUUAFFABRQAUUAFFABRQAUUAFFABRQAUUAFFABRQAUUAFFABS0AJS0AFFABS0AFFAC0UALS0AFLQAtFADqKAHUlAFuozQA00w0ANNJQAlJQAlFACUlABRQAlFABS"
}
File data_7075646_2023-01-25T20-06-55:
826c64aa9ea6e0826c60aa9ea66103f04553455250f600000000ff1f2f00029f170000988bd1630b062e06000646080f024b08350d1b00090049082c0d4205200325012300060f7a03160006035c0302000300090384028202830273030700060347005b030b001100170008030c030200820355e300baeb81b23d00ffff0300ffff000000000000000000000000000000000000000000000f150c003f03faffe904000000000000000000000000000000000300020002000200020002000100010002000300020002000200020002000100010002000200020002000200020002000100020002000902fb0106020802a00206029c029e029c02f703f503f2039c029f029e029e029f029d0277030200
Decoded result:
❯ decode_frame Sharjahsat1 ~/Downloads/data_7075646_2023-01-25T20-06-55
{
"dest_callsign": "A62UOS",
"src_callsign": "A60UOS",
"src_ssid": 0,
"dest_ssid": 0,
"ctl": 3,
"pid": 240,
"identifier": "ESER",
"tm_id": 80,
"data_length": 246,
"packet_counter": 0,
"op_mode": 8191,
"restart_count": 47,
"last_reset_cause": 2,
"system_uptime": 6047,
"system_time": 1674677144,
"tlm_board_temp1": 1547,
"tlm_board_temp2": 1582,
"tlm_board_temp3": 1536,
"tlm_vbat_v": 2118,
"tlm_vbat_i": 527,
"tlm_vbat_plat_v": 2123,
"tlm_3v3_plat_v": 3381,
"tlm_vbat_periph_i": 27,
"tlm_3v3_periph_i": 9,
"tlm_vbat_periph_v": 2121,
"tlm_3v3_periph_v": 3372,
"temperature": 1536,
"antenna_status": 15,
"vbat": 890,
"ibat": 22,
"vpcm3v3": 774,
"vpcm5v": 860,
"ipcm3v3": 2,
"ipcm5v": 3,
"tbrd": 777,
"tbat1": 644,
"tbat2": 642,
"tbat3": 643,
"vpcmbatv": 883,
"ipcmbatv": 7,
"eps_vpcm3v3": 774,
"eps_ipcm3v3": 71,
"eps_vpcm5v": 859,
"eps_ipcm5v": 11,
"i3v3drw": 17,
"i5vdrw": 23,
"eps_tbrd": 776,
"tbrd_db": 780,
"ipcm12v": 2,
"vpcm12v": 898,
"adcs_state": 85,
"sat_pos_llh_lat": 227,
"sat_pos_llh_lon": -5190,
"sat_pos_llh_alt": -19839,
"estm_att_angle_yaw": 61,
"estm_att_angle_pitch": -1,
"estm_att_angle_roll": 3,
"adcs_gps": "//8AAAAAAAAAAAAAAAAAAAAA",
"smps_temp": 0,
"pa_temp": 0,
"current_3v3": 0,
"voltage_3v3": 0,
"current_5v": 5391,
"voltage_5v": 12,
"battery_current": 831,
"pa_current": 65530,
"battery_voltage": 1257,
"pa_voltage": 0,
"pa_temperature": 0,
"rf_output_power": 0,
"board_temp_top": 0,
"board_temp_bottom": 0,
"vbcr1": 0,
"vbcr2": 0,
"vbcr3": 0,
"vbcr4": 3,
"vbcr5": 2,
"vbcr6": 2,
"vbcr7": 2,
"vbcr8": 2,
"vbcr9": 2,
"ibcra1": 1,
"ibcra2": 1,
"ibcra3": 2,
"ibcra4": 3,
"ibcra5": 2,
"ibcra6": 2,
"ibcra7": 2,
"ibcra8": 2,
"ibcra9": 2,
"ibcrb1": 1,
"ibcrb2": 1,
"ibcrb3": 2,
"ibcrb4": 2,
"ibcrb5": 2,
"ibcrb6": 2,
"ibcrb7": 2,
"ibcrb8": 2,
"ibcrb9": 2,
"tbcra1": 1,
"tbcra2": 2,
"tbcra3": 2,
"tbcra4": 521,
"tbcra5": 507,
"tbcra6": 518,
"tbcra7": 520,
"tbcra8": 672,
"tbcra9": 518,
"tbcrb1": 668,
"tbcrb2": 670,
"tbcrb3": 668,
"tbcrb4": 1015,
"tbcrb5": 1013,
"tbcrb6": 1010,
"tbcrb7": 668,
"tbcrb8": 671,
"tbcrb9": 670,
"vidiodeout": 670,
"iidiodeout": 671,
"solar_panels_unparsed": "nQJ3AwIA"
}
Please confirm correct decoding (of course without conversion furmulas) and thank you very much for your help!
2 Likes
With the new TLE sets from space-track.org we reach the 98 objects. Reminder that the total of the payloads were 114, from which initially to be deployed were 82 and from them only 78 were confirmed. Given that we are closer to the expected number of the objects, I’ll think it is time to identify the satellites that we track some time now by following specific objects. So, here are the latest updates:
| Satellite Identifier | Satellite Name | NORAD ID to Follow | Other Possible NORAD IDs | Notes |
|---|---|---|---|---|
| DELH-6722-1461-1897-7938 | Sharjahsat-1 | 55104 | - | Identified, here are the ikhnos results |
| NJFB-9884-9643-7739-4519 | BDSAT-2 | 55098 | - | Identified, here are the ikhnos results |
| NJEX-6170-8600-1975-0468 | ION SCV-008 | 55051 | - | Identified, here are the ikhnos results |
| VPUU-7194-1121-2414-5647 | ION SCV-007 | 55060 | - | Identified, here are the ikhnos results |
| RJCF-5779-9216-5641-4111 | BRO-8 | 55011 | - | Identified, here are the ikhnos results |
| TVZK-1463-5590-8994-0377 | Connecta T1.2 | 55012 | - | Identified, here are the ikhnos results |
| LSZR-8461-9828-5431-6212 | Star Vibe | 55009 | - | Identified, here are the ikhnos results |
| JRGY-1674-7223-5551-1972 | TAUSAT-2 | 55073 | - | Identified, here are the ikhnos results |
| PDVW-9191-3063-9872-9368 | Vigoride-5 | 55056 | - | From space-track.org, we need reception and confirmation |
| ZVIO-0893-8720-4254-3996 | NSLSat-2 | 55067 | - | From space-track.org, we need reception and confirmation |
| YWEP-1897-4060-1849-8088 | YAM-5 | 55076 | - | From space-track.org, we need reception and confirmation |
| CRQN-9332-8658-6519-0456 | STERNULA-1 | 55054 | - | From space-track.org, we need reception and confirmation |
| NTDX-8976-1799-9857-6479 | LYNK TOWER 3 | 55046 | - | From space-track.org, we need reception and confirmation |
| DTYA-7731-6964-1582-7373 | LYNK TOWER 4 | 55034 | - | From space-track.org, we need reception and confirmation |
| REKY-2761-8978-3233-4536 | EOSSAT-1 | 55053 | - | From space-track.org, we need reception and confirmation |
| KCKF-9169-8304-1813-6974 | Platform-2 | 55010 | all the unidentified rest | Unfortunately it seems that the receptions were probably NSL-2 so for now I’m randomly choose to follow 55010. |
5 Likes
I updated the decoder pdf file and added the multipliers. There shouldn’t be any bytes unparsed. Maybe you skip something on the GPS part. After you apply the multipliers then it can be easier to review the outputs. Thank you for your effort.
2 Likes
Great,
I’ve indeed found the issue regarding the unparsed bytes: I was totally missing the estimated angular rates (yaw, pitch and roll), which is exactly those 6 bytes.
I need to check the conversions still, but I think I’m doing this with a dashboard. There should be plenty of data already.
Thank you!
EDIT:
Decoder is looking good now! Exploring influxDB shows the following for vbat:
Are you interested in building a dashboard on your own? Just let me know whom to add to the editors list…
https://dashboard.satnogs.org/d/HqCRmvA4z/sharjahsat-1?orgId=1
3 Likes
Thank you! It looks so good. 
We haven’t got a plan to create a dashboard for now. But if we decide to do it, I will write to you. Again, thank you for your efforts.
1 Like
I’ve put a basic dashboard in the public telemetry folder! The panel temperature sometimes go crazy - no idea if this was expected and if there’s a way to filter insane values…
Let me know if there is anything important you like me to add to it!
It would be great to have a little bit more information on the GPS data, btw.
2 Likes
The last days @ok2pnq has spotted that BDSAT-2 latest TLE set from space-track.org wasn’t accurate.
For that reason we used the previous one, however it isn’t describe well any more the satellite’s orbit. So, with some strf observations, @PE0SAT generated a new TLE set (I’ve propagated it to the current epoch) that we are going to use in DB and Network:
BDSAT-2
1 55098U 23122.20000000 .00000000 00000-0 00000-0 0 02
2 55098 97.5111 182.7032 0020493 184.8413 173.6189 15.17151402 05
3 Likes
Zeus-1 has been deployed from Vigoride 5 on 11th May. Here is the current TLE we use for tracking it:
ZEUS-1
1 99255U 23130.93040509 .00000000 00000-0 17266-3 0 9994
2 99255 097.4838 190.9789 0010826 138.7158 344.1028 15.14835688 05
3 Likes