Anan 7000 DLE MKII Sudden Connection Issues

[VK2FR]

Hi all,

2wks and counting I have been unable to use my Anan 7000 DLE MKII

I’ve recently run into an issue where I can no longer connect to my ANAN-7000DLE MKII.

For several months the setup worked flawlessly:

Starlink providing internet

Starlink Ethernet → unmanaged 5-port switch

One Ethernet from the switch to the PC NIC

One Ethernet from the switch directly to the ANAN

The ANAN was always discovered instantly by Thetis and operated normally.

At some point (no hardware changes that I’m aware of), the ANAN stopped being discoverable and I can no longer connect to it.

What I’ve tried since:

• Removing the switch and connecting the ANAN directly to the PC NIC

• Resetting Windows network settings

• Assigning static IPs on both the PC and ANAN (same subnet)

• Disabling Wi-Fi and firewall for testing

• Trying multiple Ethernet cables

Current behaviour:

• PC NIC works normally (can ping its own IP)

• Ethernet link lights are present on both the PC and ANAN

• ping to the ANAN IP fails (destination host unreachable)

Thetis does not discover the radio

When placed into bootloader mode, the ANAN shows green LEDs and the Ethernet link comes up, suggesting the Ethernet hardware itself is OK

At this point it feels like either:

A firmware / network stack issue on the ANAN, or

Something subtle I’m missing in the network configuration

Questions:

Has anyone seen this behaviour before?

I have flashed loads of different firmware versions without fail with HPSDR bootloader, the radio will simply not work.

I've tried static IP's and DHCP and nothing is working.

Hardware fault?

Any advice would be greatly appreciated.

[VK2FR]

After loading a version of protocol 1
https://youtu.be/NOw6J_4GdXg?feature=shared

[w-u-2-o]

Jordan--this sort of non-systematic, "shotgun" approach is clear not working

If we assume it is not some sort of hardware failure in the 7000, I recommend proceeding as follows:

1. Confirm and label the Bootloader switch positions, and confirm that the switch is not broken. You say Bootloader is working fine, discovering the board, erasing and loading no problem, correct? If so, then that is how you test these things. If the Bootloader switch is working properly, then Bootloader should only do these thing with the switch in one position. If it does it in both positions then the switch is broken and the ANAN is stuck in Bootloader mode.

2. Make certain you power cycle the ANAN after and every time you move the Bootloader switch. Put it in Bootloader position--power cycle. Put it in normal position--power cycle.

3. Test the Ethernet cables. It is possible to have a cable that appears to be working but has a single broken pin. This will cause the link to go to 100BASE-T (100Mb/s) mode, or half duplex GigE mode. You want full duplex GigE and that requires all pins and wires on the cable to be good. To test all the cables, connect them between your switch and the PC one at a time. Make sure the Windows network control panel reports a full-duplex, GigE connection, and that the color of the LEDs on the switch report the same thing. Bootloader firmware runs at 100BASE-T only, so it can be successful with a partially broken cable. P2 firmware runs at GigE only. There is no automatic speed or duplex negotiation in any openHPSDR firmware.

4. If all the cables test good, visually inspect the Ethernet connectors on the 7000 and the switch and make certain they are in good repair.

5. Put the original P2 firmware back into place. What version were you using, do you remember? It's super-important to have the right version because of the three different FPGAs that have been used across the family of 7000's. See this topic: viewtopic.php?t=4462 If you are unsure of what P2 firmware to use then you can either a) try all three versions or, b) peek inside and identify the FPGA part number.

6. Change the IP addressing on both the PC and ANAN back to DHCP (for now) in order to avoid any sort of IP address conflicts or other misconfigurations on your network. In the ANAN that means use Bootloader to set the IP to 0.0.0.0.

7. Assuming all of the above has been done correctly and no problems are found, when you power up the 7000 with the correct P2 firmware and a good Ethernet cable and connectors, check the LED indications on the switch to see if it has obtained a GigE link with the 7000.

If you can report back on the above steps and tests it will help to either fix, or at least narrow down, the problem.

[VK2FR]

Jordan--this sort of non-systematic, "shotgun" approach is clear not working

If we assume it is not some sort of hardware failure in the 7000, I recommend proceeding as follows:

1. Confirm and label the Bootloader switch positions, and confirm that the switch is not broken. You say Bootloader is working fine, discovering the board, erasing and loading no problem, correct? If so, then that is how you test these things. If the Bootloader switch is working properly, then Bootloader should only do these thing with the switch in one position. If it does it in both positions then the switch is broken and the ANAN is stuck in Bootloader mode.

2. Make certain you power cycle the ANAN after and every time you move the Bootloader switch. Put it in Bootloader position--power cycle. Put it in normal position--power cycle.

3. Test the Ethernet cables. It is possible to have a cable that appears to be working but has a single broken pin. This will cause the link to go to 100BASE-T (100Mb/s) mode, or half duplex GigE mode. You want full duplex GigE and that requires all pins and wires on the cable to be good. To test all the cables, connect them between your switch and the PC one at a time. Make sure the Windows network control panel reports a full-duplex, GigE connection, and that the color of the LEDs on the switch report the same thing. Bootloader firmware runs at 100BASE-T only, so it can be successful with a partially broken cable. P2 firmware runs at GigE only. There is no automatic speed or duplex negotiation in any openHPSDR firmware.

4. If all the cables test good, visually inspect the Ethernet connectors on the 7000 and the switch and make certain they are in good repair.

5. Put the original P2 firmware back into place. What version were you using, do you remember? It's super-important to have the right version because of the three different FPGAs that have been used across the family of 7000's. See this topic: viewtopic.php?t=4462 If you are unsure of what P2 firmware to use then you can either a) try all three versions or, b) peek inside and identify the FPGA part number.

6. Change the IP addressing on both the PC and ANAN back to DHCP (for now) in order to avoid any sort of IP address conflicts or other misconfigurations on your network. In the ANAN that means use Bootloader to set the IP to 0.0.0.0.

7. Assuming all of the above has been done correctly and no problems are found, when you power up the 7000 with the correct P2 firmware and a good Ethernet cable and connectors, check the LED indications on the switch to see if it has obtained a GigE link with the 7000.

If you can report back on the above steps and tests it will help to either fix, or at least narrow down, the problem.

Hi Scott,

Thanks for you're detailed response to my issues, I endeavour to follow your instructions above and record my findings and report back on my next free days off work before the end of the week.

Many thanks!