Date   

Re: MMVARI Config File

Bob
 

Look in the Logger32.INI file for a section [MMVARI]. Also, there are some MMVARI settings in the section [Sound Card Data Settings]. 73.

On 10/19/2021 5:40 AM G4GIR via groups.io <i.frith@...> wrote:
 
 
Morning Bob
 
Is there a config file for MMVARI, I see one for MMTTY.
 
73
 
Ian G4GIR


Re: Freq problem

Bob
 

Larry, for the moment ignore clicking on a DX Spot. I suspect that your CAT is not working. Look at the radio debug window ... Do you see Logger32 polling the radio? Do you see the radio replying to the polls? Change the radio VFO frequency or band, does Logger32 follow it? 73.

On 10/18/2021 8:15 PM Larry Fravel <lfravel93@...> wrote:
 
 

I am having a problem with logger32 in that when I select a spot from the band map or the spot window the information will display properly in the log entry widow (call, mode, freq, operator, etc).  However, after a second the frequency disappears,  but all the other information remains.  The radio (an IC-7600) follows the spots when they are selected. This happens on any band in any mode.  I can click on the spot again and the frequency information will populate and then disappear in another second.  It started happening with the last update (.278)  but if I re-clicked the spot,  the frequency would stay populated.  With update .279 the frequency will not stay displayed longer than a second.  The configuration for the radio has not changed.  Varying the poling rate (set at 100) or the baud rate (set at 9600 does not help in any way. 

This is the first problem I have had in a long long time.  Appreciate any help.

Larry K8YYY

Shinnston, WV EM99uk

--


Re: MMVARI Config File

Jan <hamlogger@...>
 

Ian

It is in the Logger32 directory called yourcallsoundcardmacro's

73
Jan
PA4JJ

Op 19-10-2021 om 11:40 schreef G4GIR via groups.io:
Morning Bob
 
Is there a config file for MMVARI, I see one for MMTTY.
 
73
 
Ian G4GIR

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi zero:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Re: RTTY

G4GIR
 

Fabio
 
I found this thread, below is extract from it. But for some reason, my RX delay at the end of TX has gone. I haven't got a clue why it has changed.
 
73
Ian G4GIR
 
 
 
By Closure of PTT do you mean before the data starts flowing at
the beginning of the transmission?
Or do you mean a delay at the end of transmissions.

Nothing has changed with MMVARI that affects the delays.

MMVARI has a very slight TX delay at the beginning to allow
TX to get up to power before data transmission starts.
There is also about a 2 second tail at the end to insure the
transmit buffer is empty.

As for as I know, it has always worked this way.

 

----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:41:41
Subject: Re: [hamlogger] RTTY

It seems links refer to "general" issues or radio configuration, not to the slowness about MMVARI.
I don't think it's related to our problem.

Ciao.


73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:35, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
I will have to look again but if you look for message from F5NZY you will find one of them in the IO Groups site.
 
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:29:42
Subject: Re: [hamlogger] RTTY

Please give me links.
Thanks.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:20, g4girhb0 via groups.io
<ian.frith@...> ha scritto:
Thanks' Fabio,
 
I found other threads referencing IC-7100 and IC-7300 suffering the same problem.
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:16:09
Subject: Re: [hamlogger] RTTY

I use Icom IC-7300 and Yaesu FT-857D.
Both radios, same "slowness" behaviour with MMVARI.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 19:48, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
What rig are you using? I use TS990 here. I wondered if it was a rig problem as the K3 by all accounts seems to be ok! I have tried to interface IC-7100, and FT-991  to see if the same problem exists, but can't get PTT to work on either rig.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 17/10/2021 21:14:50
Subject: Re: [hamlogger] RTTY

If this is the sequence, why the radio switch to RX and MMVARI window starts to decode again after the QSO is putted in the log?
If you see the video, you will see that behaviour.

73s
Fabio, IZ8MBW

Il dom, 17 ott, 2021 alle 21:55, Bob
<k4cy@...> ha scritto:
Looking at the video, I see that Logger32 switched to receive at about 9.5 seconds (you can see 'Transmitting' change to 'Receiving'). Receive signals start appearing on the display at about 12 seconds. 
When switching to receive, the sequence of events is as follows:
a) Queue the radio command to switch to transmit
b) Change the text from Transmitting or receiving
c) Log the QSO if necessary.
So, it appears it is taking your setup 2.5 seconds for the time Logger32 queues the switch to receive radio command until it is executed by the radio. Siesta time? SeventyThree(s).
On 10/17/2021 2:34 PM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
In this video you can see the delay I have using both $logimmediate$ or $log$ macros in MMVARI:
73
Fabio, IZ8MBW
On Sunday, October 17, 2021, 08:23:41 PM GMT+2, G4GIR via groups.io <i.frith@...> wrote:
Thanks' Bob

That's working Ok now.

I have yet another problem.

After sending any of the Macros, there is about a 2 second delay before the rig goes back to receive, most annoying.

Any clues?

73

Ian

----- Original Message -----
From: g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:22:15
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


Roger, that sounds good..

73

Ian

----- Original Message -----
From: Bob < k4cy@...>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:18:13
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


I'd guess you could program a macro button to $logimmediate$, or append a $log$ to the end of your standard 'sign-off' message. SeventyThree(s).

> On 10/17/2021 12:04 PM g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io> wrote:
>

> Thanks' Bob/Fabio
>
> No Fabio even with 0 RF still fails.
>
> Yes Bob twa's the PTT Set up had Shared Radio Port selected in stead of Radio Command.
>
> Whilst on RTTY, once the Logging widow is populated is there a command from the RTTY window to save the QSO?
>
> 73
>
> iAN g4gir
>
> ----- Original Message -----
> From: Bob < k4cy@...>
> Reply-To: < hamlogger@groups.io>
> To: < hamlogger@groups.io>
> Sent: 17/10/2021 16:36:51
> Subject: Re: [hamlogger] RTTY
> ________________________________________________________________________________
>
>
> How have you configured the MMVARI PTT? What does the radio debug reveal? Does polling stop, or does polling continue and the radio stops replying? SeventyThree(s).
>
> > On 10/17/2021 11:24 AM G4GIR via groups.io <i.frith= ntlworld.com@groups.io> wrote:
> >
> > 
> > Thought I would play with the sound card today. With the RTTY contest in swing.
> >
> > Problem.
> >
> > Running MMVARI, Receives and Transmits OK.
> > Click on Call in Receive Window, L32 Logging window populates
> > Transmit to station, Station answers, Cat Control of Radio is Lost i.e Frequency in logging widow goes to .00 and no mode is shown.
> >
> > Any help to solve please.
> >
> > 73
> >
> > Ian G4GIR
> >
> >
> >
>
>
>
>
>
>












MMVARI Config File

G4GIR
 

Morning Bob
 
Is there a config file for MMVARI, I see one for MMTTY.
 
73
 
Ian G4GIR


Re: Problem with a log with a large number of QSOs ?

Alain F5LMJ
 

Hi Bob,
Yes it work fine for editing QSL Status, but not for QSO fields (QTH, Grid, Primary or secondary, ...). Maybe a wish of an "Edit QSO" option with a single window (could be the same as "Add QSO") to  add or update some QSO fields ?
73's Alain F5LMJ


Re: Invalid QSO

Prasad
 

Nice one Paul - I loved this solution :)

On Tue, 19 Oct 2021 at 12:05 AM, Paul F6EXV <f6exv@...> wrote:
Like this ?
Asterixasterix

Le 18/10/2021 à 20:31, g4girhb0 via groups.io a écrit :
Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is 
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is : 
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV









--

73 de Prasad VU2PTT, W2PTT (ex-AF6DV)

