Date   

Re: N1MM Crash due to bad Audio Config

Patrick Herborn
 

On Wed, 2 Oct 2019 07:30:10 -0400
"John Bednar via Groups.Io" <k3ct=verizon.net@groups.io> wrote:

Pat,
Hiya John!

Post your function key text.
Since we don't use function keys on this machine, the function key
text will be as per installation default (ie we haven't changed it).
I won't have access to this until Thursday night - but presumably
the fact we haven't changed it should help in the meantime.

Were you in S&P or RUN mode?
This was in S&P mode. The only time we went into Run mode last night
was after the event, as a testing thing, where I tried function keys
to see if they, like Insert, could crash N1MM+ and indeed they could.
Once the audio was configured to a dummy device (ie not one connected
to the rig or outputting an audible level of sound) it was possible
to hit F keys - this included F1 which then put N1MM+ into Run mode.

I expect that ESM was enabled.
I don't recall having enabled ESM, so unless it's a default setting
then it wouldn't have been enabled. I should perhaps have stated that
N1MM+ was being used purely as a logger for a VHF SSB contest (though
we do use the spectrum, bandmap, check, log and mults/squares windows).

Please confirm.
I can do that, but not until Thursday.

John, K3CT
Best regards,

Pat.


-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Patrick Herborn
Sent: Wednesday, October 02, 2019 7:18 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] N1MM Crash due to bad Audio Config


Last night I think I finally figured out why N1MM+ would occasionally
crash - previously I had it narrowed down to "being in the Locator
box and pressing <unknown> key(s)" but last night I caught it. I think
what had previously happened was going to the locator box to correct
it (eg if someone /P is in a different locator to "normal") and then
hitting Enter to log it. Between the correction, the <unknown> key
and pressing Enter, an error box would pop up, and Enter would
acknowledge it - so whilst in full typing flow, it was not possible
to see what was in the error box, by the time it would pop up, Enter
was already being pressed.

Last night was less of a rush and I caught it. The issue was the
Insert key and the error box was warning of a bad Audio config. OK
fair enough, BUT that should not crash N1MM+ to the point that it
exits! Moreover, given that there was no file to be found associated
with the Insert key, it seems that the cart was put before the horse,
metaphorically - ie there's little point in even trying to open
an audio device if the audio file you would then play, doesn't
exist. It seems to me to be more sensible to check for that file
first.... but even the way round that it is, it looks like there
is an exception that's not being caught properly. Just to be sure
I checked other F-keys and sure enough they also cause crashes,
so it can be summarised as ANY attempt to play audio will cause
a fatal crash.

So long as some dummy audio devices are configured N1MM+ will not
crash - it just warns that the audio file does not exist and carries
on as one would expect. This is a workaround rather than a fix.

This was observed last night on the latest release, on Win7 64 bit
and it was set to normal audio (never been configured since we
don't use that feature on that station), ie not Logger+ Audio.

Best regards,

Pat. (M0MGO)

--
Patrick Herborn <pat@...>





--
Patrick Herborn <pat@...>


New Super Check Partial files available VER20191002 (02 OCT 2019)

Stu K6TU
 

A New release of the Super Check Partial database files is available at:

http://www.supercheckpartial.com

Calls in the MASTER.DTA file: 36,908

If you would like to contribute your CABRILLO format logs for the SCP database, please send them at any time.

The easiest thing to do is to bcc the following email address:

logs@...

...when you submit your log to the sponsor’s robot after each contest.

Please DO NOT send ADIF files, your LOGGER database file, 3830 postings... just CABRILLO! :-)

You can send more than one log attachment in a single email BUT PLEASE DON’T SEND THEM IN A ZIP file!

If you want to check the version of the SCP files you are using, look for a call beginning with “VER2". Every SCP file includes the version number in the list of calls in the format VERYYYYMMDD.

The next release of the database will be at the beginning of November 2019. Any requested changes or deletions of callsigns received by NOON PDT on November 1st, 2019 will be included in that release.

PLEASE MAKE SURE TO SEND ADD/CHANGE MESSAGES WITHOUT ATTACHED LOGS OTHERWISE I PROBABLY WON’T SEE YOUR REQUEST due to the email processing robot.

IMPORTANT: Before sending an add/change message, please check the LATEST version of the SCP database to see whether your requested change (especially add requests) is unnecessary because the call is already present.

Please let me know if you find any bad calls in the files.
Thanks again to all the contributors!
Stu K6TU


Re: M/1 Partner TXing

Lu Romero - W4LT
 

Not a bad suggestion/idea to have this info available in a more convenient location.  I agree it would be important in a remote operator environment. While the info is available in the Network windows, it isn't intuitive to find there.

My preference, if this is considered, to NOT put it in the Entry Window. My preference would be for this to be displayed in a SEPARATE window that could be turned on or turned off as needed.  One of the best things about this Logger is the ability to customize the display by adding or subtracting windows as needed for both a given operator use case.

While it would be handy for some operator environments to display this info in a more convenient place, not all operator environments need this information.  

Keep the Entry window simple and uncluttered with information and displays that may not be needed for the majority of use cases.

73

-lu w4lt-


Re: N1MM Crash due to bad Audio Config

John Bednar
 

Pat,

Post your function key text.

Were you in S&P or RUN mode?
I expect that ESM was enabled. Please confirm.

John, K3CT

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Patrick Herborn
Sent: Wednesday, October 02, 2019 7:18 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] N1MM Crash due to bad Audio Config


Last night I think I finally figured out why N1MM+ would occasionally
crash - previously I had it narrowed down to "being in the Locator
box and pressing <unknown> key(s)" but last night I caught it. I think
what had previously happened was going to the locator box to correct
it (eg if someone /P is in a different locator to "normal") and then
hitting Enter to log it. Between the correction, the <unknown> key
and pressing Enter, an error box would pop up, and Enter would
acknowledge it - so whilst in full typing flow, it was not possible
to see what was in the error box, by the time it would pop up, Enter
was already being pressed.

Last night was less of a rush and I caught it. The issue was the
Insert key and the error box was warning of a bad Audio config. OK
fair enough, BUT that should not crash N1MM+ to the point that it
exits! Moreover, given that there was no file to be found associated
with the Insert key, it seems that the cart was put before the horse,
metaphorically - ie there's little point in even trying to open
an audio device if the audio file you would then play, doesn't
exist. It seems to me to be more sensible to check for that file
first.... but even the way round that it is, it looks like there
is an exception that's not being caught properly. Just to be sure
I checked other F-keys and sure enough they also cause crashes,
so it can be summarised as ANY attempt to play audio will cause
a fatal crash.

So long as some dummy audio devices are configured N1MM+ will not
crash - it just warns that the audio file does not exist and carries
on as one would expect. This is a workaround rather than a fix.

This was observed last night on the latest release, on Win7 64 bit
and it was set to normal audio (never been configured since we
don't use that feature on that station), ie not Logger+ Audio.

Best regards,

Pat. (M0MGO)

--
Patrick Herborn <pat@...>


N1MM Crash due to bad Audio Config

Patrick Herborn
 

Last night I think I finally figured out why N1MM+ would occasionally
crash - previously I had it narrowed down to "being in the Locator
box and pressing <unknown> key(s)" but last night I caught it. I think
what had previously happened was going to the locator box to correct
it (eg if someone /P is in a different locator to "normal") and then
hitting Enter to log it. Between the correction, the <unknown> key
and pressing Enter, an error box would pop up, and Enter would
acknowledge it - so whilst in full typing flow, it was not possible
to see what was in the error box, by the time it would pop up, Enter
was already being pressed.

Last night was less of a rush and I caught it. The issue was the
Insert key and the error box was warning of a bad Audio config. OK
fair enough, BUT that should not crash N1MM+ to the point that it
exits! Moreover, given that there was no file to be found associated
with the Insert key, it seems that the cart was put before the horse,
metaphorically - ie there's little point in even trying to open
an audio device if the audio file you would then play, doesn't
exist. It seems to me to be more sensible to check for that file
first.... but even the way round that it is, it looks like there
is an exception that's not being caught properly. Just to be sure
I checked other F-keys and sure enough they also cause crashes,
so it can be summarised as ANY attempt to play audio will cause
a fatal crash.

So long as some dummy audio devices are configured N1MM+ will not
crash - it just warns that the audio file does not exist and carries
on as one would expect. This is a workaround rather than a fix.

This was observed last night on the latest release, on Win7 64 bit
and it was set to normal audio (never been configured since we
don't use that feature on that station), ie not Logger+ Audio.

Best regards,

Pat. (M0MGO)

--
Patrick Herborn <pat@...>


Re: Most Recent Update

John Bednar
 

Tom,

 

If it still exists, tell us how to duplicate your observation.

 

If you move focus to another non-N1MM Logger program like email the ESC key will be sent to that software and not our code. So make sure the Entry window has focus.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Tom Owens via Groups.Io
Sent: Wednesday, October 02, 2019 4:35 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Most Recent Update

 

Did it address the problem with the ESC key not killing repeating CQs?

Tom, K7RI


Most Recent Update

Tom Owens
 

Did it address the problem with the ESC key not killing repeating CQs?

Tom, K7RI


Re: Two observations from CQWW RTTY

Dave Hachadorian
 

The function key lockup that I experienced was not a temporary lockup for just a few seconds.  It was a complete and total lockup of the function keys on a very fast computer.  I think it always occurred after ESM had gotten out of sequence in the QSO.
 
Only CTRL-K, or INSERT got things working again.
 
Dave Hachadorian, K6LL
Yuma, AZ
 

From: K7XC Tim Marek
Sent: Tuesday, October 1, 2019 11:33 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Two observations from CQWW RTTY
 
Hi Folks,
 
I had several windows open and that caused N1MM+ ,while running RTTY as well, to freeze for a few seconds now and then. I closed all but what was needed and the problem became much less.
 
73s de Tim - K7XC - DM09jh... sk
 
Adapt, Overcome, Succeed!
 
 
On Mon, Sep 30, 2019 at 6:46 PM Richard Zalewski <dick.w7zr@...> wrote:
I experienced #2 also.

Richard
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV

 
Be joyful in hope, patient in affliction, faithful in prayer
 
 
On Mon, Sep 30, 2019 at 11:17 AM Jamie WW3S <ww3s@...> wrote:
we at K3LR observed #1 as well....dont recall ever seeing #2. Our biggest concern was the callsign stack window not staying open on the screen, and telnet randomly closing when minimized.....now if there was only a button to cancel solar events during the contest !!!! For the most part everything ran well. If I had one wish it would be to  move the run/mult indicator from the INFO window to the entry window and also the bandchange counter.....okay, amybe thats 2 wishes !!! Great job N1MM team, and kudos to Rick N2AMG for fantastic support during the contest.....
 
------ Original Message ------
From: "Dave Hachadorian" <k6ll.dave@...>
To: "N1MM Loggerplus" <N1MMLoggerPlus@groups.io>
Sent: 9/30/2019 2:06:08 PM
Subject: [N1MM+] Two observations from CQWW RTTY
 
1. When you click on a Telnet spot from the band map, the call goes into the on-deck area above the call sign field in the data entry window.  So far so good.  But when you call the station by hitting the Enter Key (ESM), the call sign does not drop down into the call sign field.  You have to hit the space bar to make it drop down.  Shouldn’t the call drop down automatically, if the “big gun” switch is activated in config/function keys, with the cursor sitting in the next data entry field?
 
2.  About ten times during the contest, all of the function keys, including the Enter key, totally locked up.  I think this always happened when the ESM sequence had been disturbed somehow.  I found that I could recover by hitting CTRL-K and sending the desired message manually.  Everything worked normally after that.  The operators at W7WW reported the exact same experience, about ten lockups on abnormal
ESM sequences, but they found that they could recover by hitting the INSERT key.
 
Other than that, the program worked flawlessly in SO2R for the entire 48 hours.
 
Thanks!
 
Dave Hachadorian, K6LL
Yuma, AZ
 


Re: RTTY Spot Question

Ty K3MM
 


Yes!  Reminds me of the now ancient RITTY by K6STI.  It would jump directly on freq rather than slowly sliding like others. It was way ahead of its time.  I hung onto my DOS machines as long as I could to run WF1B with unsupported RITTY.  It took a while but we now have the much more advanced N1MM and very good Gritty/2tone decoders with loads of flexibility. Still way more fun and faster than rigid FT4/8 automation.

73, Ty K3MM
Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Tuesday, October 1, 2019, Tim Shoppa <tshoppa@...> wrote:

Yeah, Auto-QSX is the Jackrabbit icon :-)

I keep one Gritty running with it turned on, and another one with it turned off. 

MMTTY AFC is near-useless, and 2-Tone's AFC is useful for eventually tuning in the very slightly off-frequency callers, but Gritty Jackrabbit mode is terrific and instantaneously (in fact "backwards in time") locks onto callers who are 50-200Hz or more off frequency.

Tim N3QE


On Tue, Oct 1, 2019 at 8:37 PM Jamie WW3S <ww3s@...> wrote:
Is jackrabbit mode what the author calls Auto-QSX?


On Oct 1, 2019, at 3:22 PM, Ty K3MM via Groups.Io <k3mm@...> wrote:

AFC is mostly fine if you set the MMTTY response to a about 4 and to reset to 2125 after a QSO.  

Ty K3MM

Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Tuesday, October 1, 2019, Tim Shoppa <tshoppa@...> wrote:

The convention for "RTTY Frequency" is the Mark frequency.

Although sometimes you see spots like 14070.42, those are rare and you will much more likely see 14070.4. The accuracy and repeatability of RBN RTTY spots is often as good as +/-100Hz but almost as often can be +/- 200Hz. None of 100 or 200 Hz is accurate enough to necessarily get a decode on a 170Hz shift signal. So after any clicking on a spot you have to fine tune (either with VFO knob or with AFC in the decoder) by 50-200Hz. I can tell you, with extensive RTTY practice giving me superb ear-hand coordination, I can tune in a RTTY signal with the VFO knob in a fraction of a second so I do not use AFC in the decoder which tends to respond much slower. (ALTHOUGH Gritty jackrabbit mode actually "tunes backwards in time" if that makes any sense to you and is also useful. I usually keep two Gritty's open, one with jackrabbit mode off and the other with jackrabbit mode on).

Pete, when using AFSK, you can get N1MM's frequency readout and QSY'ing to clicked on spots, to do the math for the 2.1kHz (or whatever audio offset you use) offset by choosing "Turn Auto TRXUpdate On" inside The DI Setup menu. Note that many radios can be programmed to do the 2.1kHz offset for AFSK and if you do that, then you DO NOT want to use the 2.1kHz offset applied by Auto TRXUpdate. If you are using decoders with AFC enabled, your receive frequency can go ALL OVER THE PLACE and I hate hate hate operating with AFC enabled because it never does the right thing.

Tim N3QE

<image.png>

On Tue, Oct 1, 2019 at 7:55 AM Pete Smith <n4zr@...> wrote:

Last weekend's CQWWRTTY left me wondering why spots, either conventional or from the RBN, were so little use for S&P.  There are a number of contributory causes, beginning with the frequency calibration of RBN nodes, but in the course of putting this all together I realized that I don't know some fundamental things.   I've looked in the manual, without success, so I'm hoping somebody can point me in the right direction.

First off, I was running AFSK  on my K3, with MMTTY as my only decoder.  All weekend long,the title bar of the Entry window was reporting a radio frequency that was about 2.1 KHz lower than my radio's frequency readout.  I presumed at the time that my radio was reporting my suppressed carrier frequency, while MM+ was reporting either the Mark or the Space frequency in Lower Sideband.  Is that in fact the case?  If I had been running FSK, would the two (the K3 and MM+) agree on the frequency?  What's the convention, if there is one?  Mark or Space, or?

This phenomenon appears to go along with whether the Digital Interface is open.  In fact, when I began to write this, I had N1MM open but the DI not, and the radio and program frequencies were the same.  What's the rationale - or is this something imposed by MMTTY, somehow?

As an experiment, I hooked up directly to the Telnet output of the RBN server, because some RBN nodes now are sending two significant digit spots on RTTY - like 14070.42.  It's damned hard to find RTTY spots from RBN nodes reporting 2-digit frequencies in non-contest time - in fact, I ran MM+ overnight collecting spots from the RBN's Telnet feed, and did not get any 2-digit RTTY spots, so this remains an open question.

-- 

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.

<image.png>


Re: RTTY Spot Question

Tim Shoppa
 

Yeah, Auto-QSX is the Jackrabbit icon :-)

I keep one Gritty running with it turned on, and another one with it turned off. 

MMTTY AFC is near-useless, and 2-Tone's AFC is useful for eventually tuning in the very slightly off-frequency callers, but Gritty Jackrabbit mode is terrific and instantaneously (in fact "backwards in time") locks onto callers who are 50-200Hz or more off frequency.

Tim N3QE


On Tue, Oct 1, 2019 at 8:37 PM Jamie WW3S <ww3s@...> wrote:
Is jackrabbit mode what the author calls Auto-QSX?


On Oct 1, 2019, at 3:22 PM, Ty K3MM via Groups.Io <k3mm@...> wrote:

AFC is mostly fine if you set the MMTTY response to a about 4 and to reset to 2125 after a QSO.  

Ty K3MM

Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Tuesday, October 1, 2019, Tim Shoppa <tshoppa@...> wrote:

The convention for "RTTY Frequency" is the Mark frequency.

Although sometimes you see spots like 14070.42, those are rare and you will much more likely see 14070.4. The accuracy and repeatability of RBN RTTY spots is often as good as +/-100Hz but almost as often can be +/- 200Hz. None of 100 or 200 Hz is accurate enough to necessarily get a decode on a 170Hz shift signal. So after any clicking on a spot you have to fine tune (either with VFO knob or with AFC in the decoder) by 50-200Hz. I can tell you, with extensive RTTY practice giving me superb ear-hand coordination, I can tune in a RTTY signal with the VFO knob in a fraction of a second so I do not use AFC in the decoder which tends to respond much slower. (ALTHOUGH Gritty jackrabbit mode actually "tunes backwards in time" if that makes any sense to you and is also useful. I usually keep two Gritty's open, one with jackrabbit mode off and the other with jackrabbit mode on).

Pete, when using AFSK, you can get N1MM's frequency readout and QSY'ing to clicked on spots, to do the math for the 2.1kHz (or whatever audio offset you use) offset by choosing "Turn Auto TRXUpdate On" inside The DI Setup menu. Note that many radios can be programmed to do the 2.1kHz offset for AFSK and if you do that, then you DO NOT want to use the 2.1kHz offset applied by Auto TRXUpdate. If you are using decoders with AFC enabled, your receive frequency can go ALL OVER THE PLACE and I hate hate hate operating with AFC enabled because it never does the right thing.

Tim N3QE

<image.png>

On Tue, Oct 1, 2019 at 7:55 AM Pete Smith <n4zr@...> wrote:

Last weekend's CQWWRTTY left me wondering why spots, either conventional or from the RBN, were so little use for S&P.  There are a number of contributory causes, beginning with the frequency calibration of RBN nodes, but in the course of putting this all together I realized that I don't know some fundamental things.   I've looked in the manual, without success, so I'm hoping somebody can point me in the right direction.

First off, I was running AFSK  on my K3, with MMTTY as my only decoder.  All weekend long,the title bar of the Entry window was reporting a radio frequency that was about 2.1 KHz lower than my radio's frequency readout.  I presumed at the time that my radio was reporting my suppressed carrier frequency, while MM+ was reporting either the Mark or the Space frequency in Lower Sideband.  Is that in fact the case?  If I had been running FSK, would the two (the K3 and MM+) agree on the frequency?  What's the convention, if there is one?  Mark or Space, or?

This phenomenon appears to go along with whether the Digital Interface is open.  In fact, when I began to write this, I had N1MM open but the DI not, and the radio and program frequencies were the same.  What's the rationale - or is this something imposed by MMTTY, somehow?

As an experiment, I hooked up directly to the Telnet output of the RBN server, because some RBN nodes now are sending two significant digit spots on RTTY - like 14070.42.  It's damned hard to find RTTY spots from RBN nodes reporting 2-digit frequencies in non-contest time - in fact, I ran MM+ overnight collecting spots from the RBN's Telnet feed, and did not get any 2-digit RTTY spots, so this remains an open question.

-- 

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.

<image.png>


Re: RTTY Spot Question

Jamie WW3S
 

Is jackrabbit mode what the author calls Auto-QSX?


On Oct 1, 2019, at 3:22 PM, Ty K3MM via Groups.Io <k3mm@...> wrote:

AFC is mostly fine if you set the MMTTY response to a about 4 and to reset to 2125 after a QSO.  

Ty K3MM

Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Tuesday, October 1, 2019, Tim Shoppa <tshoppa@...> wrote:

The convention for "RTTY Frequency" is the Mark frequency.

Although sometimes you see spots like 14070.42, those are rare and you will much more likely see 14070.4. The accuracy and repeatability of RBN RTTY spots is often as good as +/-100Hz but almost as often can be +/- 200Hz. None of 100 or 200 Hz is accurate enough to necessarily get a decode on a 170Hz shift signal. So after any clicking on a spot you have to fine tune (either with VFO knob or with AFC in the decoder) by 50-200Hz. I can tell you, with extensive RTTY practice giving me superb ear-hand coordination, I can tune in a RTTY signal with the VFO knob in a fraction of a second so I do not use AFC in the decoder which tends to respond much slower. (ALTHOUGH Gritty jackrabbit mode actually "tunes backwards in time" if that makes any sense to you and is also useful. I usually keep two Gritty's open, one with jackrabbit mode off and the other with jackrabbit mode on).

Pete, when using AFSK, you can get N1MM's frequency readout and QSY'ing to clicked on spots, to do the math for the 2.1kHz (or whatever audio offset you use) offset by choosing "Turn Auto TRXUpdate On" inside The DI Setup menu. Note that many radios can be programmed to do the 2.1kHz offset for AFSK and if you do that, then you DO NOT want to use the 2.1kHz offset applied by Auto TRXUpdate. If you are using decoders with AFC enabled, your receive frequency can go ALL OVER THE PLACE and I hate hate hate operating with AFC enabled because it never does the right thing.

Tim N3QE

<image.png>

On Tue, Oct 1, 2019 at 7:55 AM Pete Smith <n4zr@...> wrote:

Last weekend's CQWWRTTY left me wondering why spots, either conventional or from the RBN, were so little use for S&P.  There are a number of contributory causes, beginning with the frequency calibration of RBN nodes, but in the course of putting this all together I realized that I don't know some fundamental things.   I've looked in the manual, without success, so I'm hoping somebody can point me in the right direction.

First off, I was running AFSK  on my K3, with MMTTY as my only decoder.  All weekend long,the title bar of the Entry window was reporting a radio frequency that was about 2.1 KHz lower than my radio's frequency readout.  I presumed at the time that my radio was reporting my suppressed carrier frequency, while MM+ was reporting either the Mark or the Space frequency in Lower Sideband.  Is that in fact the case?  If I had been running FSK, would the two (the K3 and MM+) agree on the frequency?  What's the convention, if there is one?  Mark or Space, or?

This phenomenon appears to go along with whether the Digital Interface is open.  In fact, when I began to write this, I had N1MM open but the DI not, and the radio and program frequencies were the same.  What's the rationale - or is this something imposed by MMTTY, somehow?

As an experiment, I hooked up directly to the Telnet output of the RBN server, because some RBN nodes now are sending two significant digit spots on RTTY - like 14070.42.  It's damned hard to find RTTY spots from RBN nodes reporting 2-digit frequencies in non-contest time - in fact, I ran MM+ overnight collecting spots from the RBN's Telnet feed, and did not get any 2-digit RTTY spots, so this remains an open question.

-- 

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.

<image.png>


Re: Two observations from CQWW RTTY

Rag LB-Three-RE Stein-Roar
 

Hello

This happens if you have long time to store spots in telnet/bandmap

Default is 5 minutes

I set to 1 minute, if 5 min then rtty window freeze or hang

I had to use writelog for rtty

Best Regards,
Stein-Roar Brobakken
LB3RE K3RAG 
Skype: lb3re.rag

1. okt. 2019 kl. 20:33 skrev K7XC Tim Marek <K7XCNV1@...>:

Hi Folks,

I had several windows open and that caused N1MM+ ,while running RTTY as well, to freeze for a few seconds now and then. I closed all but what was needed and the problem became much less.

73s de Tim - K7XC - DM09jh... sk

Adapt, Overcome, Succeed!


On Mon, Sep 30, 2019 at 6:46 PM Richard Zalewski <dick.w7zr@...> wrote:
I experienced #2 also.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV


Be joyful in hope, patient in affliction, faithful in prayer


On Mon, Sep 30, 2019 at 11:17 AM Jamie WW3S <ww3s@...> wrote:
we at K3LR observed #1 as well....dont recall ever seeing #2. Our biggest concern was the callsign stack window not staying open on the screen, and telnet randomly closing when minimized.....now if there was only a button to cancel solar events during the contest !!!! For the most part everything ran well. If I had one wish it would be to  move the run/mult indicator from the INFO window to the entry window and also the bandchange counter.....okay, amybe thats 2 wishes !!! Great job N1MM team, and kudos to Rick N2AMG for fantastic support during the contest.....

------ Original Message ------
From: "Dave Hachadorian" <k6ll.dave@...>
To: "N1MM Loggerplus" <N1MMLoggerPlus@groups.io>
Sent: 9/30/2019 2:06:08 PM
Subject: [N1MM+] Two observations from CQWW RTTY

1. When you click on a Telnet spot from the band map, the call goes into the on-deck area above the call sign field in the data entry window.  So far so good.  But when you call the station by hitting the Enter Key (ESM), the call sign does not drop down into the call sign field.  You have to hit the space bar to make it drop down.  Shouldn’t the call drop down automatically, if the “big gun” switch is activated in config/function keys, with the cursor sitting in the next data entry field?
 
2.  About ten times during the contest, all of the function keys, including the Enter key, totally locked up.  I think this always happened when the ESM sequence had been disturbed somehow.  I found that I could recover by hitting CTRL-K and sending the desired message manually.  Everything worked normally after that.  The operators at W7WW reported the exact same experience, about ten lockups on abnormal
ESM sequences, but they found that they could recover by hitting the INSERT key.
 
Other than that, the program worked flawlessly in SO2R for the entire 48 hours.
 
Thanks!
 
Dave Hachadorian, K6LL
Yuma, AZ
 


Re: RTTY Spot Question

Ty K3MM
 

AFC is mostly fine if you set the MMTTY response to a about 4 and to reset to 2125 after a QSO.  

Ty K3MM

Sent from AOL Mobile Mail
Get the new AOL app: mail.mobile.aol.com

On Tuesday, October 1, 2019, Tim Shoppa <tshoppa@...> wrote:

The convention for "RTTY Frequency" is the Mark frequency.

Although sometimes you see spots like 14070.42, those are rare and you will much more likely see 14070.4. The accuracy and repeatability of RBN RTTY spots is often as good as +/-100Hz but almost as often can be +/- 200Hz. None of 100 or 200 Hz is accurate enough to necessarily get a decode on a 170Hz shift signal. So after any clicking on a spot you have to fine tune (either with VFO knob or with AFC in the decoder) by 50-200Hz. I can tell you, with extensive RTTY practice giving me superb ear-hand coordination, I can tune in a RTTY signal with the VFO knob in a fraction of a second so I do not use AFC in the decoder which tends to respond much slower. (ALTHOUGH Gritty jackrabbit mode actually "tunes backwards in time" if that makes any sense to you and is also useful. I usually keep two Gritty's open, one with jackrabbit mode off and the other with jackrabbit mode on).

Pete, when using AFSK, you can get N1MM's frequency readout and QSY'ing to clicked on spots, to do the math for the 2.1kHz (or whatever audio offset you use) offset by choosing "Turn Auto TRXUpdate On" inside The DI Setup menu. Note that many radios can be programmed to do the 2.1kHz offset for AFSK and if you do that, then you DO NOT want to use the 2.1kHz offset applied by Auto TRXUpdate. If you are using decoders with AFC enabled, your receive frequency can go ALL OVER THE PLACE and I hate hate hate operating with AFC enabled because it never does the right thing.

Tim N3QE

image.png

On Tue, Oct 1, 2019 at 7:55 AM Pete Smith <n4zr@...> wrote:

Last weekend's CQWWRTTY left me wondering why spots, either conventional or from the RBN, were so little use for S&P.  There are a number of contributory causes, beginning with the frequency calibration of RBN nodes, but in the course of putting this all together I realized that I don't know some fundamental things.   I've looked in the manual, without success, so I'm hoping somebody can point me in the right direction.

First off, I was running AFSK  on my K3, with MMTTY as my only decoder.  All weekend long,the title bar of the Entry window was reporting a radio frequency that was about 2.1 KHz lower than my radio's frequency readout.  I presumed at the time that my radio was reporting my suppressed carrier frequency, while MM+ was reporting either the Mark or the Space frequency in Lower Sideband.  Is that in fact the case?  If I had been running FSK, would the two (the K3 and MM+) agree on the frequency?  What's the convention, if there is one?  Mark or Space, or?

This phenomenon appears to go along with whether the Digital Interface is open.  In fact, when I began to write this, I had N1MM open but the DI not, and the radio and program frequencies were the same.  What's the rationale - or is this something imposed by MMTTY, somehow?

As an experiment, I hooked up directly to the Telnet output of the RBN server, because some RBN nodes now are sending two significant digit spots on RTTY - like 14070.42.  It's damned hard to find RTTY spots from RBN nodes reporting 2-digit frequencies in non-contest time - in fact, I ran MM+ overnight collecting spots from the RBN's Telnet feed, and did not get any 2-digit RTTY spots, so this remains an open question.

-- 

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: Two observations from CQWW RTTY

K7XC Tim Marek
 

Hi Folks,

I had several windows open and that caused N1MM+ ,while running RTTY as well, to freeze for a few seconds now and then. I closed all but what was needed and the problem became much less.

73s de Tim - K7XC - DM09jh... sk

Adapt, Overcome, Succeed!


On Mon, Sep 30, 2019 at 6:46 PM Richard Zalewski <dick.w7zr@...> wrote:
I experienced #2 also.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV


Be joyful in hope, patient in affliction, faithful in prayer


On Mon, Sep 30, 2019 at 11:17 AM Jamie WW3S <ww3s@...> wrote:
we at K3LR observed #1 as well....dont recall ever seeing #2. Our biggest concern was the callsign stack window not staying open on the screen, and telnet randomly closing when minimized.....now if there was only a button to cancel solar events during the contest !!!! For the most part everything ran well. If I had one wish it would be to  move the run/mult indicator from the INFO window to the entry window and also the bandchange counter.....okay, amybe thats 2 wishes !!! Great job N1MM team, and kudos to Rick N2AMG for fantastic support during the contest.....

------ Original Message ------
From: "Dave Hachadorian" <k6ll.dave@...>
To: "N1MM Loggerplus" <N1MMLoggerPlus@groups.io>
Sent: 9/30/2019 2:06:08 PM
Subject: [N1MM+] Two observations from CQWW RTTY

1. When you click on a Telnet spot from the band map, the call goes into the on-deck area above the call sign field in the data entry window.  So far so good.  But when you call the station by hitting the Enter Key (ESM), the call sign does not drop down into the call sign field.  You have to hit the space bar to make it drop down.  Shouldn’t the call drop down automatically, if the “big gun” switch is activated in config/function keys, with the cursor sitting in the next data entry field?
 
2.  About ten times during the contest, all of the function keys, including the Enter key, totally locked up.  I think this always happened when the ESM sequence had been disturbed somehow.  I found that I could recover by hitting CTRL-K and sending the desired message manually.  Everything worked normally after that.  The operators at W7WW reported the exact same experience, about ten lockups on abnormal
ESM sequences, but they found that they could recover by hitting the INSERT key.
 
Other than that, the program worked flawlessly in SO2R for the entire 48 hours.
 
Thanks!
 
Dave Hachadorian, K6LL
Yuma, AZ
 


Band plan window

Daryl Popowitch
 

If the window has no entries (as in no data within, no frequency values within, window is blank in content), and the window is open or closed, will this condition affect operation of N1MM+?

Daryl - N8AID


Re: M/1 Partner TXing

Steve London
 

Network Status->Stations, Msg field will show this, as long as the operator is sending, using an N1MM+ function key.

73,
Steve, N2IC

On 10/01/2019 10:50 AM, Craig Thompson wrote:
Asking for a friend....
Two persons operating...one running and the other is S&P. Can you see that your partner is TXing looking at the N1MM screen somewhere? I know that the information is there because of the lockouts but can't find how to "see" the other station is TXing.
This might be useful for operating remote from each other. I just may be overlooking something.
Thanks for your help
73, Craig K9CT


Feature request

Mpridesti
 

Perhaps this feature is there but can’t find it in the document area?

Looking for a visual on the entry window instead of looking at radio display (small print on the K3). 

See below. 

Regards,

Mark, K1RX


Begin forwarded message:

From: "Mpridesti via Groups.Io" <mpridesti@...>
Date: September 29, 2019 at 10:34:17 AM EDT
To: N1MM List <N1MMLoggerPlus@groups.io>
Subject: [N1MM+] Feature request
Reply-To: N1MMLoggerPlus@groups.io

Would love to have shown in the entry window a message that show when certain function buttons are active.

Example: F10 select RX Antenna (on/off) shows RX Antenna (in red, large font) just below entry fields.

Another approach might be light up the button with RED when active?  I have labeled the button “F10 RX Ant”.

Regards,

Mark, K1RX






Re: M/1 Partner TXing

Jamie WW3S
 

It’s in the networking window, kinda clunky to use in the contest, but it’s there...you can even see what function key is being used....after several contests now with MM, I wish some of this stuff could be moved to unused space in the entry window...

Band change counter
Mult/run station indicator
Other station transmitting “meatball”

I think the other station meatball used to be in the info window, not in front of pc to check....


On Oct 1, 2019, at 12:50 PM, Craig Thompson <craig@...> wrote:

Asking for a friend....

Two persons operating...one running and the other is S&P. Can you see that your partner is TXing looking at the N1MM screen somewhere? I know that the information is there because of the lockouts but can't find how to "see" the other station is TXing. 

This might be useful for operating remote from each other. I just may be overlooking something. 

Thanks for your help

73, Craig K9CT


M/1 Partner TXing

Craig K9CT
 

Asking for a friend....

Two persons operating...one running and the other is S&P. Can you see that your partner is TXing looking at the N1MM screen somewhere? I know that the information is there because of the lockouts but can't find how to "see" the other station is TXing. 

This might be useful for operating remote from each other. I just may be overlooking something. 

Thanks for your help

73, Craig K9CT


locked Re: New Version

Tom - N1MM
 

Version 1.0.7960 (Oct 2, 2019)
  1. Entry Window: Changed the Config menu first line wording. (K3WYC) (Coded by K3CT)
  2. AZ QSO Party: Changed the bonus station callsign. (Coded by K3CT)
  3. Callstack Window: Window state was not saved to .ini file. It is now (Coded by N2AMG)
  4. WSJT Interface: Complete re-write of radio TCP connection. Is now a multi-connectiion client. (Coded by N2AMG)
    1.  This will now allow for users to switch configurations and the need to restart the radio connection is no longer needed.
    2.  This should also result in the radio dropouts as were previously happening.
    3.  Reworks the connection status on the WSJT Radio window.
  5. Adjusts some code needed for use with upcoming release of JTDX with FT4 Mode. (Coded by N2AMG)
  6. Entry Window: In RTTY when call is in On Deck window pressing Enter in ESM with the Big Gun switch on and MyCall Key highlighted will drop the call into the Entry Window and call the station. (K6LL)(Coded by N2AMG)
  7. Documentation PDF: Changed program download pointer >Tools "Download latest N1MM Logger PDF" for new File Manager on the website (Coded by K8UT)