Group Actions
Engagement
  • Author Author: daemoninformatica
  • Date Created: Date Created
  • Views 1012 views
  • Likes 6 likes
  • Comments 6 comments
Related
Recommended

How assumptions can lead to self-immolation of your work project

daemoninformatica

Also called 'How the mother of all mess-ups (lets not curse now) can mess up your entire morning.'...

This is my first blog on this board, so be gentle. Also as you might observe, I have a rather self-deprecating sense of humor. I hope you enjoy it.

 

 

As true electronics enthousiasts, most of you will be aware of audio jack-plugs. There are various shapes and sizes, with 2 connections, three and sometimes four. (Never seen one with 5, and 1 connection is usually called a banana-plug. Often used in conjunction with power-supplies.)

Typically, these things are used in audio-equipment, for connecting audio inputs and outputs, such as microphones, lines and speakers. But lets face it: pretty much anything that needs a power, ground and one or two data-lines (I/O) could connect over these connectors.

 

At my work, we use these connectors to connect sensors to a main controller board. Quite frankly, I can't go into much detail (especially since this is an R&D project) but sufficing to say, we're doing pretty much what I descibed above: Tip is Vcc, ring is data I/O (bi-directional) and sleeve is ground.

 

At one point in time, I was building the firmware to process these connections and something odd struck me: To simulate an input, I had a switch wired up to signal and ground and to pull the data line low, I'd simply flick the switch. But the weirdest thing: The moment I did that, the controller would glitch out and reboot, and keep glitching until I put the switch back. Now, I'd like to point out that I'm not the one that actually designed the circuit board, but the guy that did is pretty good at it. (given the decennia of experience he has..) On my request, he looks over my shoulder as I demo the behaviour, we study the schematic, rule out shorts in some pull-up resistors and are left scratching our heads.

 

Designer: "Well... if I didn't know any better, we're browning out the LDO (voltage regulator). But between the couple dozen mA's for the controller, the mA's for some leds and the current through this pull-up resistor, it really shouldn't..."

 

Me: "Well, we ruled out any possible short outs or wrong specced resistors. There's one FET that might have caused a short to ground, but it would cause the short even without the switch.."

 

Designer: "There's the second LDO we could switch on for high power mode. That will give more power. See if that solves the brown-out."

 

Me: "Gimme a sec.... "

Fiddles with the test-code. Compiles and writes the code to target.

 

Me: "Ok, switching."

 

Throws switch, debugger characteristically glitches over the brown-out reboot of the controller.

 

Me: "Nope, same effect, controller still glitches on sw-OH-CARPONACRACKER!"

 

Through reaction speeds honed throughout the years as an embedded developer, I kill the power at the PSU and hope I didn't break anything expensive. The mainboard survived, but upon inspection with a magnifying glass, one of the fets powering the pull-up circuit gave the ghost blue-smoke. At this point, me and colleague are stumped. He suddenly frowns and says:

 

"Gimme the board. I'll replace the FET and want to check on something."

 

He replaces the board and does some beep-testing with a breakout plug he has for this port. It doesn't take him 2 minutes...

 

Designer: "So, did you figure it out yourself yet? Or want me to tell you?"

 

Me: "Is it my fault? "

 

Designer (grins) "Nope. Ok, Observe the Jack-plug female: It has 3 connection pins, a tip, ring and sleeve, right? So when you see these three pins (shows a connector unsoldered) you'd think that the pin at the end is the tip, the next one is the ring, and the closest one to the opening is the sleeve. The good news is, we were right about the sleeve. However.. (Shows with multimeter beep) The signal and tip have switched positions."

 

I frown and study the connector.

 

Me: "Sooo... switching on the switch, I pulled Vcc, over the FET, straight to ground. The low-power LDO browned out before the FET could seriously harm itself, but the larger LDO supplied enough current before It browned out to fry the FET.

Somebody actually went through the trouble of casting a connector chassis with a conduction pattern to physically switch the two pins? Why even..?"

 

In our defense: The datasheets for these things was either wrong, or it was the wrong datasheet. I can't imagine it's a production error (I wanted to pull the connector apart to see what it looked like inside, but that would have been destructive and designer needed it still) and why do it this complex? That part we haven't figured out yet, but I'm glad that this was still a prototype board. So since we already had an ample supply of connectors, we simply changed the board for now and went with that. (I assume we'll keep an eye on the possibility that the next batch of connectors might magically be 'the right way around' again, but that's not (yet) my problem..)

  • in reply to dougw

    Douglas,

     

    Picturing that in my mind, it actually makes kind of sense, I suppose.

    I think it didn't help that, so far we've always used a type of connector that's

    1) Surface mounted instead of through-hole.

    2) One could actually see where and how the conductive pieces were essentially forming the wrap around the jack.

     

    These surface mounts didn't have a cantilever pin though.

  • in reply to neilk

    Mostly frustrating, really. It wasn't nearly as scary as the time where I built an experiment using a backplane that carried multiple circuitboards, and one of the boards actually carried 220V.

    I was pretty careful, but in my enthousiasm I miscounted some pins on the headers for the PCB's. So effectively shorted out my input voltage. During test, I sat a bit back, and had the clearance of mind to hook up the board to an extension cord with a switch.

     

    I sat there, took a deep breath and pressed the switch. Then the PCB went in to Rapid Unscheduled Deconstruction and I very nearly did something involuntarily. ^_^

     

    (In my defense: I was 14 years old at the time.)

  • in reply to jw0752

    Hi John,

     

    Thanks for the welcome. image I've actually started eyeing the blog functionality since starting as a RoadTester, since it was encouraged in the Road Testing methods to stay objective and avoid writing your roadtest as some spy-thriller. The blogs have no such limitation. ^_^

    That said: Pretty much everything in this blogpost happened as I described it, safe for perhaps some paraphrasing in the dialogues and my reactions to events as they played out. (I was probably quite a bit more colorful in my metaphores during the period..)

     

    I have one or two more ideas already for other blog-posts, one of which was actually during my last roadtest.

  • I have run into this before with audio connectors and been perplexed as to why they chose a nonintuitive (aggravating) pin position.

    I am not saying I got bitten by this problem, although I might have and just conveniently "forgotten" about it or more probably blotted the embarrassment from my memory.

    The one I took apart needed the extra distance from the actual contact point to allow room for the length of the cantilever contact spring.

  • Martin, that's a really scary story! Glad you sorted it out.

     

    I have used 2.5mm jacks in a similar way to you - Vcc, signal, ground. I always spend ages with the meter checking and double checking what connects to where!

     

    Neil