Yesterday I was in communication with SPE regarding their “Application Programmers Guide” document and I thought I’d share some information that was identified.

The same version – Rev 1.1 dated 15.10.2015 – is the latest available for all amplifier models excluding the original 1k-fa. This is somewhat dated, missing some specific content for more recent amplifiers, notably the 1.5k-fa and 1.5k-Taurus but overall remains applicable.

SPE were kind enough to confirm the following:

• That Status message/string, field “ID” may contain one of the following: “13K”, “15K”, “15T” or “20K”. The “T” suffix identifies a Taurus amplifier
• For the 1.5k-fa and 1.5k-Taurus, the ‘Memory Bank’ field can be either “A” or “B”
• For the 1.5k-fa and 1.5k-Taurus, the ‘Tx Antenna and ATU status’ field is as specified for the 1.3k-fa
• That Status message/string field ‘SWR ATU’ is the value measured by sensor SWR 1 and field ‘SWR ANT’ is that measured by sensor SWR 2. Note: The SPE Expert User Manual contains a block diagram that identifies sensors SWR 1 and SWR 2.

Andy

This is just a short post to alert users of my SPE Expert Controller App that the Waveshare network / serial adapter, specifically model “RS232/485/422 To RJ45 Ethernet Module, TCP/IP To Serial, with POE Function”, firmware V1.452 appears to have what I consider a defect in its DHCP implementation. I wanted to make those who have this device or who are thinking about purchasing this device aware.

Firstly let me give a brief overview of DHCP. When a client using DHCP starts it broadcasts a DHCP Discover message to identify DHCP servers. A server receiving this will Offer an IP address plus other network config information to the client. With this information the client will Request the IP addressing information it wishes to use (as several servers could have responded) and the corresponding server will send an Acknowledgement.

The IP address information Offered has a lease time, a validity time if you like. Once the lease expires the client should no longer use that address information. What a client should do is renew the lease prior to its expiry, often at a period equating to half the lease duration.

OK, with that knowledge I can now say that my Waveshare adapter correctly obtains its IP information on power-on. But it does not appear to respect the lease time so simply continues to use the IP information beyond its lease period / validity period. It does not attempt to renew the lease either.

So what’s the impact of this? Well, two things spring to mind, neither good. As the DHCP server never sees a renewal it expires the IP address and is then within its rights to offer the same address to another client. This results in two devices with the same IP address! That’s going to cause problems. Secondly, its common to configure DHCP servers to push name information to DNS when they allocate an address and to remove that information from DNS when a lease expires. As the Waveshare adapter doesn’t renew the lease my DNS server removes its name from DNS when the lease expires. So name resolution no longer works!

This is not the first time I’ve observed this sort of behavior but its been a few years and that device was another cheap and cheerful Chinese piece of IoT kit.

So, if you have your Waveshare adapter configured to use DHCP and are seeing some hard-to-explain issues, check whether there are two devices using the same IP. If DNS lookups of the Waveshare device are failling after a while (after the lease time) then this is likely the cause.

Andy