Abstract
The relatively new Standard Test Interface Language (STIL) facilitates the transportation of digital test data from creation in Computer-Aided Engineering (CAE) environments, to use on Automated Test Equipment (ATE). Attempts to use STIL for this purpose have identified apparent disconnects in this flow. This paper presents disconnects identified to date, their causes, and presents solutions to address these issues. A practical example is presented of the process to transition an existing, known-good, test flow to this new environment.