Barry, After the F/W upgrade the devices will operate the full specified temp. range of -40C (-40F) to +65C (+150F).
There aren't any defective components nor are any compromises being made to get the devices working. Hope this gives you the assurance from our side. With best regards, Nish smartBridges -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barry at Mutual Data Sent: Tuesday, July 22, 2003 7:48 PM To: 'Tom Haynes' Subject: Re[5]: [smartBridges] Firmware Issue Hello Tom, Thanks for the explanation. However in 90 days some of us will begin to experience very cold weather. Will the silicon decide to work then? The flawed chip that was used in the units that are failing is a hardware issue. SB is using firmware to work around the flaw. The correct chip does not need this workaround. My original post was in relation to the "magic" comment. Personally, I hope Atmel is paying SB for the mess up, especially if they made the substitution without design approval from SB. I still don't understand why I would need to wait 15-30 minutes before I repower the unit up. Is the radio sill transmitting off an internal power source? Or is it the flash rom needs to cool off so it will correctly operate? Which sounds like a hardware issue to me. Barry Monday, July 21, 2003, 10:16:32 PM, you wrote: TH> When the firmware program requests information from the flash ROM, it sends TH> the request over the data bus and waits a preset amount of time for the TH> requested information to appear on the data bus. If that information does TH> not appear the firmware program crashes. The flash rom module supplied by TH> Atmel in the past put the information on the data bus in an approiate amount TH> of time, however Atmel replaced the flash rom without notice and the new TH> flash rom responded slower. Under normal circumstances, everything was fine. TH> When the temperature rises in the chip, the response time slowes down. The TH> slower response time makes the flash rom place the requested information on TH> the data bus to late (after the firmware program quits waiting) and the TH> system fails. TH> The hardware is still functional at higher temperatures but the firmware TH> does not wait long enough for the information to be supplied. This is why a TH> firmware update can fix the problem and it is not called a hardware failure. TH> I hope this helps TH> -----Original Message----- TH> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] TH> On Behalf Of Barry at Mutual Data TH> Sent: Monday, July 21, 2003 9:08 PM TH> To: Dan Petermann TH> Subject: Re[3]: [smartBridges] Firmware Issue TH> Hello Dan, TH> So explain why heat is affecting it? And why the long power down time? TH> Barry TH> Monday, July 21, 2003, 7:18:10 PM, you wrote: DP>> If you had read the archives you would have found out that it is not DP>> "flaky" hardware but a timing issue. DP>> Big difference. Amtel changed the specs of the chip and SB had to change DP>> the firmware to compensate. DP>> If you have been in the business as long as you say then you know that TH> this DP>> is possible. DP>> Dan Petermann DP>> Wyoming.com DP>> At 06:36 PM 7/21/2003 -0400, you wrote: >>>Hello sB, >>> >>>This is not the response I want to see or hear about a product that is >>>in my network. "MAGIC" is BS when the customer quits telling me they >>>are always down. >>> >>>I don't believe for an instant that "firmware" is fixing an >>>overheating issue. I was trained as an Electronics Tech and have 12 >>>plus years of fixing electronics to the board level as experience. >>>Adding some code is not going to change a flaky component. Basically >>>is the firmware degrading the radio operation to the point the >>>component does not overheat? >>> >>>Fortunately, I only have a few SB products left in the system plus the >>>ones in the junk box. >>> >>>Barry >>> >>>Monday, July 21, 2003, 2:05:44 PM, you wrote: >>> >>>sTS> I know this is hard to believe. Sometimes when you try to >>>sTS> associate to AP that has no WEP enabled, it tell you to check the >>>sTS> authentication and WEP, try do a power cycle the unit or reboot >>>sTS> the PC, it may work then. It is just a magic trick. >>> >>> >>> >>>sTS> Alex >>> >>>sTS> sB Tech Support >>> >>>--- >>>[This E-mail scanned for viruses by Declude Virus] >>> >>>The PART-15.ORG smartBridges Discussion List >>>To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe >>>smartBridges <yournickname> >>>To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe >>>smartBridges) >>>Archives: http://archives.part-15.org DP>> The PART-15.ORG smartBridges Discussion List DP>> To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe TH> smartBridges <yournickname> DP>> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe TH> smartBridges) DP>> Archives: http://archives.part-15.org DP>> --- DP>> [This E-mail scanned for viruses by Declude Virus] -- Best regards, Barry mailto:[EMAIL PROTECTED] --- [This E-mail scanned for viruses by Declude Virus] The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
