UPDATE : I tried to work around the problem until emlid fixes this issue with dronekit by using mavproxy in the following method :
1>set gcs in navio2 to 192.168.1.100:14550 which is the ip of my laptop
2>next run mavproxy on my laptop (GCS) and specify master to be the local host 127.0.0.1:14550 and forwared the mavlink messages to 192.168.1.103 (which is the ip of the raspberry pi that navio2 is on ) using --out 192.168.1.103:14550
3>finally i run the python script on my laptop specifying the local host as the connect argument in this way : python2 myscript --connect 127.0.0.1:14550
And again another problem that has been there for about a year with no solution :
GPIO_Sysfs: Unable to get value file descriptor for pin 4.
GPIO_Sysfs: Unable to write pin 16 value.
repeating infinitely
I saw this problem has been posted in the community forums here Arducopter spams GPIO related mavlink messages
which states to work around this problem by typing : set shownoise False
but it didn’t solve the problem .
Please Emlid team try fixing the problem , because these specs are what distinguish navio2 from other flight controllers , so what’s the point if they can’t run .