![]() ![]() Rig or your log entries will be incorrect. ![]() Have to ensure that WSJT-X is switched to the same band as your To make sure any audio harmonics are eliminated. If you intend to use WSJT-X without CATĬontrol then you should stick to Tx audio offsets above 1500 Hz Hardware PTT arrangement using RTS or DTR on a pair of serial WSJT-X will run fine without CAT control of a rig so Then you will have to disable rig control in one application or (Hamlib rigctld, Omni-Rig, or something that looks like a rig toĮach application but is more than a dumb serial port splitter), Support one of the rig server programs that WSJT-X also supports If the N3FJP FD logging application does not You cannot have two applications directly using the same rig forĬAT control. But if I try to add WSJT-X to the mix, it simplyīill Somerville wrote on 6/21/20 7:03 PM: AllĪpplications can set and read mode and frequency as well as PTT Simultaneously using VSPE to set up a port splitter. I have multiple applications utilizing CAT control all the time. I would like to minimize the transition time between modes and not have to shut everything down and restart the whole works with different sequences between modes. Then I would stop WSJT-X or fldigi and return to phone. I want to start N3FJP and leave it running all the time, then start WSJT-X or fldigi as needed to use the digital modes. However, most of the time I will be running phone, with WSJT-X and fldigi not running and doing all my logging directly through N3FJP. If all I was doing is running FT8, this would be fine. TBH, if disabling rig control in the N3FJP FD logging application is as easy as it is in WSJT-X ("Settings->Radio->Rig->None" and "Settings->Radio->PTT Method->VOX", then click "Ok") or simply exit WSJT-X when you are not using it as restarting will bring it right back where you left it, then switching rig control is probably the easiest and quickest option. You will also have to ensure that WSJT-X is switched to the same band as your rig or your log entries will be incorrect. If you intend to use WSJT-X without CAT control then you should stick to Tx audio offsets above 1500 Hz to make sure any audio harmonics are eliminated. Either VOX or a wire-ored hardware PTT arrangement using RTS or DTR on a pair of serial ports will get you PTT. WSJT-X will run fine without CAT control of a rig so long as you can still control PTT. If the N3FJP FD logging application does not support one of the rig server programs that WSJT-X also supports (Hamlib rigctld, Omni-Rig, or something that looks like a rig to each application but is more than a dumb serial port splitter), then you will have to disable rig control in one application or the other. You cannot have two applications directly using the same rig for CAT control. Get a "Rig Control Error" box asking to set up the rig I have followed the various tutorials and My understanding is to start N3FJP > WSJT-X > JTAlert I guess hamlib must be built into WSJT-X and I don't use itįor Field Day. ![]() While exchanging VFOs." Subsequent tests fail for frequency Saying "Rig Failure Hamlib error:Command rejected by the rig TEST CAT, the rig changes to 28.335.19 and a box pops up I go to configurations, all settings are correct, when I hit The error is that N3FJP is setup to control the rig, if youĬould turn that off, and let WSJT-X control the rig, you'll be Transition time between modes and not have to shut everything downĪnd restart the whole works with different sequences betweenīuilt into the WSJT-X executable. Or fldigi as needed to use the digital modes. Start N3FJP and leave it running all the time, then start WSJT-X Running and doing all my logging directly through N3FJP. The time I will be running phone, with WSJT-X and fldigi not I was doing is running FT8, this would be fine. Only when N3FJP is running do I have an issue. When I start WSJT-X, I get a "Rig Control Error" box asking to set up the rig parameters (IC-7300). I have followed the various tutorials and instructions for setting these up. My understanding is to start N3FJP > WSJT-X > JTAlert in that order. I guess hamlib must be built into WSJT-X and I don't use it otherwise. I suggest that the reason you're getting the error is that N3FJP is setup to control the rig, if you could turn that off, and let WSJT-X control the rig, you'll be fine.Īdditionally, if I go to configurations, all settings are correct, when I hit TEST CAT, the rig changes to 28.335.19 and a box pops up saying "Rig Failure Hamlib error:Command rejected by the rig while exchanging VFOs." Subsequent tests fail for frequency change and mode change. Try starting WSJT-X, JT-Alert, then N3FJP. ![]() Hamlib is built into the WSJT-X executable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |