Date   
Re: RTTY call stacking: Next Call not working with ESM

Jamie WW3S
 

What he said....logthenpop the way to go....


On Feb 12, 2020, at 10:39 AM, ve3ki <ve3iay@...> wrote:

For what it's worth, my own procedure works like this (I have the right-click sends Enter option checked):

Right-click in the RX window to send my CQ.
Two stations respond. I left-click on both call signs, one after the other. One is now on the call stack, the other in the Entry window.
Right-click sends my exchange to the station whose call is in the Entry window.
He sends his exchange, I left-click on it, then right-click to send the Next message, pop the call stack and start the next QSO.
The second station sends his exchange. I left-click on it, then right-click to send my TU message.

This is basically the same as responding to a single caller - the only difference is that I click on two (or three) call signs instead of only one before right-clicking to start the first QSO. Everything else proceeds with my standard left-click, right-click alternation. I don't look at the Grab list at all, and my mouse pointer stays inside the RX window the whole time.

73,
Rich VE3KI


On Wed, Feb 12, 2020 at 09:26 AM, Mike Dodd wrote:
On 2/11/2020 11:29 PM, Steve Bookout, NR4M wrote:
Mike, I’ve got it working well here. Come over some time and I can
show you what I know. I have it working with ESM just fine.
FB, Steve. Does it use the call stack or the Grab list on the Digital 
Interface?
he
--- Mike N4CF

Re: RTTY call stacking: Next Call not working with ESM

ve3ki
 

For what it's worth, my own procedure works like this (I have the right-click sends Enter option checked):

Right-click in the RX window to send my CQ.
Two stations respond. I left-click on both call signs, one after the other. One is now on the call stack, the other in the Entry window.
Right-click sends my exchange to the station whose call is in the Entry window.
He sends his exchange, I left-click on it, then right-click to send the Next message, pop the call stack and start the next QSO.
The second station sends his exchange. I left-click on it, then right-click to send my TU message.

This is basically the same as responding to a single caller - the only difference is that I click on two (or three) call signs instead of only one before right-clicking to start the first QSO. Everything else proceeds with my standard left-click, right-click alternation. I don't look at the Grab list at all, and my mouse pointer stays inside the RX window the whole time.

73,
Rich VE3KI


On Wed, Feb 12, 2020 at 09:26 AM, Mike Dodd wrote:
On 2/11/2020 11:29 PM, Steve Bookout, NR4M wrote:
Mike, I’ve got it working well here. Come over some time and I can
show you what I know. I have it working with ESM just fine.
FB, Steve. Does it use the call stack or the Grab list on the Digital 
Interface?
he
--- Mike N4CF

Re: Development Feature request - Multicast support

Rick Ellison
 

This is on my list to add. Just not much time for programming at the moment..

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of pete.thomas.fi
Sent: Wednesday, February 12, 2020 1:52 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Development Feature request - Multicast support

 

GridTracker cannot be run whilst running WSJT-X from within N1MM+ Logger because both programs use the same udp port to talk to WSJT and the UDP port can’t be shared.. . On this subject, the devloper of GT Tag Loomis replied:
"Everyone but N1MM and JTAlert have implemented Multicast support (224.0.0.1) so that we can share the UDP port.

 

It’s super simple for him to add support for this."
73' 
Pete T

Oh2euu

Re: RTTY call stacking: Next Call not working with ESM

Mike Dodd
 

On 2/11/2020 11:29 PM, Steve Bookout, NR4M wrote:
Mike, I’ve got it working well here. Come over some time and I can
show you what I know. I have it working with ESM just fine.
FB, Steve. Does it use the call stack or the Grab list on the Digital Interface?

--- Mike N4CF

Re: Winkey configuration glitch

John Bednar
 

I don’t think you can change it in N1MM Logger but check the weighting setting with the WinKey program.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Neil K6UIP
Sent: Tuesday, February 11, 2020 6:19 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Winkey configuration glitch

 

When I configure Winkey for use the dits are fine but the dahs last forever There must be a simple change that I am missing?

Development Feature request - Multicast support

pete.thomas.fi
 

GridTracker cannot be run whilst running WSJT-X from within N1MM+ Logger because both programs use the same udp port to talk to WSJT and the UDP port can’t be shared.. . On this subject, the devloper of GT Tag Loomis replied:
"Everyone but N1MM and JTAlert have implemented Multicast support (224.0.0.1) so that we can share the UDP port.

 

It’s super simple for him to add support for this."
73' 
Pete T

Oh2euu

Re: RTTY call stacking: Next Call not working with ESM

Steve Bookout, NR4M
 

Mike,
I’ve got it working well here.
Come over some time and I can show you what I know.
I have it working with ESM just fine.

Steve, NR4M

On Feb 11, 2020, at 11:26 PM, Mike Dodd <mike@...> wrote:

On 2/11/2020 10:08 PM, ve3ki wrote:
You are confusing LOGTHENGRAB with LOGTHENPOP. They are two different
things and work differently. The Next key (your F10) only works with
LOGTHENPOP.
OK, I think I understand now. LOGTHENPOP works with calls on the call stack, the Next Call key, and ESM, while LOGTHENGRAB uses calls on the Grab stack, does not use the Next Call key, and thus does not work with ESM. Correct?

That's a shame. I really like ESM, and was looking forward to using it with call stacking. I suppose I'll have to get used to hitting F10 to call the next station, or Enter if I just want to send TU CQ.

Thank you for the clarification.

--
73, Mike N4CF
Louisa County, VA USA
Elecraft K-Line: K3s / P3 / KPA500 / KAT500
Carolina Windom up 45'
http://n4cf.mdodd.com


Re: RTTY call stacking: Next Call not working with ESM

Mike Dodd
 

On 2/11/2020 10:08 PM, ve3ki wrote:
You are confusing LOGTHENGRAB with LOGTHENPOP. They are two different
things and work differently. The Next key (your F10) only works with
LOGTHENPOP.
OK, I think I understand now. LOGTHENPOP works with calls on the call stack, the Next Call key, and ESM, while LOGTHENGRAB uses calls on the Grab stack, does not use the Next Call key, and thus does not work with ESM. Correct?

That's a shame. I really like ESM, and was looking forward to using it with call stacking. I suppose I'll have to get used to hitting F10 to call the next station, or Enter if I just want to send TU CQ.

Thank you for the clarification.

--
73, Mike N4CF
Louisa County, VA USA
Elecraft K-Line: K3s / P3 / KPA500 / KAT500
Carolina Windom up 45'
http://n4cf.mdodd.com

Re: RTTY call stacking: Next Call not working with ESM

ve3ki
 

You are confusing LOGTHENGRAB with LOGTHENPOP. They are two different things and work differently. The Next key (your F10) only works with LOGTHENPOP. Read <https://n1mmwp.hamdocs.com/manual-operating/single-operator-contesting/#digital-call-stacking> carefully.

73,
Rich VE3KI



On Tue, Feb 11, 2020 at 09:36 PM, Mike Dodd wrote:
Having just finished CQ WPX RTTY, I looked into call stacking for the next RTTY contest. I read the manual, and have the following set up:
  • Configurer: Next Call key set to F10
  • Function keys: F10 Next call,{TX} ! {LOGTHENGRAB}TU NOW...{F5}{F2} {RX}
  • Digital Interface: Call stacking enabled
Receiving, calls are stacked in the DI's Grab pane. When I test a run QSO and press F10, the Q is logged, the next callsign is grabbed, and the TU NOW....exchange is transmitted. It works fine. But this does not happen if I use ESM. When I hit Enter, this does not happen. Instead, the Q is logged and the next callsign is popped from the stack, but it is not copied to the main window and my standard TU N4CF CQ message is sent.

