eive/eive-obsw
eive/eive-obsw
13
4
Fork 0
Code Issues 4 Pull Requests 1 Releases 120 Wiki Activity

another minor update
Some checks are pending
EIVE/eive-obsw/pipeline/head This commit looks good
Details
EIVE/eive-obsw/pipeline/pr-develop Build started...
Details

Browse Source
This commit is contained in:
Robin Müller 2021-10-11 11:10:30 +02:00
parent 7d6022ab09
commit f3f96e02a2
No known key found for this signature in database
GPG Key ID: 71B58F8A3CDFA9AC
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -576,13 +576,14 @@ Note: When now setting up a debug session in the Xilinx SDK or Eclipse, the host
to localhost instead of the IP address of the Q7S. to localhost instead of the IP address of the Q7S.
# <a id="tmtc-testing"></a> TMTC testing # <a id="tmtc-testing"></a> TMTC testing
The OBSW supports sending PUS TM packets via TCP or the PDEC IP Core which transmits the data as The OBSW supports sending PUS TM packets via TCP or the PDEC IP Core which transmits the data as
CADU frames. To make the CADU frames receivabel by the CADU frames. To make the CADU frames receivabel by the
[TMTC porgram](https://egit.irs.uni-stuttgart.de/eive/eive-tmtc), a python script is running as [TMTC porgram](https://egit.irs.uni-stuttgart.de/eive/eive-tmtc), a python script is running as
`systemd` service named `tmtc_bridge` on the flatsat PC which forwards TCP commands to the TCP `systemd` service named `tmtc_bridge` on the flatsat PC which forwards TCP commands to the TCP
server of the OBC and reads CADU frames from a serial interface. server of the OBC and reads CADU frames from a serial interface.
You can check whether the service is running with You can check whether the service is running the following command on the flatsat PC
```sh ```sh
systemctl status tmtc_bridge systemctl status tmtc_bridge