Cannot find Radio in direct connect.

[zl2...@gmail.com]

HL2 is working correctly using any one of 3 networked PCs,

But hey will not connect when radio is plugged directly to their PC ethernet port.

Is not a cable fault.

The problem is showing up with Thetis and SDR Console.

The radio "IP" LED blinks at 2 Hertz 

Since the last time I used the radio directly I have added the band volt components to the end plate (is working)  and updated the firmware to Ver 7.4.

Any help or suggestion would be greatly received.

Keith

ZL2TPQ

[brhl...@gmail.com]

You will not get an IP from your PC or is on the PC DHCP running?

[Keith ZL2TPQ]

It is strange. In the past, I just disconnected the LAN cable from the radio and connected one from the laptop and it just worked. I wonder if there is a bug in the firmware update?

[ron.ni...@gmail.com]

Did you try connecting to the HL2's default self assigned IP address of 169.254.19.221 ?

Or did you assign a fixed IP address?

Of is your PC running a DHCP server?

73,Ron, N6YWU

[Josh Logan]

What is the order of operation as well?

If you are using DHCP between the wired devices, and then you are going direct are you powering off the radio?  Does the operating system have a static or DHCP address?

For the self assigned HL2 IP address to work the operating system also needs to be on DHCP and then convert to 169.254.x.x

73, KD7HGL

Josh

--
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/dc9c5645-34c5-48aa-8626-fd3e9532a9f7n%40googlegroups.com.

[Scott Massey]

Are you using a router/switch or a cross-over cable?  If a single cable connection (cross-over), then probably need to set both HL2 and PC to static IPs.  I know it’s a dumb question but I’ve supported a bunch of guys that missed silly stuff.

Good luck!

Scott Massey | M +1.248.535.6510

(iPhone transmission)

On Jan 21, 2024, at 12:34, ron.ni...@gmail.com <ron.ni...@gmail.com> wrote:



[Steve Haynal]

Hi Keith,

Please see this issue tracker:

https://github.com/softerhardware/Hermes-Lite2/issues/148

I would argue that it is a bug for any device to retain its IP once the ethernet cable is removed. I suggest setting a fixed IP which your laptop knows about or use the APIPA address.  See the network guide for more details:

https://github.com/softerhardware/Hermes-Lite2/wiki/Troubleshoot-Network

73,

Steve

kf7o

[Keith ZL2TPQ]

DHCP is running in the PC. 

Thetis 2.10.3.4 ,   SDR Console,  and SparkSDR all cannot connect to HL2 directly.

They all can connect to HL2 via the ethernet network.

On Sunday, January 21, 2024 at 11:48:59 AM UTC+13 brhl...@gmail.com wrote:

[Scott Massey]

At the threat of beating a horse, are you using a crossover cable when you are trying to establish a single cable connection between your PC and the HL2?  If you are using a standard Ethernet cable, it cannot work.  It’s no surprise that your system works with a router/switch.  The reason is a router/switch automatically connects the output of one Ethernet device to the input of the second Ethernet device. 

You can think of this connect like a serial link where transmit of one device is connected to the receive of the other device.  The difference is there are four pairs within an Ethernet cable instead of a single pair within a serial connection.

Once the cabling is fixed, you probably still have some work to do: establishing a static IP address scheme.  The reason is your PC doesn’t “assign“ DHCP addresses.  That is the job of your WAN/LAN router.  So, to get around this, set up static IPs for both devices.  

So if I haven’t misread this thread (your configuration works with a router but not in a direct connection mode) and your are not using a crossover cable, I think that’s your problem.

Good luck, Scott KE8KYP

Scott Massey | M +1.248.535.6510

(iPhone transmission)

On Jan 23, 2024, at 23:16, Keith ZL2TPQ <collar...@gmail.com> wrote:

DHCP is running in the PC. 

--
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/173b3537-b36c-4d79-a5e5-a2c91f5f8052n%40googlegroups.com.

[G4ZAL]

It is not necessary to use a crossover ethernet cable nowadays.

Most modern devices are capable of auto-sensing.

I use a straight cable between my HL2 and a 7 year old laptop with no problem.

Nigel

G4 ZAL

[Scott Massey]

Hmm… I’ve not had that experience.  Do you have to switch to static?  Or is your PC assigning IPs?

Scott Massey | M +1.248.535.6510

(iPhone transmission)

On Jan 24, 2024, at 08:29, G4ZAL <devon...@gmail.com> wrote:

It is not necessary to use a crossover ethernet cable nowadays.

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/66769c99-ed64-41d8-b49e-d608cd1af789n%40googlegroups.com.

[G4ZAL]

I don't do anything special, network-wise (this assumes you have not set any non default settings, i.e. manually assigned a static IP etc).

Connect an ethernet cable direct from computer to Hermes-Lite 2.

Then, simply boot the computer and power the HL2.

Both will (should) use the APIPA method and when the SDR software starts, it will send a broadcast to the network and the HL2 should be found and respond.

Nigel

G4ZAL

[ron.ni...@gmail.com]

Some systems will not do a UDP broadcast on the self-assigned IP subnet... possibly due to a firewall setting. So automatic broadcast discovery will not work from those systems (such as an iPhone).  On those systems, one has to tell the SDR application to use the HL2's self-assigned IP of 169.254.19.221 (as set by the FPGA gateware when using the HL2's default MAC address when no DHCP IP address is served).  Another name for the self-assigned IP address is the RFC 3927 IPv4 Link Local Address, sometimes called APIPA on Windows systems.

73, Ron, n6ywu

[Kristofer Danner]

No gigabit device requires a crossover cable, auto MDIX handles this.

[Keith ZL2TPQ]

I updated the gateware from original to V7.4 so the band voltage output would work. It does

But I now have the "Direct connection not working" problem. 

Shorting the PTT while HL2 is booting has allowed V7.0 to load and restored the ability to connect directly to the HL2. But the Band voltage feature is lost.

Am I able to either, clear the v7.4 and try another version that might not have this bug ?

Would the gateware installer overwrite the V7.4 with a third install?
Another option would be that I clear the V7.4 and continue with the ability to direct connect, which is the most important to me.

Your advice would be appreciated.

Best regards

Keith 

ZL2TPQ

[Keith ZL2TPQ]

NO radios will connect when using updated gateware when HL2 and laptop are directly connected.
All radios will connect using Factory gateware and connected directly or via LAN.

Hermes Lite 2 Build 9
Factory installed FW V7.0 P1 HL2 booted with Key/PTT short. connected via Ethernet LAN
Thetis V2.10,  SDR++ v1.1.0,  Spark SDR,   SDR Console
All radios work correctly

HL2 powered on normaly and connected via the Ethernet LAN and tested with the following FW upgrades,
71p2, 72p2, 72p3, 72p5, 73p2, and others unrecorded incuding 69p?
All the softwares connected and worked properly as above.

HL2 powered on with Key/PTT short, Factory FW boot. HL2 directly connected to laptop via patch cable.  
All radio softwares working correctly as above.

HL2 powered normally booting on upgrade FW, and connected to the laptop with the patch cable.
None of the radios work with any of the update versions.

I have tried setting a fixed IP,  but may not have done this correctly. 

But it would appear that the HL2 and laptop (Windows 11) are quite happy to connect irrespective of interface, if the HL2 is running the original gateware.

Any more thoughts?

73

Keith ZL2TPQ

On Monday, January 22, 2024 at 4:06:48 PM UTC+13 softerh...@gmail.com wrote:

[tmoto...@gmail.com]

Hi All –

 

Working good on this config

 

HL2 direct cable to Win10 i7 Dell Laptop working fine.

 

Firmware:

Ver 7.4.2

ID Hermes Lite

Protocol 1

 

on

 

Thetis v2.10.3.4 x64 for HL2

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/ad7acda2-dc07-44e5-aed2-705c9f1c9718n%40googlegroups.com.

[Keith ZL2TPQ]

Thank you Tom,

I take it, you don't do anything special and can plug in the direct cable or the ethernet cable and start your program  and it all works correctly.

That's the way HL2 has worked for years.  But since updating the gateware I cannot connect directly from any of PCs and using any one of four software radios.

I've tried many of the updates too

I have tried using fixed IP addresses as suggested, although I'm not too sure I'm doing that right.

Bottom line is, that I shouldn't have to as your installation has proved.

  If I start the radio while forcing the "Factory Load", the radio works on any connection method as it used to.

I'm wondering if there is a fault in the gate hardware.

[tmoto...@gmail.com]

Hi Keith –

That would be one of the possibilities, maybe something has gotten the gateware corrupt or how it reads the file.

Have you tried to role back to an earlier gateware?

 

I haven’t looked into how the file structure works – whats flashed or written in against the base factory load. Past that its above my interaction with the upgrades.

 

I would expect Steve mind be able to point you in the right direction.

 

Tom – K2TC

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/5f059bfa-0bc6-4478-82e6-87708a70aaffn%40googlegroups.com.

[Keith ZL2TPQ]

Thank you Steve,

I cannot connect directly to the radio when using any gateware update version. 

I have tried using fixed addresses etc without success. 

A direct connection is always successful when using the factory installed gateware. (Accessed by powering up the radio with the PTT shorted.)

Ethernet LAN connections work with all variations of gateware, PC and radio softwares. 

The comments above are true with all of my PCs and 4 radio softwares.

I don't attempt to change connection with power on.

Other HL2 owners do not have this problem.

Could there be a fault in the gate array? 

Keith ZL2TPQ

On Monday, January 22, 2024 at 4:06:48 PM UTC+13 softerh...@gmail.com wrote:

[Duncan Clark]

I use a computer with two NICS.  A USB wifi connection to a router a 100ft away from the shack is used solely for an internet connection

One NIC connects to my HL2 and the other connects directly to another computer which I connect to with a Remote Desktop Connection as a VM.  

The computer with two NICs runs under Windows 10 Pro.  I've run an APIPA connection from one NIC to my HL2 for a long time, moving to new gateware's as they become available. Never an issue.

I recently changed that NIC to using a fixed IP address.

So whilst connected under an APIPA address  I changed the IP address on my HL2, using SPARK, to 192.168.3.11.

Naturally it will not then connect as the IP address on the computer NIC is still an APIPA address.

So I now manually change the IP address for that NIC to a fixed IP i.e. 192.168.3.10.

Now the NIC and HL2 are on the same subnet and everything connects fine. SPARK and Thetis find the HL2 without any issue. I have a second HL2 with a fixed IP of 192.168.3.12 and an old ANAN100. They too all connect fine. 

I do not think there is any problem with the gatewares. I would look at how you are configuring the computer NIC that your HL2 plugs in to.

Duncan

[Steve Haynal]

Hi Keith,

After a gateware update, you may try booting in factory mode and making sure that fixed IP and favor dhcp are not enabled. This can be done with SparkSDR or Quisk. Perhaps when you boot with new gateware installed one of these are active and causing your problem. These settings have no effect in factory mode. There was a recent related issue solved where the user had to enable favor dhcp after gateware update for the HL2 to be found on his network.

Except for honoring or not honoring the ethernet settings, there is not difference in the ethernet portions of the gateware between factory and regular.

73,

Steve

kf7o