search

foxsi / GSE-FOXSI-4

GSE for calibration and flight operation of FOXSI-4
Other
0 stars 1 forks source link

Clarify uplink packet format and define command bitstrings #6

Open thanasipantazides opened 1 year ago

thanasipantazides commented 1 year ago

What to figure out

Packets are (abstractly) composed like this:

<target system address> <command> <argument>

and wrapped in UDP/Ethernet packets for transmission. This is very basic.

A much more verbose/explicit definition is:

<uplink ID number> <ID delimiter> <target system address> <address delimiter> <command> <command delimiter> <argument> <end of packet>

Is that better? What aspects for the verbose packet should be adopted?

thanasipantazides commented 1 year ago

Packet terminator <end of packet> is probably not needed. Packet contents should be delivered whole to Formatter or not at all due to Ethernet CRC function.

thanasipantazides commented 1 year ago

I do like the idea of an uplink ID number. It could make for easy post-mortem if it is only logged on Formatter, and packet uplink count should be tracked on the ground anyway. Suggest making uplink ID number 32 bits (for plenty of room).

Issue: how to synchronize? What if GSE reboots while Formatter on?