Wireless connection to Pixhawk - Niklas Fehringer #5


 Starting point


As a necessary step to implement path planning, we needed a Wi-Fi connection from topside to the companion computer. A very good starting point is provided through the following Link:


wireless configuration for companion


Although this explanation is very useful, it assumes an existing setup of 192.168.2.1 for the surface/topside computer. We used a different router which reserved this address for itself independently of it’s configuration. If that guide works for you, stick with it. If not, you might want to try the one provided on this blog entry.


Useful commands for debugging and monitoring


The following commands and addresses were used for configuration/monitoring/debugging throughout the Wi-Fi configuration. It’s not necessary for the configuration but likely a good reference in case things go wrong:


My debugging/network monitoring setup:

- 3 powershell/cmd windows with:

ping 192.168.2.2 (connection to companion)

ping google.com (connection to internet)

tracert google.com (way to internet --> shows where it may break)


- Web-browser tab with 192.168.2.2:2770/network
                                                                (shows if companion has internet connection,          assuming topside has internet)

- Web-browser tab with 192.168.2.2:8088
                                                                 (command line of companion to use
                                                                  ping 192.168.2.4
                                                                  traceroute google.com)

Companion default login: username: pi, password: companion


Steps to implement Wi-Fi


For the following steps, you will need a router which will be connected by Ethernet to your companion computer. (Therefore you may not use your home router)


- Go to your routers configuration page and login. (If you don’t know how to login, search your routers default login in the web)

- Find the configuration of “DHCP-lease”. 

- Change it to use 192.168.2.3 as first address (router) with the subnet 255.255.255.0

- You likely will be disconnected from the router. Use the new router address to access the configuration page again.

- You may need to add the companions mac address with the ip 192.168.2.2, but we will ignore this step for now. You might try it, if this explanation don’t work out.

- connect the companion to the router per Ethernet

- on the topside, go to network adapter settings and change the ipv4 address to:

address:     192.168.2.4

subnet:     255.255.255.0

gateway: 192.168.2.3



Your topside computer should now be connected wirelessly to the companion. 

Comments

Post a Comment

Popular posts from this blog

How to: Tello drone to micro bit - Victor Alikberov, Blog#1

Image
1. Introduction. The purpose of this blog is to explain everything that is needed in order to connect tello drone to micro bit. It will cover wiring,  javascript code behind custom created tello extension and how to use this extension to connect and drive tello via microbit. 2. Wiring. Since tello drone creates its own wi-fi hotspot, additional wi-fi module is required in order to establish wireless connection between micro bit and tello. ESP8266 will be used to connect micro bit to tello wi-fi hotspot and also to establsih UDP communications between micro bit and drone. The pinout of the ESP8266 chip is shown below. ESP8266 chip pinout. Receiving port (Rx) is connected to transmitting port of the micro bit (pin 2) and transmitting port (Tx) of the ESP8266 is connected to receiving port of the micro bit (pin 1).  3.3 volts power supply should be provided both to micro bit and ESP8266 chip. Chip enable port is also connected to 3.3v power supply.  ESP8266 plus microbi...
Read more

First USV Test - Jack Pender, Blog #5

Image
Introduction: On the 18 th of March we held our first field test at Killurin Bridge in Wexford. We met there at 10 am, with a plan of finishing up at 2 pm, giving us plenty of time to test each aspect of the project we have been working on. It was great to see the USV on the water for the first time, and it helped to visualise it in the setting that its use is intended for. Testing: The main tests for this first field test were to trial the driving functionality; Manual Drive, Microbit Drive and Cloud Drive. Using the controller, the drive of the USV was successful and it was great to finally see its speed and mobility on the water. With the Manual Drive, controlled by Patryck, going according to plan, this allowed us to test the Microbit Drive, which would be controlled by Adam. Using two Microbits to control the direction and thruster power, Adam completed a successful drive of the USV. This was great to see as it meant that the control of the USV could be friendly to everyone...
Read more

OpenCV To RoboRealm - Jack Pender, Blog #7

Image
Introduction: Developing further on getting the camera feed from the Tello drone to a viewable format, it was decided to try and get the camera feed into RoboRealm. Once the camera feed is in RoboRealm, it can essentially be sent to anywhere from there, in our case Ubidots, but if this were to change we would now have a better starting point. RoboRealm: RoboRealm was created in 2006 to take advantage of lower cost generic computing, a widening range of lower cost imaging devices, an increasing need and usage of vision as a primary sensor device and the desire to come to a solution with an interactive user interface with minimal programming. This made it ideal for this project as it meant that for future iterations it would be quick and simple for someone else to get up and running with. Procedure: Using multiple of the built-in features of RoboRealm I created a programe that would start a screen capture in order to have RoboRealm capture the drone feed. Firstly, within an if ...
Read more