jcarmody

My system begins when an operator scans a barcode containing a part and serial number. The part number tells the system which sequence steps to execute and the limits for each test in those steps. Results are stored and retrievable within the system, too. It sounds like G2's web page doesn't do dTRAK justice.

I have a product line with a few dozen part numbers with common & unique tests based on product family and it sounds similar to your situation, although at a much smaller scale. I use a product from an NI Alliance Partner called dTRAK (http://g2tek.com/dcp/i/products-dtrak). My first thought while reading your post was to ask how much experience you have, then I saw the "CLA" in your signature. It's worth giving them a call, anyway, as they've already done a lot of the heavy lifting. Good luck.

My company is seeking an engineer to replace me and I'd like to help . The job listing is at http://www.utc.com/Careers/Job/Sr-Eng-Test-Reliab-Wilson-North-Carolina/2840BR. The position is located in Wilson, NC. This position is responsible for developing and supporting all of the production test functions for several commercial aviation products including smoke detectors and pressure transducers, most of which communicate using CAN. You'll also: be involved with the Design Engineering group to make sure that they don't build/specify anything horrible inherit a lot of my applications (be kind!) and one larger one that we bought from an NI Alliance partner train/support production personnel on the use of your equipment ... You'll encounter: Access and SQLite databases (but I'll nag you about using SQL Server) the JKI State Machine a somewhat complex test system that uses LabVIEW and TestStand with a web app and a SQL Server database ... I'd be thrilled (but it's not required by the folks doing the hiring) if you: are a regular contributer to the forums are certified in LabVIEW and/or TestStand use a version control system can teach me how to use the Actor Framework I love the job; you may love it, too. PM me on LAVA if you'd like to discuss it further. I'll help you get your information into the right hands. Good luck. cross-posted on http://forums.ni.com/t5/LabVIEW-Job-Openings/Test-Engineer-LabVIEW-TestStand/m-p/3091105

My job satisfaction stems from the fact that most of my responsibilities are AWESOME! The parts of my job that aren't awesome don't drown out the other awesomeness. Also, I have good bosses and coworkers. Also, my company is profitable. Also, flexibility. Forget it. I don't know...

Just to be clear, I showed two Event structures just to show the two approaches. Pick whichever one suits your application, although it sounds like the upper one isn't applicable with the other events you need to handle.

The easiest way is as ned said, shown in the top image. If you can't use a 30-second timeout because you need to handle other things during those 30 seconds, the lower loop will evaluate whether 30 seconds has elapsed every 0.025 seconds. You'll need to pass the "reset timer' command back into the Timeout event using a Shift Register. Maybe post your VI? Are you really using LabVIEW 2015?

http://www.xkcd.com/1270/

That's one of the sticking points I have with convincing folks to use TestStand. The HTML reports are about useless (without adding some thought and effort).

I'm leaning back toward TestStand, even though everyone else is moving away. I figure that a debug/deployment license is a drop in the bucket compared to a new ATE, and a deploy-only license is nearly free. (I work for a larger company where I'm not questioned about $600.) I want to leverage TestStand's user management, database and reporting pieces, but the debugging opportunities mentioned in the article are also valuable.

Well, you could put the Case structure in an Event structure and respond to the Value Changed event of a control wired to the selector terminal of the Case structure. I'm not sure I understand what you've got in mind, though. Are you anticipating receiving many messages and wanting to manually examine some of them? How will you isolate the ones you want to examine?

You don't need multiple Case structures for every message if you'll wire ArbIDOrHeader directly to the Case structure you already have. Just add a new case for every message. Generally, it's silly to compare a value with a constant to decide which case to execute. Just wire directly into the structure.

Pertinent Idea Exchange entry - "Almost Equal" functions for Float comparison​s

GPS info includes elevation data.

Perfect timing. I have a 40-mile "race" this Saturday. triplelakesrace.com

I use it. I like it. I don't think it's what the OP is looking for.

Have you tried installing/repairing MAX and/or the Instrument I/O assistant?

You've run up against the difference between the Measurement I/O and Instrument I/O pallets. Try using the Instrument I/O Assistant. You'll be able to communicate with your Agilent 34970A with that.

Another bubble burst. I thought that was a portrait and that Shane was a really tough astronaut.

All the discussion I've seen regarding similar needs ended up following some form of hooovahh's advice. There's a lot of communication going on behind-the-scenes in order to accomplish the load making it not worth the effort to build something you can call from a command line.

Will this work - http://lavag.org/files/file/117-abort-vi/

I can't convert it for you, but someone here can. http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion

I recently took delivery of two ATEs from G2 Technologies in Apex, NC. They're a good bunch of people. I used to work there, but they've grown a lot in the past few years so I don't know many of the developers or instructors. Have fun.

I bought it but tossed it to the side when I had trouble getting the Arduino driver working. It's worth the price just for the LabVIEW license, though. My son has it on his computer.

That's well and good until you realize that someone like me was on the first page for a long time. I managed one RCF plugin that got a bit of attention for a while, and most of the rest of my posts were "liked" because I was being silly. That's my legacy

Definitely interesting. Good luck with your PhD.