|
I remeber back in my school days using an OP-Amp (probably a 741) with some PLC (Prog Logic Controlers) and a few missteps later a loud crack and a perfect circle appear in the top of the chip...nothing on the insides, I'm guessing the wafer was on a circular base...never foound the top. 
|
|
|
|
|
In a college lab I managed to reverse Vcc and ground on a 1489 RS-232 driver chip. When things didn't work, I fingertip-tested each chip to see if they were warm. When I got to the driver, it had reached the melting point of the plastic. It took a year for me to get sensation back in the tip of my index finger.
Software Zen: delete this;
|
|
|
|
|
I don't know why but your story reminded me of the time I was giving an instructional lab over the inner workings of the cabinet for a AN/SPS-67[^] navigation radar and I got my finger too close to the 530 VDC transmit trigger pin while it was active. I tell you, my head felt fuzzy all day and my arm hurt for a week after that  .
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
Similar thing in College, I had built this over complicated circuit to analyse waveforms the simulation worked (PSPICE...) the actual hardware didn't. so I pinky around the board find a transistor where I put it down wrong and got a huge blister on on my finger and left a finger print on the darn thing!
|
|
|
|
|
Awesome
Neveer tried that experiement but good to know they're tough.
Someone's therapist knows all about you!
|
|
|
|
|
I have named the board Deadpool as its a bit mangled but still working, with a freaking hole in it...
|
|
|
|
|
I've got them so hot that you could barely touch, but never blowed a hole in one. Good to know they'really rugged.
Someone's therapist knows all about you!
|
|
|
|
|
Left it too cool down, tried it after I had ordered another one too look busy, the little trooper was fine apart from two inputs I was using that had 24v across them. Atmels really are military spec... 
|
|
|
|
|
Good story and very cool that you lost some pins but not the entire device.
I have a similar story related to a lightning bolt.
A few months ago we had a lightning strike about 10 feet from my garage and about 25 feet from the location of my arduino bluetooth garage door opener (documented here on CP Never Buy A Garage Door Remote Again: Open Your Door With Your Android Phone (via Bluetooth)[^] ).
We lost a wifi router, a cable modem and a PS4 had to be repaired.
My garage door special has no casing or anything and it began not responding to my bluetooth signal.
I noticed that it still powered up and all that, but it didn't work.
I put it back on the bench and found that the one pin (which I output on to activate the relay) no longer worked but the rest of the chip was entirely fine. I simply changed the code to use a new pin. Swapped out the relay input wire to the new pin and everything worked again.
Those arduindos and ATMegas are great stuff. 
|
|
|
|
|
Quote: Those arduindos and ATMegas are great stuff. Smile |
Darn near idiot proof! MSP430's are similar, PICs will die totally from what I did to it (trust me I know)
|
|
|
|
|
glennPattonWork wrote: PICs will die totally from what I did to it
Interesting, did not know that.
So the atmega / arduino is actually more resilient than some others.
Didn't know if it was just luck. interesting that the chip designers may have created circuits that protect better like that in the chip.
|
|
|
|
|
Possibly unfair to PIC, I remember a problems with a particular 16F658 batch kept me going for a couple of weeks.
|
|
|
|
|
I am trying to convert my VB6 code to C# (Desktop programs). I am looking for tools that will help increase my efficiency and shorten the learning curve. Any suggestions? Other than "give it up!"
If everything seems to be going well you are obviously overlooking someone or something....
|
|
|
|
|
This[^] is the traditional method of conversion.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Resharper.
And don't give it up, C# isn't terribly difficult. Like an English muffin, it just has many nooks and crannies, and is infinitely better with butter(Resharper).
I would suggest a functional clone rather than direct conversion, though. It's unlikely that a VB6 program is structured in a way that will work well in C#.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Thanks, I will check it out. And yes I am actually re-writing a functional clone as you suggest. Sorry I did not make that clearer. The Program is around 400,000 lines of code. 
|
|
|
|
|
No worries, just wanted to make sure you didn't end up down the rabbit hole 
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Ed Aymami wrote: around 400,000 lines of code
Imagine how rewarding it will be when you can finally "select-all, delete!" the VB code 
On the other hand, you have different fingers. - Steven Wright
|
|
|
|
|
You Can Use .NET De-compiling Tools Like RedGate .NET Reflector For Simply Read Your Assembly And Translate It To Different Versions Of C#, VB.NET Or C++.NET.
I Use That Tool To Read My Students Codes And Learn Some Of Tricks They Use... 
|
|
|
|
|
Nathan Minier wrote: Resharper.
Gesundheit!
Honestly, I love that nagging thing almost as much as I do JavaScript!
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Nathan Minier wrote: Resharper.
|
|
|
|
|
Nathan Minier wrote: Resharper.
Eric
|
|
|
|
|
Presumably, in a world of reuse, I am the only one concerned when I hear “rewrite”, “redesign” or “refactor”. IT staff spend an inordinate amount of time reinventing the wheel over and over rather than moving on and accomplishing something new. I suppose it maintains the inflated “need” for IT workers.
|
|
|
|
|
Or it could be that one obsolete language is architecturally incompatible with best practices in another. Crazy, I know.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Unless it's less than 1000 lines of code, avoid auto-conversion software. I'd strongly recommend re-designing and then re-writing it in C#. The re-design is important because things are done way differently in modern .NET than it was during the VB6 days.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
