Date   
Re: WAE RTTY QTC sending with N1MM+ and TinyFSK

Jim Ciurczak
 

Larry I remember seeing another post about garbled QTC's being sent but I no longer see it. I had responded to it because I had several requests for my QTC's to be resent as they were garbled. The set up here is N1MM+ 1.0.7300, Windows 10, FT2000 and a Microham USB III interface in FSK mode.. Wondering if this bug may have had the same effect?

Jim K2QB

Re: WAE RTTY SQTC issue

John Huecksteadt
 

I had exactly that problem. Always #10 and many times #9.

On Nov 13, 2018, 14:57 -0600, Kenneth Grimm <grimm@...>, wrote:
When sending QTCs nine times out of ten, the receiving station would ask for a repeat of NR 10.  Occasionally there would be other NRs that would be requested, but invariably, if a repeat was requested, NR 10 was always included.  A couple of questions:  1) Did anyone else observe anything like this? and 2) Any suggestions for fixing this issue?

The one possibility that occurred to me was that maybe in the SQTC Setup for RTTY for QTC spacing, I might use {ENTERLF} instead of {ENTER}.  I'm reluctant to make the change without knowing for sure that I'm not going to mess something up by doing so.

73,
--
Ken - K4XL
BoatAnchor Manual Archive
BAMA - http://bama.edebris.com

Re: WAE RTTY SQTC issue

N6KW Chuck Miller
 

Perhaps merely QSB instead of something wrong with the software? Condx not very friendly right now, at least here in the great frozen north of Seattle.

73, Chuck N6KW

On 2018-11-13 14:06, John Huecksteadt wrote:
I had exactly that problem. Always #10 and many times #9.
On Nov 13, 2018, 14:57 -0600, Kenneth Grimm <grimm@...>, wrote:
When sending QTCs nine times out of ten, the receiving station would ask for a repeat of NR 10.  Occasionally there would be other NRs that would be requested, but invariably, if a repeat was requested, NR 10 was always included.  A couple of questions:  1) Did anyone else observe anything like this? and 2) Any suggestions for fixing this issue?

The one possibility that occurred to me was that maybe in the SQTC Setup for RTTY for QTC spacing, I might use {ENTERLF} instead of {ENTER}.  I'm reluctant to make the change without knowing for sure that I'm not going to mess something up by doing so.

73,
--
Ken - K4XL
BoatAnchor Manual Archive
BAMA - http://bama.edebris.com

Re: WAE RTTY SQTC issue

Olli
 

I observed this as a QTC recipient a few times. The effect was always that the sending station stopped it‘s transmission in the middle of QTC 10 about in the middle of the callsign transmitted as part of QTC 10. A few times this already happened during transmission of QTC 9 so I had to ask for repeats of both, QTC 9 & 10.

When sening QTCs myself I was not asked for more repeats of QTC 10 than others (in general very seldomly at all) using NL+ latest version. But I did not send that many QTCs.

Maybe it‘s a problem of NL+ QTC tx module?

73, Olli - DH8BQA
https://www.dh8bqa.de/





Dienstag, 13. November 2018, 21:57 +0100 von grimm@... <grimm@...>:

When sending QTCs nine times out of ten, the receiving station would ask for a repeat of NR 10.  Occasionally there would be other NRs that would be requested, but invariably, if a repeat was requested, NR 10 was always included.  A couple of questions:  1) Did anyone else observe anything like this? and 2) Any suggestions for fixing this issue?

The one possibility that occurred to me was that maybe in the SQTC Setup for RTTY for QTC spacing, I might use {ENTERLF} instead of {ENTER}.  I'm reluctant to make the change without knowing for sure that I'm not going to mess something up by doing so.

73,
--
Ken - K4XL
BoatAnchor Manual Archive
BAMA - http://bama.edebris.com

Re: WAE RTTY SQTC issue

Steve NN2NN
 

Yes... noticed that here. Nearly always 10 and sometimes QTC 7, 8 or 9. I can’t remember exactly which one, but in my observation, it seemed like a LF was missing ( could have been QRM or QSB) which messed it up for the receiving station. Just that it was regularly the same QTC’s which makes me believe it was not a signal strength issue.

Steve NN2NN

Re: WAE RTTY SQTC issue

Walt K <k2waltk@...>
 

Sounds like buffer overflow.

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On
Behalf Of Steve NN2NN
Sent: Tuesday, November 13, 2018 5:55 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] WAE RTTY SQTC issue

