Hello,
In general, no. The standards change to keep up with changes in interference level, spectrum planning, problems seen, etc. As I think John Woodgate already said.. You can sit on the standards committee and influence it. I used to be on the group for writing EN 300 328 and EN 301 893 (I am not anymore, I should add! V1.8.1 was not me! J ) and the group was mostly made up of manufacturers protecting the interests of their companies, and regulators protecting their spectrum. Can I ask exactly what the problem is? Is it the Medium Access Protocol issue? Are you concerned that your device may choose to change channel mid-operation, or something? Actually, I'm guessing that (spectrum sharing) cannot be the issue because that aspect of V1.8.1 became mandatory on 23rd October 2012. Is it the new power measurements? I'm curious because maybe there is a solution, after all. If that fails, I have the ETSI group chairman's e-mail address, if you want it. J Michael. Michael Derby Regulatory Engineer ACB Europe From: Mark Tucker [mailto:[email protected]] Sent: 07 August 2013 18:01 To: [email protected] Subject: [PSES] Grandfathered requirements for ETSI Hi, My company makes 2.4 GHz proprietary wireless products for European use (not WiFi, BT or ZB). These units are qualified under EN 300 328. We understand that EN 300328 v1.8.1 will become law the 1st of 2015. We've been selling wireless products for many years in the EU and the installed base is in the 10s of thousands of units. However, the changes dictated by v1.8.1 will break our radio protocol and destroy the compatibility between new units (that must be v1.8.1 compliant) and those already installed in the field. This is a huge issue for us and any other vendor that may have the misfortune of having a large installed base of pre-existing products. Is there any provision in ETSI rules that allows for backwards compatibility with preexisting products? I have a hard time believing that they wouldn't have made some sort of provision for this. Any help or advice would be greatly appreciated. Mark Mark Tucker Director of Hardware Engineering RFM 3079 Premiere Parkway, Suite 140 Duluth GA 30097 [email protected] ----- Forwarded by Mark Tucker/US/MuRata on 08/07/2013 12:57 PM ----- From: "IEEE LISTSERV Server (16.0)" <[email protected]> To: Mark Tucker <[email protected]>, Date: 08/07/2013 12:56 PM Subject: Welcome to the emc-pstc email list _____ [Last updated on: 18-Oct-2011] ******************************************* * * * The IEEE PSES EMC-PSTC E-Mail Forum * * * ******************************************* 18 Oct 2011 Welcome to the EMC-PSTC E-Mail Forum! ** To send a message to the EMC-PSTC Forum, simply send an e-mail message to the following address: [email protected] All mail sent to this Internet address will be re-sent to about 900+ worldwide subscribers to the EMC-PSTC list by an automated list server (Listserv). Listserver posting may take up to 8 hours. Please set your mailer to ASCII text. ASCII text is readable by all mailers, while other mail formats are not. Do not attach files. ** To SUBSCRIBE to the EMC-PSTC mailing list, send an email message to [email protected] and place the command: SUB EMC-PSTC <full_name> in the body of the message. ** HOW TO UNSUBSCRIBE The only way to UNSUBSCRIBE, or remove your name, from a list is to send an email message to [email protected] and place the command SIGNOFF EMC-PSTC in the body of the message. Do not append a signature file. ** HOW TO SET LISTSERV OPTIONS The listserv understands many commands and has many options. For a complete list of options send the command "INFO REFCARD" to [email protected] and a complete list of commands will be emailed back to you. The most commonly used commands are listed below. As with all commands to the listserv, send an email message to [email protected] and include the commands in the body of your message, one command per line. ** Old messages will be Archived at (aprox. Feb. 2003): <http://www.ieeecommunities.org/emc-pstc> http://www.ieeecommunities.org/emc-pstc ** Should you have any questions, send them to: Jim Bacher: [email protected] David Heald: [email protected] ** Subscribe or Unsubscribe issues should addressed to: Scott Douglas [email protected] Mike Cantwell [email protected] ......................................................................... ************************************** * * * Charter and Guidelines * * * ************************************** 05 September 2001 This Forum is operated by the IEEE Product Safety Engineering Society. The Forum was founded to discuss product safety issues. But, we also discuss product EMC and other product regulatory issues. We discuss world-wide standards and regulations. We discuss technical issues related to interpretation and measurement. And, we discuss safety and EMC issues not currently published in standards and regulations. This Forum is a tool to help us do our jobs by sharing information. MESSAGE CONTENT GUIDELINES -------------------------- 1. Postings and responses should be limited to information or queries relating to Product Safety, EMC, or Regulatory Compliance topics. 2. Posted information should not be confidential or in any way proprietary. 3. Please don't use the EMC-PSTC for private correspondence. Private correspondence should be addressed directly, unless it has broad appeal or interest. 4. Please put your name at the end of any message you send (some e-mail addresses do not identify the sender adequately). Also, we suggest that you include your position in your company and your company name. 5. Blatant or overt advertising of goods or services is not permitted. The listserver is provided as a service by the IEEE, whose policies prohibit anything that might be construed as conflict of interest. Exceptions: a) Short, non-promotional "trailers" or signature lines for the sole purpose of identifying the sender and the sender's organization. b) Answers to queries about goods or services, where the intent of the answer is to inform, but not promote. (When in doubt, send the questioner a private message.) c) New or used equipment wanted, or used equipment offered for sale (not offered by the manufacturer). d) This guideline is specific to the use of the this listserver, and in no way inhibits individuals from contacting members privately and independently. Similarly, irrelevant postings are not permitted. Irrelevant postings are those whose subject matter is irrelevant to the technical discussions. Please do not post messages about viruses or humanitarian situations. Occasional humorous stories relating to EMC or product safety are okay. 6. Posting of job openings is okay so long as they are short (i.e., one paragraph), non-commercial (no agencies or headhunters - no fees involved), infrequent (about one out of every 10 messages or less), and contain an off-EMC-PSTC contact name and phone number or e-mail address. Same goes for jobs-wanted (if you can fit your resume into one paragraph!). 7. Using key words in the title or subject line will assist members who archive the message traffic and may wish to search it later. Suggested keywords include: SPACINGS, SHOCK HAZARD, or a country name (where the information is country-specific). 8. Queries or requests for information should be focused and brief. Respondents should be careful about endorsements - when in doubt, don't. 9. Please don't attach files to messages. Many mailers cannot effectively handle attached files. If you want to make a file available to subscribers, we suggest you announce the availability of the file and make individual arrangements to send the file. Another way is to make files available through anonymous ftp or through the World Wide Web. 10. To minimize unwanted advertising, postings to the forum are restricted to members only. Listserv (i.e., the listserver) compares the poster's address to the addresses in the database. If there isn't a match, the posting will be dumped to the bit-bucket. Consequently, members should realize that postings will need to be sent from their subscribed e-mail address and not from an alias or alternate e-mail site such as home. 11. While subscribed to this Forum, and when you will be out of the office for some time, please don't use an "Auto-reply" for your electronic mail. Your auto-reply will reply to each message from this listserver, and it will go to the entire mail list. This is annoying to our subscribers. And, sometimes it tells the entire world of your plans. If you need to use the auto-reply, we suggest you unsubscribe from this listserver, and re-subscribe on your return. Or, filter your external messages into a separate mail folder and don't allow the auto-reply to respond to those messages. 12. Please be careful about cc's to internal e-mail addresses. If you add cc's (and bcc's), be aware that those addresses accompany your posting, and are distributed to the entire world. a. If a subscriber responds to your posting using a "reply-to-all" command, the cc's (and bcc's) will also get copy of the reply. b. If your cc's are aliases, and if a subscriber responds to your posting, the cc addresses will cause the mail to bounce back to the IEEE listserver, and then back to the administrators (us) as undeliverable. We research the undeliverable messages to purge bad addresses; bounced alias cc's create work for us. DISCLAIMER ---------- All postings are the sole responsibility of the message originators. The IEEE, the IEEE PSES Society, its volunteers and staff do not assure the correctness or viability of any information distributed by the listserver, nor accepts any responsibility for the use of any distributed information. ---------- We are pleased to be able to offer this discussion group and look forward to extensive use by the product safety and EMC communities. However, we would like to emphasize that this discussion group is simply a tool. Tell your co-workers and agency contacts about this forum. The more people involved, the more valuable this tool will be. Best regards, Richard Nute, Former Chief Administrator Jim Bacher, Administrator ***** Appended by RFM (www.rfm.com) ***** CONFIDENTIALITY: This message contains information which may be confidential and privileged. Unless you are the intended addressee (or authorized to receive for the intended addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender at RFM by reply email and delete the message. RFM is a subsidiary of Murata Electronics North America, Inc. . - ---------------------------------------------------------------- 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.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. 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.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. 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]>
