You do not need to download, install or use Commander. 73, Rich VE3KI On Wed, at 07:14 PM, Bud Governale wrote:ĭxLab Suite Commander is not involved at all. There are no guarantees this will work for you, as other people have been reporting difficulties, but it is more likely to work properly without LP-Bridge involved than with it. I'd suggest you try it without using LP-Bridge (N1MM+ connected directly to the rig, and WSJT-X using N1MM+ for rig control). It appears as if WSJT-X may be quite sensitive to timing of the responses it receives from the rig, leading to the potential for problems when rig control is performed with the help of other programs. Indeed, in the past some people were unable to get WSJT-X to communicate with the rig via LP-Bridge even without the involvement of the UDP packet method. Since there have already been reports that suggest that timing problems may be leading to WSJT-X sensing loss of CAT control even without LP-Bridge introducing additional delays, it is not surprising that there would be problems when LP-Bridge is also included in the mix. N1MM+ can control the rig directly without using LP-Bridge, and WSJT-X can use N1MM+ to control the rig via the UDP connection.
LINKING WSJT AND N1MM LOGGER SOFTWARE
"I use LPbridge" - the point of using the UDP communication method for CAT control is that you do not need port sharing software like LP-Bridge. When WSJT-X is started from the Window > Load WSJT/JTDX menu item in N1MM+, WSJT-X does its rig control via N1MM+ and does not need or use a direct connection to the rig. N1MM+ uses the identical UDP packet method as Commander, so as far as WSJT-X is concerned, N1MM+ is the same as Commander (although in practice, there are apparently timing differences). "DXLab Suite Commander" is WSJT-X's label for its capability to control the radio via UDP packets to another software program that is actually doing the communicating with the rig. "the addition of Commander" - Commander is not involved. On Wed, at 07:14 PM, Bud Governale wrote:
There are no guarantees this will work for you, as other people have been reporting difficulties, but it is more likely to work properly
The rig, leading to the potential for problems when rig control is performed with the help of other programs. It appears as if WSJT-X may be quite sensitive to timing of the responses it receives from Since there have already been reports that suggest that timing problems may be leading to WSJT-X sensing loss of CAT control even without LP-Bridge introducing additional delays, it is not surprising that there would be problems when LP-Bridge is also included N1MM+ can control the rig directly without using LP-Bridge, and WSJT-X can use N1MM+ to control the rig via the
WSJT-X does its rig control via N1MM+ and does not need or use a direct connection to the rig. When WSJT-X is started from the Window > Load WSJT/JTDX menu item in N1MM+, Uses the identical UDP packet method as Commander, so as far as WSJT-X is concerned, N1MM+ is the same as Commander (although in practice, there are apparently timing differences).
0 kommentar(er)
