Lost network on both of my HL2

Sven Palmersjö

unread,

Feb 22, 2020, 5:52:28 PM2/22/20

to Hermes-Lite

Hi!

I have reprogrammed both my HL2b5 and HL2b9 with new Gateware 68 successfully and but lost contact to the network. After that also tried Quartus with the hl2b2_main.jic. Can't get contact with any of the units to run my SparkSDR application!

Most left LED is flashing after reprogramming on the HL2b9 and the most right LED is on. On the HL2b5 only the most left LED is flashing

Could anyone give me a QUICK answer how to have network back again! I really need both of them for my monitoring.

73 de Sven SM6FMB

Alan Hopper

unread,

Feb 23, 2020, 1:34:05 AM2/23/20

to Hermes-Lite

Hi Sven,

that sounds like the wrong jic file, it should be hl2b5up-main.jic from https://github.com/softerhardware/Hermes-Lite2/tree/master/gateware/bitfiles/stable/20191110_68p4/hl2b5up_main

73 Alan M0NNB

Sven Palmersjö

unread,

Feb 23, 2020, 4:47:19 AM2/23/20

to Hermes-Lite

Hi!

Yes wrong jic file. Both HL2 works with the 4rx version now waiting for version handling with 6rx or why not 12rx?

73 de Sven SM6FMB

Alan Hopper

unread,

Feb 23, 2020, 11:12:22 AM2/23/20

to Hermes-Lite

Hi Sven,

good the hear they are working. It is still a guess that the problem is the 6rx firmware, It may well still be some other network problem. You could try running at higher bandwidth than normal to emulate the load with the 6rx code. If this proves stable then maybe try the 6rx again to see if the problem reappears.

73 Alan M0NNB

Sven Palmersjö

unread,

Feb 23, 2020, 4:25:02 PM2/23/20

to Hermes-Lite

Hi!

No my HL2 do not working over time!

After corrected my both HL2, HL2b5 and HL2B9 to the same firmware Hermes-Lite2/gateware/bitfiles/stable/20191110_68p4/hl2b5up_main/ for 4rx I noticed several things.

If I turn on the HL2b5 in SparkSDR alone it seems work without any issues. If I turn on the HL2b9 in SparkSDR alone it never starts. If I turn on both in SparkSDR both
seems to work, but after 1 hour this time, SparkSDR, Skimmer Server and RTTY Server stops decoding.

I also tried to stress my computer with other programs used frequently by me to see if some other program stops the activity on my main programs but I can not see any problem.

The error must be in firmware or in SparkSDR application! But I am in no way a programmer or technician. I am little desperate now with no solution in site!

73 de Sven SM6FMB

Steve Haynal

unread,

Feb 23, 2020, 10:01:01 PM2/23/20

to Hermes-Lite

Hi Sven,

Are you using Windows or Linux? Without any software running but both HL2s connected to your network, please try the following in a terminal or command prompt:

** Do a broadcast ping, the first 3 numbers 192.168.0 should correspond to your local network

** Windows: ping 192.168.0.255

** Linux: ping -b 192.168.0.255

** Post the output from the following command, same in Windows or Linux:

arp -a

** Verify that you can ping both HL2s, again with no software connected:

ping 192.168.0.X

ping 192.168.0.Y

where X and Y are for your two HL2s. Please post the output from ping.

** Turn off the HL2s and try to ping the same addresses again. Do you now see failure?

All of the above is to check that there are not two devices on your network with the same MAC or IP.

When the HL2s are connected, what is the status of the LEDs? I would like to know if they are connected at 1Gb/s and if they used a fixed IP or not.

https://github.com/softerhardware/Hermes-Lite2/wiki/LEDs

Can you step your setup backwards until it works again? I think you replaced your router/switch. Can you revert to the old one and see if that fixes the problem. Which HL2 gateware versions were you using with the last working setup? Can you try those again? Please revert to the last known working version of SparkSDR. Also, please revert anything else on your network (Red Pitaya, skimmers) to the last known good working version. We can add/remove components one by one to identify the problem.

I have just run 2 HL2s on the same network for several hours without and problems here.

73,

Steve

kf7o

Alan Hopper

unread,

Feb 24, 2020, 2:49:09 AM2/24/20

to Hermes-Lite

Hi Sven
Steve's advice is very good and I would be interested to see the results of those tests.

I don't think is as clear cut as you suggest that the problem is with spark or firmware. I'm not claiming that it can't be spark but the I still suspect a network issue.

The fact that it all ran reliably for 8 months and only went wrong when you changed the network indicates the software and radio aren't basically flawed. I believe you had a similar problem once before and a power cut fixed it, this also indicates a network issue.

Both spark and cw skimmer use a lot of network bandwidth communicating with the radios, you report the problem is reduced when you run at lower bandwidths or with fewer radios or with just one program at a time, all these are reducing the load on the network.

The fact that both cw skimmer and spark stop at the same time is interesting. There is no direct communication between the two programs so it is not something simple. If one program were to start sending udp packets to the other or the other's radio things could go wrong but spark uses 'connected udp sockets' so once running it can't (even if there is a bug) start sending to the wrong device. Network failure is an obvious thing that will affect both programs. The high ep6 number around the time of failure indicate a network problem.

I suggested trying the 4rx firmware simply as it has probably had more testing than the 6rx firmware, we can now cross that off the list.

I'm not sure how you are able to turn both radios on but not the hl2b9 on its own. Are you saying that on starting spark and without using profiles, simply clicking start on the hl2b9 does not work? If so this needs sorting out first, Steve's ping test might give some clues here.

73 Alan M0NNB

Sven Palmersjö

unread,

Feb 24, 2020, 12:20:20 PM2/24/20

to Hermes-Lite

Hi Steve!

Are you using Windows or Linux? Without any software running but both HL2s connected to your network, please try the following in a terminal or command prompt:

WINDOWS 10 WITH LATEST UPDATES

** Do a broadcast ping, the first 3 numbers 192.168.0 should correspond to your local network

** Windows: ping 192.168.0.255

** Linux: ping -b 192.168.0.255

C:\>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 1ms, Average = 0ms

** Post the output from the following command, same in Windows or Linux:

arp -a

C:\>arp -a

Interface: 192.168.0.133 --- 0x4

Internet Address Physical Address Type

192.168.0.1 e0-b9-e5-d2-c9-ae dynamic

192.168.0.31 8c-6d-50-5d-3d-ce dynamic

192.168.0.37 00-15-99-0c-7b-80 dynamic

192.168.0.67 00-1c-c0-a2-13-dd dynamic

192.168.0.84 e2-b9-e5-d2-c9-b7 dynamic

192.168.0.86 10-da-43-8e-37-10 dynamic

192.168.0.116 b8-27-eb-b7-de-5d dynamic

192.168.0.118 00-26-32-f0-61-a2 dynamic

192.168.0.239 38-94-ed-31-bd-4a dynamic

192.168.0.255 ff-ff-ff-ff-ff-ff static

224.0.0.2 01-00-5e-00-00-02 static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.251 01-00-5e-00-00-fb static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

** Verify that you can ping both HL2s, again with no software connected:

ping 192.168.0.X

ping 192.168.0.Y

where X and Y are for your two HL2s. Please post the output from ping.

C:\>ping 192.168.0.62

Pinging 192.168.0.62 with 32 bytes of data:

Reply from 192.168.0.62: bytes=32 time=833ms TTL=128

Reply from 192.168.0.62: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.62:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 833ms, Average = 208ms

C:\>ping 192.168.0.67

Pinging 192.168.0.67 with 32 bytes of data:

Reply from 192.168.0.67: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.67:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

** Turn off the HL2s and try to ping the same addresses again. Do you now see failure?

C:\>ping 192.168.0.62

Pinging 192.168.0.62 with 32 bytes of data:

Request timed out.

Reply from 192.168.0.133: Destination host unreachable.

Ping statistics for 192.168.0.62:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

All of the above is to check that there are not two devices on your network with the same MAC or IP.

C:\>ping 192.168.0.67

Pinging 192.168.0.67 with 32 bytes of data:

Request timed out.

Reply from 192.168.0.133: Destination host unreachable.

Ping statistics for 192.168.0.67:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

When the HL2s are connected, what is the status of the LEDs? I would like to know if they are connected at 1Gb/s and if they used a fixed IP or not.

flashing

on

My 2 x Netgear GS108Ev3 - 8-Port Gigabit ProSAFE Plus Switch. Yes 1 Gb/s. 192.168.0.239. I do not if static or fixed. The adress can not be find in the router IP table!

Red Pitaya rp-f061a2 192.168.0.118 00:26:32:f0:61:a2 Static lease

HL2b9 HL22-a213df 192.168.0.62 00:1c:c0:a2:13:df Static lease

HL2b5 HL21-a213dd 192.168.0.67 00:1c:c0:a2:13:dd Static lease

Can you step your setup backwards until it works again? I think you replaced your router/switch. Can you revert to the old one and see if that fixes the problem.

Which HL2 gateware versions were you using with the last working setup? Can you try those again? Please revert to the last known working version of SparkSDR. Also,

please revert anything else on your network (Red Pitaya, skimmers) to the last known good working version. We can add/remove components one by one to identify the problem.

Tried to manually step back to the setup I was early Janauari when I had worked for 9 - 10 months without any big problem but not succeeded with the step back.

I can't go back to that switch for the moment because I gave it to my son. I think it was some version of Gateware 68 hl2b5up_6rx.rbf, last version with a stable 6rx version, which I updated to either 16/10-19

but most probably 13/12-19.

I replaced my unshielded router to shielded 8-port router of same brand.

I have just run 2 HL2s on the same network for several hours without and problems here.

But you do not run as me: 2 x HL2, 1 x RP, SparkSDR, Skimmer Server, Rtty Server - Is there where the problem begins!

It seems promising with just one HL2 running. No stops yet! But I want to have 2 x HL2 with 6rx each. not 4rx!

73 de Sven SM6FMB

devices.JPG

Before.JPG

After when stoped.JPG

stat.JPG

Steve Haynal

unread,

Feb 24, 2020, 12:43:39 PM2/24/20

to Hermes-Lite

Hi Sven,

Only 1 HL2 is showing up in arp -a:

192.168.0.67 00-1c-c0-a2-13-dd dynamic