The Configurer screen has a notice above the function key assignments that says, "Make sure the key mappings below match the contents of the keys as defined in ... Config/Change Digital Buttons." See the attached screen shot.

I can't find Config/Change Digital Buttons. This might explain why ESM doesn't work. Can someone point me in the right direction?

Thanks.

--- Mike N4CF

RTTY call stacking: Next Call not working with ESM

Mike Dodd
 

Having just finished CQ WPX RTTY, I looked into call stacking for the next RTTY contest. I read the manual, and have the following set up:
  • Configurer: Next Call key set to F10
  • Function keys: F10 Next call,{TX} ! {LOGTHENGRAB}TU NOW...{F5}{F2} {RX}
  • Digital Interface: Call stacking enabled
Receiving, calls are stacked in the DI's Grab pane. When I test a run QSO and press F10, the Q is logged, the next callsign is grabbed, and the TU NOW....exchange is transmitted. It works fine. But this does not happen if I use ESM. When I hit Enter, this does not happen. Instead, the Q is logged and the next callsign is popped from the stack, but it is not copied to the main window and my standard TU N4CF CQ message is sent.

The Configurer screen has a notice above the function key assignments that says, "Make sure the key mappings below match the contents of the keys as defined in ... Config/Change Digital Buttons." See the attached screen shot.

I can't find Config/Change Digital Buttons. This might explain why ESM doesn't work. Can someone point me in the right direction?

Thanks.

--- Mike N4CF

Re: LZDOMESTIC transmits but doesn't log complete sent exchange

Lyubomir Slavov, OR2F
 

John,

Indeed the guy has transferring the cursor between CALLSIGN- and RCVD-fields not by Enter in ESM-mode or space bar ... but by the TAB-key.
If so, the field EXCH in the log remain blank.

Thanks a lot for your help !

Count the case closed please.

73,
Leo / OR2F

On Tue, 11 Feb 2020 at 17:56, Lyubomir Slavov, OR2F via Groups.Io <on8lds=gmail.com@groups.io> wrote:
John,

first of all - Thanks a lot for taking this case !

Here is what I received about the function keys :

image.png

About the cursor transfer between CALLSIGN-box and RCVD-box I'll ask the guy and let you know.

73,
Leo / OR2F

On Tue, 11 Feb 2020 at 13:57, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

Are your function key messages identical?

 

Are you both advancing the cursor from the callsign box to the exchange box by pressing ENTER in ESM or space bar in non-ESM mode?

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Monday, February 10, 2020 8:38 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] LZDOMESTIC transmits but doesn't log complete sent exchange

 

Hi All !

 

I was asked by LZ-fellow to rise the issue he has :

During whole LZ-domestic tournament period the sent exchanges are transmitted complete and correct but on some QSO lines or all of them in the log the second half / {LASTEXCH} is missing .. as well as it doesn't appear afterwards in the generated Cabrillo, ie. extra time+error risk to write them addendum in the text file.

 

image.png

 

Same behavior with LZDOMESTIC, LZOPEN, LZFILED etc.

Same behavior with Windows7 and Windows10

 

With me all is 100% OK, I can't reproduce such a phenomena ... neither on the my pc with Win7 nor Win10.

 

...

 

Just for test, on the pc with Win7 he has installed very old N1MM-Classic pack and did same simulation with same result - the 'EXCH' column of the log keeps blank:

 

image.png

 

Any idea what could be the root cause ?

 

73,
Leo / OR2F

Winkey configuration glitch

Neil K6UIP
 

When I configure Winkey for use the dits are fine but the dahs last forever. There must be a simple change that I am missing?

Re: N1MM+ crashes when ESM mode is active and *.wav files are to be played

Joe WB9SBD
 

Ahhh,

I may have found your problem.

I do not now know if it makes any difference anymore. But many , many, many years ago when I first started to use N1MM, I was told to let it install where the SOFTWARE wants to install to, do NOT  change anything where the program wants to put things because it will NOT work.

Now I do not know if this makes any difference anymore? this is why I am copying this reply to the group this time.

being in a D drive might be the whole problem?

Experts, what ya say?

Joe WB9SBD

On 2/11/2020 3:54 PM, Lyubomir Slavov, OR2F wrote:
Joe,

The location is 
D:\N1MM+ Logger\LogError.txt

image.png

I just erased the file content and saved it empty ... at 22:49 CET / volume 0 KB

Now I'll do some voice simulation work until I get several crashes and will resend you the log file.

73

On Tue, 11 Feb 2020 at 21:44, Joe <nss@...> wrote:
Wow,

Lots of errors!

OK, go in and clear that empty again and re save it empty.

It is the one that is in,

Documents>N1MM Logger+>LogError.txt

correct?

so empty it again.

and then re-run N1MM+ till you get an error, then send me what is in that log file.

Joe

On 2/11/2020 2:12 PM, Lyubomir Slavov, OR2F wrote:
Joe,

No, I don't clear the LogError.txt file often.
Yesterday, after your advise I did it ... later in the evening after I got several crashes it was still empty / blank.

Now I see, there are some error events recorded. (see the attachment, please)

In one of my previous messages I explained what happens when the logger crashes.
If necessary I could try to do a short movie record and upload it in youtube.com

73,
Leo / OR2F

On Tue, 11 Feb 2020 at 17:02, Joe <nss@...> wrote:
OK,
so far looks good,

then what happens when the error happens.

did you ever do the error log file clearing and starting over?

Joe WB9SBD

On 2/11/2020 9:46 AM, Lyubomir Slavov, OR2F wrote:
John,

the sound card belongs to the pc, it's not an USB interfaced device. See the screenshot I shared in one of my previous messages.
In case the internal sound card stops working due to some Windows reason, why it doesn't stop when concatenating function is disabled ?
...

Yes, it always stops after the current QSO is completed and logged.

Here with an example sequence of one QSO :
1. Initial parameters -
1.1. Contest = ARRL DX SSB
1.2. Mode = RUN
1.3. CQ Freq = 14230
1.4. Radio = Manual
1.5. ESM = active
1.6. Logger+ Audio = active

2. QSO sequence :
2.1. Enter = plays 'CQ message'
2.2. Input in call sign field 'K3CT'+'Enter' = plays 'K3.wav', plays 'CT.wav', plays '59_100.wav', cursor jumps to 'State' field
2.3. Input there 'PA'+'Enter' = logs the QSO, plays 'Thanks.wav', plays 'OR2F.wav', cursor jumps to 'Call Sign' field
2.4. Ready for the next input ...

These are my function keys msg :

image.png


On Tue, 11 Feb 2020 at 13:47, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

Is your sound card interfaced via a USB port? If the audio card disappears from the hardware table, it would cause an error.  In this case disable the Windows USB port power down.

 

Does it always fail after playing the same function key message? If so post your function key messages.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Monday, February 10, 2020 4:34 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

Joe,

 

The LogError.txt is located in the 'N1MM+ Logger' main folder, I don't see any 'Documents' subfolder there.

 

image.png

 

After couple of crashes the LogError.txt file is still empty.

 

image.png

 

What I notice in each crash :

1- always the current voice message finalizes but the output level decreases (headphone monitoring)

2- the keyboard comes dead

3- and the known pop up afterwards

 

image.png

 

73

 

 

On Mon, 10 Feb 2020 at 15:01, Joe WB9SBD <nss@...> wrote:

OK,

go into the N1MM+ Folder,,,

Documents>N1MM Logger+>

Open the LogError.txt with notepad.

delete it's contents and save it empty.

Now run N1MM+ till you get an error, and go back to this log file and send us the contents.

Joe WB9SBD

On 2/10/2020 7:54 AM, Lyubomir Slavov, OR2F wrote:

John,

actually I do not have any radio connected right now :-)

 

Joe,

no error log appears, just popup shared above 'N1MM+ has stopped working'

 

Keep on searching ...

 

73,
Leo / O2RF

 

On Mon, 10 Feb 2020 at 14:43, Joe WB9SBD <nss@...> wrote:

Any error box popups? and or whats the error log look like?

Joe WB9SBD

On 2/10/2020 6:53 AM, John Bednar via Groups.Io wrote:

Leo,

 

An error in concatenating files will not be intermittent. If the formats are not identical, it will fail all the time.

 

Make sure that the files used in the function keys are contained in the Letters Path and Wav\Operator path.

 

What you are seeing may have nothing to do with the audio player. Maybe you are getting RF into the computer.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Monday, February 10, 2020 7:27 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

John,

 

Unfortunately yes ... not that often but let say after 15-20 min of RUN-simulation (60-100 Qs).

 

Today, I don't have any crash since I do the test with unchecked concatenating option ... already couple of hours:

 

image.png

 

73,
Leo / OR2F

 

On Mon, 10 Feb 2020 at 13:01, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

Do you still have an issue when logging a station? If so, does the problem dissappear when you uncheck “Concatenate all Wav files”?

 

If you are playing a file in these two directories, there shouldn’t be an issue with the concatenating audio player.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Sunday, February 09, 2020 11:09 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

Thanks John,

 

now is much clear ...

 

image.png

 

73,

Leo / OR2F

 

 

On Sun, 9 Feb 2020 at 15:45, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

You do not need to set any option in these windows.

 

Logger+ Audio has an option to concatenate the wav files. See the yellow circle below. This is the concatenating audio player. Now that you are aware of this, re-read my first email.

 

John, K3CT

 

 

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Sunday, February 09, 2020 9:06 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

John,

 

I don't use any concatenating tool, all is done by the 'Logger+ Audio'.

Simply the internal sound card of the laptop and its advanced settings. Are these options correct active ?

 

image.png

 

 

No any issues to complete the voice messages (ex. missing letter files, path not found, etc.), just crashes when ESM is active and works fine when it's not.

 

73,
Leo / OR2F

 

 

 

On Sun, 9 Feb 2020 at 13:23, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

If you are using the concatenating audio player, uncheck the option. Does the error disappear?

 

Then check the option. The code scans your wav files to insure they can be played as one wav. If there are any issues they will be displayed in the window. You will need to correct this recording compatibility issues before using the concatenating audio player.

 

If this isn’t the problem, send the text of your function key with the issue.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Sunday, February 09, 2020 7:14 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

Hi All,

 

I've been trying to use a voice robot in RUN mode. ESM function is active, all paths/files are OK. Unfortunately after one, two or max three inputs (complete Qs) I hear a crack in my audio monitor and then this message appears :

 

image.png

 

When ESM mode is OFF and I do all the voice sequence manually F5+F2+F3+Enter ... or 'INS'+F3+Enter, all works fine for unlimited time period.

 

To play each individual call sign couple of *.wav files are to be played (Use Logger+ Audio):

- 1 file for the prefix;

- 1 file for the first two letters suffix;

- 1 file for the third suffix letter if exist;

- the 'report' and 'thanks' files are also separate, all with the necessary time out implemented (20 or 80 ms).

 

Same behavior on both environments Win7 and Win10.

 

Any idea about this ?

 

Thanks a lot to the whole developer team about the effort, it's a great help guys ... THANKS !

 

73,
Leo / OR2F

 

 




Re: LZDOMESTIC transmits but doesn't log complete sent exchange

Lyubomir Slavov, OR2F
 

John,

first of all - Thanks a lot for taking this case !

Here is what I received about the function keys :

image.png

About the cursor transfer between CALLSIGN-box and RCVD-box I'll ask the guy and let you know.

73,
Leo / OR2F

On Tue, 11 Feb 2020 at 13:57, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

