20 WPM for Part 97 is correct. However, there is no mention of what level is required. Whereas, Part 90, for example, used to (and probably still does) require the level be at a minimum of 80% of full system deviation. 80% of 5 KHz (the old standard) is 4 KHz, which makes for a pretty darn loud identifier. With the newer 2.5 KHz standard, that works out to 2 KHz. Generally, amateur (in particular repeaters) tend to use way less than 80%, probably more like around 50%.

N5ZUA

On 12/15/2013 8:33 PM, Jim Duuuude wrote:
Isnt there something in part 97 about max speed for CW id?

> Date: Sun, 15 Dec 2013 15:30:28 -0600
> From: ars.w5omr@gmail.com
> To: app_rpt-users@ohnosec.org
> Subject: Re: [App_rpt-users] Speaking of CW IDs
>
> On 12/15/2013 03:25 PM, Mike/W5JR wrote:
> > 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)
> >
>
> I've been meaning to ask that same question.
>
> 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


_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users