ANAN-7000DLE MkII Ethernet comms failure

Can't talk to your radio? This is the place to ask!
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Sat Dec 14, 2019 6:48 am

Hi

My ANAN-7000DLE MkII S/N 7000DLEMKII-011 failed recently, while receiving a
broadcast station. The failure started with a short crackling noise and then
reception stopped. After this, attempts at restarting mostly failed since the
Transceiver would not respond to discovery. There were just a couple of
successful discoveries but reception would not start. Then the Transceiver
became completely unresponsive to discovery.

To eliminate the possibility of my desktop computer failure, I tried using my
laptop with a clean install of the O/S (Linux) but again I had little success.
I also tried a new Ethernet cable with no luck. I also tried using my desktop
again, with a clean reinstall of the O/S but again no results.

I then tried to reload the firmware using HPSDRBootloader V2 and Protocol 2
.rbf file and somewhat surprisingly this went well. The firmware was reloaded
successfully and the Bootloader could also read and write a static IP address.
So it appears that with the bootloader switch ON the rig responds correctly. I
then switched OFF the bootloader switch and power cycled, before running the
HPSDRProgrammer V2. But the Programmer failed to discover the board, so
whatever the failure is, it manifests in the normal operating conditions.

Another thing I have noticed is that the Ethernet connection takes several
seconds longer to establish in normal operating mode (bootloader switched OFF)
compared to bootloader mode. And pinging the static IP address of the
Transceiver also fails (ping reports Destination Host Unreachable).

