Photo capture stops mid-flight?


#1

Recently we attempted to capture some imagery with our Sequoia camera using the Atlas app. The Sequoia is attached to our DJI Phantom 3 Professional with the MicaSense integration kit designed for that purpose. However, we’ve had a number of issues. This is issue 2 of 3.

I’m rather desperate to get this camera operational as the area we are trying to photograph is about to be destroyed by construction work, and after 1.5 weeks without response from Parrot technical support after creating a support case, I’m hoping that some of you may have sufficient experience with Sequoia to offer a solution or some advice.

After configuring our flight plans and camera options in the Atlas app, the mission is uploaded to our drone and the flight is flown. However, during the flight only a few (a couple dozen) photographs get successfully captured (the flight should have produced something like 300 photos [1200 TIFF files]). This happens whether we are using an SD card, or writing to internal memory.

The sequoa_diag.dat file shows a number of times that SICILIA_ERROR messages are thrown, but it appears that the system continues to work, and indeed a number of photographs are captured and stored. However, after a number (the exact number varies widely) of photos, the following errors appear in the log and no further photographs are captured:

HAL_i2c_msg_send() : 121, Remote I/O error
one or more i2c addresses are not correct
libHAL’s HAL_read() : error send
HAL_thread_handler: ERROR reading sensors (Error 2)
HAL_i2c_msg_send() : 121, Remote I/O error
one or more i2c addresses are not correct
libHAL’s HAL_read() : error send
HAL_i2c_msg_send() : 121, Remote I/O error
one or more i2c addresses are not correct
HAL_thread_handler: ERROR reading sensors (Error 2)
Gps disconnected, libgpsman not launched, aborting
GpsReader no uart connection
GpsReader thread killed
Powering off gps…
HAL_i2c_msg_send() : 19, No such device
HAL_I2C_ERROR_MSGS
libHAL’s HAL_read() : error send

This starts a series of issues in the log and eventually a crash of sensors_IR:
Memory section “colibry_sensors_IR” successfully open with revision number : 4
fd 7 not found in loop 0x76a09370
EventsFsm: void Libfsm::EventsFsm::stop() [with EventType = Sicilia::controller::eControlEvents] stop
EventsFsm: destructor
EventsFsm: void Libfsm::EventsFsm::stop() [with EventType = Sicilia::eEstimatorEvents] stop
COLIBRY_EVENT_MSG_INIT_END (datasize: 0)
worker 417 started
unw_get_proc_name failed: -1
unw_get_proc_info failed: -10
no region containing address 0 found
*** *** *** *** *** *** CRASH *** *** *** *** *** *** *** ***
exe : /usr/bin/sensors_ir

Has anyone ever had their Sequioa just stop taking pictures mid-flight? Have you ever seen such I/O errors in your log files? Do you have an suggestions on what might be the cause? Or what could be a solution?

The entire diagnostics log is available for review at:
https://smuhalifax-my.sharepoint.com/:u:/g/personal/greg_baker_smu_ca/EU769o9Z37xBnZvSm7PFl98BTpwKxZ-UpFDzNe_OYBJVsw?e=JmeLnb