Issue in Microhard paring with Slave unit

tom

@manzur If you followed all of the other configuration steps correctly there are a couple things to try.

The first thing I would try is to increase the physical distance between the two modules, if you have both on a bench then there is often RF saturation if they are too close to each other. The other thing to try is to lower the "Tx Power" setting to it's lowest setting if you are indeed doing bench testing.

manzur

@tom Thanks for reply. I followed all the configuration steps and I have also tested by keeping the Microhard further, but the connection does not seems to work. I have also tried to use lowest TX power but same result. The only possible solution I see is to access the VOXL microhard unit and check all the configuration to match with slave unit, but I do not know how to access the Microhard using USB port or from the VOXL ssh terminal. Can you suggest ?

tom

@manzur The only way to do that without having the two connected would be to switch the Microhard modems, but I wouldn't recommend doing that if you don't have the correct tools.

When you are on VOXL what do you see when you type ifconfig?

Are you able to ping 192.168.168.1 or ping 192.168.168.2 from VOXL?

manzur

@tom I have already checked the ifconfig and it shows the the VOXL is connected with microhard

and also I have tested master mode in microhard by holding the button for 10 sec. The IP ping test as follows:

I have also tested the VOXL microhard unit by putting it in slave mode by pressing the button for 5 sec and it also shows in the ping result as follows:

The problem is that, it does not connect with another microhard unit whether we keep that in master or slave. There must be some configuration issue that we must be missing and or it not matching with another unit. Can you please tell me what is the default Network ID: pDDL. For us the slave unit has pDDL. And the channel frequency is set as Channel-Frequency: 75_ 2476 MHz .

tom

@manzur pDDL is the default Network ID. Which Microhard modules are you using? 1800 MHz? 2400 MHz? It looks as though the VOXL side is fully functional.

Are you able to take the standalone side Mircohard module and plug it into a PC in order to see if it correctly connects to the PC? That way you would be able to try pinging it to determine whether the IP address is being set correctly.

manzur

@tom We are using microhard from Airborne innovations 2400 MHz unit on the other side. And I can access the slave standalone unit perfectly with PC.

tom

@manzur From what I can see, it looks as though the Microhard carrier boards are doing their jobs as the correct network interfaces are appearing.

Have you ever been able to establish a connection between these two Microhard modules in the past? It's possible that one or both are faulty.

And just to confirm, on the standalone side you are using antennas as well correct?

manzur

@tom I have not been able to establish connection between these two Microhard modules. But independently the slave standalone unit has been used for another system as well and I know It is working.
Standalone unit

tom

@manzur I see, so the standalone isn't from us. Did you acquire the Microhard module that is in the add-on board from us? And is it also a pDDL2450?

manzur

@tom Microhard module that is in the add-on board from Modal AI as an add on to m500 unit and same is pDDL2450

tom

@manzur When both modules are powered on and you wait a couple minutes with no connection, what behavior are you seeing from the LED's on the VOXL add-on board?

manzur

@tom This is the image showing LED behaviour.

From the bottom

Lnk/ACT : OFF
Lnk/100 : ON
Lnk : ON
CPU : ON
RSSI_1, RSSI_2, RSSI_3 : blinking one after another
RX : ON (continuous)
TX : Blinking (low)

Note: One thing I noticed now is that the Standalone microhard unit we have is 128 bit AES encryption model, where the Modal AI add-on module is showing 256 bit AES encryption model. Do you think this is the reason they are not communicating? All the microhard unit we have here is 128 bit AES model. If that is the case how can we access the Add-on Microhard unit?

tom

@manzur Interesting, that LED behavior indicates that the two modules are in fact connected. If the modules are searching for each other then the LEDs will cycle.

As for the encryption question, I will look into it.

manzur

@tom Thanks for your reply. Let me know if you can come up with some solution. In the mean time I am trying to get a development board for the Microhard unit to plugin and see if I can log in to the config-webpage.

tom

@manzur Okay great, there is an option in the web interface under Wireless -> RF -> Encryption Type which should allow you to change the module's encryption type to 128-bit in order to match the other module.

manzur

@tom I was able to access the web interface by plugging the Add-on Microhard unit into a development board. And indeed I found the Network ID is mismatched and was set to as pMDDL instead of pDDL. Also the frequency was set to 76-2477 which is okay since I tried with multiple band with the slave unit as well. See the default configuration of the Add-on unit before changing

tom

@manzur Interesting, thank you for the information! Perhaps I was wrong about the default Network ID, I will take a note of that.