None of my equipment has LXI though, and the Ethernet equipment that I have has been painful to use. See the Siglent troubles in this blog post, or older equipment which often doesn’t support DHCP at all.
It seems everything is an SCPI-derivative these days, and that is a protocol family not a protocol, one which could only be ill-defined and heavily vendor-extended/interpreted to the point of assumed uninteroperability at best. That said, it works. I wouldn't buy new test equipment now without LXI or some similarly scriptable interface. Manual configuration just creates too much scope for error during testing. Coming from software, electronics is hard enough without the fuzz-factor of human fur-ball and fat-finger physics frappery. Automation is worth its weight in gold, even if you don't value your own time highly. And the lifetime for equipment that can be automated is much higher as it can become part of fixed production or test setups and thus handily serve in-place as precision automation for common unit operations. Even just the documentation value of "these were the settings, this was the (precise or relative) time" is infinitely higher than manual fudge-work. That's why this good gear is going cheap - nobody commercial wants it, because it's behind the 8 ball from an era where flying solo with fuzzy manual process was fine. Skilled as any IC's engineering may be, if they get hit by a bus the company would prefer to have dropped $10K extra on test equipment this side of Y2K.
I guess that's why it's nice to see this project - because you're essentially helping to rescue gear that would be discarded for hassle-factor or manual-only interface and providing some portion of modern functions.