I would expect to see both HL2s. This is probably because you didn't ping to broadcast. Please try broadcast ping and then post arp -a output again. I just wan't to double check that the arp table on your host is properly updated.

ping 192.168.0.255

arp -a

73,

Steve

kf7o

Sven Palmersjö

unread,

Feb 24, 2020, 4:06:42 PM2/24/20

to Hermes-Lite

Hi!

For the moment I am only working with 192.168.0.67

Is this what you want to see? Here could you see my other HL2

C:\>arp -a

Interface: 192.168.0.133 --- 0x4

Internet Address Physical Address Type

192.168.0.1 e0-b9-e5-d2-c9-ae dynamic

192.168.0.31 8c-6d-50-5d-3d-ce dynamic

192.168.0.38 00-15-99-0c-7b-80 dynamic

192.168.0.62 00-1c-c0-a2-13-df dynamic

192.168.0.67 00-1c-c0-a2-13-dd dynamic

192.168.0.84 e2-b9-e5-d2-c9-b7 dynamic

192.168.0.86 10-da-43-8e-37-10 dynamic

192.168.0.116 b8-27-eb-b7-de-5d dynamic

192.168.0.118 00-26-32-f0-61-a2 dynamic

192.168.0.173 b0-6f-e0-1f-27-de dynamic

192.168.0.186 f8-04-2e-f5-25-d4 dynamic

192.168.0.187 f8-04-2e-f5-25-d4 dynamic

192.168.0.239 38-94-ed-31-bd-4a dynamic

192.168.0.255 ff-ff-ff-ff-ff-ff static

224.0.0.2 01-00-5e-00-00-02 static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.251 01-00-5e-00-00-fb static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

When I first pinged this HL2 I saw

C:\>ping 192.168.0.62

Pinging 192.168.0.62 with 32 bytes of data:

Reply from 192.168.0.133: Destination host unreachable.

Reply from 192.168.0.62: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.62:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

73 de Sven SM6FMB

Steve Haynal

unread,

Feb 24, 2020, 4:18:30 PM2/24/20

to Hermes-Lite

Hi Sven,

It is a little strange that you saw a reply from 192.168.0.133 when pinging 192.168.0.62. Quisk has the ability to write a new MAC address into the EEPROM. Can you please use Quisk to change the MAC address on both HL2s to some other different values. The MAC settings is on the Quisk radio config screen and is pretty self explanatory. Hover over the boxes or text for more description.

73,

Steve

kf7o

Jonas Sanamon

unread,

Feb 25, 2020, 3:15:46 AM2/25/20

to Steve Haynal, Hermes-Lite

Hi Steve,

I think .133 is Svens windows computer that he is running the commands from. That just means that for the first 2 attempts there was no reply, which is strange and points to some possible underlying issue.

Sven, perhaps You can confirm if 192.168.0.133 is your windows machine?

Best Regards,

Jonas

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/edb39976-b187-470c-9ddd-a010f2a662c2%40googlegroups.com.

Sven Palmersjö

unread,

Feb 25, 2020, 7:28:41 AM2/25/20

to Hermes-Lite

Hi Steve!

Sven Palmersjö

unread,

Feb 25, 2020, 7:43:57 AM2/25/20

to Hermes-Lite

Hi Steve!

I have changed MAC address in Quisk on both HL2 but I cant see any changes in my router not even after 12 hours!

Just now I am working with HL2b5 192.168.0.62 if I connect the other HL2b9 192.0.168.67 they all stop decoding, including my Red Pitaya 192.168.0.118. This take up to an hour before they all stops.

Microsoft Windows [Version 10.0.18363.657]

C:\Users\Sven>arp -a

Interface: 192.168.0.133 --- 0x4

Internet Address Physical Address Type

192.168.0.1 e0-b9-e5-d2-c9-ae dynamic

192.168.0.31 8c-6d-50-5d-3d-ce dynamic

192.168.0.33 00-15-99-0c-7b-80 dynamic

192.168.0.62 00-1c-c0-a2-13-df dynamic

192.168.0.67 00-1c-c0-a2-13-dd dynamic

192.168.0.84 e2-b9-e5-d2-c9-b7 dynamic

192.168.0.118 00-26-32-f0-61-a2 dynamic

192.168.0.173 b0-6f-e0-1f-27-de dynamic

192.168.0.239 38-94-ed-31-bd-4a dynamic

192.168.0.255 ff-ff-ff-ff-ff-ff static

224.0.0.2 01-00-5e-00-00-02 static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.251 01-00-5e-00-00-fb static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

255.255.255.255 ff-ff-ff-ff-ff-ff static

73 de Sven SM6FMB

C:\Users\Sven>ping 192.168.0.62

Pinging 192.168.0.62 with 32 bytes of data:

Reply from 192.168.0.62: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.62:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

73 de Sven SM6FMB

Steve Haynal

unread,

Feb 25, 2020, 11:52:00 AM2/25/20

to Hermes-Lite

Hi Sven,

