pMDDL2350 w/VOXL2 Carrier Board

Mastermind

@tom Both modems are connected to each other. I am still getting random reboots. I have turned almost all the services off expect the camera server and streaming service and voxl-modem. I can ping both devices, but I can only see the webpage for the MH on the host computer. When I try to pull up the webpage from the VOXL nothing responds. IF I enable voxl-portal then I can get to that webpage... which means that the IP for USB0 192.168.12.230 (which is the radio IP) is being directed to the VOXL and not the radio itself.

I just got these radios and carrier boards this week, so I am hoping I am using the correct boards. In the latest carrier board version only USB0 is populated and not ETH0 is that correct? The VOXL ifconfig is the following:

voxl2:/$ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 224  bytes 14560 (14.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 224  bytes 14560 (14.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.12.230  netmask 255.255.255.0  broadcast 192.168.12.255
        inet6 fe80::b059:aff:fe48:4e4a  prefixlen 64  scopeid 0x20<link>
        ether b2:59:0a:48:4e:4a  txqueuelen 1000  (Ethernet)
        RX packets 88  bytes 17916 (17.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 11  bytes 1350 (1.3 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I am not even sure why I am getting random reboots... but I can try to solve that problem later. For now, I want to understand why USB0 is only showing the voxl and not the MH radio? (but the radios are up and I can pass data between both systems).

Mastermind

@tom Just for this post to be complete here is my hardware:
and

tom

@Mastermind It is normal for there to only be usb0, that is not an issue at all. You're never going to see the Microhard modems IP under ifconfig because ifconfig will only show you VOXL's IPs on each network it is connected to.

I'm a little confused on what the issue is as it seems like you have the full network connection from VOXL to your PC going

Mastermind

@tom At the moment the main issue:

VOXL2 reboots either on sending video to the remote side OR randomly. Checked the overheat issue and the radio is not hot at all (we also have a fan blowing on it)
We cannot get to the MH webpage on the VOXL2, the HTTP site does not answer at all (VOXL-PORTAL will answer if started). SSH to that address results in the VOXL2 answering instead but not the normal VOXL2 response (I think if I run BASH it will be the normal SSH)

Those are the two main issues. The link is up, I can see this from the Host PC Base side. I cannot configure the radio or check its status on the VOXL2.

Vinny

Hi @Mastermind
I will try to help out a little on the HW side of things.
I am doing so because of the messages you posted with
"PMIC@SID0 Power-on reason: Triggered from SMPL (Sudden Momentary Power Loss) and 'cold' boot

That is pretty severe of a failure... under no device spec (datasheet) numbers does the microhard claim to pull more than our power module can deliver. Here is a snippet from MH docs that covers all the 2x50 modules:

Those numbers will not stress our system at all. We have 3x margin on that from a design standpoint.
So, I am inclined to think you may have a bad 2350 module, or something else is plugged in incorrectly.
To get an "SMPL" event at the main board indicates much greater than 5A total draw on 5V from the MH modem which would indicate a >3x of the spec. We never see that failure/note.
Does the RGB LED DS1 on Voxl2 ever switch from GREEN to RED during this issue? https://docs.modalai.com/voxl2-leds/#summary
If it stays GREEN, then there is no issue at all with power on Voxl2.

Are you using our power module to power Voxl2 or are you using a custom power module?

Mastermind

@Vinny @tom

Thanks. I am getting some other people from my team to post pictures of our power setup and how everything is connected so you can see. At first the reboots only happened when sending video over the link. I also had the radios set to 20dbm, but I have since changed that to 9dbm. At one point the VOXL2 was in a constant reboot loop. We moved it onto a much better power supply but we are still having an occasional reboot with the same loss of power problem. We also cannot get to the web server on the radio onboard voxl2. The IP for the USB0 responds only to the voxl and does not present the webserver as expected. I've been trying to understand why, and haven't really found a reason.

rjpking92

@Mastermind I also cannot get to the MH webpage on the VOXL2. Did you ever figure out a way to do so?

jmltt

In order to access the webserver for the radio you intend to install onboard the voxl2 you should first access the webserver when it's installed on the host pc carrier board and change the firewall settings to enable remote access. The ip address that's set as the static ip in LAN settings is the actual radio ip address. You enter that address in your browser to access the webserver, not the ip address you assigned when running voxl-configure-modem.

I recommend creating a free account on the microhard support website and downloading the product manual here:

https://support.microhardcorp.com/portal/en/kb/articles/pmddl2450-pmddl2350-pmddl2550-user-manual

It's got a pretty good walkthrough on setting up a master/slave radio configuration right up front.

Here's a pic of the general firewall settings as I have them configured. When I first tried to set up the radios I did so on the host pc carrier but when I deployed them to the voxl2 I couldn't access the webserver either. I realized the remote access is disabled by default, you have to check that middle box.

1c115717-3398-415f-961b-dc184c2f4ba2-Screenshot from 2023-07-31 09-37-33.png

Hope this helps.file:///home/joe/Pictures/Screenshot%20from%202023-07-31%2009-37-33.png

Mastermind

@josephmlullo said in pMDDL2350 w/VOXL2 Carrier Board:

In order to access the webserver for the radio you intend to install onboard the voxl2 you should first access the webserver when it's installed on the host pc carrier board and change the firewall settings to enable remote access. The ip address that's set as the static ip in LAN settings is the actual radio ip address. You enter that address in your browser to access the webserver, not the ip address you assigned when running voxl-configure-modem.

I recommend creating a free account on the microhard support website and downloading the product manual here:

https://support.microhardcorp.com/portal/en/kb/articles/pmddl2450-pmddl2350-pmddl2550-user-manual

It's got a pretty good walkthrough on setting up a master/slave radio configuration right up front.

Here's a pic of the general firewall settings as I have them configured. When I first tried to set up the radios I did so on the host pc carrier but when I deployed them to the voxl2 I couldn't access the webserver either. I realized the remote access is disabled by default, you have to check that middle box.

Hope this helps.file:///home/joe/Pictures/Screenshot%20from%202023-07-31%2009-37-33.png

Thanks Joe!

I can confirm that this is indeed the case. I can also confirm that if you have SSH turned ON for the radio, you cannot SSH to the VOXL, the radio will answer instead.

Inhan Kang

@Mastermind
"I then started voxl-streamer and got video! Happy days! Except... immediate reboot."
How did you solve that issue?? I got same issue.

tom

@Inhan-Kang What issue are you facing? It might be better if you open your own thread

Inhan Kang

@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?