ejensen

QUOTE (crelf @ Feb 4 2009, 12:04 PM) No, I've never used SCC. This is the first time I've tried to build a project with classes. I also didn't mention it before, but I'm using LLBs renamed as DLLs as per the instructions here: http://digital.ni.com/public.nsf/allkb/472...62574AC006A258B. I don't know if that might have anything to do with it, but those are the only things I've done in this project that I haven't done in previous projects.

Thanks for your reply. QUOTE (mesmith @ Feb 4 2009, 11:35 AM) I considered that, but have never encountered this before. The build always just overwrites the old files. QUOTE (mesmith @ Feb 4 2009, 11:35 AM) it sure sounds like the builder would succeed the first time if you clean out the destination folder first. I should have tried that before posting. I have confirmed that if I delete the files from the destination directory before building, I get no errors. Any ideas why this would be happening for this project, but not for any of the other projects I've built?

I have an EXE build specification for a project I'm working on. The project uses classes and overrides, but I have managed to get a fully working .exe by storing the classes as LLBs. The problem is, on alternate attempts to build the executable, it returns an error. If I close the error and try building again, it succeeds. If I try building again, it returns the same error. This behavior repeats indefinitely. This is more of a frustration than an actual problem for me, since I just have to try building a 2nd time to make it work. I have noticed that when it returns the error, it removes any old files from the build that were in the destination directory, but doesn't replace them as it would on a successful build. I was just hoping someone may have some insight in to why this might be happening. Googling has been no help so far. The error returned is as follows: An error has occurred. Expand the Details section for more information. Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference: Error 10 occurred at New VI Library.vi Possible reason(s): LabVIEW: Duplicate path. ========================= NI-488: Asynchronous I/O operation in progress.

That's going to depend on which format you save the spreadsheet as in Excel. If it has to be a .xls for some reason, you might read here: http://zone.ni.com/devzone/cda/epd/p/id/3409. Otherwise, try saving as .csv or .xml in Excel. Either would make your task easier to accomplish. EDIT: I found this after my initial post: LINK. It may also be helpful.

Verified here as well. I started the project over completely, and I now have all the functionality I had before, but with LVOOP. It will be much easier to add new boards this way. Thanks to all who offered help.

Thanks for the additional responses. I think I found the nugget neBulus referred to in his first post (nugget). It was informative, but I didn't get around to implementing it yet. I have decided to give LVOOP another shot first, and I am using Aristos' post as a starting point. I have made my classes and will get started on the wiring tomorrow. On a previous attempt at LVOOP, I ended up with essentially the same hierarchy, but was unable to get much further. I know more now than I did then. We'll see how it works out. I appreciate all the advice.

Thanks. I'll see what I can find. LVOOP was my first choice, too, but I had a hard time (my previous posts). Thanks again for the suggestions.

I was afraid that was the answer I would get. I tried to use LVOOP, but had a hard time getting the hierarchy figured out up front. I started the entire process over after several failed attempts at LVOOP. I'm afraid I need to avoid it until I can get some proper training. I don't come from a programming background and I still haven't wrapped my head around OOP. Any other ways to accomplish this?

I'm developing a system to test several boards by switching relays and taking readings with PXI DMMs. I'm hoping to make it as easy as possible to add new boards. Currently, I have a subVI containing the tests for each DUT. The VI for DUT 1 is DUT 1.vi, etc. The VI that runs is determined by the value of the DUT enum. If DUT 1 is selected, DUT 1.vi is run. Initially, I used a case statement with a case for each DUT, but I don't want to have to add cases to several subVIs to add a board. I solved the problem with a Call by Reference Node. I am trying to find a way to accomplish the same thing with a typedef. Currently, I have a case statement with a case for each board. The other cases are the same as pictured below, but have the appropriate Results and States for each DUT. I would like the typedefs to be determined by the value of the DUT enum without having to use a case statement (as with the VI above). The typedefs are just used as constants and are manually set for each DUT. Is it possible to determine which typedef will be used based on the DUT enum input?

I haven't been able to convince anyone to pay for training or Test Stand, and so I continue on with my limited knowledge. I have decided to use classes, but continue to run in to problems. I think my biggest issue is that I wasn't trained as a programmer, and I don't fully understand the class hierarchy. I am using the Drawing Tool example from expressionflow.com as a rough guide because it is the only working LVOOP example I have. I'm convinced that if I could just come up with a logical hierarchy, the rest will be easy. So, I'm asking for suggestions. I have 6 boards. One board is selected from an enum, and when start is pressed, a relay network is set to the initial state for that board (which should come from some class) to power it on. Next, the relay network is switched for the first test (according to a class?). A test is run (specified by a class?). A check is made to see if further tests should be run. If there are more tests, the relay network is switched again and tests run until finished. Then, the results of the test (coming from a class?) will be logged, and the front panel will go idle waiting on the next click of the start button. I have experimented with having a 'Board' class with each of the six boards having their own child class. The child board classes then have child classes called 'Test'. I have also tried having a 'Board' class with a child class 'Tests' and making each specific board a child of 'Tests'. I run in to problems with whatever I try. Every time I change my hierarchy, I spend hours fixing my VI. As far as I can tell, I want to be able to pass an object (maybe 'Test') through the loop. Depending on which board, the VI should be able to determine if there are any tests to run, switch relays, and run the test. Before going any further, I'd like some suggestions on how others would do this. I appreciate any help anyone can offer.

Thanks for the advice. I graduated from college last week and am hoping to do some training in the near future. I have done very well on the CLAD practice tests I've taken, and I plan to take the test in the next few weeks. At my current position, I think money is a concern, and I likely won't have any further training before I'm expected to produce this test system. I have done a few smaller projects here with good results, but nothing that required scalability. I'm sure with enough outdated books and great sites like LAVAG, I'll manage. I'll look in to the NI course books as well. Thanks again for the suggestions.

QUOTE (jhoskins @ Dec 18 2008, 04:35 PM) I have been meaning to read more about TestStand, as it seems to be designed for what I'm doing, but I assume it won't be within the budget. I will do some reading and see if I might be able to pitch it to management. I have found more useful information on classes since my initial post, and I am starting to see how that might be my best option. Any further help is still appreciated.

I will start by saying that I have only been using LabVIEW for around 8 months. I have had no formal training, and work at a company with no other LabVIEW developers. What I know has come from outdated books and sites like this one. I have been given the task of developing an automated test system for several different circuit boards. I have a PXI chassis with DMM cards and will have a relay network to switch for the various voltage and current readings. The idea is that any of the boards can be connected to the system, and the appropriate test can then be selected and run from the front panel. The results will then be logged and a pass/fail status displayed. While waiting for the final board specs, I have been playing with various implementation options. I have used producer/consumer loops with queuing, and I spent the last several days trying to understand and implement classes. I have run in to problems with each method, likely due to my limited understanding. I am hoping someone has developed a similar system and can offer some advantages/disadvantages of particular options before I get too far involved with something that won't work well. Any advice is welcome as this will be my first major LabVIEW project, and I may be in a bit over my head.