The MAC (physical address) did not change for either HL2. Did you power cycle the HL2s after making the change in Quisk? Also, once you confirm that the MAC address has changed with arp -a, please remove the CN10 jumper you have on one of the HL2s to force an alternate MAC and power cycle that unit again. One hypothesis is that this jumper is intermittent and causing the MAC address to change during operation. It is the physical address 00-1c-c0-a2-13-df and 00-1c-c0-a2-13-dd which must change.

192.168.0.62 00-1c-c0-a2-13-df dynamic

192.168.0.67 00-1c-c0-a2-13-dd dynamic

73,

Steve

kf7o

Sven Palmersjö

unread,

Feb 25, 2020, 12:44:55 PM2/25/20

to Hermes-Lite

Hi!

Quite unfamiliar with QUISK, used since yesterday! Do I change with "Eeprom IP address" and "Eeprom MAC address? Where do I confirm my changese? Have not succeeded with changes!

73 de Sven SM6FMB

Sven Palmersjö

unread,

Feb 25, 2020, 10:53:55 PM2/25/20

to Hermes-Lite

Hi!

During work with Quisk, 192.168.0.67 00-1c-c0-a2-13-dd dynamic changed to 192.168.0.60 00-1c-c0-a2-13-dd dynamic without I having changed to .60 !

Quisk reporting in the configuration setup that Configuration file not found.

I observed that SparkSDR, when starting up Skimmer Server, which I have done before, that SparkSDR produce a enormous amount of network packet drop. When not having Skimmer Server running just a few drops.

Microsoft Windows [Version 10.0.18363.657]

C:\Users\Sven>arp -a

Interface: 192.168.0.133 --- 0x4

Internet Address Physical Address Type

192.168.0.1 e0-b9-e5-d2-c9-ae dynamic

192.168.0.31 8c-6d-50-5d-3d-ce dynamic

192.168.0.33 00-15-99-0c-7b-80 dynamic

192.168.0.60 00-1c-c0-a2-13-dd dynamic

192.168.0.62 00-1c-c0-a2-13-df dynamic

192.168.0.84 e2-b9-e5-d2-c9-b7 dynamic

192.168.0.118 00-26-32-f0-61-a2 dynamic

192.168.0.173 b0-6f-e0-1f-27-de dynamic

192.168.0.182 f8-04-2e-f5-25-d4 dynamic

192.168.0.187 f8-04-2e-f5-25-d4 dynamic

192.168.0.239 38-94-ed-31-bd-4a dynamic

192.168.0.255 ff-ff-ff-ff-ff-ff static

224.0.0.2 01-00-5e-00-00-02 static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.251 01-00-5e-00-00-fb static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

255.255.255.255 ff-ff-ff-ff-ff-ff static

C:\Users\Sven>ping 192.168.0.60

Pinging 192.168.0.60 with 32 bytes of data:

Reply from 192.168.0.60: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.60:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Sven>ping 192.168.0.62

Pinging 192.168.0.62 with 32 bytes of data:

Reply from 192.168.0.62: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.62:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

73 de Sven SM6FMB

Steve Haynal

unread,

Feb 26, 2020, 12:51:20 AM2/26/20

to Hermes-Lite

Hi Sven,

The IP address, 192.168.0.62 is dynamic, so it can change to something different when you reconnect. In your case 192.168.0.60 was assigned.

It is the MAC address (00-1c-c0-a2-13-dd) that I would like to see changed. Below is a picture.

** With one HL2 powered on at a time.

** Select unique last two digits of the MAC address where the left arrow is.

** Select set address at Eeprom MAC usage where the right arrow is.

** There is no confirmation. Quisk will detect and apply changes. To be sure, click on another tab, "Status" in the upper left corner and then exit Quisk.

** Remove power from the HL2.

** Repeat the above process for the second HL2 but use different MAC address digits.

** Remove power from the second HL2.

** Remove any jumpers on CN10 on either HL2.

** Apply power to both units and see if there is any improvement

If there are still problems, do your problems go away if you do no run CW skimmer? Please try an extended test without CW skimmer. You mentioned that CW skimmer causes packet drops for SparkSDR.

73,

Steve

kf7o

Sven Palmersjö

unread,

Feb 26, 2020, 9:48:16 AM2/26/20

to Hermes-Lite

Hi!

I can't get the physical address to split. Trie with and without jumper CN10. In Quisk seems all to be correct.

C:\Users\Sven>arp -a

Interface: 192.168.0.133 --- 0x4

Internet Address Physical Address Type

192.168.0.1 e0-b9-e5-d2-c9-ae dynamic

192.168.0.31 8c-6d-50-5d-3d-ce dynamic

192.168.0.33 00-15-99-0c-7b-80 dynamic

192.168.0.60 00-1c-c0-a2-4c-33 dynamic

192.168.0.62 00-1c-c0-a2-4c-33 dynamic

192.168.0.84 e2-b9-e5-d2-c9-b7 dynamic

192.168.0.86 10-da-43-8e-37-10 dynamic

192.168.0.116 b8-27-eb-b7-de-5d dynamic

192.168.0.118 00-26-32-f0-61-a2 dynamic

192.168.0.163 08-02-8e-98-06-85 dynamic

192.168.0.169 b0-6f-e0-1f-27-de dynamic

192.168.0.182 f8-04-2e-f5-25-d4 dynamic

192.168.0.239 38-94-ed-31-bd-4a dynamic

192.168.0.255 ff-ff-ff-ff-ff-ff static

224.0.0.2 01-00-5e-00-00-02 static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.251 01-00-5e-00-00-fb static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

Steve Haynal

unread,

Feb 26, 2020, 1:01:26 PM2/26/20

to Hermes-Lite

Hi Sven,

It looks like some progress as the MAC physical address has changed, but it is a problem that they are both the same now. Did you power on only a single HL2 at a time when you set the MAC with Quisk? Did you enter different values for the MAC address into Quisk?

73,

Steve

kf7o

Sven Palmersjö

unread,

Feb 26, 2020, 3:58:51 PM2/26/20

to Hermes-Lite

Hi Steve!

I turned on the HL2's with maybe 5-10 seconds between. I set different MAC addresses into the Quisk.

Sven

Steve Haynal

unread,

Feb 26, 2020, 4:29:09 PM2/26/20

to Hermes-Lite

Hi Sven,

Two identical MAC addresses is definitely a problem for the network. Can you please retry changing the MAC address for *one* of your HL2? Again, make sure it is the only HL2 on your network at the time, and power cycle that HL2 after your changes.

I will repeat the same steps with two HL2s and Quisk once I am back home to make sure there are no other problems with this process.

73,

Steve

kf7o

Steve Haynal

unread,

Feb 27, 2020, 12:56:08 AM2/27/20

to Hermes-Lite

Hi Sven,

I just tried setting two different MAC addresses for two different HL2s with Quisk. All worked well. Below is the relevant output from arp -a on Linux. If a MAC address is set in EEPROM, then CN10 will not change it. I'd like to move away from using CN10 to select a MAC address and always use the EEPROM. Did you try to change the MAC address again for one of your HL2s?

? (192.168.33.116) at 00:1c:c0:a2:1f:77 [ether] on enp7s0

? (192.168.33.250) at 00:1c:c0:a2:63:22 [ether] on enp7s0

73,

Steve

kf7o

Sven Palmersjö

unread,

Feb 27, 2020, 5:20:52 AM2/27/20

to Hermes-Lite

rp -a

Sven Palmersjö

unread,

Feb 27, 2020, 5:36:14 AM2/27/20

to Hermes-Lite

Hi!

My HL2 is tested one by one. The HL2b9 could be changed in Quisk but HL2b5 is not recognized in Quisk. D2 and D3 flash in HL2b9 in Idle Mode on both. HL2b9 switch to only D2 flash in Run mode. HL2b5 remain in flashing both D2 and D3 when trying to get Run mode work going in Quisk. Have tested CN10 in both open and closed loop.

73 de Sven SM6FMB

Steve Haynal

unread,

Feb 27, 2020, 11:43:18 AM2/27/20

to Hermes-Lite

Hi Sven,

Both D2 and D3 flashing in idle mode means that a fixed IP was set. My guess is that you set a fixed IP for the hl2b5 that is not on your subnet by accident. With only the hl2b5 connected to your network, Power it on while both the ring and tip of the front connector CN4 are grounded. They both must be grounded when you power the unit on, but ground can be removed after you power the unit on. I usually use an audio cable with one end plugged into the hl2 and the other covered in aluminum foil. This forces the hl2 to not use any fixed MAC or IP addresses. Now try to connect with Quisk and set a fixed MAC address. For the selection "Eeprom MAC Usage" select ""Set address" but for the selection "Eeprom IP Usage" select "Ignore". This is different from the picture I sent, as I have a fixed IP address also for my HL2. I will send a new picture later today if you are still having trouble.

In general, there are two network related numbers which can be fixed: MAC and IP address. The MAC addresses of all devices on your network must be unique but can be any value. The MAC address is native to the device and never dynamically assigned. The IP addresses of all devices on your network must also be unique. They are typically dynamically assigned by your DHCP server. If you choose to use a fixed address, they must be in your subnet of 192.168.0.X where X is a unique value. If they are fixed and outside of your subnet, then there will be problems accessing the devices over the network.

73,

Steve

kf7o

Sven Palmersjö

unread,

Feb 27, 2020, 10:32:18 PM2/27/20

to Hermes-Lite

Hi Steve!

After doing this my functional HL2b9 is, which I never touched this time, not working! Having IP reachable problems.

My HL2b5 have D2 and D3 flashing and D4 and D5 steady in idle mode. Not reachable by Quisk!

Amount of dynamic set IP's in arp -a going from 9 to 5!

C:\Users\Sven>arp -a

Interface: 192.168.0.133 --- 0x4

Internet Address Physical Address Type

192.168.0.1 e0-b9-e5-d2-c9-ae dynamic

192.168.0.31 8c-6d-50-5d-3d-ce dynamic

192.168.0.33 00-15-99-0c-7b-80 dynamic

192.168.0.84 e2-b9-e5-d2-c9-b7 dynamic

192.168.0.115 00-26-32-f0-61-a2 dynamic

192.168.0.255 ff-ff-ff-ff-ff-ff static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.251 01-00-5e-00-00-fb static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

255.255.255.255 ff-ff-ff-ff-ff-ff static

73 de Sven SM6FMB

Hi Steve!

Hi!

Hi Steve!

