FWIW, Using a Flex 6600 and MacOS Mojave, xDAX and xCAT - no problems like 
those reported below. CPU usage is in line with previous versions, CAT and DAX 
operation, even via SmartLink, work smoothly.

Geo/KF2T

> On Dec 13, 2018, at 10:27 AM, Al <[email protected]> wrote:
> 
> I also have seen the problem and have come to believe that it related the 
> CAT.. 
> If I use a traditional CAT ( comport) with Kenwood TS480, I do not have this 
> problem. If is use the Flex interface for CAT  this problem returns.. 
> You should also note that the CPU usage for the WSJT task is about 10 times 
> normal, which might indicate some kind of looping fault in the program.
> 
> AL, K0VM
> 
> On 12/12/2018 2:53 PM, bergeracb--- via wsjt-devel wrote:
>> Have not seen my problem listed yet, so I will try to explain what I see.
>> Every once in a while operating, the TX function stops working. The
>> Transmitter goes into transmit but there is no audio drive so no RF is
>> produced. WSJT-X thinks it is working. If I shut down WSJT-X and try
>> to restart the program I get the message that their is another instance
>> of WSJT-X running and the program won't start. Checking the task
>> manager under the Running APPS shows no WSJT-X app listed.
>> However if I look in the Running BACKGROUND tasks, WSJT-X
>> has been moved from the APPS to the BACKGROUND tasks.
>> using END TASK there and then I can restart the program and use
>> the transmitter again. Can't decide if it is a WSJT-X problem or a
>> FLEX 6700 and DAX problem. but I have tried shutting  down and
>> restarting DAX several times without any success. Of course shutting
>> down and restarting the 6700 (after the background WSJT-X task is
>> closed)  also fixes the problem.  I'm wondering if any of the other
>> Flex owner see this problem? I have the work around so right now
>> it is just a nuisance.
>> 73 Al Berger N4AB
>> 
>> 

_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to