CAT error on SPE Expert amp
Posted: 04 Dec 2021, 17:37
My SPE Expert 1.5K-FA amp displays a "CAT error" message frequently when using Log4OM. It can occur at any time, but often occurs when switching between bands.
The factory says this error is due to a polling interval problem, with a longer polling interval tripping an error in the amp firmware. They said that some users with WSJT-X have this error, and they are looking at a firmware update to deal with it. They have sent me beta firmware they hope to deal with the WSJT-X problem to try and help, which I installed. That, itself, didn't fix the problem.
To diagnose this, I tried using HRD for rig control. I started off by getting the same error, but I increased the polling interval on HRD to 100 msec, and HRD no longer creates polling errors. ( HRD also works at a 200 msec polling, but errors appear at the 300 msec setting) With the new firmware and with the lower polling interval, I no longer receive CAT error on HRD.
To try use Log4OM, I have lowered the polling interval on OmniRig to 100 msec. The problem still continues. I tried adding a CAT delay in Log4OM of 250 ms just to see what would happen, and it seemed to help a bit.
Rig is a Yaesu FT-950 at 36400 baud. The PC connects to the rig, the rig has a CAT splitter, and the amp gets CAT data at the split.
Log4OM version 2.18.00, OmniRig 1.20, Windows 10
Thanks for any assistance.
The factory says this error is due to a polling interval problem, with a longer polling interval tripping an error in the amp firmware. They said that some users with WSJT-X have this error, and they are looking at a firmware update to deal with it. They have sent me beta firmware they hope to deal with the WSJT-X problem to try and help, which I installed. That, itself, didn't fix the problem.
To diagnose this, I tried using HRD for rig control. I started off by getting the same error, but I increased the polling interval on HRD to 100 msec, and HRD no longer creates polling errors. ( HRD also works at a 200 msec polling, but errors appear at the 300 msec setting) With the new firmware and with the lower polling interval, I no longer receive CAT error on HRD.
To try use Log4OM, I have lowered the polling interval on OmniRig to 100 msec. The problem still continues. I tried adding a CAT delay in Log4OM of 250 ms just to see what would happen, and it seemed to help a bit.
Rig is a Yaesu FT-950 at 36400 baud. The PC connects to the rig, the rig has a CAT splitter, and the amp gets CAT data at the split.
Log4OM version 2.18.00, OmniRig 1.20, Windows 10
Thanks for any assistance.