@Morten-Nissov I would advise trying to get some support from the PX4 community. I'm not aware of any use of i2c multiplexers in any current PX4 drivers but I think it's a useful feature. But that is the best place to get advice on PX4 development.

@riteshsharma , based on changelog (https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/CHANGELOG) you can use voxl-camera-server package version 1.8.10 -- dowload it from here http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/. Upgrading your SDK would also work as Tom suggested.

@maddyr13 besides enabling 4 additional channels, the changes included: introduce new UART message between PX4 and M0065 board to allow specifying output pulse with high resolution (previously limited to only command range of 0-800 which was remapped to 1-2ms) change the output pulse to OneShot, which means for every command from Flight Controller, there is only one PWM pulse (per channel) generated. This synchronizes the PWM output to Flight Controller update cycle and reduces total delay between FC and ESCs. there was a bug in case of SBUS input was used, the output PWM rate was reduced to only 100hz (normally about 400hz using 1-2ms pulse, which is a limitation of the pulse width, since flight controller update loop is 800hz). I am curious if you were using SBUS input into M0065 before for your RC, in which case the pwm update rate was reduce to only 100hz. Change to OneShot should not have effect on the pulse width, only the delay of it. It is possible that with new firmware, the ESCs are getting updates at higher rate, which could mean that if there is high frequency noise (picked up by gyro from propeller vibrations), the ESCs are now receiving more noisy commands, which would cause the motors to heat up more. If you have the PX4 logs from before the M0065 firmware change, you can take a look and see if gyro was picking up a lot of noise (more than 5-10 deg/s is considered more than normal). Additionally you can check the noise in the actuator outputs. Are you still using m500 frame? did you modify it in any way? maybe VOXL2 needs more vibration insulation. Also, what you could do is restore the original M0065 firmware, use unmodified PX4 and compare results again (making sure to save the logs). Also, did you go through the ESC calibration and updated the PX4 actuator ranges, as instructed, after uploading the new M0065 firmware? Alex

@Jonathan-Davis said in Unable to run my own offboard node in starling 2: offboard_mode Check: https://docs.modalai.com/mavros/#configure-voxl-vision-hub-localhost offboard_mode - set to “off”. When offboard_mode is on, this enables voxl-vision-hub to command the drone to move, which we don’t want (we only want MAVROS to be sending movement commands)

Hi Rowan, There is no one answer, it is entirely dependent on your circumstances. auto will be more conservative than perf. perf is intended to go as fast (and hot) as possible

Regarding enabling additional cameras, it is is not trivial and it would require a special kernel (because it would break the existing stereo camera support). Additionally, it would require a special interposer / cable in order to use a stereo pair with another camera on a single connector (this hardware does not exist now). At this time, we do not have plans to enable this functionality. As an option, you could potentially hook up a USB camera (will require an usb expansion adapter) to supplement existing cameras (using UVC interface), but we don't provide as much support for that option since that is 3rd party hardware and software.

If you need the cpu stress function to generate more heat, here is something that works. you can replace the current function with this one. It adds a memcpy() operation which uses a lot of power. You can tune do_memcpy_every_nth to control more or less heat (decreasing the number will use heat up cpu more). Original function is here #define STRESS_ARRAY_SIZE (128*1024) static void* _stress_function(__attribute__((unused)) void* arg) { uint8_t * _stress_array = malloc(sizeof(uint8_t)*STRESS_ARRAY_SIZE); uint32_t cntr = 0; while(stress_running){ cntr++; volatile double s = sqrt(rand()); //this helps slow down the while loop const int do_memcpy_every_nth = 50; //do not perform memcpy every loop because cpu can get hot very quickly if ((cntr % do_memcpy_every_nth) == 0){ memcpy(_stress_array,_stress_array+STRESS_ARRAY_SIZE/2,sizeof(uint8_t)*STRESS_ARRAY_SIZE/2); } } //printf("stress thread exiting\n"); free(_stress_array); return NULL; }

@rdjarvis , The board is in eDL mode (emergency download). Can you please check that SW2 is off and if the issue is persists, provide serial number of voxl2 board, we will check test records.

@Aaky Well, unfortunately it isn't obvious what is going wrong. You will have to start by disabling everything and when px4 comes up reliably start enabling things to find out the culprit.

@Paola-Lim , have you tried voxl-inspect-cam -a (to see all camera stats) or alternatively voxl-inspect-cam cam0 which would be just for your specific camera name.

@Aaky , we are working on resolving the GPS detection issue related to uart baud rate changes - if forcing the baud rate works reliably then just stick with that !

@muhammadbilal1 The batteries for Starling are standard Lithium Ion batteries (not Lithium Polymer). The recommended charging rate for Li-Ion batteries is 1C, so if the capacity is 3000mAh, the maximum charging rate is 3A. Charging at slower rates will extend the battery life (as is true for all batteries). The maximum voltage is 4.2V. Please use a charger setting that specifically supports Li-Ion batteries. Most LiPo chargers also support Li-Ion batteries. I will check how to proceed regarding the missing adapter.

@Aaky , the mixer should never output a value lower than mixer min (while armed).

@tom That worked! thanks for the help

@Paola-Lim You will need to follow directions from this page : https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release Tom suggested getting the SDK 1.1.3, so per instructions you should go to https://developer.modalai.com, log in, then click on Protected Downloads -> VOXL2 Platform Releases and download VOXL2 SDK 1.1.3 and follow the rest of instructions from "flashing voxl sdk" page Alex

@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.

Hi @majjam I'm glad Alex is helping you. Nothing should ever be "searing hot" in our platforms. If it is, it may be that you have a 5V supply connected to the 3.3V supply of the MCU by an errant connection using one of the connectors, and over time the MCU will fail (likely very promptly). Please double check your wiring and connections to all peripherals and connectors using this page as a guide: https://docs.modalai.com/voxl2-io-datasheet/#connector-callouts Be sure you do not connect any 5V supply to the 3.3V pins. Thanks!

Hi @Jskim We are happy to report our testing was successful. I have documented the process where you can modify MCBL-00022-2 and add the series caps for your self to unblock your USB 3 speeds: https://docs.modalai.com/cable-userguides/#how-to-modify-mcbl-00022-2-for-use-with-voxl-2-mini-usb-3-speeds Hope this helps!! Let us know how your testing progresses.

@Moderator Thank you for the response. I did come across this product of yours here: https://www.modalai.com/products/mdk-m0135?_pos=1&_sid=e4d19a51b&_ss=r that should work great after looking through some of your user guides and technical documentation.