Mike,

As quoted from the white paper;

Software Requirements for Compliance
The only requirement our FCC approval places on software is to “hard code” the transmit power control settings and channel selection options so that they always conform to the FCC certified limits. There must not be any way to configure the system to operate above the certified power levels or channel settings. Any
software can be run on the unit provided it meets this requirement.

ADI is accomplishing the power and channel hard coding with the cooperation of our commercial WISP and municipal wireless software partners – RoamAD, Valemount Networks, Antcor, and others. These partners will be providing a Pronghorn Metro™ FCC compliant code build that sets power and channel selections correctly. ADI is also underway developing an FCC compliance capability for MadWiFi. This will provide a clear path forward to FCC compliance to customers creating their own software based on MadWiFi.
Regards,
Dawn DiPietro



Mike Hammett wrote:
I see nothing about it that would fix it to Star OS, unless the IXP425 is not x86.


-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com


----- Original Message ----- From: "Dawn DiPietro" <[EMAIL PROTECTED]>
To: "WISPA General List" <[email protected]>
Sent: Tuesday, June 12, 2007 6:17 AM
Subject: [WISPA] ADI's open Architecture system




The thing that's screwing us all up with MT, StarOS and others like that is that they don't have ANY certified systems available to us.

I guess you missed my post last week about ADI Engineering.
They have a certified system that works with Star OS. This was just release a few weeks ago.

http://www.adiengineering.com/products/data/FCC-Whitepaper-R100.pdf
--
WISPA Wireless List: [email protected]

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/



--
WISPA Wireless List: [email protected]

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to