<p s

Steve Haynal

unread,

Feb 27, 2020, 11:57:57 PM2/27/20

to Hermes-Lite

Hi Sven,

Let us focus just on one hl2. Let us start with the hl2b5. Please disconnect the hl2b9 from your network and remove its power. Do not power it back up until we have the hl2b5 working again. Do not run anything else. No CW skimmer. No Red Pitaya. No other SDR software.

In your response, please provide more details. Please write every step you did, and every entry you make. Please write in your native language if that is easier and I will try Google translate. Let me know if you skip, add or change a step, or if anything unexpected happens.

Please see the two attached pictures.

1. Remove power from the hl2b5.

2. Connect the hl2b5 to the network with an ethernet cable. Do not apply power yet.

3. Ground all three contacts at the end of an audio cable plugged into CN4. See the picture. I use aluminum foil. The other end is plugged into CN4.

4. While all three contacts are grounded, apply power to the hl2b5.

5. Wait and keep the three contacts grounded for 10 seconds.

6. Remove the cable from CN4. The hl2b5 should still be powered on.

7. Start Quisk. Does it discover a HL2?

8. If yes, open the screen shown in the picture below.

9. Set unique digits for a MAC address at the bottom left red arrow Eeprom MAC Address. These are the last two hex numbers of the "Physical Address" shown in your arp command. The first 4 hex numbers are hard coded to 00:1c:c0:a2. Pick two hex numbers so that the entire address is unique on your network. What numbers did you enter?

10. Set Eeprom MAC Usage to "Set Address" at the bottom right red arrow.

11. Set Eeprom IP Usage to "Ignore" at the top red arrow on the right.

12. Click the "Status" tab in the upper left corner.

13. Exit Quisk by clicking on the X in the upper right corner.

14. Remove power from the hl2b5.

15. Wait 10 seconds.

16. Apply power to the hl2b5.

17. Start Quisk. Does Quisk discover a HL2? If so, what is printed at the top of the screen, in my picture where is says "Capture from Hermes device: Mac nn:nn:nn:nn:nn:nn, Code version XX, ID X, IP yyy.yyy.yyy.yyy?

Sven Palmersjö

unread,

Feb 28, 2020, 5:34:01 AM2/28/20

to Hermes-Lite

i Steve!

1. Remove power from the hl2b5.

CHECKED.

2. Connect the hl2b5 to the network with an ethernet cable. Do not apply power yet.

CHECKED.

3. Ground all three contacts at the end of an audio cable plugged into CN4. See the picture. I use aluminum foil. The other end is plugged into CN4.

CHECKED. FABRICATE A CORRECT CABLE. FIRST ONE FABRICATED WAS IT AN ERROR IN.

4. While all three contacts are grounded, apply power to the hl2b5.

CHECKED.

5. Wait and keep the three contacts grounded for 10 seconds

CHECKED.

6. Remove the cable from CN4. The hl2b5 should still be powered on.

CHECKED.

7. Start Quisk. Does it discover a HL2?

CHECKED. HL2B5 DISCOVERED IN QUISK

8. If yes, open the screen shown in the picture below.

CHECKED

9. Set unique digits for a MAC address at the bottom left red arrow Eeprom MAC Address. These are the last two hex numbers of the "Physical Address" shown in your arp command. The first 4 hex numbers are hard coded to 00:1c:c0:a2. Pick two hex numbers so that the entire address is unique on your network. What numbers did you enter?

CHECKED. FIRST I TOOK ONE OF THE MAC ADDRESSES PREWRITTEN IN THE EEPROM MAC ADDRESS BUT CHANGED IT TO TOP OF PAGE PRINTED LAST TWO HEX NUMBER

10. Set Eeprom MAC Usage to "Set Address" at the bottom right red arrow.

CHECKED.

11. Set Eeprom IP Usage to "Ignore" at the top red arrow on the right.

CHECKED.

12. Click the "Status" tab in the upper left corner.

CHECKED.

13. Exit Quisk by clicking on the X in the upper right corner.

CHECKED.

14. Remove power from the hl2b5.

CHECKED.

15. Wait 10 seconds.

CHECKED.

16. Apply power to the hl2b5.

CHECKED.

17. Start Quisk. Does Quisk discover a HL2? If so, what is printed at the top of the screen, in my picture where is says "Capture from Hermes device: Mac nn:nn:nn:nn:nn:nn, Code version XX, ID X, IP yyy.yyy.yyy.yyy?

CHECKED. HL2B5 DISCOVERED IN QUISK WITH HL2B5 CHANGING BY ME, Eeprom MAC Address, Eeprom MAC uSAGE AND Eeprom IP Usage. STARTED SEVERAL TIMES TO SEE IF THINGS WHERE OK.

Also tested in SparkSDR where HL2b5 192.16.0.62 worked ok.

Also tested, same procedure as above, in Quisk my other HL2b9 ???.??.?.??. No LED lights up.

73 de Sven SM6FMB

C:\Users\Sven>arp -a

Interface: 192.168.0.133 --- 0x4

Internet Address Physical Address Type

192.168.0.1 e0-b9-e5-d2-c9-ae dynamic

192.168.0.19 04-b4-29-e3-38-11 dynamic

