@Jeremy-Frederick

I would look at this being a radio thing. I would try

get some distance between the radios. if they are too close together there might be too much noise in the system monitor the radio health when you see the cut out (should be able to see that from the menu of microhard 192.168.168.2) see if this happens if you connect over straight ethernet (use this cable: https://www.amazon.com/USB-Ethernet-Adapter-Gigabit-Switch/dp/B09GRL3VCN/ref=sr_1_2_sspa?crid=1ZBIC6DOI8DB5&keywords=ethernet+to+usb+adapter&qid=1699997723&sprefix=ehternet+to+usb%2Caps%2C124&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1). If you dont see the issue, i would look closer into how the radios are configured antennas: make sure you have the right radio antennas suggested by microhard

@tom
When running our algorithm or doing voxl-streaming while connected to a microhard, the drone is experiencing a random reboot. This issue is difficult to see when connected via wifi (station mode). When the drone reboots, it is disconnected from qgc and reconnected to qgc about 1 minute later. I think they had the same problem, can you tell me how they solved it?

@Jeremy-Frederick Can you try to lower the bitrate or resolution to see if it's a bandwidth issue?

I understand that, in theory, the rendering software (VLC or QGC) shouldn't matter for your issue. But, it typically helps to see if there is a config that will work reliably and then push it from there.

@Vinny ,

Thanks for the speedy response and for the recommendations. I will discuss the options with my team. That dongle sounds like a good alternative for this use case.

Jacob

@Nick-Stroumtsos

Moderator said in Power supply brownout w/ the Microhard Carrier USB Dongle
@Nick-Stroumtsos Our carrier board design is a few years old, there's a good chance it won't meet this newer spec.

That is correct, it is not going to be supported on this design.
We designed for the 30dBm max power modes from several years ago as shown here:
f1f632e6-b6ae-4764-9042-22ea4426fe05-image.png

We have a power consumption table in our tech docs that helps a user determine the limits for various modes:
https://docs.modalai.com/microhard-add-on-datasheet/#power-consumption
but nothing above 30dBm. We'd need new hardware for that.
Sorry, but at least hopefully that explains the behaviors you are seeing.

@swickliff please submit a request at https://modalai.com/rma .

@Eric-Katzfey okay - too bad. Is it still on the to-do list or no longer in the plans?

Hi @Serhii
I'm surprised anyone knows about that design. In any case, it is not in active production, and to the best of my knowledge, not supported nor do we have any plans to support it.

M0048 is our primary focus for MH radios.

@Vinny Yep, that's what I figured. Thanks for the info!

@v_v_ramarao I don't think we can answer this, it would likely be worth reaching out to the Microhard support team

@Jetson-Nano Here's some example code: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/autopilot_monitor.c?ref_type=heads#L514

@Gus-Meyer It looks to be some kind of configuration issue rather than a hardware issue. If I turn on the board while pressing the S2 switch, the USB connection is recognized. But I'm assuming this puts it in some particular mode where the device isn't used normally, because I do not receive an IP on the ethernet device under this circumstance.

@Alex-Kushleyev Thank you very much!

@jmltt Each microhard modem hosts a web server that can be accessed via it's IP address. You can see what data is available and can likely script a query for signal strength. (They may have an API but it's not something we've investigated)