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