Date   

Re: FT8 bug after last update .401

Bob
 

Mike, I am thoroughly confused (it's easy to do). What exactly do you want? You want auto-lookup of callsigns when you click on a DX spot, you want auto-lookup of callsigns you manually enter in the logbook entry window, but you dont want auto-lookup of callsigns you are QSOing on WSJT-X? Do I understand correctly. 73

On November 18, 2019 at 4:08 AM Mike <ch25@...> wrote:

On Mon, Nov 18, 2019 at 09:56 AM, Bob wrote:
Try this: Click SETUP | AUTO LOOKUP and UNcheck the option AUTO INTERNET CALLSIGN LOOKUP (EXTERNAL). SeventyThree(s).
Now it does not look for qrz.com data at all.
It was working fine in .400, in .401 every time wsjtx have disabled TX logbook entry window is wiped from callsign, tx enable in wsjtx - callsign appears back. It wasn't working that way in .400
Mike

 


Re: No frequency and wrong mode

Bob
 

Ignacy, is Logger32 talking to the radio? Open the radio debug window - on the lower status bar, right click on the radio pane. Click the SHOW RADIO DEBUG WINDOW menu. There you will see the messages to and from the radio and at the top you will see the radio frequency and mode. What do you see. A picture would help. 73.

On November 19, 2019 at 7:51 PM Ignacy Misztal <no9e@...> wrote:

I use L32 at my regular QTH and everything works fine.

I installed it at my 2nd QTH. It is connected to a radio but the logging windows shows no frequency. But its shows correct band (e.g., 160M).  Logging QSO returns FREQ 0. Clicking on spots puts wrong mode. 

Ignacy, NO9E

 


Re: Set System Time API

Bob
 

Are you running Logger32 as an administrator? 73.

On November 19, 2019 at 2:14 PM Andy VA3PL <va3pl@...> wrote:

Hi there
After computer crash I have this:

Set System Time API

Client doesn't have permission.

How to fix it?

73 Andy SP9KR

 


Re: Set System Time API

Bob
 

.TheTime = GetQUInt32(data)
dim sTime as string
sTime = format$(.TheTime / 86400000, "hh:mm:ss")

SeventyThreE(s).

On November 19, 2019 at 2:14 PM Andy VA3PL <va3pl@...> wrote:

Hi there
After computer crash I have this:

Set System Time API

Client doesn't have permission.

How to fix it?

73 Andy SP9KR

 


No frequency and wrong mode

Ignacy Misztal
 

I use L32 at my regular QTH and everything works fine.

I installed it at my 2nd QTH. It is connected to a radio but the logging windows shows no frequency. But its shows correct band (e.g., 160M).  Logging QSO returns FREQ 0. Clicking on spots puts wrong mode. 

Ignacy, NO9E


Set System Time API

Andy VA3PL
 

Hi there
After computer crash I have this:

Set System Time API

Client doesn't have permission.

How to fix it?

73 Andy SP9KR


Re: TX7T location not being found

Ed Tobias
 

That fixed it, pal. Your assumption about the cause is probably correct. BTW, I managed to eek out a brief, 339, contact with JA1NUT the other evening, so the bands may be coming back. I’ll be keeping a ear out for ZM4T this weekend.

 

Ed

 

From: Gary Hinson
Sent: Monday, November 18, 2019 7:42 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] TX7T location not being found

 

Hi Ed.

 

Same here … so I re-ran the Club Log prefix update …

 

 

… which fixed it …

 

 

Maybe Club Log had an early end date for them, which someone has kindly corrected.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ed Tobias
Sent: 19 November 2019 13:31
To: hamlogger@groups.io
Subject: [hamlogger] TX7T location not being found

 

 

I noticed, this evening, that L32 no longer recognizes the location of TX7T.  It had been identifying it correctly (as FO\M) until yesterday or today. So, I’m not sure whether this problem relates to today’s sync with Club Log or with the 3.50.401 L32 update, which I just installed today.

 

Ed, KR3E

 

 

 


Re: TX7T location not being found

Gary Hinson
 

Hi Ed.

 

Same here … so I re-ran the Club Log prefix update …

 

 

… which fixed it …

 

 

Maybe Club Log had an early end date for them, which someone has kindly corrected.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Ed Tobias
Sent: 19 November 2019 13:31
To: hamlogger@groups.io
Subject: [hamlogger] TX7T location not being found

 

 

I noticed, this evening, that L32 no longer recognizes the location of TX7T.  It had been identifying it correctly (as FO\M) until yesterday or today. So, I’m not sure whether this problem relates to today’s sync with Club Log or with the 3.50.401 L32 update, which I just installed today.

 

Ed, KR3E

 

 


TX7T location not being found

Ed Tobias
 

 

I noticed, this evening, that L32 no longer recognizes the location of TX7T.  It had been identifying it correctly (as FO\M) until yesterday or today. So, I’m not sure whether this problem relates to today’s sync with Club Log or with the 3.50.401 L32 update, which I just installed today.

 

Ed, KR3E

 

 


Re: Clublog sync problem

Rick Ellison
 

I would open up your adif file in Notepad++ or another good text editor and do a find replace. Find <MODE:4>FT4 and replace it with MODE:4>MFSK <SUBMODE:3:>FT4 after doing that save the file and reimport it to ogger32. Make sure make a copy of the adif file in case something goes sideways.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Altman
Sent: Monday, November 18, 2019 4:06 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Clublog sync problem

 

So, I think I see what’s going on.  I downloaded my log as an ADIF from Clublog.  In it, FT4 is listed as a mode, not as a submode to MFSK.   Hmmm.  What to do?

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jim Altman via Groups.Io
Sent: Monday, November 18, 2019 12:41 PM
To: hamlogger@groups.io
Subject: [hamlogger] Clublog sync problem

 

I am not sure if this is a clublog or L32 problem, but I did a LOTW DXCC credit submission today and then synced my updated credits to clublog.  Then I synced Clublog to L32.  L32 reports 210 QSO’s not updated.  208 of them were FT4 contacts and the message was “Can’t find F4HRR at 2019-07-16 19:55:02 on 20M FT4 Granted (Mode?)”  2 were Digital Voice.  All the rest updated correctly to Granted status.  These are all the FT4 contacts down to and including yesterday.

 

I am aware of the FT4 submode issues and thought this was all straightened out.  I am running the latest L32, updated yesterday or today.  Is this a stupid human problem (i.e. Equipment Superior to Operator) or have I found a lingering issue in the app?

 

73 de w4uck

 

 

 

Jim Altman

jaltman636@...

 


Re: Macros - FH2 keypad messages

John, G4DRS
 

Well,
I can only ascribe it to finger trouble - I switched it on this evening and thought 'I'll just press it and see.' Lo and behold, it works perfectly!
So, now I have 3 choices:
I can press the button on the FH2
I can click the button on the DVK window
OR
I can click the button in the RCP

In each case, the radio sends the voice message stored in the FH2.

I suppose the 4th choice is that I actually pick up the microphone and talk into it, but where's the fun in that?

It works a treat.

I do like this program.


John
G4DRS


Re: Logger32 Can't open Sound Card(0)

Jim Hargrave
 

Fabio,

Open MMTTY > MMTY setup > Sound card and verify the correct sound card is selected.

You will also see the error if the sound card is already open by another program.

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Fabio Benedetti
Sent: Monday, November 18, 2019 3:14 PM
To: hamlogger@groups.io
Subject: [hamlogger] Logger32 Can't open Sound Card(0)

 

Hi everyone and thanks for reading this message.
I have a problem with Logger32 and Audio Interface with MTTY.

I'n using USB Interface III Microham  from a lot of years.

But only from a few days i get this message from MTTY.
Error : Can't open Sound Card(0)....

See the attached file...

 

Basically with MTTY all work fine without any problem adn with N1MM too...

Does anybody can tell me where i'm doing wrong ?

 

Many Thanks in advance !

 

'73 de IW2FUT - Fabio (aka Fabiowsky)

 


Logger32 Can't open Sound Card(0)

Fabio Benedetti
 

Hi everyone and thanks for reading this message.
I have a problem with Logger32 and Audio Interface with MTTY.
I'n using USB Interface III Microham  from a lot of years.
But only from a few days i get this message from MTTY.
Error : Can't open Sound Card(0)....
See the attached file...

Basically with MTTY all work fine without any problem adn with N1MM too...
Does anybody can tell me where i'm doing wrong ?

Many Thanks in advance !

'73 de IW2FUT - Fabio (aka Fabiowsky)


Re: Clublog sync problem

Jim Altman
 

So, I think I see what’s going on.  I downloaded my log as an ADIF from Clublog.  In it, FT4 is listed as a mode, not as a submode to MFSK.   Hmmm.  What to do?

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jim Altman via Groups.Io
Sent: Monday, November 18, 2019 12:41 PM
To: hamlogger@groups.io
Subject: [hamlogger] Clublog sync problem

 

I am not sure if this is a clublog or L32 problem, but I did a LOTW DXCC credit submission today and then synced my updated credits to clublog.  Then I synced Clublog to L32.  L32 reports 210 QSO’s not updated.  208 of them were FT4 contacts and the message was “Can’t find F4HRR at 2019-07-16 19:55:02 on 20M FT4 Granted (Mode?)”  2 were Digital Voice.  All the rest updated correctly to Granted status.  These are all the FT4 contacts down to and including yesterday.

 

I am aware of the FT4 submode issues and thought this was all straightened out.  I am running the latest L32, updated yesterday or today.  Is this a stupid human problem (i.e. Equipment Superior to Operator) or have I found a lingering issue in the app?

 

73 de w4uck

 

 

 

Jim Altman

jaltman636@...

 


Re: Macros - FH2 keypad messages

Dave Colliau
 

I have a cw message programed in my rcp and yes it can be done. I have everything from split, modes ,bands and frequency's,power levels ,volume settings and power on and off on my RCP fr my 5k. NR,NB,Lokc on and off. The possibilities are endless. I havent tried the voice messaging but it should work just like the CW with the proper command.
Dave N8DC

On November 18, 2019 at 11:52 AM "John, G4DRS via Groups.Io" <g4drs@...> wrote:

[Edited Message Follows]

what kind of rig you have

John,
I realised part-way down the thread that I hadn't actually specified the type of rig!

It's an FTdx5000.

The premise of the question was that I was curious to know whether I could use a macro in the RCP, similar to those I already have in place) to send voice messages from the FH2. 
The current answer seems to be that I can't, I can only send them by clicking the buttons in the DVK window (or by pressing the physical button, of course, but where's the fun in that?). I'm going to have another play this evening.
N1MM+ sends them quite happily if I include PB02 (for example) in the SSB function key messages/macros, but then N1MM+ has a very different voice keying regime.

It all works great, I was just seeing if I could 'push the boundaries'.

By the way, the PS1 macro seems to turn the FT5k on, too. Must be some difference between the radios.

John
G4DRS

 


Clublog sync problem

Jim Altman
 

I am not sure if this is a clublog or L32 problem, but I did a LOTW DXCC credit submission today and then synced my updated credits to clublog.  Then I synced Clublog to L32.  L32 reports 210 QSO’s not updated.  208 of them were FT4 contacts and the message was “Can’t find F4HRR at 2019-07-16 19:55:02 on 20M FT4 Granted (Mode?)”  2 were Digital Voice.  All the rest updated correctly to Granted status.  These are all the FT4 contacts down to and including yesterday.

 

I am aware of the FT4 submode issues and thought this was all straightened out.  I am running the latest L32, updated yesterday or today.  Is this a stupid human problem (i.e. Equipment Superior to Operator) or have I found a lingering issue in the app?

 

73 de w4uck

 

 

 

Jim Altman

jaltman636@...

 


Re: Macros - FH2 keypad messages

John, G4DRS
 
Edited

what kind of rig you have

John,
I realised part-way down the thread that I hadn't actually specified the type of rig!

It's an FTdx5000.

The premise of the question was that I was curious to know whether I could use a macro in the RCP, similar to those I already have in place) to send voice messages from the FH2. 
The current answer seems to be that I can't, I can only send them by clicking the buttons in the DVK window (or by pressing the physical button, of course, but where's the fun in that?). I'm going to have another play this evening.
N1MM+ sends them quite happily if I include PB02 (for example) in the SSB function key messages/macros, but then N1MM+ has a very different voice keying regime.

It all works great, I was just seeing if I could 'push the boundaries'.

By the way, the PS1 macro seems to turn the FT5k on, too. Must be some difference between the radios.

John
G4DRS


Re: Macros - FH2 keypad messages

John Owens
 


  I must have missed your earlier message as I have no way of knowing what kind of rig you have. Given the reference to F-2, I assume is is a Yaesu. I do have an RCP for my FTDX-101MP. All works except for turning the rig on. I have to do that manually. I only use my FH-2 for stored CW and SSB messages. 

John Owens -  N7TK



Re: Macros - FH2 keypad messages

John, G4DRS
 

PB01, 02 03 etc.... plays the voice memory back 
.
KY1 to KY5 play back the keyer memory(messages recorded using a key)

Thanks, Vince.
I'll do some more tinkering this evening.


John
G4DRS
 


Re: Macros - FH2 keypad messages

Vince Shirley
 

John. Bob..

LM sets the radio up to record a voice memory rather than using the FH-2 keypad.

PB01, 02 03 etc.... plays the voice memory back 
.
KY1 to KY5 play back the keyer memory(messages recorded using a key) test  and KY6 to KYA play back CW messages that are input in text format (page 63 of the manual refers) On this model it is possible to have both messages input with the key and messages input in text format effectively giving 10 memory banks.

The original Yaesu CAT manual was for, I think, the FT-950 and FT-2000 and they were very error-strewn documents  I remember spending hours either trying to guess what they meant or trying things when the command shown in the manual didn't work.

All they have done since then is adjust the manual for each new model, which means that some errors have been carried over from one manual to the next.

There are so many commands missing from the FTdx101D/MP manual.  For instance none of the (many) screen views can be commanded from the CAT system, it has to be done with several pushes of the front panel buttons.  The VC tune can't be switched on either and there are plenty of others.  You can bet your life it will be possible to do all of these things with a CAT command but they just don't tell the user how.

Frankly Yaesu seem always to let themselves down with the standard of their manuals. They produce a top quality radio then don't tell the users how to use it.

If only they aspired to the standard of Kenwood.  For such a complex radio their TS-990 manual and its associated documents were by some distance the best I've ever seen.  I can't recollect finding anything missing from it or any errors in it.

Vince G0ORC







On Mon, 18 Nov 2019 at 09:11, Bob <k4cy@...> wrote:
I see the radio has to companion commands LMxx (for load message) and PBxx (play back). Is there some kinda on-the-fly receive recording/playback option? But what do I know, the only FT-101 I've ever seen didn't have a D at the end. SeventyThree(s).
On November 18, 2019 at 3:39 AM "John, G4DRS via Groups.Io" <g4drs=btinternet.com@groups.io> wrote:

Thanks, Vince.
So KY 1-5 plays the CW memories and KY 6-A plays the voice memories.

I wonder what PBxx is really for...


John
G4DRS