Date
1 - 18 of 18
WPX Contest Counter Incorrect
|
Jim Ruff
I'm running WPX RTTY, and when I send my exchange, the serial number sent is different than what the actual should be. EX: On my counter in the box on the screen it should be sending 036 yet it is transmitting 042.
Any ideas on how to fix? Thanks, Jim W7JHR |
|
|
|
Haris SV1GRB
I am using this macro to send the exchange on contests with no problem: <TX> <CALL> qsl <RST> <CNTR> <CNTR> gl<RX> Haris SV1GRB Στις Κυρ, 14 Φεβ 2021 στις 5:51 μ.μ., ο/η Jim Ruff via groups.io <W7JHR=yahoo.com@groups.io> έγραψε: I'm running WPX RTTY, and when I send my exchange, the serial number sent is different than what the actual should be. EX: On my counter in the box on the screen it should be sending 036 yet it is transmitting 042. |
|
|
|
Jim Ruff
I’m using a similar exchange: 599 <CNTR> <CNTR> <MYCALL>
|
|
|
|
Ed W3NR
Are you also using N3FJP ?
Ed W3NR |
|
|
|
Jim Ruff
Yes I’m using their CQ WPX contest log.
|
|
|
|
Haris SV1GRB
No N3FJP log application used, just Fldigi. Haris Στις Κυρ, 14 Φεβ 2021 στις 6:47 μ.μ., ο/η Ed W3NR <autek@...> έγραψε: Are you also using N3FJP ? |
|
|
|
Hi Jim, Gary here (VE3DZP).
I added two new Macro buttons. #-1 <INCR> <CNTR> #2 <DECR> <CNTR> Every once in a while it would screw up but these helped me get it back right. Plus if you close the program you need to bring it back to the proper count. GL Gary |
|
|
|
Jim Ruff
Thanks everybody for all your help.
73. Jim W7JHR |
|
|
|
Dave
I saw the same thing happening, and saved my receive window text several times asking the way to confirm what I was seeing.
For example, it sent #066 to two stations in a row, although the S# (display) and the logged "sent" serial number was incremented correctly. The effect was that I sent 599 066 to one particular guy, but my log says I sent 599 067 and we will both lose the QSO point. This happened about a dozen times during ~150 QSOs. The first part of the contest I was using the N3FJP software with FLDigi and the rest without. The problem occurs In both ways. KZ1O |
|
|
|
Fred K2DFC
I had the same problem two years ago using N3FJP and FLdigi. The number sent was sometimes incorrect. For this reason I no longer get into the CQ WPX RTTY Contest. Maybe it's a configuration problem. I don't think it has anything to do with the N3FJP log. The number is generated by FLdigi.
K2DFC |
|
|
|
Jamie WW3S
Why not switch software ( hint N1MM) rather than sit out the contest ?!?!
toggle quoted message
Show quoted text
On Feb 15, 2021, at 1:47 PM, Fred K2DFC via groups.io <k2dfc@...> wrote: |
|
|
|
Fred K2DFC
Re-read my comment. The problem isn't with the contest software.
K2DFC |
|
|
|
Jamie WW3S
I had the same problem two years ago using N3FJP and FLdigi. The number sent was sometimes incorrect. For this reason I no longer get into the CQ WPX RTTY Contest. Maybe it's a configuration problem. I don't think it has anything to do with the N3FJP log. The number is generated by FLdigi.
so change software, like I said..... |
|
|
|
Fred K2DFC
Last time I looked at N1MM, which was a few years ago, you had to connect to another program like FLdigi to operate digital modes.
|
|
|
|
Rick Ellison
With N1MM the MMVARI engine is built in. you can load Fldigi, MMTTY, 2-Tone or use a TNC if you do not want to use the built in engine.
toggle quoted message
Show quoted text
The program supports over 400 contest modules and every Digital contest is supported. It also connects to WSJT or JTDX to use in the couple FTx mode contests that are supported. 73 Rick N2AMG (N1MM Digital Developer) -----Original Message-----
From: winfldigi@groups.io [mailto:winfldigi@groups.io] On Behalf Of Fred K2DFC via groups.io Sent: Monday, February 15, 2021 9:55 PM To: winfldigi@groups.io Subject: Re: [winfldigi] WPX Contest Counter Incorrect Last time I looked at N1MM, which was a few years ago, you had to connect to another program like FLdigi to operate digital modes. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
|
|
|
ve3ki
...and it is N1MM+ that generates and logs the exchanges, not the digital engine program. N1MM+'s serial number support is a core functionality that has been tested by thousands of users in innumerable CW, SSB and RTTY contests.
toggle quoted message
Show quoted text
73, Rich VE3KI On Mon, Feb 15, 2021 at 10:05 PM, Rick Ellison wrote:
With N1MM the MMVARI engine is built in. you can load Fldigi, MMTTY, 2-Tone or use a TNC if you do not want to use the built in engine. |
|
|
|
W5IO <w5io@...>
I just had the same problem with N3FJP Contest Logger for CQ WPX. This was my first time using this logging program and FLdigi.
|
|
|
|
W5IO <w5io@...>
In response to multiple comments here on Winfldigi I asked the ACLog group and recieved the below response from Scott, N3FJP.
It will hopefully help next contest where we need to send a serial number.
73
Maury
W5IO
Hide original message
----- Forwarded Message ----- From: Scott Davis via groups.io <snkdavis@...>
To: N3FJPSoftwareUsers@groups.io <n3fjpsoftwareusers@groups.io>
Sent: Thursday, February 18, 2021, 06:16:45 PM CST
Subject: Re: [N3FJPSoftwareUsers] Serial number problem
Hi All,
Thanks for your e-mail. Fldigi sends the serial number, so it needs to ensure it has the correct value. There are two ways to accomplish this. The following is from:
http://www.n3fjp.com/help/api.html
To determine the next serial number to be sent:
<CMD><NEXTSERIALNUMBER></CMD> (only functions in programs where a serial number is required).
N3FJP Software responds:
<CMD><NEXTSERIALNUMBERRESPONSE><VALUE>123</VALUE></CMD>
You can also set the next serial number to be sent:
<CMD><SETSERIALNUMBER><VALUE>12</VALUE></CMD>
Fldigi needs to implement one of these two methods to ensure it send the proper serial number. Please be sure to pass this along to the Fldigi developers. You'll find their support group here:
|
|
|