Sharing Test Programs Using Easy-Wire Export & Import
Best Practices When Sharing Test Programs Between Cable Testers
The Cirris Server Software allows multiple test stations to share a single Easy-Wire database which gives each test station on the network access to the current versions of test programs. However, test programs can also be provided to stations that don’t share a database using the Easy-Wire Export and Import functions. Following a few basic rules will ensure a smooth export / import experience
Export Packages
Before reviewing the process, it’s helpful to understand that the export package for a test program typically consists of multiple files including a text file and graphic files. One of the unique and powerful features of the Easy-Wire software is the capability to display connector graphics for use in guided assembly and troubleshooting. The graphic files support this capability.
It’s also helpful to recognize that all the default connectors provided initially in the Easy-Wire Connector Registry include connector graphics. In typical usage, new connectors are added over time and the user can choose whether to include a connector graphic when creating a new connector. Finally, graphics for existing connectors can be added or edited if the connector type is not already in use.
Text File
The exported text file includes the test program instructions, test parameters, information about the associated connectors and their profiles, the test points to connector position mapping, and additional miscellaneous data. The exported filename is the test program name with a “.txt” extension.
The text file will be the only file exported if none of the connectors referenced in the test program require a separate graphic file. A connector does not require a graphics file if:
- The connector does not have an associated image. This occurs when the user selects No Image in Step 5 of the connector creation process.
- The only graphic used on the connector is the placement of the contacts using a glyphic and the contact identification tag alone. This means no connector outlines or other image is drawn.
Graphic Files
Typically, connectors referenced in the test program do require the export of a separate graphics file. The type of file depends on the graphic used.
CGD Files
If the test program references connectors that include associated graphics that were drawn using the tools in Easy-Wire, the export package will include a separate file with a “.cgd” filename extension for each such connector.
JPEG Files
If the test program references connectors that include associated graphics using a photograph for the background, each such connector requires a separate file with a “.jpg” filename extension.
Best Practices
Following these tips helps limit exporting and importing issues.
Exporting
Organize Files
Create a dedicated folder to store all exported files together before transferring them to the importer. The folder with all the exported files should be transferred together.
Use Unique Connector Names
If connectors used in the program have been changed from their factory default configuration, assign the connectors new names in the Connector Registry to avoid conflicts during import. Users who have previously imported a connector may be unable to import a test program containing a connector of the same name but containing a different number of points or different point names.
The two example connectors shown below have the same number of pins, and the pins have been assigned the same names, but one is a plug and one a receptacle. Therefore, they use different graphics. Although named the same, they are not equivalent.
Connector Named ABC
≠
Connector Named ABC
Best Practices for Importing
Files
Importing the test program will also automatically import all the associated graphic files in the same folder. The text file name may be changed but the graphic file names should not be renamed.
Mapping
Test programs include mapping data that documents which system test point is connected (attached) to each connector contact. If Smart-Lights® are being used, the mapping will be automatically updated to match the test setup. If traditional test fixtures are being used, unless the device-under-test is connected to the tester exactly as it was on test system from which the test was exported, it will be necessary to reattach the defined connectors in the test program editor.
General Best Practices
Easy-Wire Version
Update Easy-Wire regularly to keep the version current. The exporting system and the importing system should be running the same versions. When the exporter’s version is newer than the importer’s, the exported file might contain information pertaining to a feature not included in the importer’s older version. In this case, the import operation will be terminated, and error messages providing details of the unsupported format errors will be displayed.
Editing
Editing the contents of an exported test program text file can have significant side effects and such changes may prevent importing. Circumstances that require text editing of exported programs are rare and each should be considered a special case. Files should only be edited under the guidance of Cirris technical support.
Managing Imported Connectors
When importing a test program, Easy-Wire searches the importer’s Connector Registry for a connector having the same name as those referenced the program text file. If no match is found, the connector from the exported file is recreated and placed in the “ALL” category of the Importer’s Connector Registry.
When a .cgd or .jpg graphics file that is required to recreate the connector is not in the folder containing the imported .txt file, the import operation is terminated, and an error message is displayed.
When a connector name match is found in the importer’s registry for a connector being imported, Easy-Wire compares details of the connectors. When a perfect details match is detected, the Importer’s registry connector is used.
Managing Imported Connector Conflicts
When detail differences between an exported connector and an importer’s registered connector of the same name are detected, the import operation is terminated, and an error message is displayed that duplicate connector names have been detected.
The Best Practice for resolving duplicate connector name conflicts begins with the exporter:
- Duplicate and rename the conflicting connectors in the Connector Registry.
- Redefine the connectors in the test program to the renamed connectors.
- Save and export the test program again.
The methods available to the importer to resolve duplicate connector name conflicts involves editing the test program text file. However, changing the test program’s exported text file adds several levels of difficulty, introduces uncertainty, and removes version control from the Exporter. Therefore, editing the test program text file should only be done with the exporter’s approval and with guidance of Cirris Technical Support.
