@Alex-Gardner all right, thanks for that 😉

@Chad-Sweet Thanks for your reply.

I am currently running firmware FCv1 - v1.11.3-0.2.3 from that link. I downloaded the image and then uploaded it through QGC as a custom firmware.

Thanks,

Karl

@Nathan-Sullivan

Awesome, great to hear! Yeah, that's a sneaky one that's gotten me a few times 🙂

Thanks,
Rich

@Chad-Sweet I can confirm that we can communicate with the pddl900 inserted into the ModalAI USB Carrier board...thanks!

@Todd-Humphreys

Hi Todd,

I believe they are replacing them with almost identical motors but with a slightly higher KV value. If you can source those then they would be a drop in replacement.

If you're interested in something else, then here's some that I've tested before. The only thing is you'd need to solder the 3 male 2mm bullet connectors onto each motor. Otherwise they're drop in replacements.
https://usa.banggood.com/Racerstar-Racing-Edition-2216-BR2216-810KV-2-4S-Brushless-Motor-For-350-380-400-450-RC-Drone-FPV-Racing-p-1083206.html?utm_source=googleshopping&utm_medium=cpc_organic&gmcCountry=US&utm_content=minha&utm_campaign=minha-usg-pc&currency=USD&cur_warehouse=CN&createTmp=1&ID=521309&utm_source=googleshopping&utm_medium=cpc_bgcs&utm_content=sandra&utm_campaign=sandra-SSC-usg-sku-1019-xp-cvrcart-11sale-21&ad_id=554267045258&gclid=CjwKCAiAjoeRBhAJEiwAYY3nDF7t6brTndAN6m0qocX3YTDihgCK1dw6y2-u2YtW9OWuC_Xq_bipZxoCnv8QAvD_BwE

@tom After playing around with CP_DIST, it seems any value > 0 causes position mode to no longer want to allow x/y translation. From what I understand, any value < 0 disables object avoidance. Is this true?

As far as I'm aware, my settings should be in parity with Modal provided guidance in regards to seeker setup with additional configurations overridden to support voxl-mapper.

Thanks for the stabilized advice @mohammednaveed, I've gone as far to replace manual mode with this setting.

@Matt-Turi Thank you for your quick response.
After updating to v0.0.5, it worked!

@Eric-Katzfey Thanks for reminding me about this 😉 So, I may have to switch to using the J8 in different scenarios.

Any updates on this?

@Remco-Roelofs You can find more information about our Microhard and Doodle Labs support here: https://docs.modalai.com/microhard-modems/ and here: https://www.modalai.com/collections/accessories/products/voxl-microhard-modem-usb-hub. I would urge you to work with Microhard and Doodle Labs directly to verify that their products can do what you need.

@Daniel-Lin ModalAI does not have any plans to produce hardware emulation at this point. However, I don't think buggy code will ruin an m500 (assuming you aren't flying, of course). We develop all of our hardware device drivers directly on target without any issue. For added safety, please remove the propellers before doing any such development.

@Eric-Katzfey Thank you for your help. I followed your steps and it worked immediately. I am now also able to generate the ipk-package and push it to the VOXL. When I use adb shell, the file appears in home/root/ipk.

I tried a few things, but I still have some questions:
How can I run the i2c related files from "libapq8096-io/lib/python" on the VOXL, for example voxl_i2c_scan.py?
Can I also make my own python scripts and run them?

Mavlink messages for setting flight mode use the MAVLINK_MSG_ID_SET_MODE message type (same as APM).

Modes are defined in the uOrb layer under the vehicle_status.msg fie, which C headers are auto-generated at build time. The auto-generated file is under the build directory as vehicle_status.h via the NAVIGATION_STATE_* variables.

And example of using modes in runtime code are in the mavlink_messages.cpp file
(search for vehicle_status_s::NAVIGATION_STATE_AUTO_MISSION) and modes are processed in the Commander.cpp file. Both files under the src/modules directory of PX4.

@prjana Can you arm the drone? Obviously with appropriate safety precautions as this can be an extremely dangerous thing to do if you aren't very careful! But arming the drone will cause the motors to spin.

@modalab Hello, can you help me to resolve this problem?

Hi @마페링 ,

Double checking, do you have a VOXL Flight and not a VOXL?

For the USB connection, what port are you using?

The ADB connection is to talk to Linux (not PX4) and to talk to PX4 over USB you will want to use the J1006 connector.

Thanks!

One of the Modal team can probably chime in on this... but I'll throw out a few thoughts.

It would definitely be feasible with the Seeker drone, but would require some programming knowhow to leverage the mapping software Modal has out of the box. You could walk the drone around the space manually once to build the first map and then from there on have a path with waypoints around the space for it to fly the Insta360 around to capture updates of construction. Alternatively you could use one of the VOXL cameras to capture.

Cliff,

Apologies for hijacking this thread slightly, but in another one I was interested in this transition mechanism.

It looks like the responsible code to monitor GNSS signals and perform the transition is here: https://github.com/modalai/px4-firmware/pull/1/files#diff-4086bdb716e4bb6c6668a2d61f8c87ef3f15caf4c7d7032595c7ec28a4cffdc7R106

Are these changes merged into the official build of v1.11.3-0.2.3 on the ModalAI site at?: https://storage.googleapis.com/modalai_public/flightcore-releases/v1.11.3-0.2.3-modalai_fc-v1_default.px4

I haven't seen the firmware ever "flip" the EKF2 mask, but perhaps there is another parameter I need to set to enable the GNSS quality monitoring. I'll poke around a bit more, just wanted to make sure I was on the right track with the above changeset.

Thanks much for any insight!
Steve

Great to hear.

I forgot about the ToF. Chad beat me to the punch here.

Glad that helped!