Patch 1 #1
Patch 1 #1
Conversation
switching to TCP because it works
README.md
Outdated
| - `cd /etc/systemd/network` | ||
| - edit lidar.network and set IP that talks to the beaglebone (where the LIAR is normally) to be 192.168.0.4 | ||
| - `sudo apt install socat` | ||
| - Run `ifconfig` on each to verify that the microhard radio is `enp0s20f0u5u3` |
There was a problem hiding this comment.
No longer necessary now that it uses TCP instead of UDP multicast (only multicast needs to specify the device)
README.md
Outdated
| - edit lidar.network and set IP that talks to the beaglebone (where the LIAR is normally) to be 192.168.0.4 | ||
| - `sudo apt install socat` | ||
| - Run `ifconfig` on each to verify that the microhard radio is `enp0s20f0u5u3` | ||
| - From home directory, `git clone https://github.com/shield-ai/rtlizer.git` |
There was a problem hiding this comment.
Robot does not need any code, just socat installed
There was a problem hiding this comment.
robot still needs ./shockwave_proxy.sh, doesn't it?
There was a problem hiding this comment.
No, because the contents of it are actually just copied directly into skywalker
README.md
Outdated
| - `cd rtlizer/client` | ||
| - `make` | ||
| - `cd ..` | ||
| - Edit fake_ground_station to set the device to the network device through which your ground station is connected to wave relay (perhaps `eth0` or `enp3s0` or `wlan0` or `wlp2s0`) |
There was a problem hiding this comment.
No longer necessary with TCP, only UDP multicast
There was a problem hiding this comment.
GCS still needs socat, correct?
There was a problem hiding this comment.
Yes, it still needs everything except setting the network device
README.md
Outdated
| On the beaglebone, see `~/rtlizer/start.sh`. If you set `fake_data` to true, it will | ||
| On the beaglebone: | ||
| - `cd ~/rtlizer` | ||
| - `./start.sh` |
There was a problem hiding this comment.
These new steps are not necessary because the rc.local change runs start.sh automatically
README.md
Outdated
| On skywalker, run `shockwave_proxy.sh`. | ||
| On skywalker,: | ||
| - `cd ~/rtlizer` | ||
| - `./shockwave_proxy.sh`. |
There was a problem hiding this comment.
This script is actually full redundant with the socat changes in skywalker. No need to run it manually; it should either be deleted or called from skywalker
| @@ -2,4 +2,4 @@ | |||
|
|
|||
| microhard=enp0s20f0u5u3 | |||
|
|
|||
| socat UDP4-RECV:5555 UDP4-DATAGRAM:224.255.0.1:6666,ip-add-membership=224.255.0.1:$microhard | |||
| socat UDP4-RECV:5555 TCP4-LISTEN:8888 | |||
There was a problem hiding this comment.
Note that this script is not run, so either these changes need to be made in skywalker or this script should be called from there
There was a problem hiding this comment.
Added to the instructions to run this line on skywalker
|
|
||
| On the ground station, run `fake_ground_station` or `real_ground_station`, espective of the value of `fake_data` on the beaglebone. | ||
| On the ground station: | ||
| - `socat TCP4:<robot>:8888 -` |
There was a problem hiding this comment.
The old line was correct, this change is not necessary, instead fake_ground_station needs to be updated
|
|
||
| On skywalker, run `shockwave_proxy.sh`. | ||
| On skywalker,: | ||
| - `socat UDP4-RECV:5555 TCP4-LISTEN:8888` |
There was a problem hiding this comment.
This is automatically run in the skywalker script (which needs to be updated) so nothing needs to be run manually
Lots of updates to instructions.
Modifications to use TCP instead of UDP. This works now.