Simulate Translate Test

The answer is robots. Source III’s vector translation software works with both the Teradyne FLEX (iFLEX, microFLEX, and ultraFLEX), J750 (and J750+), and Catalyst formats. Every once in a while, we like to check in on recent Teradyne news to see what else is new in this ATE company’s plans. Last month, we found out that Teradyne has recently acquired a company called MiR. What does MiR do? They create what’s known as Mobile Industrial Robots. Here’s one of these robots in action: Teradyne has a financial focus in automation, which includes not only its automatic test equipment, but also the automation in the industrial and logistics industries. Thus, the acquisition of MiR is likely the company’s way of furthering that vision, investing in a company that offers a unique automation tool for industries that benefit from greater efficiency and reliability. It also furthers their goal of investing in automated…
At Source III, our support team makes every effort to assist you with our VTRAN, DFTView, VCAP, and VGEN software. Sometimes we receive questions that we believe are important for sharing with a wider audience. Recently, we received the following question that we thought would interest other clients that use our products. If you happen to have any questions about VTRAN, or any of our products, feel free and contact our support team at any time. Q: Is it possible to rename a scalar signal to a one-bit bus in VTRAN? For example, if I have a signal named Bus A in my original vector file, and I would like it to be written to the target file as BUS A[0], is that possible? What if I want to go the other direction from single bit-bus to scalar? A: Yes. While you should use the original pin name BUS_A in the OVF…
There are many exciting things happening in the IC world. But none seem to have captured the interest in semi-conductor enthusiasts quite like the role that they will play in the self-driving cars of the future. Indeed, over the past several months, numerous articles have been written about the companies and stocks most likely to thrive in the market, and the movement that many IC companies have made to be the first to offer solutions that fit the need of this brand new automotive industry. It has also led to many interesting articles:   This article, from Electronic Design, talks about how the automotive industry and the semiconductor industry are faced with the same challenges, and that in the auto industry they are currently experiencing what they already did in semi – namely, the need for something like EDA: virtualization to speed up the system design process. This article, from…
Efficiency is critical in the world of electronic systems. Part of improving upon that efficiency often involves re-evaluating the flow of the design process, particularly whether or not traditionally different tasks can be merged into one. In some ways, this is what we try to provide with our software. VTRAN’s translations make it easier to move through the test process, DFTView merges debugging and analysis, etc. Recently, Semi-Engineering released an interesting article on another improvement to efficiency, proposing the idea of merging verification and validation. We encourage you to read the article on its source site, here: https://semiengineering.com/merging-verification-with-validation/
We recently received a great question about changing the license timeout value from something other than the default 1-hour. Since we know this question will be useful for other clients, we have decided to convert it into this blog post for easy reference: Q: How Do I Change the License Timeout to a Higher Value? A: The default with VTRAN is to timeout after 3600 seconds (1 hour). But we know there are situations that may require a longer timeframe before the license times out. Luckily, we made sure that changing the timeout length is easy. Keep in mind that all timeout lengths are in seconds, not minutes or hours. You can make this change by setting up a different environment variable in VTRAN: export S3_QUEUE_TIMEOUT=7200 ;# bash, sh, zsh setenv S3_QUEUE_TIMEOUT 7200 ;# tcsh, csh This raises the timeout to 2 hours (the number is always specified in seconds). Use…