I am looking around at all the people entering the large ballroom at the Embassy Suites in Lincoln, NE. As I wait for the buzzer that will announce the first 35-minute rotation, signaling someone I have never met, from somewhere I have never been, to come to my station, I am nervous and excited and unsure what to expect. While I may sound like a desperate bachelor at a speed-dating event, I assure you that is not the case. I am a software engineer, new to the world of ISOBUS, attending a Plugfest event for the first time. Plugfest is an event held twice a year, where the best and brightest minds in the ISOBUS industry come from around the world to test their offerings, checking for compatibility with other ISOBUS equipment manufacturers.
Welcome back to the blog! Today, I will be talking about how to operate a Cognex smart camera via a LabVIEW program. The way I will be communicating with the camera is via TCP/IP. There are other potential ways to communicate with the camera from LabVIEW, but this was determined to be the best way, giving us the most control over the camera. I will walk through some basic terminology that is necessary to discuss building a Cognex vision test. Then, I will create and set up a vision test and finally, I will briefly describe how to program LabVIEW to send/receive information to the camera and to trigger an image acquisition.
As LCD vehicle displays have become more prevalent and versatile in both on- and off-highway, the time it takes to ensure proper display functionality after a software release has increased dramatically. It is not uncommon for displays to have 15, 20, or even 30 different screens, each of which having multiple sub-selections available. If you take into consideration different supported languages, the scope of the test grows dramatically. DISTek, as a company, is always attempting to define the future needs of customers in the off-highway industry, of which vehicle display testers are one of those needs.