FlytOS cannot activate


#21

I apologize for the problem. I have created an additional fix. Please download https://drive.google.com/file/d/0B2IXB8LxWs-qQ3BqVjc4X2toV3c/view?usp=sharing and try running the executable once more.

Thanks,
Zubin


#22

Thank you Zubin,
I can use navigation api now.


#23

That is great Kuji! Happy to help!


#24

Hello,
I too have trouble activating FlytOS on my Odroid XU4.
After following the thread, I see that my adapter is ‘enx’.
I don’t know if this is related.
Should I use the files you supplied?

odroid@odroid:~/Desktop$ ifconfig
enx001e06303dc1 Link encap:Ethernet HWaddr 00:1e:06:30:3d:c1
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:279270 errors:0 dropped:0 overruns:0 frame:0
TX packets:279270 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:48324433 (48.3 MB) TX bytes:48324433 (48.3 MB)

wlx7cdd90b11971 Link encap:Ethernet HWaddr 7c:dd:90:b1:19:71
inet addr:192.168.178.30 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::7edd:90ff:feb1:1971/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7787 errors:0 dropped:0 overruns:0 frame:0
TX packets:7019 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:763859 (763.8 KB) TX bytes:6405860 (6.4 MB)

odroid@odroid:~/Desktop$ ethtool -P $(ls /sys/class/net/ | grep -E ‘enp|eth|wlp|wlan’) | grep -Po ‘Permanent address: \K.$’ | sed s/://g
ethtool: bad command line argument(s)
For more information run ethtool -h
odroid@odroid:~/Desktop$ ethtool -P $(ls /sys/class/net/ | grep -E ‘enp|eth|wlp|wlan|enx’) | grep -Po 'Permanent address: \K.
$’ | sed s/://g
001e06303dc1
odroid@odroid:~/Desktop$


#25

Hi,

If you download our latest FlytOS release from my.flytbase.com, then you won’t face the above problem.


#26

I am not at the machine right now, but I am almost certain this is the version I am running (1.21). I installed the latest version less than a week ago.


#27

Oh, I am sorry.

I forgot to see that you are working on ODROID-XU4 and not on Aero. Give me sometime, to figure out the solution. Till now, we haven’t seen enx or wlx in odroid. Did you install our image? In the meantime, please send me your kernel version and link to image which you downloaded.


#28

Hi,

Replace your file at: /flyt/flytos/flytcore/lib/python2.7/dist-packages/flyt_ms/log_helper.pyc with log_helper.pyc (11.1 KB)

and replace file at: /flyt/flytos/flytcore/lib/core_api/navigation_api with this file


#29

Thank you for the update. Will check later this weekend and let you know.


#30

Hello again,

I tried your patch and still no success. I even restarted the machine just to be sure.
The kernel version:

3.10.103-124

FlytOS version:

I can’t find the link to the debian file I downloaded flytos because you updated your site :slight_smile:


#31

Hey,
Sorry if you had any inconveniences, the link is still the same.
https://my.flytbase.com/downloads/


#32

Yes you are correct. I tried that installation and its the same with what I have already installed.
The issue still persists.
Is there any other information you need?


#33

Hi,

Can you please post flytos startup log in this thread, we might be barking the wrong tree here.


#34

I don’t see much information in the startup log:

================== FlytOS Startup Log ================
Tue May 2 16:58:07 2017: [autopilot detect] timeout reached… check if baudrate of autopilot is: 921600
Tue May 2 16:58:07 2017: [autopilot detect] visit http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html to find how to configure baudrate in FlytOS
Tue May 2 16:58:07 2017: Could not detect autopilot, proceeding with default 'PX4’
Tue May 2 16:58:07 2017: Checking internet availability…
Tue May 2 16:58:07 2017: Internet connection established
Tue May 2 16:58:07 2017: License file invalid. Please activate/reactivate your device by entering license key in flytconsole.
Tue May 2 16:58:07 2017: License activation is: False
Tue May 2 16:58:07 2017: Starting FlytOS(Restricted) - Needs Activation
Tue May 2 16:58:08 2017: Exiting Startup.License invalid!


#35

Sorry, here is the complete startup log.

flytos_startup.txt (16.1 KB)

Have in mind that the drone is not started. Is it necessary for the activation?


#36

Hi,

What happens when you try to activate from FlytConsole? any error messages in terminal? Also, what is your Ubuntu OS version? Is it 16.04? Moreover, do you know your kernel version?


#37

No it is certainly not required.


#38

Ubuntu is 16.04. My kernel version: 3.10.103-124
The first time I try to activate:


DEBUG in flask_views [/flyt/flytos/flytcore/lib/python2.7/dist-packages/rostful/flask_views.py:499]:
calling service /flytpod/flyt_ms/verify_license with msg : {‘ser_id’: ‘f0ff6cbc-4f9e-438f-b614-a230f63812f7’, ‘dev_id’: ‘ethtool: bad command line argument(s)\nFor more information run ethtool -h’}


ERROR in flask_views [/flyt/flytos/flytcore/lib/python2.7/dist-packages/rostful/flask_views.py:559]:
Service Timeout! => 504
Pyros Service call timed out.

Then, when I try again:


DEBUG in flask_views [/flyt/flytos/flytcore/lib/python2.7/dist-packages/rostful/flask_views.py:499]:
calling service /flytpod/flyt_ms/verify_license with msg : {‘ser_id’: ‘f0ff6cbc-4f9e-438f-b614-a230f63812f7’, ‘dev_id’: ‘ethtool: bad command line argument(s)\nFor more information run ethtool -h’}

[ERROR] [1493749416.800209]: LIC VERIFICATION ERROR: 404 device id not found or invalid
[ERROR] [1493749417.029425]: LICENSE READ ERROR: file not present/malformed/tampered


#39

Hi,

Can you apply the above mentioned patch again. If problem still persists, lets take it up on call and get this sorted quickly.


#40

Okay. Will do tonight.
Thanks.