Searching \ for '[PIC] stupid, more stupid and ....' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: 'stupid, more stupid and ....'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] stupid, more stupid and ....'
2005\08\30@102642 by Wouter van Ooijen

face picon face
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

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu


2005\08\30@105625 by Electron

flavicon
face

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..

2005\08\30@110051 by Shawn Tan

flavicon
face
> 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 ....

You're only human.. (and the fact that they're tiny, it makes it
difficult to see the numbers on them..)

cheers..

with metta,
Shawn Tan.

2005\08\30@131217 by Carey Fisher - NCS

face picon face

  > 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.
  >
 
My latest blooper:  The code includes an interrupt driven receive routine
with a circular buffer at the end of RAM.  As I kept adding functionality
to the program, I kept adding variables.  Well, suddenly lots
of weird things started happening, especially when comms
were happening.  Turns out I added enough variables to
overwrite the receive buffer. And I was using absolute mode.

The object lesson:  USE RELOCATBLE MODE (Olin is right!)

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...