krushikesh
commented
5 years ago @fnoop this is the log file info. for my vision_landing. It is stuked in requesting track_target to start 2018-12-03 15:42:45,971 INFO Launching track_targets with arguments:/srv/maverick/software/vision_landing/track_targets -d ARUCO_MIP_36h12 -w 640 -g 480 -f 30 -v --markerhistory 30 --markerthreshold 90 /dev/video0 /srv/maverick/software/vision_landing/calibration/logic170_calibration_0359.yml 0.19 2018-12-03 15:42:46,986 INFO Connecting to drone on: udp:localhost:14570 2018-12-03 15:42:56,881 INFO Connected to drone 2018-12-03 15:42:56,881 INFO Starting time synchronisation with flight controller 2018-12-03 15:42:59,442 INFO Initial timesync complete, offset is 13 ms 2018-12-03 15:42:59,443 INFO Initial timesync difference is 771922199194 ms 2018-12-03 15:42:59,444 INFO Initial timesync delta buffer: [1948544L, 2290560L, 6910080L, 7252096L, 9452032L, 9732992L, 11674112L, 11977472L, 13654016L, 13950080L, 18020992L, 18662656L, 23856384L, 24544512L, 3577984L, 4589440L, 20466048L, 20723968L, 22857984L, 23129984L, 6030976L, 6280576L, 7670528L, 7958016L, 15993472L, 16249472L, 18347904L, 18628864L, 20906496L, 21395456L, 6435968L, 7107584L, 13424512L, 14241920L, 12788352L, 13430912L, 12924416L, 13656064L, 32999040L, 33632128L, 9196032L, 9943552L, 14850432L, 15523584L, 9238016L, 9820928L, 14085376L, 14722432L, 9403008L, 9997952L] 2018-12-03 15:42:59,445 INFO Initial timesync jitter (standard deviation of delta buffer): 6.99 ms, 53.77% of average latency 2018-12-03 15:42:59,446 INFO Setting flight controller parameters 2018-12-03 15:42:59,455 INFO track_targets: info:FoVx~48.2247:FoVy~37.2531:vWidth~640:vHeight~480 2018-12-03 15:42:59,456 INFO track_targets: info:Size Mappings: 2018-12-03 15:42:59,457 INFO track_targets: debug:Marker History:30 2018-12-03 15:42:59,458 INFO track_targets: debug:Marker Threshold:90 2018-12-03 15:42:59,459 INFO track_targets: ['initcomp', 'Initialisation Complete'] 2018-12-03 15:42:59,460 INFO Entering main tracking loop 2018-12-03 15:42:59,461 INFO Requesting track_targets to start tracking:VehicleMode:STABILIZE 2018-12-03 15:42:59,724 INFO Newer timesync message already received, ignoring 2018-12-03 15:42:59,726 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:09,776 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:09,778 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:19,747 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:19,748 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:29,739 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:29,741 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:39,782 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:39,784 INFO Newer timesync message already received, ignoring 2018-12-03 15:43:49,769 INFO Newer timesync message already received, ignoring
@fnoop As you said vision_landing is fixed for Raspberry Pi. So I have done the installation of a maverick on raspberry pi 3B+. after running the vision_landing module camera turns on but it's not giving any output on any format .avi or over the network using UDP. how should I know that it is working properly? how to check that it is tracking the targets and sending commands to the Pixhawk? Also when I change the marker id for specific marker detection it gives error ie. "expected string but int found"