alan smith wrote: >I'm not discounting firmware yet, other than I have two boards that have NO issues at all, while two others do. And I can take a chip from one board, drop into the other and it works just fine. Thats why I am looking for some sort of external stimuli that would be present on the bad boards and not the good, but the question is....what to look for that might cause such a condition. > >Olin Lathrop wrote:alan smith wrote: > > >>So, making a long story short....anyone ever seen where the PIC A/D >>gets "stuck" on a certain value and doesn't want to change? >> >> > >I have never seen this. It sounds like a firmware bug. > >***************************************************************** >Embed Inc, embedded system specialists in Littleton Massachusetts >(978) 742-9014, http://www.embedinc.com > > When I run into problems like this I usually take a fresh pic and test some code I really know thats working. In your case I suggest you do the same or write up a new simple a/d code and test it in your customers board, just to make sure its not in the firmware. -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist