IoT M2M blog

The home of free hints and tips about wireless IoT / M2M

EN 300 328 V1.8.1 the end of 802.15.4 ?

Is EN 300 328 V1.8.1 the end of ZigBee, Z-Wave and all other radio protocols riding on 802.15.4?

Does it mean, that we all will deinstall our 804.15.4 based ISM devices? IEEE 802.15.4 divides the 2.4 GHz band into 15 channels. ETSI Draft 1.8.1 requires that a radio system must use at least 15 channels. Now, if one is disturbed, it must be kept for long periods. Now if only provides for a wireless standard 15 channels, and release even a must, it falls below the minimum number of channels. As a result of such a radio technology in 2015 are no longer permitted by the Federal Network Agency and by a user can no longer be used.
Are you aware that Google´s Open Source radio protocol on 6LoWPAN will support frequency hopping?

Text out of ETSI ERM TG11 #23 Meeting

Channel Access Mechanism (CAM)

It was decided that TG11 members should now concentrate and prepare contributions on the CAM rather than to continuing influencing the MU formula and it’s limit.

Duty cycle for hoppers

Changes on the observation time for adaptive systems (from 1s to 40s -> this means 1s for non-hoppers and 40s for hoppers). The observation time should be different to the non-adaptive. The revision of the duty cycle section is to be done offline (by correspondence). The objective is to cover duty cycle and TX-on/TX-off times in this section. The terms TX-on/TX-off should not be used.

Hopping frequency separation

Reduce the separation (0.1MHz) in order to make use of the gaps between channels. This is only for adaptive systems.

Adaptive Frequency Hopping

Many questions about how to treat that equipment which falls below the MU threshold. The question is what happens with the adaptive systems when going below the [10%] (should it remain adaptive?). Adaptive Frequency Hopping with DAA (Detect and Avoid),

Adaptive Frequency Hopping with Blacklisting

For further review.

Source: https://mentor.ieee.org/802.11/dcn/10/11-10-0024-00-0reg-sum…

3 Comments

Add a Comment
  1. ZigBee/802.15.4 is not classified as a frequency hopper. The minimum of 15 channels is for frequency hoppers only (such as Bluetooth). Therefore this part of EN 300 328 has no relevance for ZigBee/802.15.4, in the same way it has no relevance for WLAN/802.11.
    ZigBee/802.15.4 is compliant to the new rules for adaptive non-hoppers, so there will be no change in the allowed usage.
    Also, systems not complying with the new adaptive rules will not be forbidden, they just need to limit their transmitter power to 10mW (as opposed to up to 100mW).
    Best regards,
    Per Torstein Roine

  2. I got by my Facebook:
    15 channels minimum, which will defined in 1.8.1, is for all devices with more than 10mW. The most Z Wave applications for home remote control works with 10mW and is under EN 300 440. For me a very interesting question: Have you ever see a commercial 802.15.4 device??”

    My answer: The coverage with 10mW on 2400 MHz is poor. Google selected 868 / 915 MHz, 6LoPWAN and frequency hopping. Google will make it Open Source. 6LoPWAN is UDP/IP riding on a radio wave. It is IP from end to end with IPsec if you like.

    Yes, I have seen one 802.15.4 application in the last 12 month. They are using 802.15.4 with a proprietary protocol as a UART to wireless link. A cable replacement. Just a simple Peer to Peer connection. One device is like nothing. I make my money with selling of parts for wireless communication. Thanks god, there are other nice wireless technologies. My kids would like to have some corn flakes in the morning. 😉

  3. According to my calculation EN 300 328 V1.8.1 reduces the spurious emissions limits by 10 dB. Old limit = -80 dBm/Hz or -20 dBm/MHz.
    New Limit = -30 dBm/MHz. This is significant.

    Is this Correct?

Leave a Reply

Your email address will not be published. Required fields are marked *

Blue Captcha Image
Refresh

*

Harald Naumann © 2014 Frontier Theme