FlytOS cannot activate


#1

Hello,

I want to active my FlytOS, but it tell me Failed to contact server.
I install FlytOS(1.11 Intel Aero version) in my PC(not drone, ubuntu 16.04).
My computer are already connect to internet.
and when I active fail, some information show at console:
http://imgur.com/a/KZJZ6

Can someone help me?
Thanks.


Flytos is not activating on Odroid XU4(kernel 4.9.34)
#2

Hi,

Instead of installing aero debian on your machine. Can you try installing FlytSim, and get back to us if you still face the same issue.


#3

Hello srv,
FlytSim are same as FlytOS.
And this is the error message:
http://i.imgur.com/eYYDBkn.png


#4

Hey, can you post your output to following commands?

ifconfig

ethtool -P $(ls /sys/class/net/ | grep -E ‘enp|eth|wlp|wlan’) | grep -Po ‘Permanent address: \K.*$’ | sed s/://g


Having issues with the docker - flytsim
#5

Hi Dhirajd,
This is output:
http://i.imgur.com/JlCWbMY.png


#6

Got your problem. We didn’t expect an adapter with name ‘eno’. We will include this fix in next update.
For now let me come up with a workaround for you. Will get back to you soon.


#7

Replace following file in the /flyt directory.

/flyt/flytos/flytcore/lib/python2.7/dist-packages/flyt_ms/log_helper.pyc

by new file.
https://drive.google.com/file/d/0B3nv6KYvBLhGTUpSb2Q4azNMdGM/view?usp=sharing

Then start FlytOS. Register again. That should solve your problem. Let me know if you face any issue.


#8

Thank you very much!
I can active now.


#9

ENjoy! :slight_smile:


#10

Hi Dhirajd,
I have already activated my installation of FlytOS, but I am unable to make use of some of the FlytAPI functionality such as “Arm”.

ubuser@ubuserpc:~$ rosservice list
/flytsim/core_api_param/get_loggers
/flytsim/core_api_param/set_logger_level
/flytsim/core_api_payload/get_loggers
/flytsim/core_api_payload/set_logger_level
/flytsim/core_api_setup/get_loggers
/flytsim/core_api_setup/set_logger_level
/flytsim/flyt_ms/get_device_id
/flytsim/flyt_ms/get_device_type
/flytsim/flyt_ms/get_license_info
/flytsim/flyt_ms/verify_license
/flytsim/flyt_ms_node/get_loggers
/flytsim/flyt_ms_node/set_logger_level
/flytsim/flytcam/image_capture/compressed/set_parameters
/flytsim/flytcam/image_capture/compressedDepth/set_parameters
/flytsim/flytcam/image_capture/theora/set_parameters
/flytsim/gazebo/apply_body_wrench
/flytsim/gazebo/apply_joint_effort
/flytsim/gazebo/clear_body_wrenches
/flytsim/gazebo/clear_joint_forces
/flytsim/gazebo/delete_model
/flytsim/gazebo/get_joint_properties
/flytsim/gazebo/get_link_properties
/flytsim/gazebo/get_link_state
/flytsim/gazebo/get_loggers
/flytsim/gazebo/get_model_properties
/flytsim/gazebo/get_model_state
/flytsim/gazebo/get_physics_properties
/flytsim/gazebo/get_world_properties
/flytsim/gazebo/pause_physics
/flytsim/gazebo/reset_simulation
/flytsim/gazebo/reset_world
/flytsim/gazebo/set_joint_properties
/flytsim/gazebo/set_link_properties
/flytsim/gazebo/set_link_state
/flytsim/gazebo/set_logger_level
/flytsim/gazebo/set_model_configuration
/flytsim/gazebo/set_model_state
/flytsim/gazebo/set_physics_properties
/flytsim/gazebo/spawn_sdf_model
/flytsim/gazebo/spawn_urdf_model
/flytsim/gazebo/unpause_physics
/flytsim/image_capture/get_loggers
/flytsim/image_capture/set_logger_level
/flytsim/mavros/autopilot_app_control
/flytsim/mavros/autopilot_version
/flytsim/mavros/cmd/arming
/flytsim/mavros/cmd/command
/flytsim/mavros/cmd/command_int
/flytsim/mavros/cmd/land
/flytsim/mavros/cmd/set_home
/flytsim/mavros/cmd/takeoff
/flytsim/mavros/cmd/trigger_control
/flytsim/mavros/ftp/checksum
/flytsim/mavros/ftp/close
/flytsim/mavros/ftp/list
/flytsim/mavros/ftp/mkdir
/flytsim/mavros/ftp/open
/flytsim/mavros/ftp/read
/flytsim/mavros/ftp/remove
/flytsim/mavros/ftp/rename
/flytsim/mavros/ftp/reset
/flytsim/mavros/ftp/rmdir
/flytsim/mavros/ftp/truncate
/flytsim/mavros/ftp/write
/flytsim/mavros/get_loggers
/flytsim/mavros/mission/clear
/flytsim/mavros/mission/pull
/flytsim/mavros/mission/push
/flytsim/mavros/mission/set_current
/flytsim/mavros/param/get
/flytsim/mavros/param/pull
/flytsim/mavros/param/push
/flytsim/mavros/param/set
/flytsim/mavros/set_logger_level
/flytsim/mavros/set_mode
/flytsim/mavros/set_stream_rate
/flytsim/mavros/setpoint_position/local/land
/flytsim/mavros/setpoint_position/local/take_off
/flytsim/mode_manager/get_loggers
/flytsim/mode_manager/set_logger_level
/flytsim/navigation_server/get_loggers
/flytsim/navigation_server/set_logger_level
/flytsim/param/param_create
/flytsim/param/param_delete
/flytsim/param/param_get
/flytsim/param/param_get_all
/flytsim/param/param_load
/flytsim/param/param_reset
/flytsim/param/param_save
/flytsim/param/param_set
/flytsim/payload/config_adc
/flytsim/payload/get_set_gpio
/flytsim/payload/gimbal_configure
/flytsim/payload/gimbal_set
/flytsim/payload/set_gpio_direction
/flytsim/payload/set_led
/flytsim/rosapi/get_loggers
/flytsim/rosapi/set_logger_level
/flytsim/rosbridge_websocket/get_loggers
/flytsim/rosbridge_websocket/set_logger_level
/flytsim/rostful/get_loggers
/flytsim/rostful/set_logger_level
/flytsim/setup/actuator_testing
/flytsim/setup/autopilot_reboot
/flytsim/setup/esc_calibration
/flytsim/setup/module_calibration
/flytsim/typhoon_h480/cgo3_camera/image_raw/compressed/set_parameters
/flytsim/typhoon_h480/cgo3_camera/image_raw/compressedDepth/set_parameters
/flytsim/typhoon_h480/cgo3_camera/image_raw/theora/set_parameters
/flytsim/typhoon_h480/cgo3_camera/set_camera_info
/flytsim/typhoon_h480/cgo3_camera/set_parameters
/flytsim/web_video_server/get_loggers
/flytsim/web_video_server/set_logger_level
/get_global_namespace
/rosapi/action_servers
/rosapi/delete_param
/rosapi/get_param
/rosapi/get_param_names
/rosapi/get_time
/rosapi/has_param
/rosapi/message_details
/rosapi/node_details
/rosapi/nodes
/rosapi/publishers
/rosapi/search_param
/rosapi/service_host
/rosapi/service_node
/rosapi/service_providers
/rosapi/service_request_details
/rosapi/service_response_details
/rosapi/service_type
/rosapi/services
/rosapi/services_for_type
/rosapi/set_param
/rosapi/subscribers
/rosapi/topic_type
/rosapi/topics
/rosapi/topics_for_type
/rosout/get_loggers
/rosout/set_logger_level

