Cirris announces the formation of a "Customs Group" within Cirris.

When Cirris began to build cable testers 27 years ago, the idea was to build a standard, off-the-shelf tester with interchangeable adapters as the "customizable part" of the tester. As the years went by, more customers asked for tweaks of the hardware or the software (or both) for very legitimate test application reasons. As a result of those challenging test applications we learned some very important lessons. We learned we have some thoughtful and clever people and they came up with some very creative ways to shape solutions for testing difficult applications.

Visit our Customs Group Web Brochure to learn about past projects that solved specific challenges.

Our Customs Group Web Brochure (above) focuses on photos of the many projects and ideas we have completed over the last few years, the Success Stories webpage, on the other hand, focuses on very specific problems and the Cirris solutions that solved the specific challenge. The Problem/Solution format enables a quick overview of each problem with more details about how the solution was fabricated. If you are struggling with difficult testing issues, you may want to scan our list of problem/solutions to see if one of our Success Stories holds the key to solving an issue you are currently dealing with.

For many years we have designed and built custom adapters to help our customers solve awkward or difficult interfacing challenges. This page illustrates a wide variety of different approaches that can be used to solve thorny interfacing problems. The concept is simply this; Cirris is in business to help you solve your testing challenges, whatever they might be. Give us a call today to discuss your custom adapter requirements.

Scripts are almost always used when you desire the tester to respond differently to events either external to the tester itself, or to test results, (good or bad cable). Using Scripts to control your test process is essentially running a mini-software program to control your tester. For example, you may want to read a barcode off an assembly and have the tester respond in 4 distinctly different ways depending on the results of the scan. Or you may have an automated assembly/test line and you want the tester to turn a switch on or off depending on whether or not the DUT tests good or bad. Scripts can be large and complicated or small and simple. The control of your test process is completely in your control with custom scripts.