Topics created by JoeC

@Alex-Kushleyev Hi Alex, Thanks! Yes, that was exactly the problem. I switched to the dev branch using 'voxl-configure-pkg-config', downloaded the latest voxl-portal ('apt get update && apt install voxl-portal'), and then switched back to the 1.4.0 pkg. Voxl-Portal works just fine now.

@JoeC Hello, all relevant files that you are looking for are included in the "3D STEP Sentinel" link provided at: https://docs.modalai.com/sentinel-functional-description/
Link directly to the download: https://storage.googleapis.com/modalai_public/modal_drawings/Sentinel_Drone_STEP.zip

@JoeC Sure. There is a configuration script at /etc/modalai/voxl-px4.conf that has some high level configuration values that affect how the startup script executes. The actual startup script now resides in /usr/bin. It is /usr/bin/voxl-px4-start. This is actually called from the higher level script /usr/bin/voxl-px4.

@Zachary-Lowell-0 Thanks Zach, this does answer. I have been used to ROS1/MAVROS where sending position targets was completely ignored unless in offboard mode so my node would typically blast setpoint_raw messages whether in offboard or not (in part to keep the option of switching to 'offboard' mode "alive").

I will proceed from now on in ROS2/MicroXRCE assuming I should constantly send offboard control mode messages, but send traj setpoints only when offboard mode is confirmed. I appreciate the clarification on why this is.

-Joe

@Eric-Katzfey Thanks for your help. I've confirmed that I was able to use J19 with the "RC=M0065_SBUS" option successfully. Hence, if no VOXL_ESC, one should use J18 for the VOXL2 IO board and if there IS a VOXL_ESC board, one should use the J19 for the VOXL2 IO board. The firmware seems to be "smart" enough to figure out as long as /etc/modalai/voxl-px4.conf is set as you suggested.

-Joe

@modaltb ok thanks! I'll proceed with the 412 variant.

@Moderator Apologies for the lack of clarity. It's mentioned in an earlier version of the SDK (pre SDK 0.9.5), here in fact: https://docs.modalai.com/voxl-camera-server-0_9/ (search for "flip"). I added "flip" to the .conf file, but it didn't have an effect it seems. I haven't checked out 1.0 or 1.1 yet (I'm holding off on going past 0.9.5 until VOXL IO board is supported) but I'm hoping such basic image manipulation is available in those versions as well.

@Chad-Sweet Hey Chad! Yes 100% I'm open to the PC tools to get it done as well. I suppose I'm a bit uncertain about the hardware pipeline in this case. I'll want to have the traditional m500 ESC and motor, so I'll need to generate the PWM calibration curve somehow and generate the correct parameters. Should I use a surrogate m500 VOXL1 board to just get the values and run with those?

-Joe

@tom Confirmed, installing the normal way doesn't corrupt the apt repo..... THANKS!

@Eric-Katzfey Thanks Eric, for future readers, I've created a new post at Voxl 2 Spektrum RC Issue.

@JoeC gotcha. If you could email us at: contact@modalai.com we can get started

Hi Joe!

We're most of the way through a big update that'll make all of our packages able to run on multiple architectures, this release will be paired with a system image update. If you'd like to manually build the latest from our gitlab in the meantime, simply add the line arch arm64 7 to /etc/opkg/arch.conf and then run opkg update on voxl.