Pixhawk Ordroid communication issues


#1

I’m having a lot of problems getting the pixhawk and odroid to communicate through FlytOS.

Currently I have a pixhawk and odroid XU4 connected through an FTDI adapter. I can confirm that the pixhawk and odroid are talking (I can connect to the pixhawk using mavproxy on the odroid), however the pixhawk refuses to switch to offboard mode or register as connected in the flytconsole.

I switched where flyt_core looked for the pixhawk as outlined in the debug page of the docs. I’ll reply shortly with the startup log.


#2

yeah startup log would be of great help.


#3

================== FlytOS Startup Log ================
Fri Jun 2 21:50:55 2017: [autopilot detect] check if connection to autopilot is indeed on port: /dev/ttyUSB0
Fri Jun 2 21:50:55 2017: [autopilot detect] visit http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html to find how to configure port in FlytOS
Fri Jun 2 21:50:55 2017: Could not detect autopilot, proceeding with default 'PX4’
Fri Jun 2 21:50:55 2017: Checking internet availability…
Fri Jun 2 21:50:55 2017: Internet connection established
Fri Jun 2 21:50:55 2017: Checking license on server…
Fri Jun 2 21:50:56 2017: Check license status: 200 OK, Response: True
Fri Jun 2 21:50:56 2017: License activation is: True
Fri Jun 2 21:50:56 2017: Auto-Update: ON
Fri Jun 2 21:50:56 2017: Download-Ready: True
Fri Jun 2 21:50:56 2017: Downloaded version: 1.31
Fri Jun 2 21:50:56 2017: Blacklisted version:
Fri Jun 2 21:50:56 2017: Updates ready for installation.
Fri Jun 2 21:50:56 2017: Starting installation with previous run flag 0:
Fri Jun 2 21:50:56 2017: bash: cannot set terminal process group (1242): Inappropriate ioctl for device
Fri Jun 2 21:50:56 2017: bash: no job control in this shell
Fri Jun 2 21:50:57 2017: bash: [: !=: unary operator expected
Fri Jun 2 21:50:57 2017:
Fri Jun 2 21:50:57 2017: [WARN] prev installation FAILED, not creating another backup
Fri Jun 2 21:50:57 2017:
Fri Jun 2 21:50:57 2017: [INFO] /flyt/updates/download/flytosv1.3-1c.zip file found, unzipping it to /flyt/updates/download/flytosv1.3-1c
Fri Jun 2 21:50:57 2017: Archive: /flyt/updates/download/flytosv1.3-1c.zip
Fri Jun 2 21:50:58 2017: inflating: /flyt/updates/download/flytosv1.3-1c/flytosv1.3-1c.deb
Fri Jun 2 21:50:58 2017:
Fri Jun 2 21:50:58 2017: [INFO] dry running installation of /flyt/updates/download/flytosv1.3-1c/.deb
Fri Jun 2 21:51:01 2017: (Reading database … 236088 files and directories currently installed.)
Fri Jun 2 21:51:01 2017: Preparing to unpack …/flytosv1.3-1c.deb …
Fri Jun 2 21:51:01 2017:
Fri Jun 2 21:51:01 2017: [INFO] Success: dry running installation of /flyt/updates/download/flytosv1.3-1c/
.deb. Continuing with installation procedure
Fri Jun 2 21:51:01 2017:
Fri Jun 2 21:51:01 2017: [INFO] FlytPilot Firmware : /flyt/updates/download/flytosv1.3-1c/nuttx-flytpod-v1-default.flyt not found
Fri Jun 2 21:51:02 2017: Reading package lists…
Fri Jun 2 21:51:03 2017: Building dependency tree…
Fri Jun 2 21:51:03 2017: Reading state information…
Fri Jun 2 21:51:06 2017: 0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
Fri Jun 2 21:51:06 2017: 1 not fully installed or removed.
Fri Jun 2 21:51:06 2017: After this operation, 0 B of additional disk space will be used.
Fri Jun 2 21:51:06 2017: Setting up flytcore-pe (1.3-1c) …
Fri Jun 2 21:51:07 2017: /flyt/flytos/flytcore/share/core_api
Fri Jun 2 21:51:07 2017:
Fri Jun 2 21:51:07 2017:
Fri Jun 2 21:51:07 2017: Congratulations! FlytOS installation completed
Fri Jun 2 21:51:07 2017:
Fri Jun 2 21:51:07 2017:

However using mavproxy yields.

root@flytpod:/home/flytpod# mavproxy.py --master=/dev/ttyUSB0 --baudrate 1500000 --aircraft MyCopter
Connect /dev/ttyUSB0 source_system=255
no script MyCopter/mavinit.scr
Log Directory: MyCopter/logs/2017-06-02/flight1
Telemetry log: MyCopter/logs/2017-06-02/flight1/flight.tlog
Waiting for heartbeat from /dev/ttyUSB0
MAV>

Which to my knowledge indicated a successful connection.


#4

Can you follow this, and also send this log.


#5

Also, is your baudrate truly 1500000 ? And have you updated /flyt/flytos/flytcore/share/core_api/launch/core_api_autopilot.launch file accordingly. Can you please try and reduce the baudrate to 921600?

Moreover, can you go here, and install the mentioned dependencies.


#6

In the launch file I changed the default to tty/USB0. I’ve tried both baudrates, 150000 is the baudrate specified in QGroundControl for the APM stack.

Also the link in your second post is not working for me…can you please paste the link.

My launch file…

arg name=“fcu_url” value="/dev/ttyUSB0:1500000"


#7

http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html

section: install dependencies


#8

The result of installing the dependencies. At this point I should note I’m using the flytos image for the odroid.

Reading package lists… Done
Building dependency tree
Reading state information… Done
python-concurrent.futures is already the newest version (3.0.5-1).
python-flask is already the newest version (0.10.1-2build2).
python-mock is already the newest version (1.3.0-2.1ubuntu1).
python-serial is already the newest version (3.0.1-1).
python-sqlalchemy is already the newest version (1.0.11+ds1-1ubuntu2).
python-twisted is already the newest version (16.0.0-1).
python-future is already the newest version (0.15.2-1).
python-wtforms is already the newest version (2.1-1).
python-zmq is already the newest version (15.2.0-0ubuntu4).
python-pip is already the newest version (8.1.1-2ubuntu0.4).
0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up flytcore-pe (1.3-1c) …
/flyt/flytos/flytcore/share/core_api

Congratulations! FlytOS installation completed

insserv: script flytos: service flytcore-pe already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package flytcore-pe (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
flytcore-pe
E: Sub-process /usr/bin/dpkg returned an error code (1)
Requirement already satisfied: flask_cors in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: flask_reverse_proxy in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: flask_restful in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: tblib in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: webargs in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: click in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: flask_security in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: httplib2 in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: simple_json in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: pyzmp in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: pyros-setup in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: requests in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: Six in /usr/lib/python2.7/dist-packages (from flask_cors)
Requirement already satisfied: Flask>=0.9 in /usr/lib/python2.7/dist-packages (from flask_cors)
Requirement already satisfied: pytz in /usr/lib/python2.7/dist-packages (from flask_restful)
Requirement already satisfied: aniso8601>=0.82 in /usr/local/lib/python2.7/dist-packages (from flask_restful)
Requirement already satisfied: marshmallow>=2.0.0 in /usr/local/lib/python2.7/dist-packages (from webargs)
Requirement already satisfied: Flask-Login<0.4,>=0.3.0 in /usr/local/lib/python2.7/dist-packages (from flask_security)
Requirement already satisfied: Flask-Mail>=0.7.3 in /usr/local/lib/python2.7/dist-packages (from flask_security)
Requirement already satisfied: Flask-Principal>=0.3.3 in /usr/local/lib/python2.7/dist-packages (from flask_security)
Requirement already satisfied: Flask-WTF>=0.8 in /usr/local/lib/python2.7/dist-packages (from flask_security)
Requirement already satisfied: itsdangerous>=0.17 in /usr/lib/python2.7/dist-packages (from flask_security)
Requirement already satisfied: passlib>=1.6.1 in /usr/local/lib/python2.7/dist-packages (from flask_security)
Requirement already satisfied: simplejson in /usr/local/lib/python2.7/dist-packages (from simple_json)
Requirement already satisfied: pytest>=2.9.1 in /usr/local/lib/python2.7/dist-packages (from pyzmp)
Requirement already satisfied: pyzmq in /usr/lib/python2.7/dist-packages (from pyzmp)
Requirement already satisfied: pytest-timeout in /usr/local/lib/python2.7/dist-packages (from pyzmp)
Requirement already satisfied: pyros-config>=0.1.5 in /usr/local/lib/python2.7/dist-packages (from pyros-setup)
Requirement already satisfied: Werkzeug>=0.7 in /usr/lib/python2.7/dist-packages (from Flask>=0.9->flask_cors)
Requirement already satisfied: Jinja2>=2.4 in /usr/lib/python2.7/dist-packages (from Flask>=0.9->flask_cors)
Requirement already satisfied: python-dateutil in /usr/lib/python2.7/dist-packages (from aniso8601>=0.82->flask_restful)
Requirement already satisfied: blinker in /usr/lib/python2.7/dist-packages (from Flask-Mail>=0.7.3->flask_security)
Requirement already satisfied: WTForms in /usr/lib/python2.7/dist-packages (from Flask-WTF>=0.8->flask_security)
Requirement already satisfied: py>=1.4.29 in /usr/local/lib/python2.7/dist-packages (from pytest>=2.9.1->pyzmp)
Requirement already satisfied: MarkupSafe in /usr/lib/python2.7/dist-packages (from Jinja2>=2.4->Flask>=0.9->flask_cors)
Reading package lists… Done
Building dependency tree
Reading state information… Done
Note, selecting ‘libxslt1-dev’ instead of 'libxslt-dev’
libxml2-dev is already the newest version (2.9.3+dfsg1-1ubuntu0.2).
libxslt1-dev is already the newest version (1.1.28-2.1ubuntu0.1).
ros-kinetic-camera-info-manager is already the newest version (1.11.12-0xenial-20170404-022429-0800).
ros-kinetic-control-toolbox is already the newest version (1.15.0-0xenial-20170407-180017-0800).
ros-kinetic-eigen-conversions is already the newest version (1.11.8-0xenial-20170309-083700-0800).
ros-kinetic-image-proc is already the newest version (1.12.20-0xenial-20170430-145314-0800).
ros-kinetic-image-transport is already the newest version (1.11.12-0xenial-20170403-214401-0700).
ros-kinetic-image-transport-plugins is already the newest version (1.9.5-0xenial-20170407-185349-0800).
ros-kinetic-pyros-utils is already the newest version (0.1.4-0xenial-20170321-021601-0700).
ros-kinetic-rosbridge-suite is already the newest version (0.7.17-0xenial-20170310-055659-0800).
0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up flytcore-pe (1.3-1c) …
/flyt/flytos/flytcore/share/core_api

Congratulations! FlytOS installation completed

insserv: script flytos: service flytcore-pe already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package flytcore-pe (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
flytcore-pe
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists… Done
Building dependency tree
Reading state information… Done
lsof is already the newest version (4.89+dfsg-0.1).
locate is already the newest version (4.6.0+git+20160126-2).
minicom is already the newest version (2.7-1build1).
v4l2loopback-utils is already the newest version (0.9.1-4).
gstreamer1.0-plugins-base is already the newest version (1.8.3-1ubuntu0.2).
gstreamer1.0-plugins-good is already the newest version (1.8.3-1ubuntu0.4).
gstreamer1.0-tools is already the newest version (1.8.3-1~ubuntu0.1).
libglib2.0-dev is already the newest version (2.48.2-0ubuntu1).
gstreamer1.0-plugins-bad is already the newest version (1.8.3-1ubuntu0.2).
gstreamer1.0-plugins-ugly is already the newest version (1.8.3-1ubuntu0.1).
0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up flytcore-pe (1.3-1c) …
/flyt/flytos/flytcore/share/core_api

Congratulations! FlytOS installation completed

insserv: script flytos: service flytcore-pe already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package flytcore-pe (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
flytcore-pe
E: Sub-process /usr/bin/dpkg returned an error code (1)
Requirement already satisfied: certifi in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: pyserial in /usr/lib/python2.7/dist-packages
Requirement already satisfied: pymavlink in /usr/local/lib/python2.7/dist-packages
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package ‘modemmanager’ is not installed, so not removed
Package ‘xfce4-power-manager’ is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up flytcore-pe (1.3-1c) …
/flyt/flytos/flytcore/share/core_api

Congratulations! FlytOS installation completed

insserv: script flytos: service flytcore-pe already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package flytcore-pe (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
flytcore-pe
E: Sub-process /usr/bin/dpkg returned an error code (1)


#9

root@flytpod:/home/flytpod/Documents# sudo $(rospack find core_api)/scripts/launch_flytOS.sh
Direct import of flyt_ms and rostful

Upon trying to launch flytos after stopping it. I’m going to change the flight stack to px4 and follow the setup tutorial in docs again in hopes of a different result.


#10

Can you launch flytos again. and send whatever is printed in the shell.


#11

Okay I switched to the px4 flight stack. Went through the initial setup, edited the SYS_COMP and MAV_ID to the appropriate values, and finally changed the startup files baudrate to the correct value. This was the startup log…

***I can confirm that the device is showing up as USB0.

================== FlytOS Startup Log ================
Fri Jun 2 22:38:26 2017: [autopilot detect] check if connection to autopilot is indeed on port: /dev/ttyUSB0
Fri Jun 2 22:38:26 2017: [autopilot detect] visit http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html to find how to configure port in FlytOS
Fri Jun 2 22:38:26 2017: Could not detect autopilot, proceeding with default 'PX4’
Fri Jun 2 22:38:26 2017: Checking internet availability…
Fri Jun 2 22:38:26 2017: Internet connection established
Fri Jun 2 22:38:26 2017: Checking license on server…
Fri Jun 2 22:38:27 2017: Check license status: 200 OK, Response: True
Fri Jun 2 22:38:27 2017: License activation is: True
Fri Jun 2 22:38:27 2017: Auto-Update: ON
Fri Jun 2 22:38:27 2017: Download-Ready: True
Fri Jun 2 22:38:27 2017: Downloaded version: 1.31
Fri Jun 2 22:38:27 2017: Blacklisted version:
Fri Jun 2 22:38:27 2017: Updates ready for installation.
Fri Jun 2 22:38:27 2017: Starting installation with previous run flag 0:
Fri Jun 2 22:38:27 2017: bash: cannot set terminal process group (1246): Inappropriate ioctl for device
Fri Jun 2 22:38:27 2017: bash: no job control in this shell
Fri Jun 2 22:38:28 2017: bash: [: !=: unary operator expected
Fri Jun 2 22:38:28 2017:
Fri Jun 2 22:38:28 2017: [WARN] prev installation FAILED, not creating another backup
Fri Jun 2 22:38:28 2017:
Fri Jun 2 22:38:28 2017: [INFO] /flyt/updates/download/flytosv1.3-1c.zip file found, unzipping it to /flyt/updates/download/flytosv1.3-1c
Fri Jun 2 22:38:28 2017: Archive: /flyt/updates/download/flytosv1.3-1c.zip
Fri Jun 2 22:38:29 2017: inflating: /flyt/updates/download/flytosv1.3-1c/flytosv1.3-1c.deb
Fri Jun 2 22:38:29 2017:
Fri Jun 2 22:38:29 2017: [INFO] dry running installation of /flyt/updates/download/flytosv1.3-1c/.deb
Fri Jun 2 22:38:32 2017: (Reading database … 236088 files and directories currently installed.)
Fri Jun 2 22:38:33 2017: Preparing to unpack …/flytosv1.3-1c.deb …
Fri Jun 2 22:38:33 2017:
Fri Jun 2 22:38:33 2017: [INFO] Success: dry running installation of /flyt/updates/download/flytosv1.3-1c/
.deb. Continuing with installation procedure
Fri Jun 2 22:38:33 2017:
Fri Jun 2 22:38:33 2017: [INFO] FlytPilot Firmware : /flyt/updates/download/flytosv1.3-1c/nuttx-flytpod-v1-default.flyt not found
Fri Jun 2 22:38:34 2017: Reading package lists…
Fri Jun 2 22:38:34 2017: Building dependency tree…
Fri Jun 2 22:38:34 2017: Reading state information…
Fri Jun 2 22:38:36 2017: 0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
Fri Jun 2 22:38:36 2017: 1 not fully installed or removed.
Fri Jun 2 22:38:36 2017: After this operation, 0 B of additional disk space will be used.
Fri Jun 2 22:38:36 2017: Setting up flytcore-pe (1.3-1c) …
Fri Jun 2 22:38:38 2017: /flyt/flytos/flytcore/share/core_api
Fri Jun 2 22:38:38 2017:
Fri Jun 2 22:38:38 2017:
Fri Jun 2 22:38:38 2017: Congratulations! FlytOS installation completed
Fri Jun 2 22:38:38 2017:
Fri Jun 2 22:38:38 2017:
Fri Jun 2 22:38:38 2017: insserv: script flytos: service flytcore-pe already provided!
Fri Jun 2 22:38:38 2017: insserv: exiting now!
Fri Jun 2 22:38:38 2017: update-rc.d: error: insserv rejected the script header
Fri Jun 2 22:38:38 2017: dpkg: error processing package flytcore-pe (–configure):
Fri Jun 2 22:38:38 2017: subprocess installed post-installation script returned error exit status 1
Fri Jun 2 22:38:38 2017: Errors were encountered while processing:
Fri Jun 2 22:38:38 2017: flytcore-pe
Fri Jun 2 22:38:43 2017: E: Sub-process /usr/bin/dpkg returned an error code (1)
Fri Jun 2 22:38:44 2017: Setting up flytcore-pe (1.3-1c) …
Fri Jun 2 22:38:44 2017: bash: cannot set terminal process group (2301): Inappropriate ioctl for device
Fri Jun 2 22:38:44 2017: bash: no job control in this shell
Fri Jun 2 22:38:45 2017: /flyt/flytos/flytcore/share/core_api
Fri Jun 2 22:38:45 2017:
Fri Jun 2 22:38:45 2017:
Fri Jun 2 22:38:45 2017: Congratulations! FlytOS installation completed
Fri Jun 2 22:38:45 2017:
Fri Jun 2 22:38:45 2017:
Fri Jun 2 22:38:45 2017: insserv: script flytos: service flytcore-pe already provided!
Fri Jun 2 22:38:45 2017: insserv: exiting now!
Fri Jun 2 22:38:45 2017: update-rc.d: error: insserv rejected the script header
Fri Jun 2 22:38:45 2017: dpkg: error processing package flytcore-pe (–configure):
Fri Jun 2 22:38:45 2017: subprocess installed post-installation script returned error exit status 1
Fri Jun 2 22:38:46 2017: Errors were encountered while processing:
Fri Jun 2 22:38:46 2017: flytcore-pe
Fri Jun 2 22:38:46 2017:
Fri Jun 2 22:38:46 2017: [INFO] FlytOS dependencies will now be installed
Fri Jun 2 22:38:46 2017: /flyt/flytos/flytcore/share/core_api/scripts/updates/flytos_dependency.sh: 5: [: !=: unexpected operator
Fri Jun 2 22:38:46 2017: Hit:1 http://deb.odroid.in/5422 xenial InRelease
Fri Jun 2 22:38:46 2017: Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
Fri Jun 2 22:38:46 2017: Hit:3 http://packages.ros.org/ros/ubuntu xenial InRelease
Fri Jun 2 22:38:46 2017: Hit:4 http://ppa.launchpad.net/saiarcot895/myppa/ubuntu xenial InRelease
Fri Jun 2 22:38:47 2017: Hit:5 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
Fri Jun 2 22:38:47 2017: Hit:6 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease
Fri Jun 2 22:38:47 2017: Hit:7 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
Fri Jun 2 22:39:01 2017: Reading package lists…
Fri Jun 2 22:39:01 2017: Reading package lists…
Fri Jun 2 22:39:02 2017: Building dependency tree…
Fri Jun 2 22:39:02 2017: Reading state information…
Fri Jun 2 22:39:03 2017: ros-kinetic-compressed-image-transport is already the newest version (1.9.5-0xenial-20170407-180346-0800).
Fri Jun 2 22:39:03 2017: ros-kinetic-compressed-image-transport set to manually installed.
Fri Jun 2 22:39:03 2017: ros-kinetic-cv-bridge is already the newest version (1.12.4-0xenial-20170315-122144-0700).
Fri Jun 2 22:39:03 2017: ros-kinetic-cv-bridge set to manually installed.
Fri Jun 2 22:39:03 2017: ros-kinetic-opencv3 is already the newest version (3.2.0-4xenial-20170315-020151-0700).
Fri Jun 2 22:39:03 2017: ros-kinetic-opencv3 set to manually installed.
Fri Jun 2 22:39:03 2017: 0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
Fri Jun 2 22:39:03 2017: 1 not fully installed or removed.
Fri Jun 2 22:39:03 2017: After this operation, 0 B of additional disk space will be used.
Fri Jun 2 22:39:03 2017: Do you want to continue? [Y/n] Abort.
Fri Jun 2 22:39:03 2017: Reading package lists…
Fri Jun 2 22:39:04 2017: Building dependency tree…
Fri Jun 2 22:39:04 2017: Reading state information…
Fri Jun 2 22:39:06 2017: flytcore-pe is already the newest version (1.3-1c).
Fri Jun 2 22:39:06 2017: 0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
Fri Jun 2 22:39:06 2017: 1 not fully installed or removed.
Fri Jun 2 22:39:06 2017: After this operation, 0 B of additional disk space will be used.
Fri Jun 2 22:39:06 2017: Setting up flytcore-pe (1.3-1c) …
Fri Jun 2 22:39:07 2017: /flyt/flytos/flytcore/share/core_api
Fri Jun 2 22:39:07 2017:
Fri Jun 2 22:39:07 2017:
Fri Jun 2 22:39:07 2017: Congratulations! FlytOS installation completed
Fri Jun 2 22:39:07 2017:
Fri Jun 2 22:39:07 2017:
Fri Jun 2 22:39:08 2017: insserv: script flytos: service flytcore-pe already provided!
Fri Jun 2 22:39:08 2017: insserv: exiting now!
Fri Jun 2 22:39:08 2017: update-rc.d: error: insserv rejected the script header
Fri Jun 2 22:39:08 2017: dpkg: error processing package flytcore-pe (–configure):
Fri Jun 2 22:39:08 2017: subprocess installed post-installation script returned error exit status 1
Fri Jun 2 22:39:08 2017: Errors were encountered while processing:
Fri Jun 2 22:39:08 2017: flytcore-pe
Fri Jun 2 22:39:12 2017: E: Sub-process /usr/bin/dpkg returned an error code (1)
Fri Jun 2 22:39:12 2017:
Fri Jun 2 22:39:12 2017: [ERROR] FlytOS debian installation FAILED, kindly contact Flytbase admin. Reinstalling backup FlytOS
Fri Jun 2 22:39:12 2017: Reading package lists…
Fri Jun 2 22:39:12 2017: E: Unsupported file /flyt_bak/updates/installed/*.deb given on commandline
Fri Jun 2 22:39:13 2017: Reading package lists…
Fri Jun 2 22:39:13 2017: Building dependency tree…
Fri Jun 2 22:39:13 2017: Reading state information…
Fri Jun 2 22:39:14 2017: 0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
Fri Jun 2 22:39:14 2017: 1 not fully installed or removed.
Fri Jun 2 22:39:14 2017: After this operation, 0 B of additional disk space will be used.
Fri Jun 2 22:39:15 2017: Setting up flytcore-pe (1.3-1c) …
Fri Jun 2 22:39:15 2017: /flyt/flytos/flytcore/share/core_api
Fri Jun 2 22:39:15 2017:
Fri Jun 2 22:39:15 2017:
Fri Jun 2 22:39:15 2017: Congratulations! FlytOS installation completed
Fri Jun 2 22:39:15 2017:
Fri Jun 2 22:39:15 2017:
Fri Jun 2 22:39:16 2017: insserv: script flytos: service flytcore-pe already provided!
Fri Jun 2 22:39:16 2017: insserv: exiting now!
Fri Jun 2 22:39:16 2017: update-rc.d: error: insserv rejected the script header
Fri Jun 2 22:39:16 2017: dpkg: error processing package flytcore-pe (–configure):
Fri Jun 2 22:39:16 2017: subprocess installed post-installation script returned error exit status 1
Fri Jun 2 22:39:16 2017: Errors were encountered while processing:
Fri Jun 2 22:39:16 2017: flytcore-pe
Fri Jun 2 22:39:22 2017: E: Sub-process /usr/bin/dpkg returned an error code (1)
Fri Jun 2 22:39:22 2017: Setting up flytcore-pe (1.3-1c) …
Fri Jun 2 22:39:22 2017: bash: cannot set terminal process group (2988): Inappropriate ioctl for device
Fri Jun 2 22:39:22 2017: bash: no job control in this shell
Fri Jun 2 22:39:23 2017: /flyt/flytos/flytcore/share/core_api
Fri Jun 2 22:39:23 2017:
Fri Jun 2 22:39:23 2017:
Fri Jun 2 22:39:23 2017: Congratulations! FlytOS installation completed
Fri Jun 2 22:39:23 2017:
Fri Jun 2 22:39:23 2017:
Fri Jun 2 22:39:23 2017: insserv: script flytos: service flytcore-pe already provided!
Fri Jun 2 22:39:23 2017: insserv: exiting now!
Fri Jun 2 22:39:23 2017: update-rc.d: error: insserv rejected the script header
Fri Jun 2 22:39:23 2017: dpkg: error processing package flytcore-pe (–configure):
Fri Jun 2 22:39:23 2017: subprocess installed post-installation script returned error exit status 1
Fri Jun 2 22:39:24 2017: Errors were encountered while processing:
Fri Jun 2 22:39:24 2017: flytcore-pe
Fri Jun 2 22:39:24 2017:
Fri Jun 2 22:39:24 2017: [FATAL] Backup FlytOS debian installation FAILED, kindly contact Flytbase admin.
Fri Jun 2 22:39:24 2017: Install status: False
Fri Jun 2 22:39:24 2017: FlytOS installation failed. Installation will be retried on next boot up. To avoid installing this version, you can blacklist it using FlytConsole. If you need support, post details on FlytOS forums.
Fri Jun 2 22:39:24 2017: Starting FlytOS…
Fri Jun 2 22:39:25 2017: Checking for new updates
Fri Jun 2 22:39:25 2017: Checking internet availability…
Fri Jun 2 22:39:25 2017: Internet connection established
Fri Jun 2 22:39:25 2017: Checking license on server…
Fri Jun 2 22:39:25 2017: Check license status: 200 OK, Response: True
Fri Jun 2 22:39:26 2017: Checking for updates on server…
Fri Jun 2 22:39:26 2017: Check updates status: 200 OK, Response: 1.31
Fri Jun 2 22:39:26 2017: FlytOS version is already up-to-date.
Fri Jun 2 22:39:26 2017: Exiting Startup #IFFSUC.

I tried stopping and starting flytos again and got the same thing as before…

root@flytpod:/home/flytpod# sudo $(rospack find core_api)/scripts/launch_flytOS.sh
Direct import of flyt_ms and rostful


#12

Interesting aside…I was trying to go line by line for the dependency thinking there might be a problem with the script, this was the result.

root@flytpod:/home/flytpod/Documents# apt install -y python-pip python-serial python-flask python-wtforms python-sqlalchemy python-concurrent.futures python-mock python-zmq python-twisted python-future
Reading package lists… Done
Building dependency tree
Reading state information… Done
python-concurrent.futures is already the newest version (3.0.5-1).
python-flask is already the newest version (0.10.1-2build2).
python-mock is already the newest version (1.3.0-2.1ubuntu1).
python-serial is already the newest version (3.0.1-1).
python-sqlalchemy is already the newest version (1.0.11+ds1-1ubuntu2).
python-twisted is already the newest version (16.0.0-1).
python-future is already the newest version (0.15.2-1).
python-wtforms is already the newest version (2.1-1).
python-zmq is already the newest version (15.2.0-0ubuntu4).
python-pip is already the newest version (8.1.1-2ubuntu0.4).
0 upgraded, 0 newly installed, 0 to remove and 361 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up flytcore-pe (1.3-1c) …
/flyt/flytos/flytcore/share/core_api

Congratulations! FlytOS installation completed

insserv: script flytos: service flytcore-pe already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package flytcore-pe (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
flytcore-pe
E: Sub-process /usr/bin/dpkg returned an error code (1)

In fact anytime I try and run the apt-get installations I get a similar error. The pip installs work fine.


#13

Yeah it seems there is a conflict between older and newer package. It is harmless, but if you want it to vanish run the following command:

sudo dpkg --purge flytcore-pe
sudo rm -rf /flyt

then go to my.flytbase.com, download and install the latest flytos.

But I think this is not your current issue.
I am requesting you again, PLEASE send the screen log dump, that you see when flytos starts up, and NOT the content of the startup log file.


#14

I apologize for the miscommunication, however I have sent the screen log dump. When I follow the instructions on the link provided this is truly all i see.

root@flytpod:/home/flytpod/Documents# sudo $(rospack find core_api)/scripts/stop_flytOS.sh
flytstartup not running
3321
3321
3321
3321
3321
root@flytpod:/home/flytpod/Documents# sudo $(rospack find core_api)/scripts/launch_flytOS.sh
Direct import of flyt_ms and rostful

control + c (after about 2/3 minutes of waiting) yields this

^C^C^C^C[rospack] Error: package ‘core_api’ not found
sh: 0: Can’t open /scripts/check_md5_paramfile.sh
[rospack] Error: package ‘core_api’ not found
bash: $(rospack find core_api)/param_files/global_namespace.yaml: No such file or directory
[rospack] Error: package ‘core_api’ not found
sed: can’t read /launch/core_api_autopilot.launch: No such file or directory
[core_api_autopilot.launch] is neither a launch file in package [core_api] nor is [core_api] a launch file name
The traceback for the exception was written to the log file

I’ve followed the section of the FAQ regarding core_api not found, and I can confirm that the lines given are present in the /etc/bash.bashrc and NOT present in the ~/.bash


#15

Tried starting and stopping again…this time after waiting 3/4 minutes I ctrl+c’d again…however this time I did get a long print out.logDump.txt (80.1 KB)


#16

Lets set up a call and get this sorted out. In the meantime, can you follow my previous reply(Pixhawk Ordroid communication issues), and cleanly update your device.

What time would be preferable for you?


#17

Okay! Anytime in the next couple of hours works for me. Please PM me with your preferred contact method…I also have teamviewer set up on my machine; which can ssh into the odroid.


#18

Unfortunately its almost 12 midnight here, and won’t be able to have a call now. Is it possible to schedule it tomorrow? any time should be fine for me.