Sometime I think why there is no robot for diagnostic and repair faults for every electronic cards,by using arduino we can save data sheets libraries and component abriviations ,names and cards numbers.
by loading idle card information(it's number or picture ,etc.) the processor will search for approperait data sheets and related information and simulate the circuit by tracing a signal in it,till the point of break the energy will radiated due to standing wave principle and there is a mean to detect this radiation and determine the idle component,then make replacement to it by robot.
i'd found like this robots but it's specialist in certain cards not general.
best regards.

 

Big databases and powerful computers can do a lot, and there will be ever more of this as time passes. I think robots would make good diagnosticians in medicine, for instance. But we have not yet solved the limiting problem of computer databases: $hit in, $hit out. As long as there are manufacturers that will not enter their accurate schematics into your robot's database, then your robot technician is going to run into the same roadblocks that human technicians do - lack of good information. The cost of robot labor is not free, either. You cannot afford to have a million dollar robot trying to diagnose $2 circuit boards.

 

It would be easy to do with the right data base. One should be able to diagnose any board......and pin point the defective components.......with a short test. The test would consist of a series of amplitudes and frequencies to the board connections.......while monitoring all other board connections.

With the right amplitudes and frequencies to test that board.......one should be able to pin point down to one, if not at least two component defects. In other words, the resolution would be 2 components.

The test signals and respective response levels would be published at time of board manufacture. Imagine the data base cost.

But that's not the problem. Does the repair save money or time? What's more valuable?
Why buy diagnostic equipment/robots(and maintain database).......take time to replace components.......when one can replace with new board immediately?

Why pay $100 and 3 days time, to fix tv......when one can buy new better tv for $200?

I used to take unknown, un-documented circuit boards...and using a scope octopus....replace defective components. Charged a fortune and guaranteed for 90 days. What few came back.....simply replace all components......about 2-3 hrs time........still made high markup.

But now......the price of replacement boards is not that high. They can stamp them out like chips.

 

You cannot afford to have a million dollar robot trying to diagnose $2 circuit boards.

Let's say the million-dollar robot can diagnose & repair enough boards to generate $500k per year in savings for the next three years (vs throwing them away), I would invest.

 

Let's say ... I would invest.

Sure, there could be scenarios where a robot can be justified. Those scenarios seem unlikely except when the robot is specialized to a particular task, not attempting to be a generalist.

 

Automated board test systems really aren't anything new including board test systems running with ATE (Automated Test Equipment). Robotics simply place a board in place and remove it from the test fixture after test. Test results are printed out and the entire process is automated. About 35 years ago I was involved in the manufacture of aircraft systems starter / generators including the GCU (Generator Control Unit). We were running board test using early 286 AT computers. Even 35 years ago failures were diagnosed and on passed boards all the data was printed on old Epson dot matrix printers.

Board test systems even then could accommodate a wide range of boards by arranging pins which made contact with the boards in addition to the board's edge card connectors. Today robotics are used extensively in board manufacture and also board test. Board test systems also do the diagnostics when a board fails. I guess what I am saying is automated board test using robotics was in use over 35 years ago including the use of ATE.

Ron

 

Automated board test systems really aren't anything new including board test systems running with ATE (Automated Test Equipment). Robotics simply place a board in place and remove it from the test fixture after test. Test results are printed out and the entire process is automated. About 35 years ago I was involved in the manufacture of aircraft systems starter / generators including the GCU (Generator Control Unit). We were running board test using early 286 AT computers. Even 35 years ago failures were diagnosed and on passed boards all the data was printed on old Epson dot matrix printers.

Board test systems even then could accommodate a wide range of boards by arranging pins which made contact with the boards in addition to the board's edge card connectors. Today robotics are used extensively in board manufacture and also board test. Board test systems also do the diagnostics when a board fails. I guess what I am saying is automated board test using robotics was in use over 35 years ago including the use of ATE.

Ron

Those Epson printouts are likely still in storage boxes somewhere.

 

Those Epson printouts are likely still in storage boxes somewhere.

<OFF TOPIC>
Gopher, as many know much of my work focused on government stuff, matter of fact we did the generators for the Screaming Eagle also known as the F15 Eagle McDonnel Douglas Aircraft. We called the generators the screamers as their test speed was 15,000 RPM. The government loves paper, they really love paper. Each unit had a complete "history book" where every nut, bolt and piece of hardware that went into each unit has a documented history. Yes, every history book went into an archive. I really got to understand paper when I became involved with the Nuclear Navy program. The history book on a reactor control rod drive mechanism was like an old encyclopedia set. Paper, ream after endless ream of paper and to change a test method or procedure required more paper. Software documentation was allowed as long as it was backed up on paper.

Yes Gopher, you nailed it absolutely right.

</OFF TOPIC>

Ron