Date   

Re: FT1000mp macro "USER" for RCP

Carlo, I4HRH
 

Hi Svein LA3PU,

Ok thanks, but I have already configured menu 8-6 and it works ok.

I have to press the "USER" button by hand.

I would like to do it automatically with the macro, in the same way that I set the USB / LSB / RTTY / CW / etc mode.

"USER" I have to do it by hand, with my finger !

Maybe the macro for that service doesn't exist !

73 'de Carlo I4HRH


Il 19/04/2020 19:56, Svein Henriksen ha scritto:

Go to menu 8-6 and set as follows.

Menu: 8-6

Mode: PKT

Disp Offset: 0

RX PLL: 1500

RX CAR: 453.450

TX PLL: 1500

TX CAR : 453.450

RTTY Offset : 0

EASY set : Off

 

Then Select PKT and then press USR.

LSB will still be lit but it is now USB.

This setup has worked fine on my FT1000MP for a long time.

 

73 de LA3PU Svein

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Carlo, I4HRH
Sent: 19. april 2020 19:14
To: hamlogger@groups.io
Subject: Re: [hamlogger] FT1000mp macro "USER" for RCP

 

Hi John N7TK, thanks for the reply.

In the FT1000mp there is no PKT-USB mode, only PKT-LSB and PKT-FM.

To configure the PKT-USB mode I have to use the option that the FT1000mp offers me: I have to configure PKT-USB with the USER function.

I try to start this mode automatically with RCP or anchors with UDP macros for JTDX.

I searched the command in the manual without success. I fear there is no such possibility.

Thanks John, 73 de Carlo I4HRH

       

 

 

Il 19/04/2020 17:59, John Owens ha scritto:

Not sure what you are asking. I have an RCP that works with L32� for the FT-1000MP and also the FTDX-5000. I am using a modified version of it for my FTDX-101MP.

John Owens -� N7TK


Virusfri. www.avg.com


Re: FT8 Cherrypicking - "did not switch to transmit"

Gary Hinson
 

Hello there.

 

I haven’t noticed the ‘failed to transmit’ messages lately … but that’s mostly because I’m hardly using the cherry-picker, not the boring full-auto robot anyway.  The point-n-click manual picker is more useful to chase whatever DX has caught my eye, without either hounding him continuously or watching the decodes closely for my brief opportunities to call.

 

If and when I see ‘failed to transmit’, I stop and restart both JTDX and Logger32 to clear it.  I find expressing some choice Anglo-Saxon words smooths the process: the challenge is to find enough words to fill the gap without repetition or deviation.

 

Like me, my PC is still a bloater.  As if Windows isn’t enough, I’m now running the Folding@Home thing to model protein folding and mop up any remaining unused CPU cycles.  I just have to remember to set it to “Light” during the daytime when I need the CPU to do FT8 and Other Stuff  since the “Only When Idle” setting evidently thinks I am never idle, and its true I’m always on the go.  Busy busy.

 

The main cause of PC business is FT8 decoding on a wide-open band, with loads of signals filling the UDP band map thanks to having a decent RX and a DX antenna in a rural QTH (as opposed to Bob The Cave Dweller).  The clue is to watch the Decode button light up at the end of each FT8 period: if it stays lit for ~two seconds or more, the system is clearly struggling to process each batch of messages in time.  You may also notice decodes from your QSO partners arriving after your system has started transmitting a message back to them, which confuse can autosequencing the (there be bugs).  And the end-of-cycle CPU peaks are obvious using Resource Monitor.

 

A more annoying sporadic bug on my system causes the JTDX waterfall to go black with no signals or noise displayed … although the decodes continue so it appears to be just a display problem.  Without the working waterfall, I can’t keep an eye on my transmit frequency for QRM but I can continue FT8ing ‘blind’.  Again, restarting JTDX and Logger32 clears it for another few hours and is another chance to rehearse my vocabulary.  [I haven’t reported that bug to Yuri yet: due to the language barrier, I’m taking it one bug at a time.  So far, it has taken several attempts over many months to get him to even acknowledge that there might conceivably be leeetle bugs in the autosequencer. I think he’s more interested in tweaking the decoders to make them even more sensitive, and fair enough.  Autosequencing is supposed to be an operating aide, not an op replacement.]

 

I’m using recent/current betas of Logger32 and JTDX.  I launch both programs from adjacent task bar icons, so after two quick clicks the race is on.

 

73 GL

Gary@home  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 20 April 2020 03:18
To: hamlogger@groups.io
Subject: Re: [hamlogger] FT8 Cherrypicking - "did not switch to transmit"

 

Vince, my PC is a user of JTDX. Maybe once every couple of weeks I will see the dreaded 'failed to transmit' message. Gary <ZL2IFB> can comment more accurately on his findings, but he was plagued by these messages. We compared CPU utilization of our PCs, and his was (by comparison) very high compared to mine. Apparently his PC is loaded with every bloatware package known to man. He worked on trimming things down. Uncharacteristically for him, he has been very quiet on the subject lately. As a reference, my PC, with JTDX and Logger32 running idles at about 6% with decode time peaks of 16%. JTDX alone is maybe 1% less.

 

A word of caution, JTDX has adopted a default directory policy that follows the release number. For example, the latest 64bit version rc150_4 defaults to  c:\jtdx64\150_4\bin\ ... It is not uncommon for the Logger32 menu to start JTDX to be pointing to a version less than the most recent.

 

SeventyThree(s).

 

PS. See, I told you BREXIT would be painless. I'll bet it hasn't crossed your mind once in the past two months 😀

On April 19, 2020 at 6:27 AM Vince Shirley <vince.g0orc@...> wrote:

Hi all,

I've used WSJT-X from day 1 wth no issues but after several recommendations have switched to JTDX.

Everything seems to work OK but I intermittently get a "JTDX did not switch to transmit" message.

In other words, sometimes it works, sometimes it doesn't.

I've tried a variet of adjustment and have now run out of ideas.  A search of the archives reveals only one other conversation ablut this, which seemed to be inconclusive.

Anyone any ideas where I'm going wrong?

Vince G0ORC


 


Re: FT1000mp macro "USER" for RCP

Svein Henriksen
 

Go to menu 8-6 and set as follows.

Menu: 8-6

Mode: PKT

Disp Offset: 0

RX PLL: 1500

RX CAR: 453.450

TX PLL: 1500

TX CAR : 453.450

RTTY Offset : 0

EASY set : Off

 

Then Select PKT and then press USR.

LSB will still be lit but it is now USB.

This setup has worked fine on my FT1000MP for a long time.

 

73 de LA3PU Svein

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Carlo, I4HRH
Sent: 19. april 2020 19:14
To: hamlogger@groups.io
Subject: Re: [hamlogger] FT1000mp macro "USER" for RCP

 

Hi John N7TK, thanks for the reply.

In the FT1000mp there is no PKT-USB mode, only PKT-LSB and PKT-FM.

To configure the PKT-USB mode I have to use the option that the FT1000mp offers me: I have to configure PKT-USB with the USER function.

I try to start this mode automatically with RCP or anchors with UDP macros for JTDX.

I searched the command in the manual without success. I fear there is no such possibility.

Thanks John, 73 de Carlo I4HRH

       

 

 

Il 19/04/2020 17:59, John Owens ha scritto:

Not sure what you are asking. I have an RCP that works with L32 for the FT-1000MP and also the FTDX-5000. I am using a modified version of it for my FTDX-101MP.

John Owens - N7TK


Virusfri. www.avg.com


Re: N2AMG sync software removed (on purpose) but have issues with Eqsl tag

Bob
 

Try this: On the Logbook Entry Window, right click on ant entry field. Click SETUP | QSLING & QSO EXPORT | REMOVE EXTERNAL EXPORT QSL FLAGS. Is the Export QSO FOR EQSL PROCESSING checked? If so, UNcheck it and click APPLY. SeventyThree(s).

On April 19, 2020 at 11:38 AM "John GM0OPS via groups.io" <j.m.dundas@...> wrote:

Hi Folks

I have removed N2AMG Log32sync software from my pc.  The issue I now have is that for some reason when a contact is logged from WSTJ it then appears in the log with the SENT EQSL Tick.

How can I stop this happening as its a pain having to go in and untick the entry. I also have a contest to import and dont want to do it until I know that this issue has been resolved as I dont want to go through 100s of contacts to remove then Tick it to Send Eqsl

Thanks in advance

John
GM0OPS

 


Re: WPX mismatch with LOTW

jim watkins
 

Hi Bob,

Back in 1991, I worked 1A0KM on 20M and 40M. In 2019 I worked 1A0C on 20M.

SET/SHOW AWARD CREDITS, there are 8 boxes and inside each box is DXCC_CW and IOTA. On the bottom is 1 check mark in LOTW Received.

CQWPX is not in any of the boxes.

Thanks
Jim

Jim Watkins 


VA3XOV / VO1SF

Never drive faster than your Guardian Angel can fly..



On Sunday, April 19, 2020, 09:22:11 a.m. EDT, Bob <k4cy@...> wrote:


Now I've had another cup of coffee, made a dummy logbook of faux 1A0 QSOs, and changed my mind. Multiple QSOs with a station are listed/worked/counted. Find the 2019 1A0C QSO in the Logbook and right click on it. On the menu click SET/SHOW AWARD CREDITS. Is CQWPX checked somewhere? SeventyThree(s).
On April 18, 2020 at 9:16 PM "jim watkins via groups.io" <james_vo1sf@...> wrote:

I got Logger32 and LOTW "DXCC" with the correct numbers. Perfect match. YEAH!!!

My WPX is gone haywire. LOTW shows 1565 and Logger32 shows 1281.The first Prefix in LOTW is 1A0 and the QSO was with 1A0C on 20M from last year. I checked Logger32 and I have 3 QSO with 1A0, 2 from 1991 (neither one LOTW QSL Received), and 1 from last year. When I open up Logger32 WPX I show QSO's with Prefix 1A0 on 20M and 40M. When I hit Worked on 20M, only the QSO from 1991 shows up, not the one from last year. A log search for 1A0C and it shows LOTW QSL Received. Now, if it is received, why is it not showing up in my WPX total? 

I wonder if there is something simple I am over-looking? Any comments or suggestions would be appreciated.

73s

Jim Watkins 


VA3XOV / VO1SF

Never drive faster than your Guardian Angel can fly..


 


Re: WPX mismatch with LOTW

jim watkins
 

Hi Aki,

I have;

Mixed Mode , All Operators , LOTW Only , All Credits

If I set it the way you have in your screen shot (All QSL Types), it shows 2031 Credits, but I should only have 1565.

73s

Jim Watkins 


VA3XOV / VO1SF

Never drive faster than your Guardian Angel can fly..



On Saturday, April 18, 2020, 10:53:05 p.m. EDT, ja1nlx <ayoshida0205@...> wrote:


Jim

You select correct options ?

73


On 2020/04/19 10:16, jim watkins via groups.io wrote:
I got Logger32 and LOTW "DXCC" with the correct numbers. Perfect match. YEAH!!!

My WPX is gone haywire. LOTW shows 1565 and Logger32 shows 1281.The first Prefix in LOTW is 1A0 and the QSO was with 1A0C on 20M from last year. I checked Logger32 and I have 3 QSO with 1A0, 2 from 1991 (neither one LOTW QSL Received), and 1 from last year. When I open up Logger32 WPX I show QSO's with Prefix 1A0 on 20M and 40M. When I hit Worked on 20M, only the QSO from 1991 shows up, not the one from last year. A log search for 1A0C and it shows LOTW QSL Received. Now, if it is received, why is it not showing up in my WPX total? 

I wonder if there is something simple I am over-looking? Any comments or suggestions would be appreciated.

73s

Jim Watkins 


VA3XOV / VO1SF

Never drive faster than your Guardian Angel can fly..

--
73 de aki
JA1NLX


Re: FT1000mp macro "USER" for RCP

Carlo, I4HRH
 

Hi John N7TK, thanks for the reply.

In the FT1000mp there is no PKT-USB mode, only PKT-LSB and PKT-FM.

To configure the PKT-USB mode I have to use the option that the FT1000mp offers me: I have to configure PKT-USB with the USER function.

I try to start this mode automatically with RCP or anchors with UDP macros for JTDX.

I searched the command in the manual without success. I fear there is no such possibility.

Thanks John, 73 de Carlo I4HRH

       


Il 19/04/2020 17:59, John Owens ha scritto:

Not sure what you are asking. I have an RCP that works with L32� for the FT-1000MP and also the FTDX-5000. I am using a modified version of it for my FTDX-101MP.

John Owens -� N7TK


Re: N2AMG sync software removed (on purpose) but have issues with Eqsl tag

Tom Wylie
 

What is your logging software John, as I don't think wsjt has anything to do with it.

Tom
GM4FDM 

On Sun, 19 Apr 2020, 16:38 John GM0OPS via groups.io, <j.m.dundas=btinternet.com@groups.io> wrote:
Hi Folks

I have removed N2AMG Log32sync software from my pc.  The issue I now have is that for some reason when a contact is logged from WSTJ it then appears in the log with the SENT EQSL Tick.

How can I stop this happening as its a pain having to go in and untick the entry. I also have a contest to import and dont want to do it until I know that this issue has been resolved as I dont want to go through 100s of contacts to remove then Tick it to Send Eqsl

Thanks in advance

John
GM0OPS


Re: Searchable Logger32 Manual

Hew Lines
 

To my knowledge, there is no actual Logger32 "Manual" if you are thinking of a "User Manual" .

There are three versions of the Logger32 Helpfiles, Logger32.chm, Logger32.docx and Logger32.pdf. Each one of them is "Searchable" for any "word" or "Words" your heart desires by using each individual documents "Search" capabilities.

73 Hew VA7HU
Helpfile Editor


Re: Searchable Logger32 Manual

Hew Lines
 

To my knowledge, there is no actual Logger32 "Manual" if you are thinking of a "User Manual" . There are three versions of the Logger32 Helpfiles, Logger32.chm,  Logger32.docx and Logger32.pdf. Each one of them is "Searchable" for any "word" or "Words" your heart desires by using each individual documents "Search" capabilities.

73 Hew VA7HU
Helpfile Editor



On 2020-04-19 9:19 a.m., Herbert Slade wrote:
Rick,
I followed your directions up to Search, where you suggested I enter what I am looking for.  I tried "Logger32 manual" and "manual", followed by enter, and/ or pressing the search button (which changed color but did nothing else).  Each time I got a long string of items that had nothing to do with a manual.

I am not complaining, and I am grateful for you help, but can you please tell me what I need to specify when I search, for reference to a "searchable" version of a Logger32 manual that I can download?
73,
Herb Slade AA2BF


Re: FT1000mp macro "USER" for RCP

Bob
 

John, if you look in the \Logger32 directory, you will find a file called RadioPanel.INI This is the file where all your fancy Radio Control Panel macros are stored. If your macros work for an FT-1000MP, that's the file that's being requested. SeventyThree(s).

PS. Interesting that someone with an eMail address of yaesu.org was also requesting a copy 😮

On April 19, 2020 at 11:59 AM John Owens <jcowens1@...> wrote:

Not sure what you are asking. I have an RCP that works with L32  for the FT-1000MP and also the FTDX-5000. I am using a modified version of it for my FTDX-101MP.

John Owens -  N7TK

 


Re: Searchable Logger32 Manual

Jim Altman
 

Let’s try this again.

 

  1. Run Logger32
  2. Across the top of the program are the words File Tools View Awards Setup Utilities and Help
  3. Click on Help
  4. A box of items drops down which will include the word Help
  5. Click on Help
  6. Up pops a manual and on a tab near the right is the word Search
  7. Click on search
  8. Type your search term in the box for that purpose

 

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Herbert Slade
Sent: Sunday, April 19, 2020 12:19 PM
To: hamlogger@groups.io
Subject: [hamlogger] Searchable Logger32 Manual

 

Rick,

I followed your directions up to Search, where you suggested I enter what I am looking for.  I tried "Logger32 manual" and "manual", followed by enter, and/ or pressing the search button (which changed color but did nothing else).  Each time I got a long string of items that had nothing to do with a manual.



I am not complaining, and I am grateful for you help, but can you please tell me what I need to specify when I search, for reference to a "searchable" version of a Logger32 manual that I can download?

73,

Herb Slade AA2BF


Searchable Logger32 Manual

 

Rick,
I followed your directions up to Search, where you suggested I enter what I am looking for.  I tried "Logger32 manual" and "manual", followed by enter, and/ or pressing the search button (which changed color but did nothing else).  Each time I got a long string of items that had nothing to do with a manual.

I am not complaining, and I am grateful for you help, but can you please tell me what I need to specify when I search, for reference to a "searchable" version of a Logger32 manual that I can download?
73,
Herb Slade AA2BF


Re: FT1000mp macro "USER" for RCP

John Owens
 

Not sure what you are asking. I have an RCP that works with L32  for the FT-1000MP and also the FTDX-5000. I am using a modified version of it for my FTDX-101MP.

John Owens -  N7TK


N2AMG sync software removed (on purpose) but have issues with Eqsl tag

John GM0OPS
 

Hi Folks

I have removed N2AMG Log32sync software from my pc.  The issue I now have is that for some reason when a contact is logged from WSTJ it then appears in the log with the SENT EQSL Tick.

How can I stop this happening as its a pain having to go in and untick the entry. I also have a contest to import and dont want to do it until I know that this issue has been resolved as I dont want to go through 100s of contacts to remove then Tick it to Send Eqsl

Thanks in advance

John
GM0OPS


Re: FT8 Cherrypicking - "did not switch to transmit"

Bob
 

Vince, my PC is a user of JTDX. Maybe once every couple of weeks I will see the dreaded 'failed to transmit' message. Gary <ZL2IFB> can comment more accurately on his findings, but he was plagued by these messages. We compared CPU utilization of our PCs, and his was (by comparison) very high compared to mine. Apparently his PC is loaded with every bloatware package known to man. He worked on trimming things down. Uncharacteristically for him, he has been very quiet on the subject lately. As a reference, my PC, with JTDX and Logger32 running idles at about 6% with decode time peaks of 16%. JTDX alone is maybe 1% less.

A word of caution, JTDX has adopted a default directory policy that follows the release number. For example, the latest 64bit version rc150_4 defaults to  c:\jtdx64\150_4\bin\ ... It is not uncommon for the Logger32 menu to start JTDX to be pointing to a version less than the most recent.

SeventyThree(s).

PS. See, I told you BREXIT would be painless. I'll bet it hasn't crossed your mind once in the past two months 😀

On April 19, 2020 at 6:27 AM Vince Shirley <vince.g0orc@...> wrote:

Hi all,

I've used WSJT-X from day 1 wth no issues but after several recommendations have switched to JTDX.

Everything seems to work OK but I intermittently get a "JTDX did not switch to transmit" message.

In other words, sometimes it works, sometimes it doesn't.

I've tried a variet of adjustment and have now run out of ideas.  A search of the archives reveals only one other conversation ablut this, which seemed to be inconclusive.

Anyone any ideas where I'm going wrong?

Vince G0ORC

 


Re: WPX mismatch with LOTW

Bob
 

Now I've had another cup of coffee, made a dummy logbook of faux 1A0 QSOs, and changed my mind. Multiple QSOs with a station are listed/worked/counted. Find the 2019 1A0C QSO in the Logbook and right click on it. On the menu click SET/SHOW AWARD CREDITS. Is CQWPX checked somewhere? SeventyThree(s).

On April 18, 2020 at 9:16 PM "jim watkins via groups.io" <james_vo1sf@...> wrote:

I got Logger32 and LOTW "DXCC" with the correct numbers. Perfect match. YEAH!!!

My WPX is gone haywire. LOTW shows 1565 and Logger32 shows 1281.The first Prefix in LOTW is 1A0 and the QSO was with 1A0C on 20M from last year. I checked Logger32 and I have 3 QSO with 1A0, 2 from 1991 (neither one LOTW QSL Received), and 1 from last year. When I open up Logger32 WPX I show QSO's with Prefix 1A0 on 20M and 40M. When I hit Worked on 20M, only the QSO from 1991 shows up, not the one from last year. A log search for 1A0C and it shows LOTW QSL Received. Now, if it is received, why is it not showing up in my WPX total? 

I wonder if there is something simple I am over-looking? Any comments or suggestions would be appreciated.

73s

Jim Watkins 


VA3XOV / VO1SF

Never drive faster than your Guardian Angel can fly..


 


Re: Remoterig RRC1258 Winkeyer fails with CW machine

tk5ep
 

HI,

I noticed that when i run Wintest before running Logger32, evrything works fine !

Maybe something to do with a a driver or sys file that changes something in the Logger32 configuration ?

Thanks and  73,
Patrick.


Re: WPX mismatch with LOTW

Bob
 

It looks like things are not working correctly for the WPX Award. I did a quick test here, and notice that a particular callsign is only checked/listed/counted once. So, in your example of 1A0, I assume one of the two unconfirmed calls you worked back in 1991 was 1A0C. I will investigate further. SeventyThree(s).

On April 18, 2020 at 9:16 PM "jim watkins via groups.io" <james_vo1sf@...> wrote:

I got Logger32 and LOTW "DXCC" with the correct numbers. Perfect match. YEAH!!!

My WPX is gone haywire. LOTW shows 1565 and Logger32 shows 1281.The first Prefix in LOTW is 1A0 and the QSO was with 1A0C on 20M from last year. I checked Logger32 and I have 3 QSO with 1A0, 2 from 1991 (neither one LOTW QSL Received), and 1 from last year. When I open up Logger32 WPX I show QSO's with Prefix 1A0 on 20M and 40M. When I hit Worked on 20M, only the QSO from 1991 shows up, not the one from last year. A log search for 1A0C and it shows LOTW QSL Received. Now, if it is received, why is it not showing up in my WPX total? 

I wonder if there is something simple I am over-looking? Any comments or suggestions would be appreciated.

73s

Jim Watkins 


VA3XOV / VO1SF

Never drive faster than your Guardian Angel can fly..


 


Re: No Spots on 40 meters

Bob
 

I tried you configuration - Time od day band blocking enabled, but no bands selected as blocked. No problem here. 40M DX Spots received as expected. SeventyThree(s).

On April 18, 2020 at 7:43 PM Neil Rowe <va6ak@telus.net> wrote:


Hi Bob;

Thanks for the reply. I do see 40 M spots in the Telnet window. I have 40 M in my bandplan and attached a jpg in my original message showing that. I have no time of day blocking options set.
Interesting I just checked the blocking options again, and the block bands at preset time was checked, but when I clicked on set up band blocking times, none of the bands or blocking times were checked. When I unchecked Block Bands at preset time, 40 M spots started showing up, strange behaviour?

Regards

Neil VA6AK

3301 - 3320 of 83004