We have also LOGSATS deployed earlier today, here is a TLE set for tracking it:
LOGSATS
1 98965U 23000XX 23349.56753376 .00000000 00000-0 63082-4 0 9998
2 98965 97.6454 54.1390 0016337 190.9683 348.5431 15.00589146 09
1 Like
Hi Julian,
Will the CW beacon remain on or will it also only be available when these satellites are over the TU ground station?
Best,
Bob
N6RFM
1 Like
Thanks you, i will have a look at it
1 Like
Hi Bob,
Please check out this post. There will be a beacon until first contact but two times: Monday morning for NanoFF A as well as Tuesday morning for NanoFF B. If there will be no contact for whatever reasons the beacon continues transmitting.
Sebastian
2 Likes
Hey everyone,
we were just informed by our launch provider that the deployment of our NanoFF satellites has been postponed until further notice. We will let you know when there is a new separation time.
3 Likes
Latest Status update:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update | Notes |
|---|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | |||||||
| - | EIRSAT-1 | 58472 | - | YES | YES | Identified, here are the ikhnos results | |
| - | SpIRIT | 58468 | - | YES | YES | Identified, here are the ikhnos results | |
| - | ENSO | 58470 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Hayasat | 58471 | - | YES | YES | Identified, here are the ikhnos results | |
| 98968 | ION SCV Daring Diego | 58463 | 58469 | NO | YES | Received, changed to follow 58463, other possible 58469 removed 58462 | |
| RECEIVED | |||||||
| - | OBJECT D | 58465 | - | NO | YES | Received on S-band, unknown satellite | |
| - | Lilium-1 | 58467 | - | YES | YES | Identified in space-track.org | |
| 98969 | uHETSat | 58466 | 58465(unlikely), 58467(unlikely) | NO | YES | Received, continue to follow 58466, other possible 58465(unlikely), 58467(unlikely) | Not received since |
| NOT RECEIVED WITH FREQUENCY | |||||||
| 98970 | KOYOH | 58463 | all(non-identified) | NO | YES | Randomly chosen to follow 58463, all non-identified objects are possible candidates | |
| 98965 | LOGSATS | - | - | NO | YES | Deployed recently from ION deployer, no reception yet |
2 Likes
Hi everyone,
Please find here the tool we developped to decode ENSOās beacons.
Youāll find two sections; one to decode raw beacon freshly out of the oven, and a second to add a valided beacon to our database, contributing by this way to the improvment to our platform.
Your support is a precious and appreciated help, thx for that,
Sincerly,
3 Likes
Latest status update, with a new TBA TLE set, this set is near the ION deployer and probably is the recently deployed LOGSATS:
| Temporary NORAD ID | Satellite | NORAD ID to follow | Other NORAD IDs | Identified | Deployed | Last Update | Notes |
|---|---|---|---|---|---|---|---|
| RECEIVED AND DEMODULATED | |||||||
| - | EIRSAT-1 | 58472 | - | YES | YES | Identified, here are the ikhnos results | |
| - | SpIRIT | 58468 | - | YES | YES | Identified, here are the ikhnos results | |
| - | ENSO | 58470 | - | YES | YES | Identified, here are the ikhnos results | |
| - | Hayasat | 58471 | - | YES | YES | Identified, here are the ikhnos results | |
| - | ION SCV Daring Diego | 58469 | - | YES | YES | Identified, here are the ikhnos results | |
| RECEIVED | |||||||
| - | OBJECT D | 58465 | - | NO | YES | Received on S-band, unknown satellite | |
| - | Lilium-1 | 58467 | - | YES | YES | Identified in space-track.org, here are the ikhnos results | |
| 98969 | uHETSat | 58466 | 58465(unlikely), 58467(unlikely) | NO | YES | Received, continue to follow 58466, other possible 58465(unlikely), 58467(unlikely) | Not received since |
| NOT RECEIVED WITH FREQUENCY | |||||||
| 98970 | KOYOH | 58463 | all(non-identified) | NO | YES | Randomly chosen to follow 58463, all non-identified objects are possible candidates | |
| 98965 | LOGSATS | 58642 | all(non-identified) | NO | YES | Randomly choose 58462 as it is a new object in space-track.org and near to ION deployer, no reception yet |
2 Likes
how to use Messaging system tools?
It is noteworthy that on December 22, the pocketqubes U2N and MDQpocketqube2 were deployed from the ION SCV Daring Diego
2 Likes
Given this and the tweet by Jonathan McDowell:
https://twitter.com/planet4589/status/1738794991567200719
Probably the TLE set for 58642 describes either the group of the two pocketqubes or one of them.
In https://twitter.com/AlbaOrbital/status/1738296774526128470 there is a report about U2N communication.
3 Likes
It appears that MDQubesat2 is transmitting erratically based on the reports received in TinyGS.
1 Like
Hello 
Here is what i have so far,
---
meta:
id: ax25monitor
endian: le
doc: |
:field dest_callsign: ax25_frame.ax25_header.dest_callsign_raw.callsign_ror.callsign
:field src_callsign: ax25_frame.ax25_header.src_callsign_raw.callsign_ror.callsign
:field src_ssid: ax25_frame.ax25_header.src_ssid_raw.ssid
:field dest_ssid: ax25_frame.ax25_header.dest_ssid_raw.ssid
:field rpt_callsign: ax25_frame.ax25_header.repeater.rpt_instance[0].rpt_callsign_raw.callsign_ror.callsign
:field ctl: ax25_frame.ax25_header.ctl
:field pid: ax25_frame.payload.pid
:field monitor: ax25_frame.payload.ax25_info.data_monitor
Attention: `rpt_callsign` cannot be accessed because `rpt_instance` is an
array of unknown size at the beginning of the parsing process! Left an
example in here.
seq:
- id: ax25_frame
type: ax25_frame
doc-ref: 'https://www.tapr.org/pub_ax25.html'
types:
ax25_frame:
seq:
- id: ax25_header
type: ax25_header
- id: payload
type:
switch-on: ax25_header.ctl & 0x13
cases:
0x03: ui_frame
0x13: ui_frame
0x00: i_frame
0x02: i_frame
0x10: i_frame
0x12: i_frame
# 0x11: s_frame
ax25_header:
seq:
- id: dest_callsign_raw
type: callsign_raw
- id: dest_ssid_raw
type: ssid_mask
- id: src_callsign_raw
type: callsign_raw
- id: src_ssid_raw
type: ssid_mask
- id: repeater
type: repeater
if: (src_ssid_raw.ssid_mask & 0x01) == 0
doc: 'Repeater flag is set!'
- id: ctl
type: u1
repeater:
seq:
- id: rpt_instance
type: repeaters
repeat: until
repeat-until: ((_.rpt_ssid_raw.ssid_mask & 0x1) == 0x1)
doc: 'Repeat until no repeater flag is set!'
repeaters:
seq:
- id: rpt_callsign_raw
type: callsign_raw
- id: rpt_ssid_raw
type: ssid_mask
callsign_raw:
seq:
- id: callsign_ror
process: ror(1)
size: 6
type: callsign
callsign:
seq:
- id: callsign
type: str
encoding: ASCII
size: 6
ssid_mask:
seq:
- id: ssid_mask
type: u1
instances:
ssid:
value: (ssid_mask & 0x0f) >> 1
i_frame:
seq:
- id: pid
type: u1
- id: ax25_info
type: ax25_info_data
size-eos: true
ui_frame:
seq:
- id: pid
type: u1
- id: ax25_info
type: ax25_info_data
size-eos: true
ax25_info_data:
seq:
- id: raw
type: u2
- id: var_ts
type: u4
- id: obdh_timestamp
type: u4
- id: obdh
type: u4
- id: obdh_nb_bytes_to_transmit
type: u4
- id: obdh_nb_of_obdh_resets
type: u2
- id: obdh_nb_of_errors
type: u2
- id: eps_eps_mode
size: 1
- id: eps_bat_volt
type: u1
- id: eps_bat_temp
type: s1
- id: eps_bat_volt_min
type: u1
- id: eps_bat_volt_max
type: u1
- id: eps_bat_volt_avg
type: u1
- id: raw3
size: 3
- id: eps_temp_z_minus
type: u1
- id: eps_obdh_cur
type: u1
- id: eps_eps_cur
type: u1
- id: eps_ttc_micro_cur
type: u1
- id: eps_ttc_tx_cur
type: u1
- id: eps_ttc_tx_cur_max
type: u1
- id: eps_pl_cur
type: u2
- id: eps_charge_cur
type: u2
- id: rest
type: str
encoding: utf-8
size-eos: true
instances:
eps_bat_volt_tmp:
value: eps_bat_volt * 20
eps_bat_volt_min_tmp:
value: eps_bat_volt_min * 20
eps_bat_volt_max_tmp:
value: eps_bat_volt_max * 20
eps_bat_volt_avg_tmp:
value: eps_bat_volt_avg * 20
With this ksy iām getting this result :
This looks pretty good until a certain point which is the eps_temp_z_plus, using a signed byte like for the other temperatures is giving me -53 which is probably wrongā¦ from there i have hard time identifying coherent data ā¦
Notes and other questions :
- The fields called raw 1 2 3 ā¦ are unidentified data so far. Do you have more details about the frame format ?
- eps_eps_mode has no type because itās probably a mask or static values, but i donāt have the details. Same for obdh.
- eps_ttc_tx_cur_max is, iām pretty sure an unsigned byte, but 160 doesnāt fit samples data from your Data diffusion plateform (800) . You obviously canāt get 800 out of 8 bits, so is there a multiplicator ? (x5 ? 160x5 = 800 )
Hi @yd9ckh,
Messaging tool will be available once the satelliteās commissioning will be done.
iāll keep you updated on how itās works
1 Like
Hello deckbsd!
We kindly thank you for your efforts at analyzing our missionās data and contributing.
We use different decoding procedures for different variables.
Soon this month we will post an update regarding ENSO Decoding with all of the details that you mentioned above ( raw fields and etc )
1 Like
Update Separation of NanoFF A & B
We have new separation times for our newest CubeSats. Now NanoFF B will be separated first on Wednesday morning, 10th January, targeting a time of 05:15 UTC. NanoFF A will then follow on the next day, Thursday morning, 11th January, targeting 05:38 UTC. Maybe we can publish new TLEs tomorrow evening, otherwise the ones from ION can be used (later probably updated through STRF). Afterwards it is a priority to sample GNSS data as soon as possible to generate own TLEs. Our TLEs will be published here [1], but if you wish I can also post them here. Until the first successful contact each satellite will transmit a beacon as described in the first message, we will let you know when we have disabled it.
[1] NanoFF TLEs: https://git.tu-berlin.de/rft/com/tle/-/raw/master/NanoFF.txt
2 Likes
We have got some TLEs for NanoFF B from our launch provider.
NanoFF B SatNOGS
1 98963U 24000XX 24010.21910573 .00000000 00000-0 33105-5 0 9993
2 98963 97.6457 79.4258 0017058 106.5628 73.1545 15.01768915 07
Although our ADCS specialist are thinking that the B* value might to be to low which mean they should get faster old, but for tomorrow that should be fine.
1 Like
NanoFF B Beacon has been deactivated following the first pass over the Berlin ground station. We have received first telemetry, satellite seems to be in a healthy status.
2 Likes
A short summary of NanoFF Bās first day of operation:
- First contact was successfully established during 11Ā° elevation pass over our Berlin ground station at ~08:10 UTC
- Over the day multiple passes were successfully conducted
- 250 SatNOGS Observations were done of which in 111 a signal was visible
- Satellite is in good health and most important subsystems were tested
- To complete the verification of the ejection vector by capturing more measurement data (including GNSS data), we have decided to postpone the ejection of NanoFF A by approximately 24 hours in consultation with the launch provider. This will allow us to collect more data and potentially make minor, last adjustments to the ejection vector to ensure a precise ejection of the second satellite. Because of our mission goal of formation flight that is very important. We will announce a new separation time when it has been set.
- NanoFF B operations will continue tomorrow
3 Likes