Home |
Search |
Today's Posts |
#15
![]() |
|||
|
|||
![]()
On 2005-02-10 05:31:55 +1100, Bruce in Alaska said:
In article , "Doug Dotson" dougdotson@NOSPAMcablespeedNOSPAMcom wrote: Not all that clear. The ICOM M-710 is "opened" by uploading software mods. Are you saying that if these mods are uploaded by the factory or a dealer then it is still Type Accepted, but if I do it myself then it is not? BTW, your shift key seems to be malfunctioning. Better have it checked by a qualified technician ![]() Doug, k3qt s/v Callista Geeez Doug, What does it take for you to understand, here? The software that is running in the radio, IS part of the Operational Interface, and if it is different than what was submitted to the FCC during the Type Acceptance Proceedure, and different than the software that was in the two submitted Representative Radios, then it is considered a MODIFICATION by the FCC and would incalidate the Type Acceptance of that radio when subsequently loaded in the radio by ANYONE, even the OEM. The Radio isn't the same, when the different software is loaded, unless that software was included in the Original, or Subsequent Type Acceptance Proceedure by the OEM. You can't modify the radio, in ANY substatial way after Type Acceptance has been granted, and still have that Type Acceptance be Valid. Bruce in alaska -- Bruce, don't be too hard on Doug. This is a perception thing. Generally people don't see software as the same thing as hardware. It is somehow different because it is "just a file of 1's and 0's". As more and more equipment is mushware (hardware and software combined to give a reconfigurable device) that perception will have to change. Rather than call it software if we were to call it firmware (which it may be) then most people would consider it as tied to the hardware and see it in the same light. And yes, the firmware and hardware combination is type approved as a whole entity. Theoretically a new release of the firmware would need to be certified as well but I expect the FCC as a matter of convenience does not require a retest on each new release of the firmware. -- Regards, John Proctor VK3JP, VKV6789 S/V Chagall |