@tom Thanks for your thoughts Tom, it was new to us as well! We seem to have managed to fix the problem but we're not entirely sure how / why. Our best guess is that was a software glitch with the Microhard radios themselves.

I'm documenting what we found here in case anyone else runs into a similar issue in the future.

We were able to eventually duplicate the same problem on another UAV that had previously been perfectly stable, thus eliminating the VOXL as a potential cause with two separate units showing the issue.

We were testing a variety of settings today (e.g. channel, bandwidth, power of transmitter, which module is master vs slave) just to try and identify if anything made a difference. Eventually after re-setting the settings back to the microhard defaults (which we had done several times already), the problem mysteriously stopped. We've since kept a stable link open on two UAVs for the last ~6 hours without issue, so we suspect that there was some software issue that eventually cleared when we modified the settings. The last change we made was testing which module was master/slave, and after swapping them and then swapping them back the issue went away.

Really puzzling issue, we're just glad it seems to be fixed. As I said, we suspect it was an issue with the radio and not with VOXL. Why it would be perfectly stable with one drone for hours and then have an issue with a different identical drone is beyond me.

You guys do great work, keep it up!

Hello, we recently purchased a VOXL to HDMI adapter to stream video from an infrared camera through VOXL to QGC.

In the documentation it says that we need a system image of 2.5 or higher and 'The voxl-v412 package', both of which are on request only. I saw system images higher than 2.5 in the downloads area, not sure if these are good enough or we need a specific system image here.

Where can we find a copy of the voxl-v412 package, or is there someone who can send us a copy directly?

Thanks!

@Chad-Sweet Yes, it usually is a good starting point. I do want to mention it took us 3 or 4 separate resets of all related radio settings before this particular glitch went away.

@tom Thanks for your thoughts Tom, it was new to us as well! We seem to have managed to fix the problem but we're not entirely sure how / why. Our best guess is that was a software glitch with the Microhard radios themselves.

I'm documenting what we found here in case anyone else runs into a similar issue in the future.

We were able to eventually duplicate the same problem on another UAV that had previously been perfectly stable, thus eliminating the VOXL as a potential cause with two separate units showing the issue.

We were testing a variety of settings today (e.g. channel, bandwidth, power of transmitter, which module is master vs slave) just to try and identify if anything made a difference. Eventually after re-setting the settings back to the microhard defaults (which we had done several times already), the problem mysteriously stopped. We've since kept a stable link open on two UAVs for the last ~6 hours without issue, so we suspect that there was some software issue that eventually cleared when we modified the settings. The last change we made was testing which module was master/slave, and after swapping them and then swapping them back the issue went away.

Really puzzling issue, we're just glad it seems to be fixed. As I said, we suspect it was an issue with the radio and not with VOXL. Why it would be perfectly stable with one drone for hours and then have an issue with a different identical drone is beyond me.

You guys do great work, keep it up!

@tom Yup, you're fully understanding the situation. Just the one drone is having this problem (with microhard modem+carrier board), all others seem perfectly normal.

Tried replacing the modem + carrier board on the affected drone with a spare and it has the same behavior.

Would the next step be to try re-installing VOXL Suite and redoing the microhard setup?

We have several UAVs all operating with 1.8GHz Microhard modems and VOXL Flight for communication with the GCS (SkyNav or laptop).

We've found the connection will drop for ~0.5-1 second every 30 seconds like clockwork when the problem begins, but when it starts and stops appears to be random (e.g. sometimes it happens immediately and other times can have a stable connection for >1hr without issue).

Without touching the hardware (and testing in multiple locations to rule out an environmental problem), we've observed it starting on startup, after 6 minutes, 16 minutes, and 31 minutes of connection (to provide some examples). Then, every 30 seconds the connection will momentarily drop before fixing itself, with a visible interruption in UAV telemetry. Typically a reboot will not fix the issue.

It only happens on a single UAV that we believe to be configured identically to others. We've also ruled out a temperature problem with the radio and every hardware factor we can think of.

Our best idea is to re-flash the firmware as it appears to be a software bug, but wanted to check on the forums here in case anyone has run into a similar problem or has an idea for what it could be.

Thanks!

@modaltb Interesting, that's good to know they should be identical (what I assumed), that's why I was puzzled when it didn't seem to work.

On VOXL Flight we're using port J13 and it's always worked perfectly without issue the first time we're wired up a new unit.

I have not tried starting via the command line, but that's a good idea to try.

My best guess is a loose connection in the wiring somewhere or a pin not making good contact on the board. If it should be working the most obviously problem is user error on our part or something not making contact properly.

We ended up sending them one of our VOXL Flight units where we knew it worked perfectly each time instead of using the Flight Core because they were in a rush to get things working.

Thanks for the suggestions!

Hello, I'm having trouble getting LiDAR to show up with the Flight Core via the J13 I2C connection and wanted to check it is supported in the hardware.

I'm helping a friend who has a Flight Core, I've tried connecting a LiDAR Lite v3 via the I2C interface (J13) and changing the appropriate setting (SENS_EN_LL40LS) but it still won't show up. I also tried troubleshooting via the PWM input option with another unit but I'm not sure if Flight Core supports a PWM input there as it did not show up with that method either.

I've verified the LiDAR should be receiving 5V via pin 1 on plug J10, and tested it with multiple physical LiDAR units, so we can rule out voltage and a bad LiDAR unit. I've primarily been using VOXL Flight for several projects and the LiDAR has always worked perfectly with no issues so this is proving tricky to troubleshoot.

Does the Flight Core support a LiDAR input via I2C connection on J13? Any other ideas for troubleshooting?

Thanks in advance!