Member Since: March 17, 2009

Country: United States



(Embedded) Software Engineer


American Legion, Knights of Columbus

Spoken Languages

English, some French, some Japanese

Programming Languages

C/C++, Python, Ada, HC11 assembly, and more.


Georgia Tech, RPI


Interfacing to serial (RS-232/422/485) command-response devices. Peripherals: SCI/UART, SPI, I2C, CAN.


Ice hockey player (adult no-check)




Design News, EE & SD Times

  • The ENABLE input on the TPS63070 is active high (as evidenced by the 10k pullup), but it's labeled with the inversion bar on the silkscreen and schematic as if it was active low. I recommend removing the bar in the next revision.

  • Nate, not to be too pedantic, but the thing in the first picture is a teletype like the ASR- or KSR-33, not an early computer. The explanation of the acoustic coupler is all kinds of confused; the handset doesn't act any differently just because it's in a coupler. The headset mouthpiece is a microphone, its earpiece a speaker. The coupler is the opposite. HTH.

  • Hey Feldi, just curious about something: did you look at any other master's programs in NYC before you chose NYU?

  • Those responsible for sacking the people who have just been sacked have been sacked. ROTFL!

  • The electronics market in Shenzhen is the one 'mall' in the world where I don't want to leave.
    How does it compare to Akihabara? (Disclaimer: I haven't been back in the last 20 years, so I don't know how it's changed.)

  • I can't be the only software type who, after seeing Office Space for the first time, cried out, "Oh GOD, this is my LIFE!" :)

  • Probably not NY - we only have a handful of districts on 2 hour delay here upstate. My guesses are MA (Savoy 38"), CT (Woodbury 28"), or VT (Wilmington 36").

  • Speaking of snow, it seems to me today's Nor'Easter got its calendar a little mixed up. If it had waited a day, you could have had everyone here in upstate NY and New England home from work & school helping with the server load test!

  • If you used the white RJ11 cable that's shown in the picture, that might be the cause. It looks to me like its connectors are in what I would call the "normal" orientation, so pin 1 on one end is pin 1 on the other. The short RJ11 cable I just got with a new ICD 3 is the other way around: pin 1 is pin 6 on the other end, and vice versa. I don't know why Microchip does it this way, but the poster you get with the ICD 3 does show you which pin is which. It tripped us up a little, as I found when I checked the voltage before plugging the other end into the target. (We had a pair of DB-9s in line so we just rewired one of them.)

  • Not to brag, but like pretty much everyone in the Navy, I (an EE) got to go to a basic firefighting school. Because at sea, the fire department is, well, you. :)