Not able to access flytconsole!


#1

Hey there,

I have a pixhawk 2.1 with edison on board.
I downloaded the flytos and flashed it following the instructions given in the site.
I could successfully flash it and got EDISON Wifi also seen in my list of wifi networks available.

Now , as told in the instructions , I wanted to connect to flytconsole so I connected to edison wifi network and oepned up chrome and tried navigating to 192.168.42.1/flytconsole but the site says

" This site can’t be reached
192.168.42.1 refused to connect.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED "

I tried disabling all firewalls and proxy and still no luck.
I also fired up ipconfig and got the actual IP address of the network and replaced it with the one given and still it says the same error.

What am I doing wrong ?

I want to connect the pixhawk to internet and later remotely control it. I learn that I have to have the edison in client mode.

Please help


#2

I am confused! Is the IP address of Edison different from 192.168.42.1 ?
Also, can you ssh into edison?
Moreover, connect to Edison using its USB console, and try manually launching FlytOS.


#3

Okay, So I’ve done some progress,
a) first of all , Yes edison in hotspot mode did show a different ip address at ipconfig for me, but later when i checked it in the file /etc/network/interfaces it showed 192.168.42.1 under Wlan0 inet static as expected

  1. I could connect to Edison using Putty, as given in https://software.intel.com/en-us/setting-up-serial-terminal-on-system-with-windows
    I changed the edison to a client mode and i tried running iwgetid and i confirmed that the edison is connected to my wifi hotspot, ( The Phone which is providing that hotspot also confirmed the connection success )
  2. I now connected to the same network on my laptop and tried to navigate to 192.168.42.1/flytconsole - NO LUCK , same results
  3. I notice that edison is rebooting automatically and I can see the progress in the serial terminal.
    but as it loads up it takes a long time to finish a particular task sometimes -
    " Raise network interfaces"
  4. I tried stopping flytos manually and relaunching it again from putty.
    I’ve attached relaunch log below,

root@flytos:/home/flytos# stop_flytOS
600
608
600
608
flytlaunch not running
root@flytos:/home/flytos# launch_flytOS
WARNING:root:ZMQ : Protobuf message implementation not found. Using pickle based protocol
Direct import of flyt_ms and rostful
INFO:startup_log:
================== FlytOS Startup Log ================
INFO:startup_log:Mon Feb 5 13:25:00 2018: Launching initial Log Server - you can check logs at http:///logs
INFO:startup_log:Mon Feb 5 13:25:01 2018: FlytOS will try to auto-detect autopilot in these ports : /dev/ttyMFD1, udpin:0.0.0.0:14550, /dev/ttySAC1, /dev/ttySAC0, /dev/ttyTHS1, /dev/ttyTHS2, /dev/ttyACM1, /dev/ttyAMA1, /dev/ttyAMA0, /dev/ttyUSB1,
INFO:startup_log:Mon Feb 5 13:25:01 2018: FlytOS will try to auto-detect autopilot in the above ports with baudrate: 57600, 115200, 921600,
INFO:startup_log:Mon Feb 5 13:25:01 2018: Refer http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html, if your serial port or baudrate is not included in the list. Also notify us at http://forums.flytbase.com/ so that we add it to our default list
INFO:startup_log:Mon Feb 5 13:25:01 2018: Trying to open /dev/ttyMFD1 with baudrate 57600

  • Running on http://0.0.0.0:80/ (Press CTRL+C to quit)
  • Restarting with stat
  • Debugger is active!
  • Debugger pin code: 143-775-514
    INFO:startup_log:Mon Feb 5 13:25:04 2018: Trying to open udpin:0.0.0.0:14550 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttySAC1 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttySAC0 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttyTHS1 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttyTHS2 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttyACM1 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttyAMA1 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttyAMA0 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttyUSB1 with baudrate 57600
    INFO:startup_log:Mon Feb 5 13:25:07 2018: Trying to open /dev/ttyMFD1 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:10 2018: Trying to open udpin:0.0.0.0:14550 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttySAC1 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttySAC0 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttyTHS1 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttyTHS2 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttyACM1 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttyAMA1 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttyAMA0 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttyUSB1 with baudrate 115200
    INFO:startup_log:Mon Feb 5 13:25:13 2018: Trying to open /dev/ttyMFD1 with baudrate 921600
    INFO:startup_log:Mon Feb 5 13:25:14 2018: Detected serial port: /dev/ttyMFD1 at baudrate: 921600
    INFO:startup_log:Mon Feb 5 13:25:15 2018: MAVLink protocol: 2.0 detected.
    INFO:startup_log:Mon Feb 5 13:25:15 2018: Downloading list of params from autopilot
    INFO:startup_log:Mon Feb 5 13:25:18 2018: Param download complete
    INFO:startup_log:Mon Feb 5 13:25:20 2018: Detected autopilot: px4
    INFO:startup_log:Mon Feb 5 13:25:20 2018: PX4 autopilot detected
    INFO:startup_log:Mon Feb 5 13:25:20 2018: Checking internet availability…
    INFO:startup_log:Mon Feb 5 13:25:21 2018: Internet connection established
    INFO:startup_log:Mon Feb 5 13:25:21 2018: License file invalid. Please activate/reactivate your device by entering license key in flytconsole.
    INFO:startup_log:Mon Feb 5 13:25:21 2018: License activation is: False
    INFO:startup_log:Mon Feb 5 13:25:21 2018: Starting FlytOS(Restricted) - Needs Activation
    INFO:startup_log:Mon Feb 5 13:25:22 2018: Exiting Startup.License invalid!
    INFO:startup_log:========================================================

