Embedded Systems Conference
Home    Bloggers    Blogs    Article Archives    Messages    About Us   
Tw  |  Fb  |  In  |  Rss
Steve Taranovich

Looking for Trouble in All the Wrong Places

Steve Taranovich
RedDerek
RedDerek
4/9/2014 4:37:07 PM
User Rank
Master
design versus trouble shooting
Design from the back to the front. Then trouble shoot the probem from the front to the back. Simple attack method I use.

50%
50%
DaeJ
DaeJ
4/1/2014 3:27:33 PM
User Rank
Master
Re: Troubleshooting approaches.
->One is to start with the symptom and anlalyze it while gradually moving up

I wonder whether it is possible that more detail is described as adding a specific s/w tool, actual method analytical graphic or flowchart used in the project.

50%
50%
etnapowers
etnapowers
3/31/2014 11:05:00 AM
User Rank
Artist
amplifiers performance
"The performance of some amplifiers degrades when supply voltages get too big or small, so check the supply voltages against those shown in the data sheet."

 

This is really a common issue when working with amplifiers, the supply voltage value and driving capability of the feed lines in terms of rise time, and fall time is really an aspect you would not consider at all if you have a theoretical knowledge of amplifiers but it's a pratical issue to be solved.

50%
50%
chirshadblog
chirshadblog
3/30/2014 11:39:05 PM
User Rank
Master
Re: Troubleshooting approaches.
@tzubair: IMO I feel many companies are not willing to take the next step and go ahead by taking a risk. Many are focusing on short term goals right now to stay in the market which is wrong 

50%
50%
tzubair
tzubair
3/30/2014 5:10:07 AM
User Rank
Master
Re: Troubleshooting approaches.
"Our main goal here is to determine why something does not work as expected and find out any possible solutions for that problem."

@Netcrawl: I think for this reason many companies lay so much emphasis on quality control techniques like TQM or Six Sigma. That takes care of the fact that you don't fix the problems, you fix the causes of the problem and lead your system to be of a higher quality in the long-run.

50%
50%
Netcrawl
Netcrawl
3/29/2014 5:25:09 AM
User Rank
Master
Re: Troubleshooting approaches.
Good point @tzubair, troubleshooting is a systematic approach in solving or fixing specific problem, the first step in troubleshooting is to describe and understand the problem completely. We need to know where to start and what causes the problem. Determining where the problem really originates is not an easy task but its one of the most important things in solving problem. Our main goal here is to determine why something does not work as expected and find out any possible solutions for that problem.   

50%
50%
tzubair
tzubair
3/28/2014 4:45:23 PM
User Rank
Master
Troubleshooting approaches.
"Troubleshooting is a methodical approach to finding a problem, but there's also an art to it. Looking for trouble in all the wrong places eventually leads you to the right place!"

From my experience as a support engineer in the software world, there are two approaches that you can take while troubleshooting a software. One is to start with the symptom and analyze it while gradually moving up. The other is to have a holistic approach where you test everything regardless of where the symptom is occuring. While the latter takes a lot of time and effort, it is more effective in the long run as it also takes care of potential issues that may have risen in the future.

50%
50%
More Blogs from Steve Taranovich
At this year’s APEC 2015 show, their 30th anniversary, the top trends were GaN, Digital power and shrinking power system footprint with higher switching speeds.
In today’s connected world, software frequent-field updates are necessary to improve accuracy, or add on benefits or even fix bugs. If you like these updates to be invisible to you, you are going to love this idea - Instant updates that do not require your software to restart or cause any glitch in the power supply.
More and more companies in wired and wireless communication, enterprise server and storage, and even industrial segments use PMBus power supplies
A DC/DC converter converts an input voltage source to a desired voltage level. When the input voltage is higher than the desired output voltage, you need a buck converter. Conversely, when the input voltage is lower than the output voltage, you need a boost converter. In applications where the input voltage could be either higher or lower than the output voltage, what you need is a buck-boost converter.
Much time is spent discussing the need for more efficient use of limited energy resources, and with good reason. Energy demand continues to grow and the number of loads is predicted to climb exponentially as Internet of Things (IoT) deployment becomes real.
flash poll
educational resources
 
follow Planet Analog on Twitter
Planet Analog Twitter Feed
like us on facebook
our partners
Planet Analog
About Us     Contact Us     Help     Register     Twitter     Facebook     RSS