Yes... noticed that here. Nearly always 10 and sometimes QTC 7, 8 or 9. I
can't
remember exactly which one, but in my observation, it seemed like a LF was
missing
( could have been QRM or QSB) which messed it up for the receiving
station. Just
that it was regularly the same QTC's which makes me believe it was not a
signal
strength issue.

Steve NN2NN

Re: ICOM 7300 using DVK Messages

Scott
 

Thank you Rich, John, etc. for the replies. I was working on this tonight and I was successfully able to send a series of my .wav files for the exchange:

Two examples:

F2 Exch,! nr.wav # ssexch.wav -  (I'm able to send entire exchange for late night operating and not wake up the XYL)

F4 KN3A,{CAT1Hex FE FE 94 E0 28 00 01 FD} - Sends my callsign from in the rig - I like the recorded audio quality better than Audacity.

Thanks for the help everyone and see you in the contest and hopefully a clean sweep.

73 Scott
KN3A

Re: ICOM 7300 using DVK Messages

Scott
 

Rich,

As I just posted a few minutes ago, I got the EXCH working like this: F2 Exch,! nr.wav # ssexch.wav 

I just tried doing this: F2 Exch,! nr.wav # {END}{CAT1Hex FE FE 94 E0 28 00 01 FD} - however it did not read the exchange from in the 7300.

No big deal, I will be using my 7300 DVK for everything else. My guess is there's not a way to mix the two in one macro.

Scott
KN3A

3 bugs in the DI under RTTY So2r operation

Jeff AC0C
 

#1 - Callstack - in the WAE contest not too many opportunities to use the callstack function but it seems the "blank" callsign problem remains meaning a couple of times the program thought I had a callsign in the stack when there was none and it sent the NOW message with a blank callsign.  Fortunately it was easy to clear this time which is a big improvement over the CQ DX RTTY. This comment is based only on perhaps 15 uses of the callstack function this weekend.

#2 - Callstack - the FIFO/mults first function does not work. It's LIFO only.

#3 - CLEAR ON QSY - The clear grab and receive window on QSY has a bug that I think has been around for a long time in some variation.  The way I saw it this weekend was:

QSY on rig 1 --> clears DI window for rig 2 (problem with this one)
QSY on rig 2 --> clears DI window for rig 2 (correct function)

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com

New version of MM issue (no SS mults)

wk4r
 

Downloaded new version and have a problem which I did not have before the download.  I am unable to pull up the window for the section/states for SS.  I did not have this issue with the old version for SSCW.  Went back to the SSCW I did two weeks ago and the mults will not appear there anymore either.

Bill KH7XS/K4XS

Re: New version of MM issue (no SS mults)

Tom Wagner (N1MM)
 

That was not affected by the changes.

Try opening it again. -or-

Try opening it again while holding the ctl key down. Look at the bottom edge of all monitors for the window. The title bar should be just visible. -or-

Change this section in your ini file:

[SectionMults]
Height=367
IsOpen=False
Left=133
Top=288
Width=944
WindowState=0

Change the Left & Top values to zero.

73,

Tom - n1MM

On 11/14/2018 12:06 AM, wk4r via Groups.Io wrote:
Downloaded new version and have a problem which I did not have before the download.  I am unable to pull up the window for the section/states for SS.  I did not have this issue with the old version for SSCW.  Went back to the SSCW I did two weeks ago and the mults will not appear there anymore either.

Bill KH7XS/K4XS

Re: New version of MM issue (no SS mults)

wk4r
 

Tom

Followed your recommendations.  All is good.  You're the man!

73  Bill  K4XS/KH7XS

SntNR 001 twice

Jaan, SM9X
 

I have seen a issue when running contests every week for at least two latest versions of the Logger +

I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR

QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005

This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC

I noticed the same from another ham in a SOAPBOX comment: 

OH3BCX: N1MM made a double on the 1st QSO, and I thought I have to correct them all... "


I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.

Regards, Jaan
SM9X

Re: SntNR 001 twice

Steve London
 

Can you reproduce this outside of the contest ?

Can you go back to an earlier version and show that it doesn't happen ?

73,
Steve, N2IC

On 11/15/2018 01:25 AM, Jaan, SM9X wrote:
I have seen a issue when running contests every week for at least two latest versions of the Logger +
I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR
QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005
This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC
I noticed the same from another ham in a SOAPBOX comment:
*OH3BCX:* N1MM made a double on the 1st QSO, and I thought I have to correct them all... "
I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.
Regards, Jaan
SM9X

Re: SntNR 001 twice

'Zaba' OH1ZAA
 

Hello Steve,

It was during OK1WC Memorial (MWC) that I was running OH3BCX and
the log started with a double 001 given sequence at the start...
It did the same with another contest, but then ever since it has
not occurred again. I guess I was also running v.1.0.7300 at the time.

Cheers/73, Zaba OH1ZAA



Steve London kirjoitti 15.11.2018 16:23:

Can you reproduce this outside of the contest ?
Can you go back to an earlier version and show that it doesn't happen ?
73,
Steve, N2IC
On 11/15/2018 01:25 AM, Jaan, SM9X wrote:
I have seen a issue when running contests every week for at least two latest versions of the Logger +
I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR
QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005
This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC
I noticed the same from another ham in a SOAPBOX comment:
*OH3BCX:* N1MM made a double on the 1st QSO, and I thought I have to correct them all... "
I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.
Regards, Jaan
SM9X

Re: SntNR 001 twice

Barry Bettman
 

In some contest, being a multi will have a separate set of serial number for each band. Could this be the case in your situation? Barry K6ST


On Thursday, November 15, 2018, 'Zaba' OH1ZAA <elefa@...> wrote:

Hello Steve,

It was during OK1WC Memorial (MWC) that I was running OH3BCX and
the log started with a double 001 given sequence at the start...
It did the same with another contest, but then ever since it has
not occurred again. I guess I was also running v.1.0.7300 at the time.

Cheers/73, Zaba OH1ZAA



Steve London kirjoitti 15.11.2018 16:23:
Can you reproduce this outside of the contest ?

Can you go back to an earlier version and show that it doesn't happen ?

73,
Steve, N2IC

On 11/15/2018 01:25 AM, Jaan, SM9X wrote:
I have seen a issue when running contests every week for at least two latest versions of the Logger +

I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR

QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005

This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC

I noticed the same from another ham in a SOAPBOX comment:

*OH3BCX:*       N1MM made a double on the 1st QSO, and I thought I have to correct them all... "


I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.

Regards, Jaan
SM9X










--

Barry

Barry Bettman, ATL, PCC
"Approved Tribal Leader" consultant for workplace culture
"Professional Certified Coach" with leaders and executives
775-622-3801

LEADERSHIP FOR EVERYONE TO BE GREAT TOGETHER
Executive Producer, Stage 5 Leadership Productions - Real Time High Engagement Teleseminars

Update today - No Permission - Aborting ??

Richard Stein
 

Not sure what this is about but when I went to update my laptop today I got a message that said something like this: No Permission – Aborting

Never seen this before & I generally update each week when an N1MM update is available.

Anyone know what’s happening

73,

Dick, K2ZR

 

Re: Update today - No Permission - Aborting ??

Gilbert Baron W0MN
 

There should be more information than that. Show the entire message. It could mean a million things.

Did you get any messages when you tried to start the update? Are you running any Malware programs?

 

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Richard Stein
Sent: Thursday, November 15, 2018 12:41
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Update today - No Permission - Aborting ??

 

Not sure what this is about but when I went to update my laptop today I got a message that said something like this: No Permission – Aborting

Never seen this before & I generally update each week when an N1MM update is available.

Anyone know what’s happening

73,

Dick, K2ZR

 

Re: Update today - No Permission - Aborting ??

Gerald Boutin (VE1DT)
 

On Thu, Nov 15, 2018 at 02:41 PM, Richard Stein wrote:

Not sure what this is about but when I went to update my laptop today I got a message that said something like this: No Permission – Aborting

Never seen this before & I generally update each week when an N1MM update is available.

Anyone know what’s happening

73,

Dick, K2ZR

 

Dick,

Does the error stil happen or was it a one time event?

The exact wording and where the error came from would help in diagnosing the issue. If it is an N1MM error, the error message should be in the LogError.txt file, which is typically stored in: C:\Users\username\Documents\N1MM Logger+

N1MM+ error messages are time stamped and saved in that file.

It could be that your antivirus program was being overly suspicious and caused this error to show up. To test, you ccn either add an exception to the antivirus software or just temporarily disable it while doing the update.
 
--
Gerald, VE1DT

Re: Log window frequency precision

Todd Shiffer
 

I changed those settings from 2 to 9 both is numbers & currency, n1mm still rounds up! column is wide enough. change say 14074.38 to 14074.388 log window displays 14074.39 but leave it as 14.074.38 log window displays 14074.38