Are your function key messages identical?

 

Are you both advancing the cursor from the callsign box to the exchange box by pressing ENTER in ESM or space bar in non-ESM mode?

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Monday, February 10, 2020 8:38 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] LZDOMESTIC transmits but doesn't log complete sent exchange

 

Hi All !

 

I was asked by LZ-fellow to rise the issue he has :

During whole LZ-domestic tournament period the sent exchanges are transmitted complete and correct but on some QSO lines or all of them in the log the second half / {LASTEXCH} is missing .. as well as it doesn't appear afterwards in the generated Cabrillo, ie. extra time+error risk to write them addendum in the text file.

 

image.png

 

Same behavior with LZDOMESTIC, LZOPEN, LZFILED etc.

Same behavior with Windows7 and Windows10

 

With me all is 100% OK, I can't reproduce such a phenomena ... neither on the my pc with Win7 nor Win10.

 

...

 

Just for test, on the pc with Win7 he has installed very old N1MM-Classic pack and did same simulation with same result - the 'EXCH' column of the log keeps blank:

 

image.png

 

Any idea what could be the root cause ?

 

73,
Leo / OR2F

Re: N1MM+ crashes when ESM mode is active and *.wav files are to be played

Lyubomir Slavov, OR2F
 

John,

the sound card belongs to the pc, it's not an USB interfaced device. See the screenshot I shared in one of my previous messages.
In case the internal sound card stops working due to some Windows reason, why it doesn't stop when concatenating function is disabled ?
...

Yes, it always stops after the current QSO is completed and logged.

Here with an example sequence of one QSO :
1. Initial parameters -
1.1. Contest = ARRL DX SSB
1.2. Mode = RUN
1.3. CQ Freq = 14230
1.4. Radio = Manual
1.5. ESM = active
1.6. Logger+ Audio = active

2. QSO sequence :
2.1. Enter = plays 'CQ message'
2.2. Input in call sign field 'K3CT'+'Enter' = plays 'K3.wav', plays 'CT.wav', plays '59_100.wav', cursor jumps to 'State' field
2.3. Input there 'PA'+'Enter' = logs the QSO, plays 'Thanks.wav', plays 'OR2F.wav', cursor jumps to 'Call Sign' field
2.4. Ready for the next input ...

These are my function keys msg :

image.png


On Tue, 11 Feb 2020 at 13:47, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

Is your sound card interfaced via a USB port? If the audio card disappears from the hardware table, it would cause an error.  In this case disable the Windows USB port power down.

 

Does it always fail after playing the same function key message? If so post your function key messages.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Monday, February 10, 2020 4:34 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

Joe,

 

The LogError.txt is located in the 'N1MM+ Logger' main folder, I don't see any 'Documents' subfolder there.

 

image.png

 

After couple of crashes the LogError.txt file is still empty.

 

image.png

 

What I notice in each crash :

1- always the current voice message finalizes but the output level decreases (headphone monitoring)

2- the keyboard comes dead

3- and the known pop up afterwards

 

image.png

 

73

 

 

On Mon, 10 Feb 2020 at 15:01, Joe WB9SBD <nss@...> wrote:

OK,

go into the N1MM+ Folder,,,

Documents>N1MM Logger+>

Open the LogError.txt with notepad.

delete it's contents and save it empty.

Now run N1MM+ till you get an error, and go back to this log file and send us the contents.

Joe WB9SBD

On 2/10/2020 7:54 AM, Lyubomir Slavov, OR2F wrote:

John,

actually I do not have any radio connected right now :-)

 

Joe,

no error log appears, just popup shared above 'N1MM+ has stopped working'

 

Keep on searching ...

 

73,
Leo / O2RF

 

On Mon, 10 Feb 2020 at 14:43, Joe WB9SBD <nss@...> wrote:

Any error box popups? and or whats the error log look like?

Joe WB9SBD

