On Wed, 2 Dec 2009 11:32:31 -0500, Larry Stillings <[email protected]> wrote:
> EN 300 440-1 / -2 latest in the OJ can be used for GPS receivers. > There is a section for receivers in the standard. Thanks Larry and other person who responded. I checked the list and found EN 300 440 covers the GPS frequency, but also noticed that the standard is for Short Range Devices - and GPS receiver is not a short range deivce, I believe. Is there any clause or something which make the standards officially applicable to GPS receivers? Even if there are no such justification, I think we can always say something like "It appears there are no harmonised standard which exactly covers GPS receiver, so we would recommend to use EN 300 440 instead" anyway, but its better for me to have some justification. Regards, Tom -- Tomonori Sato <[email protected]> URL: http://homepage3.nifty.com/tsato/ > -----Original Message----- > From: T.Sato [mailto:[email protected]] > Sent: Wednesday, December 02, 2009 12:18 AM > To: [email protected] > Subject: GPS receiver and R&TTE directive > > A question. > > Does anyone have an idea whether should we apply article 3.2 of the R&TTE > directive to GPS receivers? > And if we should, what harmonised standard can we use for that? > > I thought maybe we don't have to apply article 3.2, as GPS receivers are > receive only equipment and will not transmit radio wave. > However, I think the directive doesn't say we don't have to apply article > 3.2 to receive only equipment at least in explicitly, and I also found a > harmonised standard, ETS 300 487, for other type of receive only equipment > which covers article 3.2 of the directive. > > Any comment would be welcome. > > Regards, > Tom > > -- > Tomonori Sato <[email protected]> > URL: http://homepage3.nifty.com/tsato/ > > - > ---------------------------------------------------------------- > This message is from the IEEE Product Safety Engineering Society emc-pstc > discussion list. To post a message to the list, send your e-mail to > <[email protected]> > > All emc-pstc postings are archived and searchable on the web at: > http://www.ieeecommunities.org/emc-pstc > Graphics (in well-used formats), large files, etc. can be posted to that > URL. > > Website: http://www.ieee-pses.org/ > Instructions: http://listserv.ieee.org/request/user-guide.html > List rules: http://www.ieee-pses.org/listrules.html > > For help, send mail to the list administrators: > Scott Douglas <[email protected]> > Mike Cantwell <[email protected]> > > For policy questions, send mail to: > Jim Bacher: <[email protected]> > David Heald: <[email protected]> > > - > ---------------------------------------------------------------- > This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> > > All emc-pstc postings are archived and searchable on the web at: > http://www.ieeecommunities.org/emc-pstc > Graphics (in well-used formats), large files, etc. can be posted to that URL. > > Website: http://www.ieee-pses.org/ > Instructions: http://listserv.ieee.org/request/user-guide.html > List rules: http://www.ieee-pses.org/listrules.html > > For help, send mail to the list administrators: > Scott Douglas <[email protected]> > Mike Cantwell <[email protected]> > > For policy questions, send mail to: > Jim Bacher: <[email protected]> > David Heald: <[email protected]> - This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at: http://www.ieeecommunities.org/emc-pstc Graphics (in well-used formats), large files, etc. can be posted to that URL. Website: http://www.ieee-pses.org/ Instructions: http://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
