|
Can Fldigi be setup to where when I am doing a contest, and sending the Message by macros that the serial number info can be automatically increased each time in the message I send. Or is there a way to make a Macro update to the next serial number automatically? I have been reading in the help manual and still haven't figured that out. Or if that is possible.
|
Ken,
Use the <INCR> macro command to increment the SN. Be sure to initialize the serial number in the General Contest config by choosing a starting number and then Reset.
toggle quoted message
Show quoted text
On Feb 8, 2023, at 20:52, Ken Smith via < kls235@...> wrote:
Can Fldigi be setup to where when I am doing a contest, and sending the Message by macros that the serial number info can be automatically increased each time in the message I send. Or is there a way to make a Macro update to the next serial number automatically? I have been reading in the help manual and still haven't figured that out. Or if that is possible.
|
This is what I have to get serial to increment each time I send report.
<TX> <CALL> 599? <CNTR>? <CNTR>? <INCR>? <MYCALL> <RX>
I didn't add any message or commands in the Contest Exchange Serial No. (Send) box . As I am not sure what should be put in there.
|
Well the WPX contest isn't going well.? No one would reply to me, but I can reply to them and send report and get report.
But the serial number I send is one number lower that shows up in the log. I tried to straighten it out.?
And when I had to resend again to the same operator, the serial no. increased again. I was getting screwed up and gave up.?
More work to do.
|
Cliff - many thanks for your comment about clicking on the Reset button to get things rolling.? That was the piece I was missing.??
Butch - KF4HR
|
When I send a report, the serial No, that is in the? "S #" box? which is right under the Call sign,?
that number prints on the screen to the other operator.
But the number that shows up in the log "Ser In" box is one number higher than what was sent.
Then I have to go to the log and manually change the number to which was actually sent.
|
> shows up in the log "Ser In" box is one number higher than what was sent.
Does your macro look like
...<RX><INCR><LOG>
or
...<RX><LOG><INCR>
That is, do you log before you increment the number, or after?? Even better, you can use the <XBEG> and <XEND> to actually save/log what you sent.? (see )
|
Last time I did a RTTY contest like this I had nothing but problems with the serial numbers. I have avoided contests like this ever since. I would think a CONFIG feature could make this easier by advancing the serial number when a QSO is logged instead of having to make it a macro item, since so many appear to have problems. As an example, the N3FJP Nov SS contest log. The serial number starts at 001 and advances automatically after each QSO is entered (logged). The OP doesn't have to do anything but concentrate on the contest. The last time I did the WPX RTTY test I had to watch and correct the serial number being sent and set up two additional macros to do it.
Fred
K2DFC
|
flrig etal is "open source and
free (not as in free beer)" software.? The source code is
available at the same place at which you downloaded the binary
executable.? You are "free" to modify, build, test and submit
any changes you make so that others may enjoy the benefits of
your work.
73, David, W1HKJ
On 2/11/23 09:59, Fred K2DFC via
groups.io wrote:
toggle quoted message
Show quoted text
Last time I did a RTTY contest like this I had nothing but problems with the serial numbers. I have avoided contests like this ever since. I would think a CONFIG feature could make this easier by advancing the serial number when a QSO is logged instead of having to make it a macro item, since so many appear to have problems. As an example, the N3FJP Nov SS contest log. The serial number starts at 001 and advances automatically after each QSO is entered (logged). The OP doesn't have to do anything but concentrate on the contest. The last time I did the WPX RTTY test I had to watch and correct the serial number being sent and set up two additional macros to do it.
Fred
K2DFC
|
Thanks Dave. I am not a programmer, but maybe someone who is will come along and make it happen.
73, Fred
K2DFC
|
No, it is only <LOG>
I tried this <RX><INCR><LOG> and the number doubled, Like should be 95, but doubled to 97.
Next? I used <RX><DECR><LOG> and that made it come out correctly, but when I respond to another station it won't transmit.
So, not good yet.
|
Ken,
Your first example of the macro that sends the data to the OP increments the counter. Take that out and put it after <LOG> and you should be good.
toggle quoted message
Show quoted text
On Feb 11, 2023, at 13:23, Ken Smith via < kls235@...> wrote:
[Edited Message Follows]
No, it is only <LOG> I tried this <RX><INCR><LOG> and the number doubled, Like should be 95, but doubled to 97.
|
Ken,
this is what you reported as your sending macro:
This is what I have to get serial to increment each time I send report.
<TX> <CALL> 599? <CNTR>? <CNTR>? <INCR>? <MYCALL> <RX>
Take the <INCR> out of that macro and put it after the <LOG> macro.
toggle quoted message
Show quoted text
On Feb 10, 2023, at 16:08, Ken Smith via < kls235@...> wrote:
This is what I have to get serial to increment each time I send report.
<TX> <CALL> 599? <CNTR>? <CNTR>? <INCR>? <MYCALL> <RX>
|
Ken,
I guess I confused things by my email.
Quoting your previous email - below is what you are sending to the other station:
<TX> <CALL> 599? <CNTR>? <CNTR>? <INCR>? <MYCALL> <RX>
I am suggesting remove the <INCR> from your macro quoted above. The <INCR> in that position causes the serial number to increment before you log it.?
After you log then increment it after the logging macro, such as <LOG><INCR> ?No need for <RX> to start out the macro. This way the serial number will be incremented before your next contact, ASSUMING that you log each contact.
If you don't do it this way then if you use the <DECR>, as you seem to be trying now, your next contact will have the wrong serial number.?
You could also put it all in one macro if you want, however I would not do it that way because you may not want to log every one for some reason:
<TX> <CALL> 599? <CNTR>? <CNTR> ?<MYCALL> <RX> <LOG> <INCR>
On Feb 11, 2023, at 13:23, Ken Smith via < kls235@...> wrote:
[Edited Message Follows]
No, it is only <LOG> I tried this <RX><INCR><LOG> and the number doubled, Like should be 95, but doubled to 97. Next? I used <RX><DECR><LOG> and that made it come out correctly, but when I respond to another station it won't transmit. So, not good yet.
|
My macro:
<TX> 599 <CNTR> <CNTR> <RX>
next macro:
<LOG><INCR>
Rules say RST & Serial number, so why is everyone over-thinking a simple macro ?
Ed W3NR
|
This is working:?
Message Macro: <TX> <CALL> 599? <CNTR> <CNTR> <MYCALL> <RX>
Log Macro: <LOG> <INCR>
Thanks Cliff
K5XOM
|
If using FLDIGI and N3FJP Contest log, you have to be very
careful that the serial number you are sending in FLDIGI is the
same as the one that is posting in N3FJP. N3FJP Will increment the
serial number by one based on the previous serial number. If you
inadvertently hit the wrong macro, or get confused say for some
reason when you hit log it does not log in N3FJP because for
instance the serial number does not transfer into the N3FJP
Logging program due to it not being clicked on correctly, you are
in a hurry and don't notice it. Then your numbers get off by one
in the N3FJP Logger. You can be sending a number to the guy in you
are working in FLDIGI that is different than the one that is
posting in N3FJP. This happens frequently so you have to watch the
Log very carefully every time you send a number and make sure it
is the same number that is in the log. My Macros are as follows:
Last transmission when running a freq after receiving the other
guys information
<TX>
?TU CQ <MYCALL><LOG><INCR><RX>
When searching and pouncing
<LOG><INCR>
The problem I have frequently is that macros that have to timer
associated with them will repeat randomly for a reason which I
cannot figure out. This is frustrating as it will just start
repeating when I am trying? to copy the other guys information.
This drives me nuts
Larry? N8CWU
On 2/11/2023 2:23 PM, Ken Smith via
groups.io wrote:
toggle quoted message
Show quoted text
[Edited Message Follows]
No, it is only <LOG>
I tried this <RX><INCR><LOG> and the number
doubled, Like should be 95, but doubled to 97.
Next? I used <RX><DECR><LOG> and that made it
come out correctly, but when I respond to another station it won't
transmit.
So, not good yet.
|
As you? know I am new to all this. Having recently participated in a contest I've learned some things.
I use <LOG><INCR>? On it's own Macro
and I don't hit it until the exchange is over and there are no questions.
Because if the other op has a question and they ask you to resend your serial number
but? you already updated it by hitting log. Now it;s a new number. Then you have to start manually typing a number back to him.
So I don't log it until it's over.
The first day was hectic with the logging.
Last day was much better.
Thank you everyone.
K5XOM
|
Glad to hear that you've gotten it going and enjoyed the contest.
toggle quoted message
Show quoted text
On Feb 13, 2023, at 02:13, Ken Smith via < kls235@...> wrote:
As you? know I am new to all this. Having recently participated in a contest I've learned some things.
I use <LOG><INCR>? On it's own Macro
and I don't hit it until the exchange is over and there are no questions.
Because if the other op has a question and they ask you to resend your serial number
but? you already updated it by hitting log. Now it;s a new number. Then you have to start manually typing a number back to him.
So I don't log it until it's over.
The first day was hectic with the logging.
Last day was much better.
Thank you everyone.
K5XOM
|
Ken Smith
Dave