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

Minor update for README #105

Closed
muellerr wants to merge 13 commits from mueller/master into develop
pull from: mueller/master
merge into: eive:develop
Conversation 0 Commits 13 Files Changed 4 +9 -2
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 7d6022ab09 - Show all commits

11
README.md
View File

@ -580,8 +580,15 @@ The OBSW supports sending PUS TM packets via TCP or the PDEC IP Core which trans
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
`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. The PUS packets transported with
the CADU frames are extracted
server of the OBC and reads CADU frames from a serial interface.
You can check whether the service is running with
```sh
systemctl status tmtc_bridge
```
The PUS packets transported with the CADU frames are extracted
and forwared to the TMTC program's TCP client. The code of the TMTC bridge can be found
[here](https://egit.irs.uni-stuttgart.de/eive/tmtc-bridge). To connect the TMTC program to the
TMTC-bridge a port forwarding from a host must be set up with the following command: