Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
11/12/05 02:29
Read: times


 
#103607 - Purpose of this...
Responding to: ???'s previous message
I'm not entreprenur and not even working for someone.
I do small projects for small/medium scale companies.
(just started )

The equipment i'm designing will be used at construction site, concrete mixing/batching plant , weigh indicators etc..

Now here in India at least, these sites are not that 'state of the art' sophisticated. Also working conditions are not that good. Skilled labour might be also problem.

So becoz of improper handeling and/or operating the equipment may get damaged:
1. Some links/paths broken
2. component may get loosen a bit

Also one may encounter problem bcoz of
1. component failure
2. Flaw in design itself.

Now ofcourse we can or ratherwe should try our best to rule ot the above two mentioned possibilities. But we cant completely rule them out.


Now suppose eqpt. is not working for some reason.
We replace it, install the new one, take the old/faulty back with us for the repair work.

Now PCB might be large in size: time consuming job
PCB very small: Complex job

So now suppose i remove the original, application specific programmed microcontroller and insert fault finding microcontroller and do some (few) changes in connections, if required.
( now if fault is those connections....obviously more problems problems n problems, but somewhere we need to understand limitations and define boundry for ourselves.. we cant keep on asking, "what if..?" for everything )

For now lets get back to main point.
So now this fault finding chip should check all

(as many as possible and that too individually [hence some changes in connections may be required, as i quoted earlier] )

components and display results. This should help in zeroing on at particular component/area where fault is located.

So instead of manually testing, we can find out fault by using such microcontroller i.e. by s/w method.



Now can anyone suggest methods to do this,
On what basis one should decide wheather given component is
working or not ?
What to check for ADC, DAC, memory, op-amp etc...

Please suggest some check points.
Thanking all of you.

Best regards,
Neil.


List of 12 messages in thread
TopicAuthorDate
S/w for H/w Testing            01/01/70 00:00      
   adc o/p checking            01/01/70 00:00      
   Nothing special            01/01/70 00:00      
   what are you making? If it is not extrem            01/01/70 00:00      
      Waste of time?            01/01/70 00:00      
   Doubtful            01/01/70 00:00      
      Purpose of this...            01/01/70 00:00      
         just replace the darn thing            01/01/70 00:00      
            not everything can be replaced            01/01/70 00:00      
               I could possibly support that were it no            01/01/70 00:00      
         design for the application            01/01/70 00:00      
   Yes            01/01/70 00:00      

Back to Subject List