@Matthew-Wellner , the M0181 board supports just Boson or Hadron (boson + color camera in one unit). You can find the details for M0181 here : https://docs.modalai.com/voxl2-hadron/
Please double check that your Boson is plugged into the correct ucoax port on M0181 (per documentation linked above)
Just to double check, which board is plugging into your Boson? M0xxx?
Alex
@Jetson-Nano said in doodle labs and joystick setup:
This is the output i am getting while running listener manual_control_setpoint
What is the parameter COM_RC_IN_MODE set to?
@Jetson-Nano said in doodle labs and joystick setup:
I am not able to see the option you have mentioned VOXL_ESC_T_ON
In the Mavlink console what do you see with "param show VOXL_ESC_*"?
And what about "ver all"?
@Ege-Yüceel This is definitely not supported by ModalAI. However, a sophisticated developer has access to enough documentation and source code that it is possible to make that work.
@tonygurney Try the test application voxl-send-esc-pwm-cmd. Source code is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-io-server/-/blob/dev/tools/voxl-send-esc-pwm-cmd.c?ref_type=heads
@Jetson-Nano , this is likely related to the fact that the FC starts quicker than the ESC bootloader's 1s wait time. We discussed this before.
So if you are saying that delaying the start of voxl_esc driver in px4 on your FC solves the problem, then the issue is exactly that.
Please delay the start of the voxl_esc driver in your px4 start-up script, for example you can see it at the bottom of the script here : https://github.com/modalai/px4-firmware/blob/bugfix-fpv-rev0-airframe/boards/modalai/fc-v2/init/rc.board_sensors
if param greater VOXL_ESC_CONFIG 0
then
usleep 1500000
voxl_esc start
fi
Hello @ROBERT-JUDD and @somalley ,
Thank you for following up and I appreciate your feedback. I have relayed your comments (again) to the team and will push to get the workaround out.
For Starling 2 Max, the workaround is to install a mast, so we are working on making those details available. Shielding the GPS receiver in the default location is not as effective. Please refer to the testing done with a mast in the center of the drone in this thread : https://forum.modalai.com/topic/4226/starling-2-max-no-gps-data/38 . However, the workaround is probably going to have the mast in the back of the Starling 2 Max.
For Starling 2, @somalley , a similar solution should be possible (with a mast). We are targeting the fix for the Starling 2 Max first, however you may be able to use the same approach (elevate the GPS receiver as well as getting it farther from the usb wifi dongle, which is right under the gps receiver, and seems to cause interference sometimes on Starling 2). We have seen improvement on Starling 2 when the wifi dongle is mounted elsewhere, but also elevating the GPS receiver should help as well as putting a small shield at the bottom.
voxl-portal now supports displaying the GPS SNR, so it should be easier to validate the signal improvements based on SNR directly (as opposed to time to lock, etc).
Again, sorry for the inconvenience and I will check in a few days regarding the status of the workaround.
Alex
@jared , you potentially have the pin order swapped. Both sides (M0188) and your leopton breakout board should have the pin1 marked, so just make sure pin1 goes to pin1, etc, otherwise it is a straight through cable, but it could be reversed in your case. Well.. it is only straight through if you use our Lepton breakout board 
I doubt that supplying 2.8 instead of 3.3V to the lepton breakout board would cause VOXL2 to fail to boot. If 2.8V is shorted to GND (which would be the case if the wiring is flipped), then this would cause PMIC on VOXL2 to prevent the board from booting.
@shawn_ricardo , thank you for the details. i will investigate shortly.
Also, just wanted to mention, your motor kV is very low, i don't think we have tested anything below ~400. So you should definitely put the ESC through sufficient testing to ensure that there are no de-syncs. For the tests, i definitely recommend running them from your desktop / laptop, as you get more instant feedback (plots) and can iterate much more quickly. If you need more details for the testing, let me know, but obviously the first step is to get a good calibration done. The step tests, etc, are listed in the low kv tuning guide.
Alex
The voxl2_io driver works as a standard PX4 actuator, supporting up to 8 actuator outputs.
When voxl2_io driver is enabled, you can select which outputs to assign to the 8 pwm outputs using QGC, just like any actuator setup.
Then during normal operation, the PX4 mixer will send the standard commands (based on your PWM channel assignment) to the voxl2_io module (the commands typically range between 1000-2000, but the range can be changed).
voxl2_io driver, will take these values and package them into a special packet, which is then sent out via UART to M0065 board.
M0065 board will receive the pwm control packet and set its pwm values based on the packet contents.
There is no SBUS involved in this communication (standard UART between VOXL2 and M0065 board).
Does that clarify the data flow from PX4 to the M0065 board?
Alex