@tom I am running The Latest one 1.3.5. I had tried all possible things mentioned on docs but still not getting imu server running.

@scosgrove , I just wanted to mention that our ESC driver for PX4 is also using UART running at 2Mbit. The Flight Control loop sends out commands at 800Hz and each control packet is 15 bytes long. Also one ESC channel (out of four) sends feedback to the DSP for every command. The feedback packet size is 16 bytes (at 800hz), that would be 12800 bytes/s. We almost never see missed RX data. I have also experimented with larger feedback packets (~42 bytes at 800hz = 33600 bytes/s received by DSP).

Can you please clarify how the data is batched when the byte loss happens - how many bytes are sent without a break?

Alex

@Jainik-Mehta , can you please let me know what you are viewing in voxl-portal? A single camera (which) or all cameras?

Alex

@voxl-phoenix J19 has pins for 2 UARTs. We put GNSS on one and RC on the other. So if you are able to hook up everything correctly, configure the TBS crossfire receiver correctly, and configure PX4 correctly then it should work.

I did more digging and it seems that the problem is related to the v1.14+ firmware I upgraded it to (from the Flight Core v2 downloads). For some reason in recent firmware updates it breaks the SBUS input.

I verified this by also upgrading a working VOXL Flight and was able to reproduce the same problem with the upgraded firmware in 1.14 and 1.15.

Any idea why this would break on the latest firmware releases?

@Vinny Thanks @Zachary-Lowell-0 @Vinny !!

@Eric-Katzfey I will need to add the support for up to 8 PWM outputs on VOXL 2 IO board. Right now it only supports 4. You should be able to do test flights without the gimbal with 4 PWM outputs.

@Eric-Katzfey Thank you for providing the updated package.
I will test it within the next three days.
I’ll get back to you with the results shortly.

@griffin Unless you have your network setup to manually cycle IP addresses every so often then your PC's IP address should stay the same. They're usually logged by mac address

@Jetson-Nano , the following link shows location of all the connections and test points that are being utilized: https://docs.modalai.com/voxl-fpv-esc-datasheet/#hardware-overview . If there is a test point that is not documented, it means it is not supported in firmware or only used for production testing. If you have a specific question, please let me know.

The following link describes the Neopixel led support : https://docs.modalai.com/voxl-fpv-esc-datasheet/#neopixel-led-support . A single string with up to 32 LEDs is supported. VAUX regulator is dedicated for this output and can handle 500-600mA. We also have a way to control this output to be 3.3V or 5.0V (3.3V default) but the control feature is disabled at the moment. You can test the Neopixel output while PX4 is not running using voxl-esc tools : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/voxl-esc-neopixel-test.py (we also have a helper command to use the LED while PX4 is running). https://gitlab.com/voxl-public/voxl-sdk/services/voxl-io-server/-/blob/master/tools/voxl-send-neopixel-cmd.c -- this tool is a command line tool which sends the control data to PX4 and then PX4 forwards it to the ESC. Right now the C example only supports white color, but we will extend it to RGB.

The payload connector just outputs VBATT, so as long as your desired current is within the JST connector spec, you should be ok. (4Amps per manufacturer's spec).

J1 is used for UART communication with FC or the voxl-esc test scripts and the data that is send are the ESC commands (rpm or power) and other commands like Neopixel commands, PWM output.. The ESC also sends back the ESC status.

Let us know if you have any more questions 🙂

Alex

@Jeremy-Frederick Okay, well then you will need to add support for such an external Mavlink enabled peripheral into voxl-mavlink-server. We don't currently support that.

@extmoddrv

We support the following modes for IMX412 cameras:

Full frame 4056x3040 : 30FPS, possibly 60FPS (need to double check) 4K 60FPS 1080P 180FPS (maybe 240 FPS, need to double check) 720P (cropped) 240FPS

AR0144 FPS is currently limited to 50FPS (camera maximum is 60fps, but we have seen some stability issues). Resolution for AR0144 is fixed at 1280x800.

If you provide your specific requirements, I can confirm whether that is supported. Are you looking for the h264/5 encoded video for IMX412 camera? What about AR0144 tracking cameras - just RAW?

Alex

@Zachary-Lowell-0

All our robots are currently operating on ROS1, and we haven’t transitioned to ROS2 yet. Any help, advice, or guidance on this would be greatly appreciated. Thank you!

@Vinny Appreciate the heads up

@tom thanks I had opened the board so I did not notice it, only if I had assemble I would have noticed it.
Thank you so much it worked!

@Alex-Kushleyev Thanks, everything looks alright now that I've removed the other cameras from the config file