element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Embedded and Microcontrollers
  • Technologies
  • More
Embedded and Microcontrollers
Embedded Forum Embedded Design Testing
  • Blog
  • Forum
  • Documents
  • Quiz
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Embedded and Microcontrollers to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 482 subscribers
  • Views 539 views
  • Users 0 members are here
Related

Embedded Design Testing

Former Member
Former Member over 13 years ago

Hi,

 

I hope this discussion is in the right group but here goes...

 

I have recently started using Perl on my PC to auotmattically test serial features of my embedded designs. It works really well, but the designs do not just have serial I/O, but have Analogue and Digital I/O, which means I cannot test the whole design.

 

Thinking about solving the problem, I though the same Perl test program could also talk to a 'Smart' Test Harness in addition to the serial communication direct to the embedded design under test. It would be a good project to do, a micro with I/O interface circuits, some kind of serial software interface that would allow for control the I/O. But I do not have time, and I am sure other people do this kind think.

 

I know about the NI equipment and Labview, but that would be overkill for my applications.

 

What do others in this group use for their automated testing of their designs? Is there an a relative inexpensive device that would fit my needs?

  • Sign in to reply
  • Cancel
Parents
  • DAB
    0 DAB over 13 years ago

    Hi Ross,

     

    Before you can adequately test your device, you need to define your testing requirements.  I cannot tell you about the number of projects I was tossed into where they only budgeted the development effort and not the test effort.  If you are going to do quality work, you need to assess and budget for both.

     

    In many respects, your testing rig will need more work than your device.  Why?  Because you have to verify and validate your test rig before you can adequately test your device.  I know it sounds a little wierd, but when you sit down and look at the problem, you will find that your testing rig might well be more expensive to build than your actual device.

     

    Once you document what your test rig needs to include, then you can look for off the shelf components that fit your needs.  Once you reach a stable configuration, you then need to assess what additional testing items you need to verify that your test rig works.

     

    I could go on, but I think I have made my point about the importance of understanding your testing needs and the care you must take to do it right.

    After all, if your test rig is faulty, then your device will contain errors as well.  Proper testing is just as important as the development process.

     

    If you spend the time in testing, you will end up with happy customers.  Otherwise, you may find that they seek out others to do their next job.

     

    Just a thought,

    DAB

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • DAB
    0 DAB over 13 years ago

    Hi Ross,

     

    Before you can adequately test your device, you need to define your testing requirements.  I cannot tell you about the number of projects I was tossed into where they only budgeted the development effort and not the test effort.  If you are going to do quality work, you need to assess and budget for both.

     

    In many respects, your testing rig will need more work than your device.  Why?  Because you have to verify and validate your test rig before you can adequately test your device.  I know it sounds a little wierd, but when you sit down and look at the problem, you will find that your testing rig might well be more expensive to build than your actual device.

     

    Once you document what your test rig needs to include, then you can look for off the shelf components that fit your needs.  Once you reach a stable configuration, you then need to assess what additional testing items you need to verify that your test rig works.

     

    I could go on, but I think I have made my point about the importance of understanding your testing needs and the care you must take to do it right.

    After all, if your test rig is faulty, then your device will contain errors as well.  Proper testing is just as important as the development process.

     

    If you spend the time in testing, you will end up with happy customers.  Otherwise, you may find that they seek out others to do their next job.

     

    Just a thought,

    DAB

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube