ModalAI Forum

@wilkinsaf Yeah no leds or noise. Welp, I am going to send this back for hardware inspection. See if a cable is loose. Thanks again @modaltb

On my setup yes that was all I needed to do, but we are still going to do a "full proper tune" on our S500 based frame (Sentinel dev drone) and I will confirm with you that we are getting performance as expected after this and share a video. Our flight test team will be doing that this week, thanks for the patience!!!

Hi @pfranklin , Sorry for the lag. The VOXL 2 architecture has a few processors, the I2C on the 5G modem port is mapped to the applications processor. The I2C we use by default in PX4 is connected to a DSP (image here https://docs.modalai.com/images/voxl2/m0054-px4-block-diagram-0.4.png). For each driver we've used on the DSP, we've had to make a few small mods to get going. Here's an example of an I2C driver we use on the DSP for talking to a baro: https://github.com/modalai/px4-firmware/tree/voxl-dev/src/drivers/barometer/icp10100 It's enabled in the build here: https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/rb5-flight/qurt.cmake#L55 Are you already using J19 pins 3 and 4? If not we could hijack those from the mag driver perhaps and you could use the sensor there.

@Aks You can probably get better answers by contacting Doodle Labs themselves and VOXL2 really only acts as a bridge to pass through data to the Doodle Labs network as the smart radios handle most of the networking themselves. Here's a datasheet for the Helix smart radio: https://doodlelabs.com/datasheets/smart-radio-platform-1625-2510-mhz-datasheet/

Hi, good question. For the low speed connector on VOXL 2, Zybax makes what you are looking for. https://www.zebax.com/index_files/page2540.htm Last I checked they did not have one for our high-speed connector. We're hoping they make on though. If we can find a contact, we will reach out to them and see if they are going to. Otherwise, any specific requests? We may have something in the works that will be useful.

@modaltb Thank you. It works....

HI @Akhil-Raj , We might be OK with the sequencing. All OVT's specs are shared under NDA, so we do not have access to every sensor spec sheet that they make. However, it should be OK if you can share the one chart of power up sequence requirements, and I can check our design to flag any issues or concerns. Most sensors have "no required sequence" such as the OV9782 Chad mentioned, and we have only come across 2 or 3 in our history that care about it, but I like to check. So, let me know if you can re-post that data in whatever format is easy for you (screen shot, re-type, etc) But be sure to respect your NDA with OVT. Thanks!

@Tamas-Pal-0 We have observed this issue a few times and the solution is always to either swap out the MCBL-0001: https://docs.modalai.com/cable-datasheets/#mcbl-00001 (power module to VOXL2 cable) or insepct the cable closely and push the wires back into the connector if they have come loose. It seems as though after time if these cables are unplugged and re-plugged often that there is enough degradation that the VOXL2 isn't able to pull the current necessary on boot and thus enters the boot cycle. We are actively looking into this issue to determine the root cause. If you aren't able to fix the issue based off this info we can get you a new MCBL-0001.

@Alex-Gardner After installing the packages from staging version the cameras are not working. How to solve it ?

@Daniel-Mellinger I am still facing the issue with the remote, but i believe its only with the remote as I was able to get it flying in offboard mode using the VIO onboard. Its flying and is quite stable at the moment. Due to the nature of our research, we dont fly with the manual remote (we only use that for initial tests). But from my experience im not sure if the remote controller could be at fault, because I have used the same RC / receiver pair on the VOXL (version 1) and its able to fly in manual mode without any problems If you look at the Manual Control input plot in the px4 review mentioned in the 1st post, you will see that there are no discontinuities present in the signal. The setpoint thrust and pitch curves look fine. Whereas the setpoint pitch and thrust going into the attitude controller is quite discontinuous In summary, we are just using the remote to change modes and trigger emergency kill switch and thus this bug is not affecting us anymore

TX Overflow happens because you are trying to connect to QGC with the serial connection being leveraged by gazebo for HITL. So what you need to do is open QGC after gazebo is running and connected to the VOXL2. Once this is done, you can only connect to QGC via the UDP connectoin. This can be done by enabling voxl-vision-px4 and voxl-mavlink-server services. So you connect to the gazebo via the serial, and QGC via the UDP connection.

Hi, When running lsmod I would expect to see a list of different kernel modules including the 88XXau kernel module which is the driver for that wifi dongle. Luckily we've also included the kernel module in the Voxl2 file system under the path: /lib/modules/4.19.125/kernel/drivers/net/wireless/88XXau.ko I would suggest first trying to load this kernel module using the insert module command: insmod /lib/modules/4.19.125/kernel/drivers/net/wireless/88XXau.ko You should then run ifconfig and see if the wlan0 interface appears, if it does then the module has been successfully loaded and you should now be able to use your wifi dongle. However, I do recommend upgrading your system image by installing our newest 1.3.1-0.8 platform release. This will upgrade your system image to 1.3.1 and install the 0.8 SDK. This can be found on our downloads page. I recommend doing this because for some reason all your kernel modules are missing. I'm not sure what might've caused this, but it might lead to other issues.

@Eric-Katzfey 232. I'm not terribly worried about it. I've worked with their VN-100 series before, which we might go with. A logic shifter should work fine. So maybe we open another UART? Our custom daughter board connects to J3 and J5 so we can get more than 1 UART even though we're currently only using UART7? from the J3.

@mawriyo Here3 GPS support is now available in voxl-px4 1.4.27 available here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.4.27-202209272330_arm64.deb. This needs to be used with the Here3 in "i2c mode" which means opening up the unit, placing the switch in the "i2c" position, and creating a custom wiring harness to route UART and i2c lines over to VOXL 2 J19. Launch voxl-px4 with the new -h flag to enable this new support. The Here3 unit has an ak09916 magnetometer and TCA62724FMG LED controller.

Hi Tamas, did you solve the problem? I have the same issue.