At 16.26 2005.08.30 +0200, you wrote:
>In my previous life (working for various companies) I always wanted to
>know what projects had done wrong rather than having to listen to the
>hurrah stories of what they did right, so I'll share my (PIC) bloopers
>with you.
>
>today:
>I am coding a gravity sensor (ADXL + 12F675). Previously the gravity PCB
>contained just the ADXL, but the wires bundle from the gravity sensor to
>the motor controller also contains the motor wires, so that gave lots of
>interference (the ADXL output is ~ 32k impedance), so I put a PIC on the
>sensor print so it can send the measurement in digital format.
>
>blooper: after 1 hour of trying to get the A/D to read something else
>than 000 I took a closer look at the PIC that I soldered onto the PCB a
>few weeks ago. It is a 12F629 ....
>
>Wouter van Ooijen


I'll add mine: when I code for Windoze, I magically always forget that
I've set my compiler to default to C calling conventions, while Windoze
wants stdcall. This always results in nasty, nasty, nasty and hard, hard
to track bugs that involve the stack (and I always intuite it), but that
I don't realize (the stdcall qualifier is missing) before days of bloody
bug hunting.

Results?

Now, finally, after the last (of many times), I've put under my monitor
a billboard saying "coding a callback routine? add the f*cking stdcall".

I'm afraid I will forget to look below the monitor.. let away that now
I've megabytes and megabytes of sources to check again and again looking
for ghosts that I sure missed lately.. (WinNT seems very robust in this
regard, it's when I test back the stuff on a Win9x/ME machine that the
crashes and other malfunctions mostly become visible).

Anyway..

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist