If we assume that the macro <REGEXP:x:y> waits for x seconds, a string
matching "y" (REGEXP means "regular expression", a kind of string
matcher), such a macro syntax might help:
<REGEXP:60:paNBEMS [WX|FLMSG]><TX>Received $Match<RX><REPEAT>
It would translate as:
Wait 60 seconds until a string matches "paNBEMS WX" or "paNBEMS FLMSG".
If yes, transmit the string "Received 'matched string'". If not, do
nothing. Then repeat the macro.
Or:
<REGEXP:60:paNBEMS [WX|FLMSG]><EXEC>echo $Match | mail -s nbems
[email protected] </EXEC><REPEAT>
... which would mean:
Wait 60 seconds until a string matches "paNBEMS WX" or "paNBEMS FLMSG".
If yes, mail the matched string. If not, do nothing. Then repeat the macro.
FYI, I am (slowly) thinking about something like that for a different
application (Frequency scanning), at the price of a couple of changes to
the macro execution logic.
Le 30.11.2010 23:35, Dave Kleber a écrit :
Well, knowing little to nothing about programming, I think what you're
saying is what I was looking for.
I brought the subject up because a local NWS station has expressed some
interest in getting set up for NBEMS. They have a fairly large call
watch area and the furthest Counties out can't be reached by VHF/UHF.
They have an HF station and antenna. The thought would be to have anyone
at the office simply turn on the station which would be locked to a
fixed 80m frequency. Then boot up the computer, which we could have
NBEMS set to open on start up. From there, have the notification feature
act upon a certain text string (i.e. "paNBEMS WX" or "paNBEMS FLMSG"),
which would trigger an event that would automatically print the wrap
message following the trigger text. The sound of the page being printed
would alert the forecasters of an incoming message. Maybe an additional
event for a wave file could be done, too.
Something along the lines of what I describe would have been a major
plus on our last Simulated Emergency Test (SET) exercise last month. A
traffic manager at our Official Relay station could have simply
collected the printed messages and managed the direction of the traffic,
by priority, to the various nets on different frequencies and bands we
were relaying to.
-Dave, KB3FXI
On 11/30/2010 5:57 PM, [email protected] wrote:
Hi,
Are you thinking about a macro with a filter string which would
trigger a program upon reception of this string ?
This macro could also try a range of frequency, waiting X seconds on
each of them.
Le 30.11.2010 21:06, Dave Kleber a écrit :
Hello all,
In reading the online help for FLDIGI, I see that the "run program"
feature under notifications is currently limited to Unix/Linux.
I'm wondering if this feature will be extended to the other operating
systems and would be interested in seeing some practical examples of
programs that might run with the notification trigger. I'd also like to
know if the following might be possible:
If notification were set, for instance, to activate upon receiving
"paNBEMS flmsg", would it be possible to activate a batch file routine
to automatically print an flmsg message following the "paNBEMS flmsg"
text?
This could be a very powerful feature in the advancement of NBEMS,
especially for EOC, NWS and Official Emergency/Relay station operations.
My thought is that with this functionality, even stations waiting for
the arrival of a licensed op could get automatic print outs of all
priority and emergency messages on a fixed frequency by simply turning
on a transceiver and booting up the connected computer and printer.
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