192.168.0.31 8c-6d-50-5d-3d-ce dynamic

192.168.0.33 00-15-99-0c-7b-80 dynamic

192.168.0.62 00-1c-c0-a2-13-dd dynamic

192.168.0.84 e2-b9-e5-d2-c9-b7 dynamic

192.168.0.86 10-da-43-8e-37-10 dynamic

192.168.0.163 08-02-8e-98-06-85 dynamic

192.168.0.171 b0-6f-e0-1f-27-de dynamic

192.168.0.239 38-94-ed-31-bd-4a dynamic

192.168.0.255 ff-ff-ff-ff-ff-ff static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.251 01-00-5e-00-00-fb static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

255.255.255.255 ff-ff-ff-ff-ff-ff static

Hi Steve!

Hi!

Hi Steve!

<p sty

HL21H.JPG

Sven Palmersjö

unread,

Feb 28, 2020, 10:17:25 PM2/28/20

to Hermes-Lite

Hi Steve!

I am most greatful for all help to get HL2b5 up and running! HL2b5 have been up and running for more than 17 hours now without any issues on SparkSDR, Skimmer Server and RTTY Server. I am just now running with many many application open, just as before problem began!

How do we going furter with HL2b9? I have tested the same proceedure as with HL2b9 but no succees, No LED is lit. Just darkness.

73 de Sven SM6FMB

Steve Haynal

unread,

Feb 29, 2020, 12:39:51 AM2/29/20

to Hermes-Lite

Hi Sven,

That is great that you can connect to your hl2b5 again, but using the same numbers as the default MAC address does not test if there is some problem with your network. Can you try setting the MAC address so something that is not 0x13 0xDD?

Regarding your hl2b9, I would start looking at the power supplies. Maybe the power connector is loose or desoldered from the board. Make a good visual inspection of the power supply connections. Also, please check if you measure the voltages shown in this picture:

https://github.com/softerhardware/Hermes-Lite2/wiki/Hardware#power-supply-shorts

73,

Steve

kf7o

Steve Haynal

unread,

Mar 9, 2020, 12:05:24 AM3/9/20

to Hermes-Lite

Hi Sven,

Any progress with changing the MAC to something other than the default on your hl2b5, and checking the power on your hl2b9? Only the Vsupply, +3V3, +2V5 and +1V2 should be active when power is applied. The other supplies are turned on during TX only.

73,

Steve

kf7o

Sven Palmersjö

unread,

Mar 9, 2020, 1:01:18 AM3/9/20

to Hermes-Lite

Hi Steve!

Quisk fixed it on the MAC adressing on the HL2b5.

On the HL2b9 a other new programming with Quartus made my HL2b9 as new!

Both HL2's has been working perfect for a week now.

Big thanks for all help!

73 de Sven SM6FMB

Ronald Nicholson

unread,

May 23, 2020, 6:32:53 PM5/23/20

to Hermes-Lite

Hi,

So I now have 2 HL2's with the same MAC address.

In the Protocol document here:

https://github.com/softerhardware/Hermes-Lite2/wiki/Protocol

It says:

"This 32-bit word has the format 0x06acA0vv where A is the address

from the table above and vv is the byte to be written. For example,

to set 0xEF of MAC U:V:W:X:Y:0xEF, the 32-bit word should be

0x06a8D0EF."

So is the 2nd byte supposed to be 0xac or 0xa8 ?

I've tried sending both, and get a ACK response to the commands in the UDP packet.

But after power cycling the HL2, arp -a still shows:

0:1c:c0:a2:13:dd

no change.

Is there something else I need to do to modify the MAC address?

Thanks,

Ron

n6ywu

Hi Steve!

Hi!

Hi Steve!

<p sty

Steve Haynal

unread,

May 23, 2020, 6:54:50 PM5/23/20

to Hermes-Lite

Hi Ron,

It should be ac. I've updated the wiki. A good reference is the Quisk code. See hermes/quisk_hardware.py. It is Python but reads like psuedocode. Below is the read/write EEPROM code. By the way, it would be great if we could have the functionality to set fixed IP and MAC as well as program the gateware in hl2setup.

73,

Steve

kf7o

def WriteEEPROM(self, addr, value):

## Write values into the MCP4662 EEPROM registers

## For example, to set a fixed IP of 192.168.33.20

## hw.WriteEEPROM(8,192)

## hw.WriteEEPROM(9,168)

## hw.WriteEEPROM(10,33)

## hw.WriteEEPROM(11,20)

## To set the last two values of the MAC to 55:66

## hw.WriteEEPROM(12,55)

## hw.WriteEEPROM(13,66)

## To enable the fixed IP and alternate MAC, and favor DHCP

## hw.WriteEEPROM(6, 0x80 | 0x40 | 0x20)

## See https://github.com/softerhardware/Hermes-Lite2/wiki/Protocol

if self.hermes_code_version >= 60:

i2caddr,value = 0xac,(value%256)

else:

i2caddr,value = 0xa8,(255-(value%256))

addr = (addr << 4)%256

self.pc2hermeslitewritequeue[0:5] = 0x7d,0x06,i2caddr,addr,value

self.WriteQueue(1)

if DEBUG: print ("Write EEPROM", addr, value)

def ReadEEPROM(self, addr):

## To read the bias settings for bias0 and bias1

## hw.ReadEEPROM(2)

## hw.ReadEEPROM(3)

if self.hermes_code_version >= 60:

i2caddr = 0xac

else:

i2caddr = 0xa8

faddr = ((addr << 4)%256) | 0xc

QS.clear_hermeslite_response()

self.pc2hermeslitewritequeue[0:5] = 0x7d,0x07,i2caddr,faddr,0

self.WriteQueue(1)

for j in range(50):

time.sleep(0.001)

resp = QS.get_hermeslite_response()

##print("RESP:",j,resp[0],resp[1],resp[2],resp[3],resp[4])

if resp[0] != 0: break

if resp[0] == 0:

if DEBUG: print("EEPROM read did not return a value")

return -1

else:

## MCP4662 does not autoincrement when reading 8 bytes

## MCP4662 stores 9 bit values, msb came first and is in lower order byte

v0 = (resp[4] << 8) | resp[3]

v1 = (resp[2] << 8) | resp[1]

if (resp[0] >> 1) != 0x7d:

## Response mismatch

if DEBUG: print("EEPROM read response mismatch",resp[0] >> 1)

return -1

elif v0 != v1:

if DEBUG: print("EEPROM read values do not agree",v0,v1)

return -1

else:

if DEBUG: print("EEPROM read {0:#x} from address {1:#x}".format(v0,addr))

return v0

Ronald Nicholson

unread,

May 24, 2020, 1:37:05 AM5/24/20

to Hermes-Lite

So the Python code below has this line in the WriteEEPROM function definition:

self.pc2hermeslitewritequeue[0:5] = 0x7d,0x06,i2caddr,addr,value

which uses 0x7d as the write command.

But the the hl2.c setup code seems to use 0x3d to set bias0 and bias1.

What's the difference?

I've been sending 0x3d, 0x06acD0EF

Also, does:

hw.WriteEEPROM(6, 0x80 | 0x40 | 0x20)

mean that is a write to register 6 with the value 0x40 or 0x60 required to enable a new MAC address value?

If after doing all of the above, the last byte of the MAC address is still the default 00:1c:c0:a2:13:dd, could something else be missing or broken?

Thanks,

Ron

n6ywu

------

Hi Steve!

Hi!

Reply from <a href="http://192.168.0.62" rel="nofollow" target="_blank" onmousedown="this.href='http://www.google.com/url?q\x3dht

Steve Haynal

unread,

May 24, 2020, 2:22:23 AM5/24/20

to Hermes-Lite

Hi Ron,

0x7d is the same as 0x3d except a 0x7d expects a response from the Hermes-Lite 2.0. We use C0[7] to flag that a response is expected. Search for RQST on

https://github.com/softerhardware/Hermes-Lite2/wiki/Protocol

Note that the values used in Python are shifted by 1 bit and don't include the C0[0] MOX bit.

The comment line hw.WriteEEPROM(6, 0x80 | 0x40 | 0x20) indicates that you must turn on use of the MAC or fixed address by writing to i2c address 6. Writing a value of 0x60 here should use the MAC address and favor a DHCP address over and fixed IP.

I just checked and I can set the MAC on the build9 I recently received from Makerfabs. See the screenshot below.

You could try the following:

** Check if Quisk allows you to set the MAC. Quisk runs on Linux (including Raspberry Pi), Windows and maybe even Mac OS. Maybe there is an issue with your board.

** See if you can read back the value your wrote. See ReadEEPROM in the Python code.

** Use wireshark to make sure your command is reaching the HL2.

Here is the Quisk code that actually calls WriteEEPROM to set the MAC:

elif name == 'Hware_Hl2_EepromMAC':

try:

addr1, addr2 = value.split()

addr1 = int(addr1, base=0)

addr2 = int(addr2, base=0)

except:

pass

else:

self.WriteEEPROM(0x0C, addr1)

self.WriteEEPROM(0x0D, addr2)

elif name == 'Hware_Hl2_EepromMACUse':

use = self.ReadEEPROM(0x06)

if use >= 0:

self.eeprom_valid = use

if value == 'Ignore':

self.eeprom_valid &= ~0b0001000000

elif value == 'Set address':

self.eeprom_valid |= 0b0001000000

self.WriteEEPROM(0x06, self.eeprom_valid)

73,

Steve

kf7o

Walter Holmes

unread,

Jul 7, 2020, 7:04:18 PM7/7/20

to Hermes-Lite

Outstanding.

Many thanks as always Steve..

Walter/K5WH

Hi Steve!

Hi!

Hi Steve!

<p sty

J P Watters

unread,

Jul 19, 2020, 3:17:36 AM7/19/20

to Hermes-Lite

To all,

It is alot easier to set using Spark. Open Spark, Turn on a Receiver, open properties, on the General tab, click on up or down to set the last two hex digits of the mac address and press set.

..jpw J P Watters

KC9KKO

Morris, IL USA

On Thursday, February 27, 2020 at 10:57:57 PM UTC-6, Steve Haynal wrote:

Hi Steve!

Hi!

Hi Steve!

<p sty

Reply all

Reply to author

Forward