IMU's can be found here.

Through QGC, the offsets can be adjusted: here

You'll have to configure the extrinsic files as well to match the rotation of the board

/etc/modalai/extrinsics.conf

Hope that helps!

@Chad-Sweet That worked! After I did the reinstall, it would not connect. I closed and reopened QGC, switched the usb cable, and then went into the auto-connect section of the general settings and disabled the NMEA GPS device drop-down.

Thank you Chad!

@Caleb-Rievley Generally, that won't work.

@sspiller The WiFi and MicroHard radios don't have any specific configuration needs for video streaming. They are just network interfaces. The issue will be with available bandwidth. If you want to stream a high resolution stream at 10Mbps and your radio can only support 5Mbps then you will lose a lot of packets and your video stream will not look very good.

Great news!
I had an older version without ToF Logging
Thanks

Did you review the PX4 documentation? It looks like it has the command set here

I've figured out why.

My original MPC_LAND_SPEED and MPC_Z_VEL_MAX_DN were 0.6 and 0.5 respectively.

Thanks to the following chunk of code from MulticopterLandDetector.cpp, descend_vel_sp will never be true.

if (_flag_control_climb_rate_enabled) { vehicle_local_position_setpoint_s vehicle_local_position_setpoint; if (_vehicle_local_position_setpoint_sub.update(&vehicle_local_position_setpoint)) { // setpoints can briefly be NAN to signal resets, TODO: fix in multicopter position controller const bool descend_vel_sp = PX4_ISFINITE(vehicle_local_position_setpoint.vz) && (vehicle_local_position_setpoint.vz >= land_speed_threshold);

Had to increase MPC_Z_VEL_MAX_DN and that solved my problem

I’m having the exact same problem, but I can’t connect to an Ethernet. Is there any other option for calibration? I’ve tried for 8 hours straight with no luck……

Sorry for the delay. To achieve 12 PWM you would need a custom solution. You could likely use an Arduino Teensy or similar

@Moderator J8 VBUS Output follows USB3 specs for voltage range (+5V +/- 10%) and a current limit set-point of 1.1A (just above USB 3 specs of 900mA for extra margin in OTG mode).

Roger that, thank you!

Hmm, it looks like none of those options are available to our configuration, so we will have to stick with USB through the 4G carrier.
I've found that the Pixhawk is rebooting now (not sure if something changed, or if I'm going crazy) but voxl-mavlink-server fails, and continues to fail if I systemctl restart voxl-mavlink-server so I have to reboot the voxl2 with every Pixhawk reboot.
Not that big of a deal. Has the bug been fixed where sudo reboot takes a couple of minutes to actually reboot the VOXL2? Each time I want to reboot the Pixhawk it's about a 5 minute process

this usually means one of the following:

camera configuration does not match what is installed. the configuration needs to match what is installed, not what you want to use a connector is not properly seated a connector is backwards

@modaltb Hey hey know it's been forever but just right now I finally got it working. 🙂
I adjusted the adress in the corresponding driver's .h file and now it's finally running.
thanks again for going through this with me.
cheers

@m4v3r said in Flight Core w/ BMI088:

Thanks so much for clarifyiing this for me and I take it you wouldn't suggest using it since it's an older part?

My only suggestion is to use the ICM parts since that will always be installed on our boards, and you'll have no software mismatch builds across platforms old and new.
It's the Bosch parts that have fallen out of favor lately in the market and were also very hard to get last year hence the move to start DNI'ing them.
Thanks!

Hey,
just to give a little update here:
I found out how to set the "force mavlink mode" variable in the voxl-vision-hub.conf which was forcing the parameter back in PX4, and simultaneously set it to "Normal" in PX4.
So far I don't see any downsides from using MAV_1_MODE=0 (normal).
I'm only making use of voxl-mavlink-server and voxl-vision-hub for the time being, basically to use VOXL's connectivity to send MAV commands to the PX4.
Do you think using "normal" will have any downsides?
The inconsistency between your documentation and the .conf and PX4 firmware files still exists though, so I'd really like to get some more insight on this.
Thanks and a great weekend to everyone. ❤

You should compare the settings as configured in the code here. We provide the code so you can fork and implement your own configuration if needed