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 +35 -7
4 changed files with 35 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
README.md
View File

@ -576,11 +576,38 @@ 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.
# <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 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 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 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:
````
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
[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.
You can check whether the service is running the following command on the flatsat PC
```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:
```sh
ssh -L 1537:127.0.0.1:7100 eive@2001:7c0:2018:1099:babe:0:e1fe:f1a5 -t bash
````
Note: The encoding of the TM packets and conversion of CADU frames takes some time. Thus the replies are received with a larger delay compared to a direct TCP connection.
```
You can print the output of the `systemd` service with
```sh
journalctl -u tmtc_bridge
```
This can be helpful to determine whether any TCs arrive or TMs are coming back.
Note: The encoding of the TM packets and conversion of CADU frames takes some time.
Thus the replies are received with a larger delay compared to a direct TCP connection.
# <a id="direct-debugging"></a> Direct Debugging

2
fsfw

@ -1 +1 @@
Subproject commit a578f0390bce6c0a3d1d1e8d59764072f1075867
Subproject commit b985bf5167be74c0d43bd70c501eb5f9640bd99e

3
scripts/q7s-port.sh
View File

@ -2,7 +2,8 @@
echo "Setting up all Q7S ports"
echo "-L 1534:192.168.133.10:1534 for connection to TCF agent"
echo "-L 1535:192.168.133.10:22 for file transfers"
echo "-L 1536:192.168.133.10:7301 for TMTC commanding"
echo "-L 1536:192.168.133.10:7301 for TMTC commanding using the TCP/IP IF"
echo "-L 1537:127.0.0.1:7100 for TMTC commanding using the CCSDS IF"
ssh -L 1534:192.168.133.10:1534 \
-L 1535:192.168.133.10:22 \

2
tmtc

@ -1 +1 @@
Subproject commit 1a176582883aed989870819e5e57e0ce0a78ecda
Subproject commit 7b49babb1febb3959f0f817aa4b4ce4c32d6d21c