Are there any indicators (LED's) in the 7000DLE that might indicate a fault
condition? They might help me to recover the transceiver, if this is not a
permanent hardware failure.

I have not received a response yet from Apache-labs support so I would be
grateful for any assistance here.

My thanks in advance.
User avatar
w-u-2-o
Posts: 2001
Joined: Fri Mar 10, 2017 1:47 pm

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby w-u-2-o » Sat Dec 14, 2019 4:05 pm

Is this the programming app you are trying to use:

https://github.com/TAPR/OpenHPSDR-Protocol2-Programmers ?

What client software are you running on a Linux OS to use with the hardware?

There are no LED indications that are very helpful other than the Ethernet link and traffic indicators.
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Sat Dec 14, 2019 6:09 pm

w-u-2-o wrote:Is this the programming app you are trying to use:
https://github.com/TAPR/OpenHPSDR-Protocol2-Programmers ?

No, these are, if I understand correctly, in "Go" source code. I am using the compiled binaries that
I downloaded a few months ago to set up the static IP address: HPSDRProgrammer_v2_nopcap_2.0.4.10.tar.gz
and HPSDRBootloader-debian-64.tar.gz. These worked well for me when the rig arrived.

w-u-2-o wrote:What client software are you running on a Linux OS to use with the hardware?
There are no LED indications that are very helpful other than the Ethernet link and traffic indicators.

I am using a client that I wrote myself, compliant with Protocol 2. This client is not complete, it only supports
receiving (AM, SSB, CW, FM) and FFT spectrum displays, of the DDC stream and Wideband stream. This client
worked very well for the last few months, even during development.

I was about to start an effort to develop support for transmitting, when this failure occurred - pity! :-(

I can see three red LED's through the rear-right side ventilation grill, one of them flashing. Have no info what
they mean though. Since the fault was intermittent for a short while, it may be a hardware failure, although
the bootloader seems to work fine.
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Sun Dec 15, 2019 5:52 am

w-u-2-o wrote:There are no LED indications that are very helpful other than the Ethernet link and traffic indicators.

Hi

I have some more clues that I believe indicate a partial failure (slow speed) of the KSZ9021RL Ethernet controller.
If I manually set the Ethernet speed to 100Mb (using "ethtool" in Linux) then the "ip link" command reports that
carrier is present. But if I set the speed to 1000Mb (required by Protocol 2) then "ip link" reports no carrier
present.

This would indicate that communication (handshake) with the 7kDLE fails at 1000Mb but works at 100Mb. But
there may be a discrepancy here, the Bootloader works well in bootloader mode but the Programmer fails in
normal mode.

If someone could confirm that the Bootloader works in the 100Mb mode, then I would be almost certain the
failure is with the Ethernet controller.

My thanks in advance for any tips! :-)

P.S. I wonder if the controller chip is user replaceable? Special tools, no doubt, needed.
User avatar
w-u-2-o
Posts: 2001
Joined: Fri Mar 10, 2017 1:47 pm

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby w-u-2-o » Sun Dec 15, 2019 12:45 pm

neoklis wrote:
w-u-2-o wrote:Is this the programming app you are trying to use:
https://github.com/TAPR/OpenHPSDR-Protocol2-Programmers ?

No, these are, if I understand correctly, in "Go" source code. I am using the compiled binaries that
I downloaded a few months ago to set up the static IP address: HPSDRProgrammer_v2_nopcap_2.0.4.10.tar.gz
and HPSDRBootloader-debian-64.tar.gz. These worked well for me when the rig arrived.
That explains things. You are making a very basic mistake. Read this topic. Once you have put P2 firmware into the hardware you can no longer use HPSDR Programmer. That is why it is failing for you. Thus it is unlikely that anything is wrong with your hardware.

I recommend you use HPSDR Bootloader to reinstall the P2 firmware you wish to use, then revisit your network and PC setup. Use a known good client to confirm operation before going back to your client.
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Sun Dec 15, 2019 2:12 pm

w-u-2-o wrote:I recommend you use HPSDR Bootloader to reinstall the P2 firmware you wish to use, then revisit your network and PC setup. Use a known good client to confirm operation before going back to your client.

Actually I made a mistake, I was trying HPSDRProgrammer_v2_nopcap. If I remember well it did work for me when I did my original set up. The important clues here is that it failed while it was working well, and then it gradually went from occasional response to discovery to total failure. I have already re-installed the firmware twice successfully so will not try that again, only an alternative client.

Thank you for your input.
User avatar
w-u-2-o
Posts: 2001
Joined: Fri Mar 10, 2017 1:47 pm

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby w-u-2-o » Sun Dec 15, 2019 2:37 pm

neoklis wrote:
w-u-2-o wrote:Actually I made a mistake, I was trying HPSDRProgrammer_v2_nopcap. If I remember well it did work for me when I did my original set up.
The only reason that worked is because there was P1 firmware loaded first. Once you loaded P2 firmware that will not work anymore, not until you put P1 firmware back into the unit.
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Sun Dec 15, 2019 5:33 pm

w-u-2-o wrote:The only reason that worked is because there was P1 firmware loaded first. Once you loaded P2 firmware that will not work anymore, not until you put P1 firmware back into the unit.

One more question - how do we use the new Bootloader/Programmer tools you mentioned earlier? Is it a matter of installing a Golang toolchain and compiling the source code?

Thanks.
User avatar
w-u-2-o
Posts: 2001
Joined: Fri Mar 10, 2017 1:47 pm

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby w-u-2-o » Sun Dec 15, 2019 9:07 pm

neoklis wrote:
w-u-2-o wrote:One more question - how do we use the new Bootloader/Programmer tools you mentioned earlier? Is it a matter of installing a Golang toolchain and compiling the source code?
The Bootloader is not new. It has existed since at least the Hermes card and maybe before that.

Why would you need to compile anything?

Did you not read the the link I posted above? If not, please do so.
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Mon Dec 16, 2019 5:54 am

w-u-2-o wrote:Did you not read the the link I posted above? If not, please do so.

Yes, I tried both the web and console versions but both failed to discover. I used Bootloader to upload the "Orion_MkII_Protocol_2_v1.9.rbf" (renamed to Metis_MkII_Protocol_2_v1.9.rbf) successfully, also set the IP address to 192.168.5.3 and verified by reading it. The Ethernet port is also set up to static IP of 192.168.5.2 with auto negotiation. This is the console printout using the command version:

[0726][neoklis@5b4az:/media/store0/temp]> ./HPSDRProgrammer_cmd
2019/12/16 07:26:10 HPSDRProgrammer_cmd version:(0.2.7)
2019/12/16 07:26:10 By Dave KV0S, 2014-11-24, GPL2

2019/12/16 07:26:10 Protocol: >1.7
2019/12/16 07:26:10 Last Updated: 2016-8-13

2019/12/16 07:26:10 For a list of commands use -help

2019/12/16 07:26:10 1 - lo ()
2019/12/16 07:26:10 2 - enp4s0 (00:01:c0:16:f6:17)
2019/12/16 07:26:10 3 - wlp2s0 (f8:16:54:86:7c:25)
[0726][neoklis@5b4az:/media/store0/temp]> ./HPSDRProgrammer_cmd -index 2
2019/12/16 07:26:15 Computer: (00:01:c0:16:f6:17)
2019/12/16 07:26:15 OS: linux (amd64) 4 CPU(s)
2019/12/16 07:26:15 Username: Neoklis (neoklis) /home/neoklis
2019/12/16 07:26:15 IPV4: 192.168.5.2
2019/12/16 07:26:15 IPV6: fe80::201:c0ff:fe16:f617
2019/12/16 07:26:15 Discover: 192.168.5.2:0 -> 255.255.255.255:1024

This is the result from ping:
[0727][neoklis@5b4az:/media/store0/temp]> ping 192.168.5.2
PING 192.168.5.2 (192.168.5.2) 56(84) bytes of data.
64 bytes from 192.168.5.2: icmp_seq=1 ttl=64 time=0.059 ms
64 bytes from 192.168.5.2: icmp_seq=2 ttl=64 time=0.079 ms
64 bytes from 192.168.5.2: icmp_seq=3 ttl=64 time=0.118 ms
64 bytes from 192.168.5.2: icmp_seq=4 ttl=64 time=0.069 ms
^C
--- 192.168.5.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3091ms
rtt min/avg/max/mdev = 0.059/0.081/0.118/0.022 ms
[0728][neoklis@5b4az:/media/store0/temp]> ping 192.168.5.3
PING 192.168.5.3 (192.168.5.3) 56(84) bytes of data.
From 192.168.5.3 icmp_seq=1 Destination Host Unreachable
From 192.168.5.3 icmp_seq=2 Destination Host Unreachable
From 192.168.5.3 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.5.3 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5139ms
pipe 4

Again my thanks for your help.
User avatar
w-u-2-o
Posts: 2001
Joined: Fri Mar 10, 2017 1:47 pm

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby w-u-2-o » Mon Dec 16, 2019 1:12 pm

As I said in my second post above, I recommend you use Bootloader. The web and command line programmer for P2 is not reliable at this time.

Also, you should be trying and most likely using the latest firmware betas available here:

viewtopic.php?f=32&t=3192
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Mon Dec 16, 2019 4:31 pm

w-u-2-o wrote:As I said in my second post above, I recommend you use Bootloader. The web and command line programmer for P2 is not reliable at this time.

Yes, the Bootloader always seems to work successfully, uploading firmware and setting IP address.

w-u-2-o wrote:Also, you should be trying and most likely using the latest firmware betas available here:
viewtopic.php?f=32&t=3192

I have just tried the latest pre4-6282 version but the situation has not changed.

My thanks again.
User avatar
w-u-2-o
Posts: 2001
Joined: Fri Mar 10, 2017 1:47 pm

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby w-u-2-o » Mon Dec 16, 2019 4:54 pm

Have you tried running Thetis?
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Mon Dec 16, 2019 6:31 pm

w-u-2-o wrote:Have you tried running Thetis?

No, but I could try if it runs in Linux, don't have windoze. However some tests I made a little while ago indicate that the Ethernet connection will not go up to 1000Mb speed. I used "ethtool" to set the computer's Ethernet controller to 1000Mb but it would not establish a link with the rig. At 100Mb it established a link quickly. That might explain why the Bootloader works (at 100Mb) but P2 clients don't. As far as I can tell with my limited knowledge, it seems that the Ethernet controller is no longer capable of 1000Mb connections, having lost performance for some reason.
User avatar
w-u-2-o
Posts: 2001
Joined: Fri Mar 10, 2017 1:47 pm

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby w-u-2-o » Mon Dec 16, 2019 6:43 pm

If you are booting into the normal P2 firmware, i.e. have not:

- loaded P1 firmware by accident
- forgotten to move the bootloader switch to the correct position
- forgotten to cycle the power after moving the bootloader switch

then it is not possible for the PHY to come up in 100BASE-T mode. P2 firmware ONLY runs in GigE mode.

So, assuming you are doing everything correctly, then it is possible you have broken hardware which will have to be returned.

However, it is possible you have a bad cable. It is also possible you have a bad PC NIC. There are a lot of possibilities.

I'd recommend going back to P1. Use piHPSDR (which I know nothing about, BTW) compiled for your system. See if things run. If so, load P2 and again try piHPSDR (it is compatible with both protocols).

If all that fails and you find nothing wrong with your networking cables or PC then I am out of ideas.
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Tue Dec 17, 2019 7:30 am

w-u-2-o wrote:If you are booting into the normal P2 firmware, i.e. have not:
- loaded P1 firmware by accident
- forgotten to move the bootloader switch to the correct position
- forgotten to cycle the power after moving the bootloader switch

No, I made certain that I got the above right and several times.

w-u-2-o wrote:So, assuming you are doing everything correctly, then it is possible you have broken hardware which will have to be returned.

I have tried to eliminate every possibility of client side hardware or software problems:
I tried more than once switching between the two Ethernet ports on my desktop computer.
I tried using my laptop' with a fresh installation of O/S and software.
I re-installed my O/S on the desktop computer.
I replaced the Ethernet cable.

BUT - looks like good news and bad news: I managed to install P1 firmware and piHPSDR and although it will not work outside a Pi (looks for GPIO pins in vain of course), it did successfully discovered the 7KDLE. With P2 installed it failed, with the same error messages as my own client - rcvefrom(): resource temporarily unavailable.

I also received an email from support (OM Doug, W5WC) - quote:
"The proper indications would be a steady link light on the ethernet connector. You should also see two red LEDs through the small vent holes near the power connector. One of the LEDs will be steady and the other flashing slowly. The flashing LED shows that the firmware is working."

This is what I get with both P1 and P2 firmware. This is encouraging, because it eliminates a failure or weakness in the hardware running the firmware and points towards the Ethernet connection failing at 1000Mb. Considering I tried three different Ethernet ports on two computers it would indicate the fault is in the rig.

Anyhow, many thanks for all you input and patience with me too! :-) Hopefully its now a matter of repairing the Orion board.
User avatar
neoklis
Posts: 18
Joined: Thu Jan 17, 2019 11:51 am
Location: Souni, Limassol, Cyprus
Contact:

Re: ANAN-7000DLE MkII Ethernet comms failure

Postby neoklis » Sun Jan 12, 2020 4:11 am

Hi all

The fault was in the end the Ethernet controller chip. This was repaired by Doug Wigley W5WC - my thanks. Both the bootloader and programmer work well, although the programmer reports the rig as unknown. However it did successfully upgrade the P2 firmware to Pre8. My own client software works well but ghpsdr will not discover the rig, don't know why, but I don't use it anyway.

Return to “Network Connections & Network Hardware”