| |||||||||||||
|
| |||||||||||||
Free Software defined radio cannot pass FCC regulations by natureFree Software defined radio cannot pass FCC regulations by naturePosted Jul 7, 2007 20:26 UTC (Sat) by rvfh (subscriber, #31018)Parent article: A green light for free-software defined radio?
I understand that:
So there must be a binary blob to set the frequency, all the rest can be
Correct me if wrong.
(Log in to post comments)
Free Software defined radio cannot pass FCC regulations by nature Posted Jul 7, 2007 23:09 UTC (Sat) by tzafrir (subscriber, #11501) [Link] Suppose I have a device I take with me from the US to Japan. How can the device magically know that it is suddenly in the domain of Japan and use the rule set for Japan? Shouldn't the software order it to do so?
Free Software defined radio cannot pass FCC regulations by nature Posted Jul 8, 2007 1:39 UTC (Sun) by pascal.martin (guest, #2995) [Link] The usual solution for vendors is to follow the most strict regulation...
Not exactly good for open source.
Free Software defined radio cannot pass FCC regulations by nature Posted Jul 9, 2007 10:34 UTC (Mon) by tialaramex (subscriber, #21167) [Link] That's not true, the only thing you could do if you obeyed "the most strict regulation" is remove all radio transceivers from your design. Several small, uninteresting countries have an almost total ban on civlian radio equipment.
What actually seems to happen is that vendors try to ensure that they can meet the letter of the law for a few major markets, such as the US, UK and Western Europe and Japan. Other countries will either certify or not, and if necessary the product won't be officially available in those countries, though if it's popular of course it will enter on the grey market.
They can meet the letter of the law by for example including a different driver CD with a different uploadable firmware for US vs European markets, in the US the driver sets a register to say 0x01, while the European driver asks during installation what country it is in, and chooses one of 0x02, 0x03 or 0x04 according to local regulations. Different radio frequencies are "not available" in software depending on which value is set.
In my country some of the 802.11 frequencies are "not available". Most wireless devices bought here can detect networks on these frequencies but will refuse to connect to them, inevitably some people (the same sort who think NAT is a security feature) see this as a way to control access to their network, they modify a wireless hub by overwriting the firmware to think its in Japan, and then make a registry change or similar small alteration to the software on PCs that connect to the network. Perhaps it may cause interference with safety-of-life critical radio systems here, but no-one cares about that.
|
|
||||||||||||