@Eric-Katzfey I fixed the problem thanks after I download the Seeker's parameter at gitlab it success arm by my RC and It can fly now

@Eric-Katzfey we are connected to the gpio pin but don't activate it during this reset. We also have a privileged access from the docker so we can change the gpio pin state to on and off from software. We use the pin 1153. The node on this docker runs our autonomy stack but does not interact with the hardware besides the gpio. i also tried removing the privileged access to the docker but still got the problem. We have 2 more dockers that gives us the ros2 mavros messages. Those one never gets resets and works fine.

@stevedan No, we have not encountered that. But can you open this up in a new thread so that it has an appropriate title? Thanks!

@Chad-Sweet That clears it up, thanks!

@Jgaucin You can check out https://www.modalai.com/pages/rma and we can attempt to recover your board

@tom I'm not having the same issue with GPS lock. I can get a GPS lock, but my GPS is showing as disabled in QGC. Is there a PX4 parameter loaded on the Sentinel's that defaults them to disable GPS? Changing the EKF2_AID_MASK to enable GPS doesn't due anything. *Ignore this part, just didn't have COM_ARM_WO_GPS set to 0 Also, I'm still concerned about the constant MAG#0 timeout errors, the unstable/unrealistic position estimates I'm getting for Local Position NED in QGC and the high loss rate I'm getting over mavlink. Do you have any suggestions for troubleshooting and is there a way to synchronize the clock on the voxl2 with the clock on the GSC? Thanks

@Eric-Katzfey this is our GPS status right now INFO [muorb] SLPI: qshell gotten: gps status INFO [muorb] SLPI: Main GPS INFO [muorb] SLPI: protocol: UBX INFO [muorb] SLPI: status: NOT OK, port: 6, baudrate: 0 INFO [muorb] SLPI: sat info: disabled INFO [muorb] SLPI: rate reading: 0 B/s INFO [muorb] SLPI: Ok executing command: gps status INFO [muorb] SLPI: Sending qshell retval with timestamp 855143719, current timestamp 855143720 INFO [qshell] qshell return value timestamp: 855143719, local time: 855147735 pxh>

@Martin-Brandt Starting the RMA process is probably the best option as opening it up yourself risks damaging other components

Hi @A-Evans This is our current WiFi solution for Voxl2, or any ModalAI board with a standard USB2 4-position JST GH port. https://www.modalai.com/products/wifi-usb-cable-add-on?_fid=da227b041&_pos=1&_ss=c If you want to use our 10-pin USB3 format connector for the Alpha USB Dongle, then you can also consider using this cable: https://www.modalai.com/products/mcbl-00022 Note: We use Alpha WiFi since it's NDAA compliant You are free to use any WiFI USB dongle sourced at the UK, and make your own cables for USB2 (not too hard for proto-type builds).

@Jgaucin you can use voxl-portal to view the output of all of the image sensors on the drone. The Sentinel has forward and rearward stereo depth pre-calibrated and tested in the factory https://docs.modalai.com/voxl-portal-cameras/ this might also be useful https://docs.modalai.com/calibrate-cameras/

@Eric-Katzfey I think it probably makes a lot of sense to leave it on there and just call it out more in unboxing. We purchased a number of platforms and it only came up with 2 of them.

@Eric-Katzfey Thanks, problem solved.

@Paul-Carff Sounds like your son knows his stuff!

@Chad-Sweet Thanks. So it sounds like a full re-flash is probably the best check to re-install base software (I'm not aware of any modifications, but came onto the project after it started) and check that connection. If the issue persists with both units, kick off an RMA? Appreciate all your help.