Mark Yedinak

QUOTE (jdunham @ Oct 9 2008, 01:13 AM) This approach will not work if you are using TCP connections though. If you use this on a TCP connection you will establish two independent connections to the device. The device should be smart enough that it returns the response on the same connection that it received the data on. It would be nice if VISA allowed true asynchronous communication. In addition, it would be nice if VISA allowed independent control of the various settings on the resource. In particular, it should allow different timeout values for the transmit and receive.

Can anyone explain how I can set the default value for a X-control. I created a X-control for connection configuration data (serial, parallel port, TCP/IP and USB) and for the life of me I can't seem to define default values for the data. The serial port configuration is the most complex and is comprised of multiple typedefed enums (for BAUD rate, parity, stop bits, etc.) and no matter what I have tried I can't get the default values I want. They always revert to the first value in the enum list. I have tried setting the default value for the typedefs, the individual controls, the controls on the facade and the internal data structures (like I said, I have tried everything). Nothing seems to work. Any suggestions would be appreciated.

QUOTE (Lars915 @ Apr 3 2008, 02:56 PM) I totally agree with this advice. It is much easier and faster to work with a 2D array than to work directly with Excel. On some of the larger projects I have worked on we have run into performance issues and race conditions (inside Excel, not LabVIEW). We found it was better to work with a simple CSV file. In some cases where native Excel was required we only wrote the Excel file at the completion of the application using the temporary CSV file as the input.

Join Zebra and EARN YOUR STRIPES!! Who is Zebra? Zebra Technologies delivers innovative and reliable specialty digital printing solutions for business improvement and security applications in 100 countries around the world. To learn more about our broad range of applications visit our homepage at www.zebra.com. Why join Zebra? Zebra Technologies is a career-defining place to work that can offer you: • A challenging job where you can really make a difference. • A friendly and collaborative work environment. • A dynamic and growing company. If you're interested in this kind of company and ready to earn your stripes, we invite you to explore this opportunity! Tell me more! We currently have an opportunity for an experienced Software Test Engineer in our Specialty Printer Solutions business unit located in Warwick, RI. Will develop software for Zebra's automated test system. This includes defining test objectives, designing new tests and enhancing the existing test software. Working with design and test engineers in multidisciplinary team environment. Help to minimize the time period from new product concept to market readiness by providing design and development engineers with high quality, scientifically based data from controlled tests. • Bachelor's degree in Computer Science or Electrical Engineering • 3-5 years work experience with C, C++, LabVIEW, TestStand • Experience with 802.11, Bluetooth, wireless security protocols is an asset • A broad based knowledge of Software and Electrical systems and subsystems is required, including knowledge of test and measurement techniques for solving multi-disciplinary design problems. What can Zebra offer me? We offer competitive salaries and a comprehensive benefits package to include Medical, Dental, Vision and Life insurance, LTD, 401(k) (with immediate company match), Profit Sharing, Employee Stock Purchase Plan, Tuition Reimbursement, and more. In addition, we offer a six month on-boarding experience to support you through your transition. To apply for the position and learn more about our benefits package, please visit our career center at www.zebra.com/career. Thank you. Jody Kelsey Recruiter Zebra

Personally, I have never been a huge fan of XML to begin with, at least for anything a human will be dealing with. XML is not very readable for humans without some other tool. I prefer generic ini file formats for configuration data. With that said, I do need to work with XML since the product I am working with returns data via XML. I found the fastest method for working with this was to write my own simple parser. I mainly need to extract values out of the XML data and a simplified text parser was easier and faster than the XML tools available with LabVIEW.