I purchased this drone only a few days ago directly from HDZero.
I updated ELRS and VTX firmware to the latest versions available and flew the drone for the first time this week in the garden.
Everything seemed to be working fine and after a few minutes of slow flight in the backyard I switched off and waited for the weekend to do a real flight test.

Suddenly today the VTX would not connect to the HDZero Goggles despite several scans. So I checked the led lights on the VTX and found that I had only one red light on, but no blue led.

Troubleshooting already done:

• power cycled the drone sever times
  
• power cycled the HDZero Goggles several times
  
• changed the power setting of the VTX from 0W to 25mW, to 200mW and back using the Radio (I setup some simple Betaflight instructions to do that)
  
• checked both ends of MIPI connector (on VTX and camera) and both connections looked ok. I did not try to unplug the MIPI connector though.
  
• flashed again the VTX firmware with the same version (most updated one}
  
• The HDZero Goggles are working OK with other 2 drones (Mobula6 Eco, Firefly Nano 2s HDZero), so I assume the problem is with the VTX
  
• Absolutely no crashes during the short flight in the backyard
  

As you can imagine I am very frustrated as I spent the whole Sunday trying to fix the VTX but did not succeed.

I already sent an email to HDZero, but in the meantime any suggestion is welcome guys...

Thanks
Dom

Update: I also tried unplugging and re seating both ends of the mipi connector, nothing changed, still no blue led.
AAARRGGHHH!

It doesn't seem this is a topic of interest, however I'd like to update this thread for anyone who will find the info useful in the future.

Further troubleshooting done:
1) remove the existing camera and used an HDZero camera from another drone --> no change
2) connect the existing camera to another HDZero VTX --> the camera works just fine
[edit] 3) flashed a beta firmware sent by Divimath on the VTX to check if the transmission section of the VTX works fine, and it did. The beta firmware sends a test image regardless of any cam attached or not.
So apparently the problem is with the VTX in the Crux35. Divimath will send me a new one, hopefully this will solve the issue.

Sorry for no responses yet, thanks for keeping us informed. I wanted to check if you have tried swapping your goggles from wide band to narrow band or visa versa. That tripped me up one time, but because of the one red light on the vtx, that seems unlikely. I don't think you mentioned your antenna, could be worth swapping for a new one just in case.
Divimath has been good to me for replacing damaged VTXs. But be warned that shipping as been slooooowwww from them.

Is it possible you flashed the newest FW to the drone VTX but not to the goggle? Could be worth flashing the goggle to the same FW as the drone.

Lastly, I could be totally mistaken, but I'm not sure you can change the VTX power from your remote without using the drones OSD stick commands. I'm pretty sure the betaflight VTX power does not change the HDZero VTX power. Someone please correct me if I'm wrong on that. I would love to change HDZero VTX power on the fly with a switch.

Best of luck, hope you get airborne again soon!

(05-Jun-2024, 05:59 PM)FPVme Wrote: Sorry for no responses yet, thanks for keeping us informed.  I wanted to check if you have tried swapping your goggles from wide band to narrow band or visa versa.  That tripped me up one time, but because of the one red light on the vtx, that seems unlikely.  I don't think you mentioned your antenna, could be worth swapping for a new one just in case.
Divimath has been good to me for replacing damaged VTXs.  But be warned that shipping as been slooooowwww from them.

Is it possible you flashed the newest FW to the drone VTX but not to the goggle?  Could be worth flashing the goggle to the same FW as the drone.  

Lastly, I could be totally mistaken, but I'm not sure you can change the VTX power from your remote without using the drones OSD stick commands.  I'm pretty sure the betaflight VTX power does not change the HDZero VTX power.  Someone please correct me if I'm wrong on that.  I would love to change HDZero VTX power on the fly with a switch.

Best of luck, hope you get airborne again soon!

Thanks for your kind reply, I feel less lonely now

I'm not sure what you mean by swapping the goggles from wide to narrow band, can you explain it to me? Anyhow, as I have no signal from the VTX in the goggles it is impossible to do any changes in the VTX using stick commands. At least not so easy.

The transmission chain of the VTX works just fine. Divimath sent me a special firmware for the VTX which sends a special image to the goggles regardless of any communication problems with the camera. Flasging this beta firmware I could get a connection with the goggles where I could see the special image (not the actual cam feed). That means that the TX section of the VTX works fine, including the antenna.

VTX and goggles firmware updated to the latest release.

Finally, "yes you can" change the VTX power with a radio switch using a simple set of betaflight CLI instructions. I assigned this to a specific AUX channel and to a 3 position switch on my radio. So I can switch the camera off, select 25mw or 200mw. It's pretty cool.
Check this video, it will help you: LINK

In your goggles, go to: Source ->HDZero BW-> switch from narrow to wide or wide to narrow

(05-Jun-2024, 08:23 PM)FPVme Wrote: In your goggles, go to: Source ->HDZero BW-> switch from narrow to wide or wide to narrow

Thanks, I just tried but nothing changed.
I can't think of anything else.

Seems like it probably is a faulty vtx. Sorry you lost time on it and I hope divimath gets the new one to you pronto. Did they make you send in the broken one?

(06-Jun-2024, 06:51 PM)FPVme Wrote: Seems like it probably is a faulty vtx.  Sorry you lost time on it and I hope divimath gets the new one to you pronto.  Did they make you send in the broken one?

No, but they asked me to take a video of all the troubleshooting phases they asked me to perform.