[wsjt-devel] Auto-logging for iOS compiuters

2024-02-20 Thread Marty Wayne via wsjt-devel
I have seen and heard of programs that automatically log a contact to LoTW but 
as far as I can determine, they are all .exe applications are there any for iOS?

Marty Wayne
mcway...@comcast.net




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Not sure if an issue

2024-02-13 Thread Marty Wayne via wsjt-devel
I have had the same issue with FT-4/8.  I leave my WSJT running and freq town 
to 40M over night.  At first use in the morning I need to restart WSJT to be 
able to transmit.

MacBook Pro
Ventura 13.6.4
FT-1000MP

73,

Marty, W6NEV
_ . ... _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023


> On Feb 13, 2024, at 2:14 AM, David Hilton-Jones via wsjt-devel 
>  wrote:
> 
> Twice now I've had WSJT and QMAP (via SDRconsole) running for several hours
> without doing anything, and then when I tried to click on station in Active
> Stations window nothing happened. Relaunched all programmes and worked fine.
> 
> Seems it didn't like running in idle for a long time.
> 
> 
> Just in case anybody else has seen this
> 
> David, G4YTL
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Auto logging to QRZ.COM

2023-12-07 Thread Marty Wayne via wsjt-devel
Is there a way to use UDP or other method to automatically log to QRZ.com log 
book?

Marty Wayne
mcway...@comcast.net




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Power Slide Bar

2022-12-30 Thread Marty Wayne via wsjt-devel
Sorry.  Operating FT-8 and FT-4.  I haven’t used other modes.

Marty Wayne
mcway...@comcast.net
408-234-8023

> On Dec 30, 2022, at 11:18 AM, Marty Wayne  wrote:
> 
> Equipment
>   FT-1000MP
>   SignaLink USB
>   MacBook Pro
>   Ventura 13.1WSJT-X v2.5.4
> Issue
>   When adjusting power using the PWR slide bar, The curser arrow moves 
> opposite direction from direction I’m  moving my mouse.  The curser remains 
> at lower end of scale although the power set inmates correctly.
> 
> Do I have something configured incorrectly?
> 
> 73,
> 
> Marty, W6NEV
> _ . .   .   . _ _   _ . . . .   _ .   .   . . . _
> mcway...@comcast.net
> 408-234-8023
> 



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Power Slice Bar

2022-12-30 Thread Marty Wayne via wsjt-devel
Equipment
   FT-1000MP
   SignaLink USB
   MacBook Pro
   Ventura 13.1WSJT-X v2.5.4
Issue
   When adjusting power using the PWR slide bar, The curser arrow moves 
opposite direction from direction I’m  moving my mouse.  The curser remains at 
lower end of scale although the power set inmates correctly.

Do I have something configured incorrectly?

73,

Marty, W6NEV
_ . .   .   . _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] V2.5.4 Auto Seq Issue

2022-09-24 Thread Marty Wayne via wsjt-devel
When using WSJTx 2.5.4, the auto sequencer frequently does not auto step to 
next TX.  Using V2.5.2, everything works dine.

Radio: Yaesu FT-1000MP
Comp: MacBook Pro
Processoe: 2.8 GHz Quad Core Intel Core i7
Memory: 16 GB 2133 MHz LPDDR3
Graphics: Intel HD Graphics 630 1536 MB

Any thoughts?

73,

Marty, W6NEV
_ . .   .   . _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Two small Issues

2022-08-04 Thread Marty Wayne via wsjt-devel
Hi,

I seem to have two small issues.

1.  Every once in a while when the logging window opens, the “OK” button shows 
up grayed out but still enters the QSO into the log.  At other times, it shows 
up as blue and also logs the contact.  This seems rather random.

2.  During a contact or while calling CQ, I get no responses.  When I click 
Halt TX or un-click the Enable TX button, I get a response from some station.  
This happens more frequently than purely random but not frequently to be a hard 
issue.

I’ve been using WSJTx since 2018 and as I recall, these have been there.

Any thoughts?

73,

Marty, W6NEV
_ . .   .   . _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Hamlib Error

2022-07-22 Thread Marty Wayne via wsjt-devel
I can’t even get the radio and wsjt-x to communicate.  I misspoke when I said 
that the Hamlib error happened while using FT8.  Actually, I had taken a short 
break.  I believe I shut down wsjt-x and restarted when I returned.  That is 
when aI started getting the Hamlib error.  I hadn’t changed the power as there 
was no communication. In checking the sound preferences, CODEC does not show up 
to select.

Does that mean anything?

Marty Wayne
mcway...@comcast.net
408-234-8023

> On Jul 22, 2022, at 5:56 AM, robert evans LAST_NAME via wsjt-devel 
>  wrote:
> 
> As a diagnostic.. 
> 
> While sending CQ for example..
> 
> Reduce the transmit power,
> by both audio and transmitter settings and see
> if the phenomenon goes away at lower powers.
> 
> If with the output minimized the phenomenon
> persists then it is probably not RFI related.
> 
> If you find a reduced output power that does
> not exhibit the phenomenon, then it is probably
> RFI related. And, you have a clue as how much
> shielding and isolation you might need.
> 
> Operating at the reduced power while introducing
> changes gives you method of testing improvements.
> 
> BCNU DE N2LO~>
> 
>> On 07/22/2022 12:07 AM Black Michael via wsjt-devel 
>>  wrote:
>> 
>> 
>> If it runs at startup but fails during/after transmit than it is probably 
>> RFI.
>> 
>> Here are some potential solutions -- ordered by cost.
>> 
>> #1 Free - Move USB cables to another port -- some ports are more susceptible 
>> than others.
>> #2 Free -- Check your grounding system.  rod-outside-the-shack is a common 
>> problem when it's not bonded to the main house ground. 
>> http://www.k9yc.com/GroundingAndAudio.pdf 
>> #3 Add some USB shield isolators (see my QRZ page).
>> #4 Good USB cables like this
>> https://www.amazon.ca/Tripp-U023-006-Device-Ferrite-Chokes/dp/B003MQ29B2/ref=sr_1_5?crid=11YRNPWDVWGCU=usb+cable+with+choke=1658187349=usb+cable+with+choke%2Caps%2C139=8-5
>>  
>> #5 Maybe free (if you have chokes...otherwise can get a bit costly) -- add 
>> chokes to USB cables first, then all other cables including power, ethernet, 
>> and control cables. 
>> Fair-Rite torroids are good quality -- do NOT buy cheap Chinese ones --  
>> https://www.fair-rite.com/product/toroids-5943003801/  You can use clip-ons 
>> but torroids allow multiple wraps and give better results.
>> https://www.fair-rite.com/product/round-cable-snap-its-431176451/ 
>> I couldn't find type 31 torroids at Fair-Rite as of 20220721 but Palomar has 
>> some 
>> palomar-engineers.com/ferrite-products/ferrite-cores/ferrite-ring-toroid-combo-pack/
>> 
>> 
>> Mike W9MDB
>> 
>> 
>> 
>> 
>> On Thursday, July 21, 2022 at 12:29:33 PM CDT, Marty Wayne via wsjt-devel 
>>  wrote:
>> 
>> 
>> I was working 20 Meter FT-4 and at one point I got a Hamlib error, 
>> communication timed out.  See report below.  Im not computer savvy. What 
>> might be the issue? 
>> 
>> Rig-FT-1000MP 
>> iOS 12.5 
>> SignaLink USB interface 
>> WSJTx 2.5.2 
>> WSJTx 2.5.4 
>> 
>> Hamlib error: Communication timed out 
>> rig_get_vfo: returning -5(Communication timed out 
>> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out 
>> read_block_generic(): Timed out 0.402040 seconds after 0 chars 
>> ft1000mp_get_update_data: Timeout 
>> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo 
>> return(-5) Communication timed out 
>> ft1000mp_get_update_data: Timeout 
>> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out 
>> read_block_generic(): Timed out 0.402040 seconds after 0 chars 
>> ft1000mp_get_update_data: Timeout 
>> ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
>> return(-5) Communication timed out 
>> read_block_generic(): Timed out 0.402040 seconds after 0 chars 
>> ft1000mp_get_update_data: Timeout 
>> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo 
>> return(-5) Communication timed out 
>> ft1000mp_get_update_data: Timeout 
>> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out 
>> read_block_generic(): Timed out 0.402040 seconds after 0 chars 
>> ft1000mp_get_update_data: Timeout 
>> ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
>> return(-5) Communication timed out 
>> read_block_generic(): Timed out 0.402040 seconds after 0 chars 
>> ft1000mp_get_update_data: Timeout 
>> ft1000mp_get_update_data: Timeout)rig_get_vfo: elapsed=439ms 
>&

Re: [wsjt-devel] Hamlib Error

2022-07-21 Thread Marty Wayne via wsjt-devel
I tried operating with WSJTx 2.5.2 and 2.5.4 with same issue.

73,

Marty, W6NEV
_ . .   .   . _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023

> On Jul 21, 2022, at 10:23 AM, Marty Wayne  wrote:
> 
> I was working 20 Meter FT-4 and at one point I got a Hamlib error, 
> communication timed out.  See report below.  Im not computer savvy. What 
> might be the issue?
> 
> Rig-FT-1000MP
> iOS 12.5
> SignaLink USB interface
> WSJTx 2.5.2
> WSJTx 2.5.4
> 
> Hamlib error: Communication timed out
> rig_get_vfo: returning -5(Communication timed out
> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
> Communication timed out
> ft1000mp_get_update_data: Timeout
> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
> return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
> Communication timed out
> ft1000mp_get_update_data: Timeout
> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
> return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeout)rig_get_vfo: elapsed=439ms
> rig.c(2587):rig_get_vfo return(-5) Communication timed out
> rig_get_vfo: returning -5(Communication timed out
> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
> Communication timed out
> ft1000mp_get_update_data: Timeout
> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
> return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
> Communication timed out
> ft1000mp_get_update_data: Timeout
> ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
> return(-5) Communication timed out
> read_block_generic(): Timed out 0.402040 seconds after 0 chars
> ft1000mp_get_update_data: Timeout
> ft1000mp_get_update_data: Timeout)rig_get_vfo: elapsed=439ms
> rig_get_vfo: elapsed=439ms while testing getting current VFO
> 
> Timestamp: 2022-07-21T17:16:46.329Z
> 
> 
> 
> 73,
> 
> Marty, W6NEV
> _ . .   .   . _ _   _ . . . .   _ .   .   . . . _
> mcway...@comcast.net
> 408-234-8023
> 



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Hamlib Error

2022-07-21 Thread Marty Wayne via wsjt-devel
I was working 20 Meter FT-4 and at one point I got a Hamlib error, 
communication timed out.  See report below.  Im not computer savvy. What might 
be the issue?

Rig-FT-1000MP
iOS 12.5
SignaLink USB interface
WSJTx 2.5.2
WSJTx 2.5.4

 Hamlib error: Communication timed out
rig_get_vfo: returning -5(Communication timed out
ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
Communication timed out
ft1000mp_get_update_data: Timeout
ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
Communication timed out
ft1000mp_get_update_data: Timeout
ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeout)rig_get_vfo: elapsed=439ms
rig.c(2587):rig_get_vfo return(-5) Communication timed out
rig_get_vfo: returning -5(Communication timed out
ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
Communication timed out
ft1000mp_get_update_data: Timeout
ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1249):ft1000mp_get_vfo return(-5) 
Communication timed out
ft1000mp_get_update_data: Timeout
ft1000mp.c(1675):ft1000mp_get_update_data return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeoutft1000mp.c(1675):ft1000mp_get_update_data 
return(-5) Communication timed out
read_block_generic(): Timed out 0.402040 seconds after 0 chars
ft1000mp_get_update_data: Timeout
ft1000mp_get_update_data: Timeout)rig_get_vfo: elapsed=439ms
rig_get_vfo: elapsed=439ms while testing getting current VFO

Timestamp: 2022-07-21T17:16:46.329Z



73,

Marty, W6NEV
_ . .   .   . _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Transmit Time oddity

2021-08-21 Thread Marty Wayne via wsjt-devel
An update,  This seems to happen on 20M FT4.  It appears on 20M FT8.  I have 
not checked other bands.

73,

Marty, W6NEV
_ . .   .   . _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023

> On Aug 21, 2021, at 5:10 PM, Marty Wayne  wrote:
> 
> Please see attached screen shot of the RTF Frequency window.  Why is my 
> transmit frequency off by 7 seconds?  This happens with both WSJTX 2.3.0 and 
> 2.3.1.
> 
> 
> Setup up is:
> FT-1000MP
> SignaLink USB
> MacBook Pro 15”
> macOS Big Sur v. 11.5.1
> 
> Marty Wayne
> mcway...@comcast.net
> 408-234-8023
> 



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Decode Highlighting

2021-08-16 Thread Marty Wayne via wsjt-devel
This is a rather selfish request but here it goes.

I have my New Call on Band Decode Highlights set up for indicating green.  
There isn’t an option to have highlights for new calls by band and mode.  I 
don’t know anything about coding and this may be very cumbersome to accomplish. 
 Is it possible to have this in a future release of WSJT-x?

73,

Marty, W6NEV
_ . .   .   . _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net
408-234-8023



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel