Hello All,
My configuration is:
- WSJT-X 2.1.2 on Windows 10 Home, "Split Operation"="Rig",
"Mode"="Data/Pkt"
- Icom IC-7300
- OmniRig 1.19 with "IC-7300-DATA" rig profile
I recently noticed that sometimes there is no output power when WSJT-X puts
the rig in transmit mode.
When start
>From time to time there are stations who are significantly unsynchronized
with the FT8 cycle, as can be seen in the DT column. As a result, making
connections by and with these stations is difficult. It is likely that the
operators are not aware of the situation. Some may also be are unable to
fix
your rig has a suitable
> AFSK data mode. Note also that Omni-Rig is quite limited in the rig
> modes that it supports and the Omni-Rig .ini file for your rig may
> require modifications to support a suitable USB data mode, this is
> particularly so with rigs that have both AFSK and FSK dat
When using Omni-Rig, I believe WSJT-X Does not control the operation mode
of the IC-7300 regardless of the "Split Operation" selection.
As far as I can tell, WSJT-X assumes the user is responsible for selecting
"USB-D" for both VFO-A and VFO-B.
Here is a scenario that demonstrated this:
- Change
Agreed.
In addition, as a CQ caller, you have no control over the order in which
WSJT-X decoded the received calls and who's first.
AFAIK, the "persistent" caller can remain 1st if he calls on a frequency
lower than the other callers and the signal is strong enough to be decoded
on the first pass
On Sun, Dec 1, 2019 at 2:22 PM Larry Burke wrote:
> >> You have no idea if they are calling blind until you send them TX2 and
> they don't send you TX3.
>
>
>
> While I agree that there are some who call blind, there are other reasons
> for the caller not replying with a TX3… QSB being the one th
hts.
> Elevated rights are only needed to access protected files and directories
> and other protected system resources, none of which are needed for basic
> user applications like log keeping, CAT control, audio streams, or
> accessing remote network resources.
>
> 73
> Bill
> G
Bill,
Yes, I've tried the non-administrative runs too. In fact, none of the
possible combinations enabled both programs to communicate with Omni-Rig.
73
Zeev
4X5ZS
On Wed, Nov 20, 2019 at 8:01 PM Bill Somerville
wrote:
> On 20/11/2019 17:52, Zeev Stadler wrote:
> > Hello Bill,
quot;, and WSJT-X is unable to communicate with the rig.
Please let me know how can I further help clarify the problem.
73
Zeev
4X5ZS
On Tue, Nov 19, 2019 at 5:31 PM Zeev Stadler wrote:
> This is my first post here. I've tried the Yahoo group, but that did not
> help. Hopefully the d
I would appreciate a word from the developers - should we expect to have
WSJT-X in parallel with other programs that use Omni-Rig?
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On Tue, Nov 19, 2019 at 7:08 PM Doug Bates wrote:
> Freq. info is passed to Log4OM via UDP as well as the logging. Read the
> Log4OM manual.
>
Hi Doug,
I followed the manual, but I do not see the frequency information in Log4OM.
The settings in both WSJT-X and Log2OM refer to 'ADIF UDP' which
s well as
> the logging. Read the Log4OM manual.
>
> On Tue, Nov 19, 2019, 10:38 AM Zeev Stadler
> wrote:
>
>> This is my first post here. I've tried the Yahoo group, but that did not
>> help. Hopefully the developers here can shed some light on the expected
>>
This is my first post here. I've tried the Yahoo group, but that did not
help. Hopefully the developers here can shed some light on the expected
behavior.
Omni-Rig main feature is "multithreading: multiple programs, written by
different authors in different languages, can control the radio via
Omn
13 matches
Mail list logo