On 2/10/2020 6:53 AM, John Bednar via Groups.Io wrote:

Leo,

 

An error in concatenating files will not be intermittent. If the formats are not identical, it will fail all the time.

 

Make sure that the files used in the function keys are contained in the Letters Path and Wav\Operator path.

 

What you are seeing may have nothing to do with the audio player. Maybe you are getting RF into the computer.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Monday, February 10, 2020 7:27 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

John,

 

Unfortunately yes ... not that often but let say after 15-20 min of RUN-simulation (60-100 Qs).

 

Today, I don't have any crash since I do the test with unchecked concatenating option ... already couple of hours:

 

image.png

 

73,
Leo / OR2F

 

On Mon, 10 Feb 2020 at 13:01, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

Do you still have an issue when logging a station? If so, does the problem dissappear when you uncheck “Concatenate all Wav files”?

 

If you are playing a file in these two directories, there shouldn’t be an issue with the concatenating audio player.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Sunday, February 09, 2020 11:09 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

Thanks John,

 

now is much clear ...

 

image.png

 

73,

Leo / OR2F

 

 

On Sun, 9 Feb 2020 at 15:45, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

You do not need to set any option in these windows.

 

Logger+ Audio has an option to concatenate the wav files. See the yellow circle below. This is the concatenating audio player. Now that you are aware of this, re-read my first email.

 

John, K3CT

 

 

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Sunday, February 09, 2020 9:06 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

John,

 

I don't use any concatenating tool, all is done by the 'Logger+ Audio'.

Simply the internal sound card of the laptop and its advanced settings. Are these options correct active ?

 

image.png

 

 

No any issues to complete the voice messages (ex. missing letter files, path not found, etc.), just crashes when ESM is active and works fine when it's not.

 

73,
Leo / OR2F

 

 

 

On Sun, 9 Feb 2020 at 13:23, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Leo,

 

If you are using the concatenating audio player, uncheck the option. Does the error disappear?

 

Then check the option. The code scans your wav files to insure they can be played as one wav. If there are any issues they will be displayed in the window. You will need to correct this recording compatibility issues before using the concatenating audio player.

 

If this isn’t the problem, send the text of your function key with the issue.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Sunday, February 09, 2020 7:14 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] N1MM+ crashes when ESM mode is active and *.wav files are to be played

 

Hi All,

 

I've been trying to use a voice robot in RUN mode. ESM function is active, all paths/files are OK. Unfortunately after one, two or max three inputs (complete Qs) I hear a crack in my audio monitor and then this message appears :

 

image.png

 

When ESM mode is OFF and I do all the voice sequence manually F5+F2+F3+Enter ... or 'INS'+F3+Enter, all works fine for unlimited time period.

 

To play each individual call sign couple of *.wav files are to be played (Use Logger+ Audio):

- 1 file for the prefix;

- 1 file for the first two letters suffix;

- 1 file for the third suffix letter if exist;

- the 'report' and 'thanks' files are also separate, all with the necessary time out implemented (20 or 80 ms).

 

Same behavior on both environments Win7 and Win10.

 

Any idea about this ?

 

Thanks a lot to the whole developer team about the effort, it's a great help guys ... THANKS !

 

73,
Leo / OR2F

 

 

locked Re: New Version

Tom - N1MM
 

Version 1.0.8152 (Feb 11, 2020)
  1. MorseRunner - added option to mute when sending. This is most useful when practicing SO2R. (Coded by N2IC)
  2. MorseRunner - Fix RTE when MorseRunner process has not started, but user tries to use MorseRunner. (DF2DR) (coded by N2IC)
  3. RadioName added to UDP Radio broadcast message. (Coded by N2IC)
  4. MorseRunner parameters are now saved. (Coded by N2IC)
  5. CW Ops Contest: Correct the contest start time to the first session when a new contest is started outside of the three hour window prior to any of the three CWT's. (DL6KVA) (Coded by K3CT)
  6. CW Ops Contest: Added additional day/time windows to select the session start time/day. (VE3KI) (Coded by K3CT)
  7. QSO Party: Validate the Exchange box text before allowing a Cabrillo to be generated. This change impacts all QSO Parties. Please test your QSO party and report bugs before the contest. (K4XU) (Coded by K3CT)
  8. KY QSO Party: Add bonus station. (ND4X) (Coded by K3CT)
  9. Program startup: Excluding Windows XP from the "Power saver" check on startup to prevent crash. (Coded by KU7T)
  10. Digital Windows: Handles IsSpotAllCallsLocally more gracefully. (Coded by N2AMG)
  11. AsyncTCPListener: When connected to WSJT and Test Cat button was pressed caused TCPLister to crash with RT error. Now Fixed (Coded by N2AMG)

Re: WSJY-x running from within N1MM+ with GridTracker #n1mm

pete.thomas.fi
 

Oh, that's very disappointing. Thankyou for the information.

Re: IC-7100 Filter change in RTTY

KG7D Greg
 

John,

When I put in the two commands I get "Filter code error, input ignored" with the red dot. Seeing what commands you were using I looked up "Data mode with filter width setting" It appears to me that the first code to set USB mode and filter isn't necessary.  When using Data setting with filter code: FE FE 88 E0 1A 06 01 01 FD  that the first 01 set the Data mode and the second 01 (or 02-03) set the filter. Perhaps I'm way off here, it didn't work anyway. Nothing I put in the Digi Wide or Digi Narrow codes makes any difference.

In my testing I also found that in SSB and CW when I set the filters to #2 as wide and #3 as narrow. A double click on the button is required to change from wide  to narrow, but only a single click for narrow to wide. Is this normal? Also, that changing the SSB wide and SSB narrow don't effect 40m and 80m, didn't test 160m, but I'm betting its something to do with all the LSB bands.

Greg Moore - KG7D

Re: WSJY-x running from within N1MM+ with GridTracker #n1mm

Rick Ellison
 

It is not possible to run GridTracker and N1MM  with WSJT at the same time. Both programs use the same udp port to talk to WSJT and the UDP port can’t be shared..

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of pete.thomas.fi
Sent: Tuesday, February 11, 2020 3:47 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] WSJY-x running from within N1MM+ with GridTracker #n1mm

 

Does anyone have WSJT-X running from within N1MM+ together with GridTracker? I need help with IP and port settings. I have GT working with WSJT-X stand alone but not when run from within N1MM+ (so that I can log FT8/4 qso's into N1MM+).

Pete T
Oh2euu

Re: LZDOMESTIC transmits but doesn't log complete sent exchange

John Bednar
 

Leo,

 

Are your function key messages identical?

 

Are you both advancing the cursor from the callsign box to the exchange box by pressing ENTER in ESM or space bar in non-ESM mode?

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Lyubomir Slavov, OR2F
Sent: Monday, February 10, 2020 8:38 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] LZDOMESTIC transmits but doesn't log complete sent exchange

 

Hi All !

 

I was asked by LZ-fellow to rise the issue he has :

During whole LZ-domestic tournament period the sent exchanges are transmitted complete and correct but on some QSO lines or all of them in the log the second half / {LASTEXCH} is missing .. as well as it doesn't appear afterwards in the generated Cabrillo, ie. extra time+error risk to write them addendum in the text file.

 

image.png

 

Same behavior with LZDOMESTIC, LZOPEN, LZFILED etc.

Same behavior with Windows7 and Windows10

 

With me all is 100% OK, I can't reproduce such a phenomena ... neither on the my pc with Win7 nor Win10.

 

...

 

Just for test, on the pc with Win7 he has installed very old N1MM-Classic pack and did same simulation with same result - the 'EXCH' column of the log keeps blank:

 

image.png

 

Any idea what could be the root cause ?

 

73,
Leo / OR2F