root@flytos:/home/flytos# … logging to /root/.ros/log/0622baf6-0a78-11e8-b145-fcdbb398a5d9/roslaunch-flytos-1159.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

Invalid roslaunch XML syntax: no element found: line 1, column 0
The traceback for the exception was written to the log file

even now when I try launching flytconsile using 192.168.42.1/flytconsole it says,

This site can’t be reached
192.168.42.1 refused to connect.
Search Google for fly console
ERR_CONNECTION_REFUSED

Am I missing something?


#4

I see one more thing that sounded out of the usual for me ,

Though using serial with baud rate of 115200 for putty worked for me to access edison terminal,
I tried to SSH Using USB, by trying to get putty run using IP set as given in
https://software.intel.com/en-us/connecting-to-intel-edison-board-using-ethernet-over-usb

Now to my surprise I see that RNDIS is not at all seen in my device manger also.
I had seen it some days ago with a yellow exclamation , before I installed intel edison drivers.

Anything missing here ?


#5

Hi @evandanrao,

Your FlytOS seems to be broken as suggested by :

The image has an older version of FlytOS, which was prone to this error. This has been solved in the later releases. We are in process of updating the image for Edison, to get this reolved. For now, I would request you to update FlytOS debian package.

For this,

  1. Download the debian package into Edison.
  2. Connect to edison via USB, and go to the directory where you have kept the package, and run this command:
    • sudo dpkg -i flytos*.deb
  3. This should install the latest FlytOS.

Now you should be able to connect to FlytConsole.

Since, your device IP is not 192.168.42.1 it would anyway won’t work. In case of client mode, please get Edison’s IP address from router’s admin page or running sudo ifconfig in Edison’s terminal, and use this IP to open FlytConsole.


#6

Can you elaborate steps 1 and 2 in the above ?
I downloaded the debian,
should I copy it to the internal otg drive that edison has?
and how do I access the same later ?

I am a little new to the platform


#7

If you can access the internet from Edison, you can use the command line to download the debian package.
Run this command:

wget https://downloads.flytbase.com/flytos/downloads/debian/master/edison/flytosv1.5-5e.deb


#8

Thanks ! Wonderful! It worked! Im in!


#9