Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
RF forwarding times
I would not normally check Request Reverse any time as it increases traffic.? If the other station does not have a forwarding record to you then that might be a time to use that.?? I believe that any time you conect messages will be both sent and received.
?
I connect no more frequently than once per hour.? And, I stagger those times by 10 minutes for each RF connection. Even that may be cutting it close if you have slow connections or ultiple ELSE clauses.
?
I do not know min or max values for those fields.
?
--
73,
Mark, N5MDT
Montgomery, Texas
?
?
? |
¿ªÔÆÌåÓýOn 2/22/25 12:10, Jim - KI0BK via
groups.io wrote:
Hi, Jim: Valid range values are, at least, 300 to 9999, as I have used them without seeing a failure. I have 'Send new messages without waiting for poll timer' enabled so, I assume that may initiate staggered start forwarding times. What values of Enable Forwarding and Request Reverse delay minutes are used when RF forwarding? It depends. It depends on band and propagation and channel occupancy. I feel that it is common to set repeat Enable Forwarding RF connections times to 1 hour. I do not recommend enabling a Request Reverse on a popular or active or congested RF channel. In one instance, I see only 5 other BBSs on a 40 meter channel. I do not see any other automatically controlled digital stations in this waterfall bandpass. On an unpopular inactive non-congested channel and because NVIS connection start and end times on 40 meters vary seasonally, I use the Request Reverse field with 2 HF neighbors and adjust the TIMES to start ~1 hour before the last successful connection times and 1 hour after the last. I hear 5 other BBSs on this 40 meter mode, so I feel that I am not generating significant channel contention. 73, Chuck |
to navigate to use esc to dismiss