Topics created by wilkinsaf

From James (the guy who set the parameter)

feel free to increase it. Starling 2 Max has a very high power to weight ratio so I artificially calmed it down by limiting throttle

@wilkinsaf yes unfortunately Gremsy doesn't sell one as of right now and I probably misunderstood your message that said "something is in the works" I though Modal AI working on developing one. Thank you

@wilkinsaf

A color AR0144 exists, but there is no current integration readily available

@h3robotics ,

Yes you should be able to test the Hadron on J8 using the instructions from the docs page (https://docs.modalai.com/voxl2-hadron/) -- just make sure you use Boson sensormodule 4 and ov64b sensormodule 5 (and camera IDs will still be 0 and 1 respectively, if there are no other cameras attached / detected).

At this point you do not need to build a custom kernel, just need to use kernel variant 1 because it enables independent camera support on J8 which is needed for Hadron. Please note that you would not be able to use our standard ucoax camera on J8U because the camera reset signal is still not correctly patched through to J8 (which would require a kernel modificaiton). But in Hadron use case, camera reset is not used (both the IR and RGB camera are always on, so it happens to work out 🙂 ).

I agree, it may be more convenient for you to switch to using the M0173 camera front end, so you can use a single kernel variant and also this would be a more future-proof approach.

Alex

@wilkinsaf , IMX327 no, but IMX664 maybe 🙂

I think IMX664 is close to or better than IMX327 for low light, what do you think?

Alex

@James-Strawson This is perfect! Thank you James!

maybe voxl-replay....

@wilkinsaf , yes, you got it. By the way, you did not have to restore the old firmware, you could have just done this:

./voxl-esc-upload-firmware.py --firmware-baud-rate 57600 -f firmware/modalai_esc_firmware_m0117_1_v0_39_RC10_eb6fb500.bin --id 0

The following note does not really help, if you also have power connected to VOXL2..

WARNING: Specified ESC ID not detected; perform manual power cycle now

However, if the ESC is connected to a PC, you can just power cycle the ESC and the the bootloader will start up and firmware update will being.

Alex

@wilkinsaf No, they are exactly the same

Following up here. We upgraded to a voxl2 and stopped since this error. we think it might have been an issue with voxl flight on the newest SDK for auto exposure

@wilkinsaf

Yeah you're absolutely right! Happy to help you out if you have any more questions about that process.

-Thomas

Noting here that flashing the wrong kernel will brick the device (ie flashing the QRB on the QSM) make sure to select the correct option when upgrading the board.

@tom After 8 hours of grueling coding: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/merge_requests/11

I will continue to use HDMI to USB:

https://www.amazon.com/gp/product/B097D5CJ4T/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

Looking at what BlueOS is setup to do...it might be easier to modify modalAI's voxl portal than to get this to work with the current setup.

The things I am looking to add immediatly is log download and additional ways to get information and status on voxl services such as journalctl logs