and then when I have launched FlytSim, I noticed that there is a red line indicating that the license file is invalid, as shown in the screenshot below.
http://i.imgur.com/U6lrc8s.png
Is this problem the same as what I have mentioned previously?


#11

You will have to activate through console once again. Earlier when you tried to activate the process failed because it was not able to detect device id. Repeat the activation process and then restart FlytOS. Let me know if it still is not working.


#12

Hi Dhirajd,

I have already stopped the FlytSim using the following command:

sudo $(rospack find core_api)/scripts/stop_flytSim.sh

and have restarted FlytSim again using the following command:

sudo $(rospack find core_api)/scripts/launch_flytSim.sh

But it is still not working.


#13

Did you follow the activation procedure again (after changing the file)?


#14

@kuji

Can you also attach your FlytOS update log: http://docs.flytbase.com/docs/FlytOS/Debugging/GettingHelpForum.html#flytos-update-log

Thanks,
Zubin


#15

Hi,
I reboot my computer and reactive my FlytOS.
But it is still not working.
There is my FlytOS update log:

================== FlytOS Startup Log ================
Mon Apr 17 18:45:24 2017: Checking internet availability…
Mon Apr 17 18:45:24 2017: Internet connection established
Mon Apr 17 18:45:24 2017: Checking license on server…
Mon Apr 17 18:45:25 2017: Check license status: 200 OK, Response: True
Mon Apr 17 18:45:25 2017: License activation is: True
Mon Apr 17 18:45:25 2017: Auto-Update: ON
Mon Apr 17 18:45:25 2017: Download-Ready: False
Mon Apr 17 18:45:25 2017: Downloaded version: null
Mon Apr 17 18:45:25 2017: Blacklisted version:
Mon Apr 17 18:45:25 2017: Starting FlytOS…
Mon Apr 17 18:45:25 2017: Checking for new updates
Mon Apr 17 18:45:25 2017: Checking internet availability…
Mon Apr 17 18:45:25 2017: Internet connection established
Mon Apr 17 18:45:25 2017: Checking license on server…
Mon Apr 17 18:45:26 2017: Check license status: 200 OK, Response: True
Mon Apr 17 18:45:26 2017: Checking for updates on server…
Mon Apr 17 18:45:27 2017: Check updates status: 200 OK, Response: 1.11
Mon Apr 17 18:45:27 2017: FlytOS version is already up-to-date.
Mon Apr 17 18:45:27 2017: Updating server with current FlytOS version:1.11
Mon Apr 17 18:45:28 2017: Set update status: 200 OK, Response: True
Mon Apr 17 18:45:28 2017: Exiting Startup.


#16

Hi,

We have identified the issue. I will generate a fix in some time and post here.

Zubin


#17

There is another file that you will replace

/flyt/flytos/flytcore/lib/core_api/navigation_api

With this file https://drive.google.com/open?id=0BxGhO3sAul8OZXdkUE9QVURYNGM

No need to register again. Just restart your Flysim and now navigation APIs should work for your laptop

Zubin


#18

Sorry, It is still not working.
Same as before.


#19

Can you show the error message you got this time?


#20

Hi, when I direct execute the navigation_api have the same error.
http://i.imgur.com/nU8kIbt.png