ARSI, ARRL, FOC, CWOPS, IFROAR, MARC
NCDXF, INDEXA, SCCC, EUPSK, IOTA, VUCC
ARRL DXCC Checkpoint
CQ Awards Checkpoint
Coordinator - VU Contest Group www.vucg.in
Webmaster - Logger32 www.logger32.net


Freq problem

Larry Fravel
 

I am having a problem with logger32 in that when I select a spot from the band map or the spot window the information will display properly in the log entry widow (call, mode, freq, operator, etc).  However, after a second the frequency disappears,  but all the other information remains.  The radio (an IC-7600) follows the spots when they are selected. This happens on any band in any mode.  I can click on the spot again and the frequency information will populate and then disappear in another second.  It started happening with the last update (.278)  but if I re-clicked the spot,  the frequency would stay populated.  With update .279 the frequency will not stay displayed longer than a second.  The configuration for the radio has not changed.  Varying the poling rate (set at 100) or the baud rate (set at 9600 does not help in any way. 

This is the first problem I have had in a long long time.  Appreciate any help.

Larry K8YYY

Shinnston, WV EM99uk

--


Re: Invalid QSO

G4GIR
 

Search for **
 
73
 
Ian
 

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Sent: 18/10/2021 19:48:57
Subject: Re: [hamlogger] Invalid QSO

Ian
That page is about importing ADIF logs....
What word should I search for ?
I searched "invalid" and cound not find anything relevant to this matter.
But anyway, I got the answer :  "=" in front of the callsign.
Thanks all !
73
Paul F6EXV

Le 18/10/2021 à 20:41, G4GIR via groups.io a écrit :
Paul
 
Page 69 of the V4 manual.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Paul F6EXV <f6exv@...>
Sent: 18/10/2021 19:35:00
Subject: Re: [hamlogger] Invalid QSO

Like this ?
Asterixasterix

Le 18/10/2021 à 20:31, g4girhb0 via groups.io a écrit :
Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is 
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is : 
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV











Re: Invalid QSO

Bob
 

Section 6.4 on page 129. SeventyThree(s).

On 10/18/2021 2:48 PM Paul F6EXV <f6exv@...> wrote:
 
 
Ian
That page is about importing ADIF logs....
What word should I search for ?
I searched "invalid" and cound not find anything relevant to this matter.
But anyway, I got the answer :  "=" in front of the callsign.
Thanks all !
73
Paul F6EXV

Le 18/10/2021 à 20:41, G4GIR via groups.io a écrit :
Paul
 
Page 69 of the V4 manual.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Paul F6EXV < f6exv@...>
Reply-To: < hamlogger@groups.io>
Sent: 18/10/2021 19:35:00
Subject: Re: [hamlogger] Invalid QSO

Like this ?
Asterix asterix

Le 18/10/2021 à 20:31, g4girhb0 via groups.io a écrit :
Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is 
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is : 
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV










Re: Invalid QSO

Paul F6EXV
 

Ian
That page is about importing ADIF logs....
What word should I search for ?
I searched "invalid" and cound not find anything relevant to this matter.
But anyway, I got the answer :  "=" in front of the callsign.
Thanks all !
73
Paul F6EXV

Le 18/10/2021 à 20:41, G4GIR via groups.io a écrit :
Paul
 
Page 69 of the V4 manual.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Paul F6EXV <f6exv@...>
Sent: 18/10/2021 19:35:00
Subject: Re: [hamlogger] Invalid QSO

Like this ?
Asterixasterix

Le 18/10/2021 à 20:31, g4girhb0 via groups.io a écrit :
Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is 
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is : 
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV











Re: RTTY

g4girhb0 <ian.frith@...>
 

Sorry Fabio, yes you are right this a problem I have with PTT not switching on IC-7100. I WILL LOOK THROUGH MY HISTORY FOR OUR PROBLEM.
 
73
 
iAN g4gir
 

----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:41:41
Subject: Re: [hamlogger] RTTY

It seems links refer to "general" issues or radio configuration, not to the slowness about MMVARI.
I don't think it's related to our problem.

Ciao.


73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:35, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
I will have to look again but if you look for message from F5NZY you will find one of them in the IO Groups site.
 
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:29:42
Subject: Re: [hamlogger] RTTY

Please give me links.
Thanks.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:20, g4girhb0 via groups.io
<ian.frith@...> ha scritto:
Thanks' Fabio,
 
I found other threads referencing IC-7100 and IC-7300 suffering the same problem.
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:16:09
Subject: Re: [hamlogger] RTTY

I use Icom IC-7300 and Yaesu FT-857D.
Both radios, same "slowness" behaviour with MMVARI.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 19:48, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
What rig are you using? I use TS990 here. I wondered if it was a rig problem as the K3 by all accounts seems to be ok! I have tried to interface IC-7100, and FT-991  to see if the same problem exists, but can't get PTT to work on either rig.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 17/10/2021 21:14:50
Subject: Re: [hamlogger] RTTY

If this is the sequence, why the radio switch to RX and MMVARI window starts to decode again after the QSO is putted in the log?
If you see the video, you will see that behaviour.

73s
Fabio, IZ8MBW

Il dom, 17 ott, 2021 alle 21:55, Bob
<k4cy@...> ha scritto:
Looking at the video, I see that Logger32 switched to receive at about 9.5 seconds (you can see 'Transmitting' change to 'Receiving'). Receive signals start appearing on the display at about 12 seconds. 
When switching to receive, the sequence of events is as follows:
a) Queue the radio command to switch to transmit
b) Change the text from Transmitting or receiving
c) Log the QSO if necessary.
So, it appears it is taking your setup 2.5 seconds for the time Logger32 queues the switch to receive radio command until it is executed by the radio. Siesta time? SeventyThree(s).
On 10/17/2021 2:34 PM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
In this video you can see the delay I have using both $logimmediate$ or $log$ macros in MMVARI:
73
Fabio, IZ8MBW
On Sunday, October 17, 2021, 08:23:41 PM GMT+2, G4GIR via groups.io <i.frith@...> wrote:
Thanks' Bob

That's working Ok now.

I have yet another problem.

After sending any of the Macros, there is about a 2 second delay before the rig goes back to receive, most annoying.

Any clues?

73

Ian

----- Original Message -----
From: g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:22:15
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


Roger, that sounds good..

73

Ian

----- Original Message -----
From: Bob < k4cy@...>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:18:13
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


I'd guess you could program a macro button to $logimmediate$, or append a $log$ to the end of your standard 'sign-off' message. SeventyThree(s).

> On 10/17/2021 12:04 PM g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io> wrote:
>

> Thanks' Bob/Fabio
>
> No Fabio even with 0 RF still fails.
>
> Yes Bob twa's the PTT Set up had Shared Radio Port selected in stead of Radio Command.
>
> Whilst on RTTY, once the Logging widow is populated is there a command from the RTTY window to save the QSO?
>
> 73
>
> iAN g4gir
>
> ----- Original Message -----
> From: Bob < k4cy@...>
> Reply-To: < hamlogger@groups.io>
> To: < hamlogger@groups.io>
> Sent: 17/10/2021 16:36:51
> Subject: Re: [hamlogger] RTTY
> ________________________________________________________________________________
>
>
> How have you configured the MMVARI PTT? What does the radio debug reveal? Does polling stop, or does polling continue and the radio stops replying? SeventyThree(s).
>
> > On 10/17/2021 11:24 AM G4GIR via groups.io <i.frith= ntlworld.com@groups.io> wrote:
> >
> > 
> > Thought I would play with the sound card today. With the RTTY contest in swing.
> >
> > Problem.
> >
> > Running MMVARI, Receives and Transmits OK.
> > Click on Call in Receive Window, L32 Logging window populates
> > Transmit to station, Station answers, Cat Control of Radio is Lost i.e Frequency in logging widow goes to .00 and no mode is shown.
> >
> > Any help to solve please.
> >
> > 73
> >
> > Ian G4GIR
> >
> >
> >
>
>
>
>
>
>












Re: RTTY

Fabio IZ8MBW
 

It seems links refer to "general" issues or radio configuration, not to the slowness about MMVARI.
I don't think it's related to our problem.

Ciao.


73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:35, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
I will have to look again but if you look for message from F5NZY you will find one of them in the IO Groups site.
 
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:29:42
Subject: Re: [hamlogger] RTTY

Please give me links.
Thanks.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:20, g4girhb0 via groups.io
<ian.frith@...> ha scritto:
Thanks' Fabio,
 
I found other threads referencing IC-7100 and IC-7300 suffering the same problem.
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:16:09
Subject: Re: [hamlogger] RTTY

I use Icom IC-7300 and Yaesu FT-857D.
Both radios, same "slowness" behaviour with MMVARI.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 19:48, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
What rig are you using? I use TS990 here. I wondered if it was a rig problem as the K3 by all accounts seems to be ok! I have tried to interface IC-7100, and FT-991  to see if the same problem exists, but can't get PTT to work on either rig.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 17/10/2021 21:14:50
Subject: Re: [hamlogger] RTTY

If this is the sequence, why the radio switch to RX and MMVARI window starts to decode again after the QSO is putted in the log?
If you see the video, you will see that behaviour.

73s
Fabio, IZ8MBW

Il dom, 17 ott, 2021 alle 21:55, Bob
<k4cy@...> ha scritto:
Looking at the video, I see that Logger32 switched to receive at about 9.5 seconds (you can see 'Transmitting' change to 'Receiving'). Receive signals start appearing on the display at about 12 seconds. 
When switching to receive, the sequence of events is as follows:
a) Queue the radio command to switch to transmit
b) Change the text from Transmitting or receiving
c) Log the QSO if necessary.
So, it appears it is taking your setup 2.5 seconds for the time Logger32 queues the switch to receive radio command until it is executed by the radio. Siesta time? SeventyThree(s).
On 10/17/2021 2:34 PM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
In this video you can see the delay I have using both $logimmediate$ or $log$ macros in MMVARI:
73
Fabio, IZ8MBW
On Sunday, October 17, 2021, 08:23:41 PM GMT+2, G4GIR via groups.io <i.frith@...> wrote:
Thanks' Bob

That's working Ok now.

I have yet another problem.

After sending any of the Macros, there is about a 2 second delay before the rig goes back to receive, most annoying.

Any clues?

73

Ian

----- Original Message -----
From: g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:22:15
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


Roger, that sounds good..

73

Ian

----- Original Message -----
From: Bob < k4cy@...>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:18:13
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


I'd guess you could program a macro button to $logimmediate$, or append a $log$ to the end of your standard 'sign-off' message. SeventyThree(s).

> On 10/17/2021 12:04 PM g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io> wrote:
>

> Thanks' Bob/Fabio
>
> No Fabio even with 0 RF still fails.
>
> Yes Bob twa's the PTT Set up had Shared Radio Port selected in stead of Radio Command.
>
> Whilst on RTTY, once the Logging widow is populated is there a command from the RTTY window to save the QSO?
>
> 73
>
> iAN g4gir
>
> ----- Original Message -----
> From: Bob < k4cy@...>
> Reply-To: < hamlogger@groups.io>
> To: < hamlogger@groups.io>
> Sent: 17/10/2021 16:36:51
> Subject: Re: [hamlogger] RTTY
> ________________________________________________________________________________
>
>
> How have you configured the MMVARI PTT? What does the radio debug reveal? Does polling stop, or does polling continue and the radio stops replying? SeventyThree(s).
>
> > On 10/17/2021 11:24 AM G4GIR via groups.io <i.frith= ntlworld.com@groups.io> wrote:
> >
> > 
> > Thought I would play with the sound card today. With the RTTY contest in swing.
> >
> > Problem.
> >
> > Running MMVARI, Receives and Transmits OK.
> > Click on Call in Receive Window, L32 Logging window populates
> > Transmit to station, Station answers, Cat Control of Radio is Lost i.e Frequency in logging widow goes to .00 and no mode is shown.
> >
> > Any help to solve please.
> >
> > 73
> >
> > Ian G4GIR
> >
> >
> >
>
>
>
>
>
>












Re: Invalid QSO

G4GIR
 

Paul
 
Page 69 of the V4 manual.
 
73
 
Ian G4GIR
 

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Sent: 18/10/2021 19:35:00
Subject: Re: [hamlogger] Invalid QSO

Like this ?
Asterixasterix

Le 18/10/2021 à 20:31, g4girhb0 via groups.io a écrit :
Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is 
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is : 
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV










Re: Invalid QSO

g4girhb0 <ian.frith@...>
 

Whoohaaa way over my head!  That's how I made my invalid QSO's show up.
 
**F6EXV
Did it work?
 
73
 
Ian
 

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Sent: 18/10/2021 19:35:00
Subject: Re: [hamlogger] Invalid QSO

Like this ?
Asterixasterix

Le 18/10/2021 à 20:31, g4girhb0 via groups.io a écrit :
Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is 
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is : 
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV










Re: Invalid QSO

Bob
 

Here is a couple of ways:

a) Change the callsign from P5DX to =P5DX
b) Right click on the QSO in the logbook page. Click Edit Country info. Scroll up to Not accepted for DXCC. Click on the row. Then Click Apply.

SeventyThree(s).

On 10/18/2021 2:27 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is :
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV



Re: RTTY

G4GIR
 

Fabio,
 
I will have to look again but if you look for message from F5NZY you will find one of them in the IO Groups site.
 
 
73
 
Ian
 

----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:29:42
Subject: Re: [hamlogger] RTTY

Please give me links.
Thanks.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:20, g4girhb0 via groups.io
<ian.frith@...> ha scritto:
Thanks' Fabio,
 
I found other threads referencing IC-7100 and IC-7300 suffering the same problem.
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:16:09
Subject: Re: [hamlogger] RTTY

I use Icom IC-7300 and Yaesu FT-857D.
Both radios, same "slowness" behaviour with MMVARI.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 19:48, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
What rig are you using? I use TS990 here. I wondered if it was a rig problem as the K3 by all accounts seems to be ok! I have tried to interface IC-7100, and FT-991  to see if the same problem exists, but can't get PTT to work on either rig.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 17/10/2021 21:14:50
Subject: Re: [hamlogger] RTTY

If this is the sequence, why the radio switch to RX and MMVARI window starts to decode again after the QSO is putted in the log?
If you see the video, you will see that behaviour.

73s
Fabio, IZ8MBW

Il dom, 17 ott, 2021 alle 21:55, Bob
<k4cy@...> ha scritto:
Looking at the video, I see that Logger32 switched to receive at about 9.5 seconds (you can see 'Transmitting' change to 'Receiving'). Receive signals start appearing on the display at about 12 seconds. 
When switching to receive, the sequence of events is as follows:
a) Queue the radio command to switch to transmit
b) Change the text from Transmitting or receiving
c) Log the QSO if necessary.
So, it appears it is taking your setup 2.5 seconds for the time Logger32 queues the switch to receive radio command until it is executed by the radio. Siesta time? SeventyThree(s).
On 10/17/2021 2:34 PM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
In this video you can see the delay I have using both $logimmediate$ or $log$ macros in MMVARI:
73
Fabio, IZ8MBW
On Sunday, October 17, 2021, 08:23:41 PM GMT+2, G4GIR via groups.io <i.frith@...> wrote:
Thanks' Bob

That's working Ok now.

I have yet another problem.

After sending any of the Macros, there is about a 2 second delay before the rig goes back to receive, most annoying.

Any clues?

73

Ian

----- Original Message -----
From: g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:22:15
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


Roger, that sounds good..

73

Ian

----- Original Message -----
From: Bob < k4cy@...>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:18:13
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


I'd guess you could program a macro button to $logimmediate$, or append a $log$ to the end of your standard 'sign-off' message. SeventyThree(s).

> On 10/17/2021 12:04 PM g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io> wrote:
>

> Thanks' Bob/Fabio
>
> No Fabio even with 0 RF still fails.
>
> Yes Bob twa's the PTT Set up had Shared Radio Port selected in stead of Radio Command.
>
> Whilst on RTTY, once the Logging widow is populated is there a command from the RTTY window to save the QSO?
>
> 73
>
> iAN g4gir
>
> ----- Original Message -----
> From: Bob < k4cy@...>
> Reply-To: < hamlogger@groups.io>
> To: < hamlogger@groups.io>
> Sent: 17/10/2021 16:36:51
> Subject: Re: [hamlogger] RTTY
> ________________________________________________________________________________
>
>
> How have you configured the MMVARI PTT? What does the radio debug reveal? Does polling stop, or does polling continue and the radio stops replying? SeventyThree(s).
>
> > On 10/17/2021 11:24 AM G4GIR via groups.io <i.frith= ntlworld.com@groups.io> wrote:
> >
> > 
> > Thought I would play with the sound card today. With the RTTY contest in swing.
> >
> > Problem.
> >
> > Running MMVARI, Receives and Transmits OK.
> > Click on Call in Receive Window, L32 Logging window populates
> > Transmit to station, Station answers, Cat Control of Radio is Lost i.e Frequency in logging widow goes to .00 and no mode is shown.
> >
> > Any help to solve please.
> >
> > 73
> >
> > Ian G4GIR
> >
> >
> >
>
>
>
>
>
>












Re: Invalid QSO

Paul F6EXV
 

Like this ?
Asterixasterix

Le 18/10/2021 à 20:31, g4girhb0 via groups.io a écrit :
Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@...>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is 
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is : 
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV










Re: Invalid QSO

g4girhb0 <ian.frith@...>
 

Paul

I think you put 2 asterisks in front of the callsign in the log.

73

Ian G4GIR

----- Original Message -----
From: Paul F6EXV <f6exv@hotmail.com>
Reply-To: <hamlogger@groups.io>
To: <hamlogger@groups.io>
Sent: 18/10/2021 19:27:39
Subject: [hamlogger] Invalid QSO
________________________________________________________________________________


Hi all
I searched the manual, and could not find anything about this.
Let's say I work a station, real one, but it later apperas that it is
invalid for DXCC (for whatever reason).
I still made that QSO so I want to keep it in my log. The question is :
how can I mark it invalid so it does not "count" ?

Thanks + 73
Paul F6EXV


Re: RTTY

Fabio IZ8MBW
 

Please give me links.
Thanks.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 20:20, g4girhb0 via groups.io
<ian.frith@...> ha scritto:
Thanks' Fabio,
 
I found other threads referencing IC-7100 and IC-7300 suffering the same problem.
 
73
 
Ian
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 18/10/2021 19:16:09
Subject: Re: [hamlogger] RTTY

I use Icom IC-7300 and Yaesu FT-857D.
Both radios, same "slowness" behaviour with MMVARI.

73s
Fabio, IZ8MBW

Il lun, 18 ott, 2021 alle 19:48, G4GIR via groups.io
<i.frith@...> ha scritto:
Fabio,
 
What rig are you using? I use TS990 here. I wondered if it was a rig problem as the K3 by all accounts seems to be ok! I have tried to interface IC-7100, and FT-991  to see if the same problem exists, but can't get PTT to work on either rig.
 
73
 
Ian G4GIR
 
----- Original Message -----
From: Fabio IZ8MBW via groups.io <iz8mbw@...>
Sent: 17/10/2021 21:14:50
Subject: Re: [hamlogger] RTTY

If this is the sequence, why the radio switch to RX and MMVARI window starts to decode again after the QSO is putted in the log?
If you see the video, you will see that behaviour.

73s
Fabio, IZ8MBW

Il dom, 17 ott, 2021 alle 21:55, Bob
<k4cy@...> ha scritto:
Looking at the video, I see that Logger32 switched to receive at about 9.5 seconds (you can see 'Transmitting' change to 'Receiving'). Receive signals start appearing on the display at about 12 seconds. 
When switching to receive, the sequence of events is as follows:
a) Queue the radio command to switch to transmit
b) Change the text from Transmitting or receiving
c) Log the QSO if necessary.
So, it appears it is taking your setup 2.5 seconds for the time Logger32 queues the switch to receive radio command until it is executed by the radio. Siesta time? SeventyThree(s).
On 10/17/2021 2:34 PM Fabio IZ8MBW via groups.io <iz8mbw@...> wrote:
In this video you can see the delay I have using both $logimmediate$ or $log$ macros in MMVARI:
73
Fabio, IZ8MBW
On Sunday, October 17, 2021, 08:23:41 PM GMT+2, G4GIR via groups.io <i.frith@...> wrote:
Thanks' Bob

That's working Ok now.

I have yet another problem.

After sending any of the Macros, there is about a 2 second delay before the rig goes back to receive, most annoying.

Any clues?

73

Ian

----- Original Message -----
From: g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:22:15
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


Roger, that sounds good..

73

Ian

----- Original Message -----
From: Bob < k4cy@...>
Reply-To: < hamlogger@groups.io>
To: < hamlogger@groups.io>
Sent: 17/10/2021 17:18:13
Subject: Re: [hamlogger] RTTY
________________________________________________________________________________


I'd guess you could program a macro button to $logimmediate$, or append a $log$ to the end of your standard 'sign-off' message. SeventyThree(s).

> On 10/17/2021 12:04 PM g4girhb0 via groups.io <ian.frith= ntlworld.com@groups.io> wrote:
>

> Thanks' Bob/Fabio
>
> No Fabio even with 0 RF still fails.
>
> Yes Bob twa's the PTT Set up had Shared Radio Port selected in stead of Radio Command.
>
> Whilst on RTTY, once the Logging widow is populated is there a command from the RTTY window to save the QSO?
>
> 73
>
> iAN g4gir
>
> ----- Original Message -----
> From: Bob < k4cy@...>
> Reply-To: < hamlogger@groups.io>
> To: < hamlogger@groups.io>
> Sent: 17/10/2021 16:36:51
> Subject: Re: [hamlogger] RTTY
> ________________________________________________________________________________
>
>
> How have you configured the MMVARI PTT? What does the radio debug reveal? Does polling stop, or does polling continue and the radio stops replying? SeventyThree(s).
>
> > On 10/17/2021 11:24 AM G4GIR via groups.io <i.frith= ntlworld.com@groups.io> wrote:
> >
> > 
> > Thought I would play with the sound card today. With the RTTY contest in swing.
> >
> > Problem.
> >
> > Running MMVARI, Receives and Transmits OK.
> > Click on Call in Receive Window, L32 Logging window populates
> > Transmit to station, Station answers, Cat Control of Radio is Lost i.e Frequency in logging widow goes to .00 and no mode is shown.
> >
> > Any help to solve please.
> >
> > 73
> >
> > Ian G4GIR
> >
> >
> >
>
>
>
>
>
>











2261 - 2280 of 88415