| Latest revision |
Your text |
| Line 7: |
Line 7: |
| | ''... mention systems that combine FHSS with mesh networking ...'' | | ''... mention systems that combine FHSS with mesh networking ...'' |
| | | | |
| − | * slow frequency hopping: after hopping to the new frequency, the transmitter sends several symbols before hopping to the next frequency. This gives the fastest data rate when running on hardware that takes a long time to switch to a different frequency.
| |
| − | * fast frequency hopping: The transmitter hops to several different frequencies, sending the same symbol on each one, before transmitting the next data symbol. This is more tolerant of single-frequency interference.
| |
| | | | |
| | * Other places we [http://opencircuits.com/Special:Whatlinkshere/FHSS talk about FHSS on Open Circuits]. | | * Other places we [http://opencircuits.com/Special:Whatlinkshere/FHSS talk about FHSS on Open Circuits]. |
| | | | |
| − | == Acquisition and tracking == | + | == further reading == |
| − | | |
| − | When a receiver is turned on, what frequency should it listen to first, and how long should it listen before trying some other channel?
| |
| − | | |
| − | There seem to be 4 possibilities:
| |
| − | * Both systems start at the same "acquisition channel", and stay on that channel until they hear from each other, then start hopping. This gives the quickest time-to-lock, if there is no interference. But if narrowband interference happens to be on that channel, then they never lock.
| |
| − | * The receiver picks a random acquisition channel (a random point on its hop sequence) -- perhaps the quietest channel with the least noise on it -- and stays on that channel until it hears the transmitter. The transmitter always goes through the hop sequence in the standard order, sending a packet on each channel. Eventually the transmitter gets to the channel the receiver is listening on, and the receiver hears that packet, synchronizes its time, and starts hopping.
| |
| − | * The transmitter picks a random acquisition channel (a random point on its hop sequence) -- perhaps the quietest channel with the least noise on it -- and transmits its time signal over and over on that channel. The receiver goes through the hop sequence in the standard order. Eventually the receiver gets to the channel the transmitter is sending on, and the receiver hears the packet and synchronizes its time. After the transmitter has given the receiver plenty of time to sample every possible channel, both should now be synchronized, and start hopping.
| |
| − | * Both the transmitter and the receiver step through the hop sequence in the standard order (starting at any arbitrary or random channel). However, the receiver stays on each channel longer (2 times as long?) as normal, taking longer (2wice as long?) to step through the whole sequence. Eventually, the transmitter "catches up" to the receiver in the hop sequence, the receiver hears that packet, synchronizes its time with the transmitter, and starts hopping at the normal hop rate.
| |
| − | * ...
| |
| − | | |
| − | == Legal considerations ==
| |
| − | | |
| − | In addition to the physical limitations mentioned above, there are also legal considerations, such as, for example:
| |
| − | | |
| − | <blockquote>
| |
| − | (h) The incorporation of intelligence within a frequency hopping
| |
| − | spread spectrum system that permits the system to recognize other users
| |
| − | within the spectrum band so that it individually and independently
| |
| − | chooses and adapts its hopsets to avoid hopping on occupied channels is
| |
| − | permitted. The coordination of frequency hopping systems in any other
| |
| − | manner for the express purpose of avoiding the simultaneous occupancy of
| |
| − | individual hopping frequencies by multiple transmitters is not
| |
| − | permitted.
| |
| − | --[http://edocket.access.gpo.gov/cfr_2005/octqtr/47cfr15.247.htm 47CFR15.247 : FCC Part 15 Section 15.247]
| |
| − | </blockquote>
| |
| − | | |
| − | Paraphrased in SWRA041 as
| |
| − | <blockquote>
| |
| − | It is not permitted to synchronize transmitters of different frequency hopping systems to each other. This
| |
| − | could lead to a super system that occupies individual frequencies for more than the allowed 0.4 seconds
| |
| − | in the 10s or 20s period. Notwithstanding this, any system may recognize others in the frequency band
| |
| − | and adapt its hop set independently to avoid hopping into an occupied channel.
| |
| − | </blockquote>
| |
| − | | |
| − | Some of the "ETSI EN 300 440" regulation is paraphrased in swra060 as
| |
| − | <blockquote>
| |
| − | 7.5 Additional FHSS requirements
| |
| − | FHSS modulation shall make use of at least 20 channels separated by the channel bandwidth ...
| |
| − | The dwell time per channel shall not exceed 0.4s.
| |
| − | ...
| |
| − | During operation every channel shall be used at least once
| |
| − | within a period of 4 times the dwell time per hop multiplied with the number of channels.
| |
| − | While the transmitter is performing hops between channels, the transmit power level shall be
| |
| − | attenuated ...
| |
| − | </blockquote>
| |
| − | | |
| − | | |
| − | Is this a hard limit on adaptive frequency hopping?
| |
| − | Or does it merely mean that a system that skips over some frequency for longer than 4*N*D seconds no longer qualifies under the "frequency hopping" section, but must fit under the (more restrictive) "other digital modulation" test limits?
| |
| − | | |
| − | | |
| − | | |
| − | ''... What other legal considerations and FCC policies are relevant to designing intelligent radio communication systems? ...''
| |
| − | | |
| − | == Direct sequence spread spectrum ==
| |
| − | ''(FIXME: make new article for other kinds of spread spectrum? Do we need a general [[spread spectrum]] article?)''
| |
| − | | |
| − | [http://www.holmea.demon.co.uk/Spread/Spread.htm Spread Spectrum Link]
| |
| − | has complete schematics, photos of hardware, and design tips for a DSSS communication link.
| |
| − | | |
| − | With any kind of spread spectrum,
| |
| − | "The most difficult area is the receiver path, ... because the receiver must be able to recognize the message and synchronize with it in real time."
| |
| − | -- [http://www.maxim-ic.com/appnotes.cfm/appnote_number/1890/ Maxim application note 1890: "An Introduction to Direct-Sequence Spread-Spectrum Communications"]
| |
| − | | |
| − | * [http://en.wikipedia.org/wiki/Spread_spectrum Wikipedia: spread spectrum]
| |
| − | | |
| − | == Further reading ==
| |
| | | | |
| | * [http://interwiki.sourceforge.net/cgi-bin/picawiki.pl/NgARN NgARN : Next Generation Amateur Radio Network] | | * [http://interwiki.sourceforge.net/cgi-bin/picawiki.pl/NgARN NgARN : Next Generation Amateur Radio Network] |
| | * The [http://en.wikipedia.org/wiki/Frequency-hopping_spread_spectrum Wikipedia:FHSS] article | | * The [http://en.wikipedia.org/wiki/Frequency-hopping_spread_spectrum Wikipedia:FHSS] article |
| − |
| |
| − | * [http://focus.ti.com/general/docs/techdocsabstract.tsp?abstractName=swra041 TI Application Report SWRA041: "Implementing a Bidirectional Frequency Hopping Application With TRF6903 and MSP430"] by Shreharsha Rao 2004
| |
| − | * [http://focus.ti.com/general/docs/techdocsabstract.tsp?abstractName=swra048 TI Application Report SWRA048: "ISM-Band and Short Range Device Regulatory Compliance Overview"] edited by Matthew Loy, Raju Karingattil, Louis Williams
| |
| − | * [http://focus.ti.com/lit/an/swra060/swra060.pdf "Application Note AN032", aka "swra060": "SRD regulations for license-free transceiver operation in the 2.4 GHz band"] by M. Engjom (discussing regulations on devices legally classified as a "short range device")
| |
| − | * [http://www.vtt.fi/inf/julkaisut/muut/2008/CHESS_Research_Report.pdf Cognitive radio: An intelligent wireless communication system: "Channel state estimation and spectrum management for cognitive radios"] discusses adaptively discovering which channels are idle and which are in use, and adaptively transmitting only on the idle frequencies. Also mentions mesh networking.
| |
