Signs a radio has failed

Hello There!

I am working with 4 60ghz cnWave devices. 1 x V5000 DN connecting to 1 x V1000 CN and 2 x V2000s CNs.

One of the links has inexplicably gone down (V2000). I can connect to it no problem, but the link is still down. The alignment of the radios has not changed. Is there something I should look for when troubleshooting to know if the radio needs to be replaced?

I have already tried troubleshooting other things. I don’t mind some advice on the troubleshooting steps to rule other things out, but at this point I’m fairly certain it is a physical issue, and I’m just trying to make the process quicker in the future.

Shane,

I can give you a few hints.

  1. Make sure the v2000 is connected to the correct sector of the v5000. When behind the v5000, that is on the pipe mount side) sector 1 is on the right, sector 2 on the left.
  2. If the range really short to the v2000? If it is, make sure the <25m box is checked. If the link is longer, make sure the box is unchecked. When I start units up on the bench, I usually have to enable <25m option, since my office is not that big.
  3. Delete the link and rebuild it in the E2E controller, or in cnMaestro.
  4. Beamforming normally looks after alignment. As long as the v2000 is pointed at the v5000, alignment is good.
  5. Make sure TX power is set to max on the v5000 as well as the v2000. The link will adjust automatically.
  6. Make sure the polarity is opposite for the v5000 and the v2000. If the v5000 is even, the v2000 should be odd.
  7. In the configuration of the v2000 in either the E2E controller, or in cnMaestro, manually set a golay code that is not being used by adjacent CN’s on the v2000.
  8. Try using Ch 4 on the V5000 sector that the v2000 should connect to. CH4 has the lowest oxygen absorption.
  9. Reset v2000 to factory default. The unit t will get its configuration from the E2E controller.

There may be a few more checks to make, but I think that is the bulk of tests to try. .

2 Likes

Thanks for the reply Dave.

I had tried most the steps you listed this week with no success. The V5000 has 2 x V2000s (one of which is down) in sector 1. Both radios are deployed in the field at ranges of ~200m.

  1. Both radios were configured to the correct sector.
  2. Range is too far for short range optimization.
  3. I deleted the link from the V5000 (and the node), then attempted to re-add.
  4. V2000 is pointed directly at the V5000.
  5. Transmit power is set to max
  6. Polarity on V5000 sector 1 is set to even, both V2000s are set to odd.
  7. Before I completed a factory reset, I confirmed the golay codes on both V2000s matched sector 1 of the V5000.
  8. After doing the reset, I changed the channel to 4 from the V5000 (on sector 1).
  9. I completed the factory reset.

It is possible that I can go to site to ensure the golay codes match and the channel is set to 4 from the downed V2000 after the reset was completed, but I am not optimistic.

I was also able to inspect the physical cabling and replace the power supply of the unit. The cabling looked fine although I wasn’t able to do a cable test.

So I am left with assuming the radio needs to be replaced unless there is something that I missed. I can login to the GUI without any issues. Are there any diagnostics I can do to see if the V2000 itself is working properly?

There are a few more things.

  1. What is the azimuth from the v5000 to each of the v2000’s? If they are within 20 degrees of each other, then you may need to re-orient the v5000 so that each one is in a different sector. I’ve seen situations where the first or the second link will come up, but not both.
  2. What are the RSSI values for both DL and UL from the unit that is working? The noise floor is approx. -72 dBm on a 2GHz channel width. Ideally, your RSSI should be -60 dBm to -50 dBm. If the RSSI is higher than -50 dBm, then try dropping the TX power on the v5000 by 3 dB.

Make sure that the system is trying to connect…watch the ignition attempts increment when the unit is not connected. If there are no ignition attempts, then that could mean the v2000 is not receiving the v5000 well enough to synchronize.

The columns I’m showing from cnMaestro may not be default in your cnMaestro. You can use the column chooser to select or de-select columns to view the info you need to see.

Have you done a plot of your system in Link Planner? Sometimes that helps to visualize what is going on.

2 Likes

Hi Dave,

The 2 x V2000 units are within 20 degrees of each other, but they had both been active for about 9 months before the one unit went offline.

The RSSI values on the working V2000 hover at -62, which is right at the mean of the expected value from Link Planner.

I hadn’t considered dropping the power on the V5000. It seemed the previous settings were working quite well. I can try this to see if it helps. So far I lowered it twice with no significant changes.

The ignition attempts for the down V2000 are still counting up. Still just not sure what could be happening. The install of these devices went very smoothly and the link was made instantly.

Sounds like you’ve done everything. Might be RMA time. I suspect that the transmitter of the V2000 is not running properly.

Hello Shane,

Sorry to hear you’re having troubles, given you have factory reset the V2000 I assume you have local access to this unit and can login to it remotely?

I’ve not heard of the V2000 fail in the field, yet, so keen to understand what’s going on.

If you have access can you capture the diags off the unit, if you login locally it’s in the tools section. If you could capture that and open a ticket we’ll jump in and look at this.

Hi Antony,

I have already opened a support ticket, so I am well on my way in that regard.

The site is not nearby, so it is a bit of a process to login to the down V2000 locally. I don’t have access remotely since the radio is down.

I am just in the process of planning a day to head to site to download the diags from the V2000.

Thanks Shane, I’ll keep a look out and see what we can do.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.