Heyu getting stuck after a few commands

[blackketter]

(Sorry if this is a crosspost, I submitted an issue, but no response...)

I've had a heyu system installed here on linux for more than 20 years, first running on a series of PCs, and for the last couple of years on a Raspberry Pi 4 running raspian.

Rock solid until now.

Suddenly a couple of weeks ago it became unreliable. To troubleshoot, I upgraded to 2.10.3 and it works for a few commands, but then after a dozen or so, it just freezes up.

I can recover it by killing the heyu_relay process or replugging the Keyspan USB-serial adapter. I've tried swapping out that adapter with another, as well as swapping the CM11A. Any way I try, it fails after a few commands.

I did try running the topic/logging branch as suggested in #25 but that version didn't seem to start at all.

Here's the output from a successful command:

Version:2.10.3
Searching for '/home/dean/.heyu/x10config'
Searching for '/etc/heyu/x10.conf'
Found configuration file '/etc/heyu/x10.conf'
Heyu directory /etc/heyu/ is writable.
Reading Heyu configuration file '/etc/heyu/x10.conf'
lockpid: Checking for file '/var/lock/LCK..heyu.write.ttyUSB0'
Trying to lock (/var/lock/LCK..heyu.write.ttyUSB0)
lockpid: Checking for file '/var/lock/LCK..heyu.write.ttyUSB0'
/var/lock/LCK..heyu.write.ttyUSB0 is locked
Alert acks are 0x52, 0x12, 0x42
lockpid: Checking for file '/var/lock/LCK..heyu.relay.ttyUSB0'
lockpid: Checking for file '/var/lock/LCK..heyu.relay.ttyUSB0'
There was already a relay running (pid = 22378)
Sending address bytes: 04 ee

xwrite() called, count=2
xread() called, count=1, timeout = 1
xread() returning 1 byte(s). The first is 0xf2
Checksum confirmed
xwrite() called, count=1
xread() called, count=1, timeout = 10
xread() returning 1 byte(s). The first is 0x55
Interface is ready.
Sending command bytes: 06 e2
xwrite() called, count=2
xread() called, count=1, timeout = 1
xread() returning 1 byte(s). The first is 0xe8
Checksum confirmed
xwrite() called, count=1
xread() called, count=1, timeout = 10
xread() returning 1 byte(s). The first is 0x55
Interface is ready.
Transmission OK
lockpid: Checking for file '/var/lock/LCK..heyu.write.ttyUSB0'
munlock: Unlink file '/var/lock/LCK..heyu.write.ttyUSB0'

and here's the next one that locks up:

Version:2.10.3
Searching for '/home/dean/.heyu/x10config'
Searching for '/etc/heyu/x10.conf'
Found configuration file '/etc/heyu/x10.conf'
Heyu directory /etc/heyu/ is writable.
Reading Heyu configuration file '/etc/heyu/x10.conf'
lockpid: Checking for file '/var/lock/LCK..heyu.write.ttyUSB0'
Trying to lock (/var/lock/LCK..heyu.write.ttyUSB0)
lockpid: Checking for file '/var/lock/LCK..heyu.write.ttyUSB0'
/var/lock/LCK..heyu.write.ttyUSB0 is locked
Alert acks are 0x52, 0x12, 0x42
lockpid: Checking for file '/var/lock/LCK..heyu.relay.ttyUSB0'
lockpid: Checking for file '/var/lock/LCK..heyu.relay.ttyUSB0'
There was already a relay running (pid = 22378)
Sending address bytes: 04 ee

xwrite() called, count=2
xread() called, count=1, timeout = 1
xread() returning 1 byte(s). The first is 0xf2
Checksum confirmed
xwrite() called, count=1
xread() called, count=1, timeout = 10
xread() returning 1 byte(s). The first is 0x55
Interface is ready.
Sending command bytes: 06 e3
xwrite() called, count=2

and then it just hangs.

Any suggestions as to where to look track this down? Like I said, I it started failing spontaneously (after a reboot) and I can't think of what might have changed... Thanks in advance!

[blackketter]

Ok, weird. I tried setting up a new (old) raspberry pi 2 and had the same problem with both Keyspan adapters (USA-19 model). Then dug around my bin and found a slightly different variant (USA-19HS) that seems to work reliably on both the Raspi4 and Raspi2. No idea why the older model stopped being reliable, but after 20 years, it's getting a well earned rest.