mailto: blog -at- heyrick -dot- eu
The other day, I noticed my personal server was down. Not only down, but the Vonets WiFi adaptor was dead and the Pi was stuck in a cycle of continually blinking its red power LED, like it was trying to start up but never quite making it.
I had thought at first that Vonets VAP11G had failed short circuit, but this does not appear to be the case. It now seems that the power supply failed, which may or may not have damaged the VAP11G.
The reason I say this hesitantly is that on the day of failure, the VAP11G was utterly dead. I tried it again on... Thursday, I think, and the VAP11G would start up and connect to the WiFi network, but would die the moment it had to actually send or receive any data. And today? It connected and handled pinging Google's DNS server (22.214.171.124) for five minutes (I stopped it then).
I have gone and got myself another power lug. Here's a photo of the inside of the old one, which is now no longer capable even of lighting up an LED lamp:
Nothing is obviously broken - no bulgy capacitors, no blown up chips, no burnt tracks on the board. However, given there's 230VAC mains within a gnat's whisker of 5VDC, I think the best thing to do is just to toss this. It's annoying to have to pay for a new PSU, but it's been bought, fitted, and the Pi runs. Not worth attempting anything at all with the old one.
The behaviour of the Vonets is certainly interesting. I grew up with the idea that "broken means broken" (you know, like "brexit means brexit", not that there's much difference between the two statements). It is certainly eyebrow raising to have a broken thing limping back to life.
What worries me is that the Vonets has a tendency to run hot. Well, today I tested the Vonets and this time put a temperature probe on it. The probe is one salvaged from work, it's pretty reliable (has to be), just some dope went and broke the pokey-proddy part. Ironically, that's more useful for me as I could tape the sensor to the chip without worrying about inaccurate readings due to ambient air cooling the majority part of the metal sensor. I tested this, by the way, and the difference with and without the metal outer was about 15°C - because the heat was only coming from one specific place.
Anyway, while the Pi was pinging, the temperature quickly rose to 68°C, and then slowed down. It was still climbing, just not as dramatically. In a few minutes in free air, the temperature of the SoC reached 73.5°C. It was still climbing, slower this time. The presence of the tape didn't make much difference, for what it's worth. Now imagine the Vonets inside its enclosure, relying purely upon air convection, though it's not as if the air holes in the casing help much here.
The other chips (Flash, RAM, and WiFi) also run worryingly hot.
I have ordered another VAP11G. There are other models available these days, but I know this thing works, once you get over the obnoxious setup requirements (a weird non-standard protocol that requires WinPCap and Windows XP).
I have also ordered a tiny fan - 25mm 5V, 100mA. I intend to punch a hole in the plastic casing and fit the fan to it, to force-cool the innards of the Vonets. As it runs off 5V, I can just piggyback it to the USB power source. If the old Vonets fails or is unreliable, I'll just swap cases and use the cooling with the new one.
Since I have the Vonets open...
There are four principal ICs:
- Marvell 88W8515-BAN1
Not much information on this. As far as can be determined, it is a WiFi/Ethernet capable SoC based around an ARM9 core. It is possibly running a custom RTOS, and clocking ~160-200MHz.
- Samsung K4S643232H-TC60
- Macronix MX29LV800C
- Marvell 88W8010-NNB1 RF Transceiver
The name says it all really. It's the RF baseband transceiver, containing a CMOS amplifier, low noise amplifier, VCO, and frequency synthesiser. As this is the VAP11G, this part supports the 802.11b and 802.11g modulation schemes.
Aaaanyway. This long winded explanation is to explain why my personal (Pi) server won't respond if you try talking to it. Those of you who know the URL, that is...
Please note that while I check this page every so often, I am not able to control what users write; therefore I disclaim all liability for unpleasant and/or infringing and/or defamatory material. Undesired content will be removed as soon as it is noticed. By leaving a comment, you agree not to post material that is illegal or in bad taste, and you should be aware that the time and your IP address are both recorded, should it be necessary to find out who you are. Oh, and don't bother trying to inline HTML. I'm not that stupid! ☺ ADDING COMMENTS DOES NOT WORK IF READING TRANSLATED VERSIONS.
You can now follow comment additions with the comment RSS feed. This is distinct from the b.log RSS feed, so you can subscribe to one or both as you wish.
(Felicity? Marte? Find out!)
- Cheesy nightmares, Monterey Jack, That Palestine thing. (2024/02/22)
- Dude..., SimpleSeq v0.23. (2024/02/18)
- Internet trauma, Sweet almond, Mowing, Beautiful brioche. (2024/02/17)
- MIDI and the broken brain, SimpleSeq v0.22, MIDI v0.12. (2024/02/11)
- SimpleSeq v0.21, Wait WAIT?, Tree hacking, Brioche against the odds, Big parcel. (2024/02/10)
List all b.log entries
Return to the site index
PS: Don't try to be clever.
It's a simple substring match.
Last read at 23:59 on 2024/02/22.
© 2016 Rick Murray
This web page is licenced for your personal, private, non-commercial use only. No automated processing by advertising systems is permitted.
RIPA notice: No consent is given for interception of page transmission.