Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems seeing commands on cFS system log #1889

Closed
mdunn47 opened this issue Feb 10, 2025 · 2 comments
Closed

Problems seeing commands on cFS system log #1889

mdunn47 opened this issue Feb 10, 2025 · 2 comments
Labels
triage More information is needed

Comments

@mdunn47
Copy link

mdunn47 commented Feb 10, 2025

I currently have a working COSMOS-cFS setup using COSMOS4 and the cFS Draco development branch along with OpenSatKit. While trying to port over the plugins and targets from COSMOS4 to COSMOS6 I am not able to view any commands in the cFS log other than the "TO_ENABLE_TELEMETRY" command. which gives the expected output and correctly enables tlm:

COMMAND CFS TO_LAB_ENABLE BIG_ENDIAN "Enable telemetry"
  #                   NAME      BITS TYPE   min VAL     max VAL    init VAL  DESCRIPTION
  APPEND_ID_PARAMETER STREAM_ID  16  UINT   0x1880      0x1880     0x1880    "Stream ID"
    FORMAT_STRING "0x%04X"
  APPEND_PARAMETER    SEQUENCE   16  UINT   0xC000      MAX_UINT16 0xC000    ""
    FORMAT_STRING "0x%04X"
  APPEND_PARAMETER    PKT_LEN    16  UINT   0x0001      0xFFFF     0x0012    "length of the packet"
  APPEND_PARAMETER    CMD_ID      8  UINT   6           6          6         ""
  APPEND_PARAMETER    CHECKSUM    8  UINT   MIN_UINT8   MAX_UINT8  0x98      ""
    FORMAT_STRING "0x%2X"
  APPEND_PARAMETER    DEST_IP   144  STRING "127.0.0.1"  

cFS log:
/TO_LAB_APP 3: TO telemetry output enabled for IP 127.0.0.1

When I use the example code for the NOOP command I do not see anything on the cFS logs;

COMMAND CFS NOOP BIG_ENDIAN "NOOP Command"
  # cFS primary header
  APPEND_ID_PARAMETER    STREAM_ID   16   UINT   0x1882      0x1882      0x1882      "Packet Identification"
      FORMAT_STRING "0x%04X"
  APPEND_PARAMETER       SEQUENCE    16   UINT   MIN_UINT16  MAX_UINT16  0xC000      ""
      FORMAT_STRING "0x%04X"
  APPEND_PARAMETER       PKT_LEN     16   UINT   0x0001      0x0001      0x0001      "Packet length"
  # cFS CMD secondary header
  APPEND_PARAMETER       CMD_ID       8   UINT   0           0           0           ""
  APPEND_PARAMETER       CHECKSUM     8   UINT   MIN_UINT8   MAX_UINT8   MIN_UINT8   ""

I tried using the general NOOP command from the Commands example file in the exact same target file (replacing the cFS NOOP example):

COMMAND TARGET NOOP BIG_ENDIAN "Do Nothing"
  PARAMETER CCSDSVER 0 3 UINT 0 0 0 "CCSDS PRIMARY HEADER VERSION NUMBER"
  PARAMETER CCSDSTYPE 3 1 UINT 1 1 1 "CCSDS PRIMARY HEADER PACKET TYPE"
  PARAMETER CCSDSSHF 4 1 UINT 0 0 0 "CCSDS PRIMARY HEADER SECONDARY HEADER FLAG"
  ID_PARAMETER CCSDSAPID 5 11 UINT 0 2047 101 "CCSDS PRIMARY HEADER APPLICATION ID"
  PARAMETER CCSDSSEQFLAGS 16 2 UINT 3 3 3 "CCSDS PRIMARY HEADER SEQUENCE FLAGS"
  PARAMETER CCSDSSEQCNT 18 14 UINT 0 16383 0 "CCSDS PRIMARY HEADER SEQUENCE COUNT"
  PARAMETER CCSDSLENGTH 32 16 UINT 0 0 0 "CCSDS PRIMARY HEADER PACKET LENGTH"
  PARAMETER DUMMY 48 8 UINT 0 0 0 "DUMMY PARAMETER BECAUSE CCSDS REQUIRES 1 BYTE OF DATA"

And I was able to see output on cFS:

`/CI_LAB_APP 8: CI: L369, cmd 100 c00 dropped, bad length=7'

In all cases I can see the packets being sent while inspecting the docker network, but I only see the output on cFS for TO_ENABLE_TELEMETRY and the general NOOP.

I'm not sure what could be causing this issue, any suggestions?

@jmthomas
Copy link
Member

What is the 'cFS log'?

When you send a command do you see it in the COSMOS CmdTlmServer LogMessages output? Do you see the Cmd Pkts counter increment. Can you see the raw bytes using the Cmd Packets tab?

@jmthomas jmthomas added the triage More information is needed label Feb 10, 2025
@mdunn47 mdunn47 closed this as completed Feb 20, 2025
@jmthomas
Copy link
Member

@mdunn47 Can you add some resolution notes to this ticket for anyone with a similar problem in the future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage More information is needed
Projects
None yet
Development

No branches or pull requests

2 participants