It is limited by this line in the app_rpt.c file and by FCC rulesmorsespeed = retrieve_astcfgint(myrpt, myrpt->p.morse, "speed", 5, 20, 20);
So... If the FCC rules don't apply to you (maybe you don't use a RF transmitter) then you could change the line to something like thismorsespeed = retrieve_astcfgint(myrpt, myrpt->p.morse, "speed", 5, 50, 20);Then 50 wpm would be the upper limit.On Sun, Dec 15, 2013 at 3:30 PM, Geoff <ars.w5omr@gmail.com> wrote:
On 12/15/2013 03:25 PM, Mike/W5JR wrote:I've been meaning to ask that same question.
So, there is a "speed=" in the morse stanza. Does it have a governor on it to limit the speed maximum to 20 wpm? My entries greater than 20 make no difference. And why would I want faster than 20 wpm you ask, my HUB nodes are only send "ID" to web transceivers, and I would like them faster. I have observed that at 20 wpm, there is a bit of jitter and faster may not be possible. (An ID I built years ago had a limit on how fast it could go before the code elements were overrun by timing)
Rules wise, since there's no CW requirement *at all* for 'any' license, then there shouldn't be a speed limit on how fast repeater id's should be limited to.
I like my code speed around 30~35wpm these days. I used to copy NTS traffic at 40+wpm. 20wpm is such a '~*yawn*~' bore...
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users