Jinx wrote: >>Hope you find it! >> >> > >I didn't find a cause, but Bill Bross did off-list. And it's so simple I >could, and should, cringe > >Unfortunately, some macros were copied from a pretty old project >and I didn't alter them > > > I told Jinx off-list that when he published his problem, it was two days after I just sent out my first F1320 based board design to the pcb vendor (a lot of boards). I was on pins and needles until I verified my little a/d worked, which had its own set of problems. Just to get some of the 'heat' off Jinx for this, I'll admit to my dufus moment with my board. I put a MCP601 op amp on it for signal conditioning my a/d input. I laid it out for the 'T' version which has VDD and VSS backwards from the normal version. My junior engineer had some LMV431 or something like that for his board he was working on. I forgot to order my MCP parts and grabbed one of his amps. Hey, 5 pin SOT op amps all have the same pin out right??? WRONG!!! My board registered about an amp of current draw for say......30 seconds before it went up in smoke. That's a mistake I won't make again. Anyway, my boards a/d worked just fine whether it was with internal or external Vref. But when I built up his circuit and used his code, I got results as he published them. It didn't take long to sort out the problem. Having a second (or about 2K ) set of eyes from the list is good backup to have whether you are a lone consultant or just a hobbyist, even if you find yourself a little embarassed occasionally. BTW, I got the message about bouncing messages so I'll look into that. Bill -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist