Jump to content

jhoskins

Members
  • Posts

    102
  • Joined

  • Last visited

Everything posted by jhoskins

  1. QUOTE (PJM_labview @ Jan 30 2009, 12:44 PM) Not sure why you would even want to use the picture for this anyway, but since you do. Can you tell us what exactly you have tried to do, so that we do not re-invent the wheel.
  2. Thanks Crelf, I went throught the courses a few years ago and have been applying what I learned in those courses eversince. My partnet in LV crime here just went through the course a couple of days ago and has the updated book and materials for 8.6. I plan on going through this material again as a refresher before I take the exam. I think I will do OK on it. I guess I just have pre-exam jitters. Thanks again, QUOTE (neB @ Jan 16 2009, 04:04 PM) So another good key is to follow the style guidelines and DOCUMENT, DOCUMENT, DOCUMENT everything. Controls, indicators, block diagram, tip strips, states of the state machine. Everything right. I will definetely keep this in mind while going through the test. I do this a lot anyway because I develope test sets for the PCB boards here and we have to make our test sets to where a "Monkey" (Pardon me if this offends the Monkey) can do it. Like I said before, it is just probably Pre-test jitters, Thanks,
  3. Thanks Crelf, I went throught the courses a few years ago and have been applying what I learned in those courses eversince. My partnet in LV crime here just went through the course a couple of days ago and has the updated book and materials for 8.6. I plan on going through this material again as a refresher before I take the exam. I think I will do OK on it. I guess I just have pre-exam jitters. Thanks again, QUOTE (neB @ Jan 16 2009, 04:04 PM) So another good key is to follow the style guidelines and DOCUMENT, DOCUMENT, DOCUMENT everything. Controls, indicators, block diagram, tip strips, states of the state machine. Everything right. I will definetely keep this in mind while going through the test. I do this a lot anyway because I develope test sets for the PCB boards here and we have to make our test sets to where a "Monkey" (Pardon me if this offends the Monkey) can do it. Like I said before, it is just probably Pre-test jitters, Thanks,
  4. I am also going to take my CLD exam in a couple of weeks. I have done some large application (what i consider large anyway) development and have been programming in LV for about 6 years. I have worked through all of the examples online and have been going through the exam preparation. I very rarely ask the forum for questions but I do answer a lot of them. There are only two LV developers in my company and although I have been programming in LV for a while now I still do not know if I am at the level of programmer that I need to be to take the CLD exam. I passed the CLAD with flying colors and I have taken the Intermediate 1 and 2 course. I my self would like more advice from people that have taken them. I know from the disclosure agreement that you cannot say much about the exam. One thing I would like to know is, is the actual exam much harder then the examples or can we really use the examples to judge our level of expertise. What are some different areas to study other than the exam prep guide, that you all feel is useful. thanks,
  5. I am also going to take my CLD exam in a couple of weeks. I have done some large application (what i consider large anyway) development and have been programming in LV for about 6 years. I have worked through all of the examples online and have been going through the exam preparation. I very rarely ask the forum for questions but I do answer a lot of them. There are only two LV developers in my company and although I have been programming in LV for a while now I still do not know if I am at the level of programmer that I need to be to take the CLD exam. I passed the CLAD with flying colors and I have taken the Intermediate 1 and 2 course. I my self would like more advice from people that have taken them. I know from the disclosure agreement that you cannot say much about the exam. One thing I would like to know is, is the actual exam much harder then the examples or can we really use the examples to judge our level of expertise. What are some different areas to study other than the exam prep guide, that you all feel is useful. thanks,
  6. Welcome to LAVA. Do not worry about asking stupid beginner questions. We have all asked "stupid beginner questions" at sometime or another. Do search first and try to find out as much as you can before you ask.
  7. You should really look into getting TestStand for automated testing. You would save yourself a whole lot of time and headache. It will take care of all the datalogging and is really easy to work with. Then all you have to do is code up a UI in LabVIEW to call the correct sequence file for the board type. Much easier than coding everything in LV. Just my 2 cents
  8. When I got my second monitor about two years ago, I found that my productivity increased by about 60%. Not only for devloping in LV but for daily activities as well. If you do use a second monitor i would suggest a program called MultiMon. this utility allows you to have a toolbar on each monitor. it also makes it easier to put hings on the 2nd monitor. If you do not have a second toolbar you have to shrink your application then move it to the 2nd mon. and then maximize it again. With MultiMon all you have to do is hit the arrow that it places on each window and it automagically puts it on the opposite monitor. I love my dual monitor setup. I absolutely hate it when I am forced to work on a computer that only has one monitor. (ie At home)
  9. QUOTE (jhoskins @ Sep 26 2008, 09:29 AM) Just to let everyone know. We got this working by downloading a utility from http://support.microsoft.com/kb/311272. It has command line inputs so I just created a batch file to run the commands that I needed to run.
  10. Our application is to develop a functional test fixture for one of our production boards that is usually installed in the NI PXI-1042 chassis with the PXI-8196 embedded controller running XP pro.We are using a Chroma ATE 52906 extender card to test our UUT so we can access the board during test. The 52906 extender card allows us to turn off power to the UUT, replace the UUT, then turn power back on without rebooting the host computer (PXI-8196) which saves us considerable test time. We use the following process to change UUT's 1. Go into Device Manager, look under Other Devices and select the UUT (shows up as: PCX Custom (OEM) PCI 9656 Board), then select Action --> Uninstall. 2. Turn off the 52906 extender card and replace the UUT. 3. Turn on the 52906 extender card and wait for the UUT to boot up. 4. Go into Device Manager, select the computer icon at the top of the device tree, then select Action --> Scan for Hardware Changes. 5. The Found New Hardware Wizard will open. Follow the steps and allow the wizard to automatically search for and install the driver. 6. The UUT is ready for test. My goal is to accomplish steps 1, 4 and 5 programatically using LabVIEW. Any Ideas Thanks,
  11. QUOTE (JFM @ Sep 9 2008, 08:59 AM) Or try this.
  12. welcome, glad to have you aboard. :beer: Cheers
  13. QUOTE (crelf @ Apr 29 2008, 04:30 PM) My point exactly. i could not have put it any other way. I wonder, within all of this rambling, did we answer this guys question? Thanks Rolf for all of your insight I always enjoy your posts
  14. This conversation can go on and on. Simply put we know that LV can lots of things just as good as TS. I prefer the LV-TS combination when it comes to complex testing that contain multiple developement environments. ie C, C++, LV, CVI.
  15. Rolf makes some great points, but I still prefer teststand. I have written dlls that Labview just will not interface with (even with a wrapper) it just does not see the inputs or sometimes will not produce an output. I have sent the dlls to NI and they cannot figure out why they do not work. I have also had dlls that will work just fine in one VI that will not work in another VI. LV has problems with dlls. Not only that all the dlls for LV must be written in C. TestStand can use dlls form: LV, CVI, C++, .NET. I also love the fact that you can set a breakpoint in your sequnce and if you have both developement environments on your pc then you can enable tracing and debug C code. I am not saying that TS is always the best way to go, sometimes it is overkill. I personally think that TS is a great tool and is worth every penny I put in to getting it. it serves my purpose very well.
  16. QUOTE (Michael_Aivaliotis @ Apr 28 2008, 04:12 PM) I would'nt. We have a lot of legacy dlls that LabVIEW just will not use correctly. I love the fact that I can code my tests in just about any language. I prefer LV but the other people around here prefer C or C++ and even .NET, using TS allows me to reuse code that they already have written. Also the debug capabilities are great to. Try debugging a C dll in a LV statemachine! I am not knocking statemachines or anything else, I am just stating that for me and my situation the LV-TS combo works great and I would not trade it. Although sometime TS is an overkill.
  17. I use LabVIEW and teststand together all of the time. I keep it a simple (yeah right) concept though. I keep LV as the user interface to teststand and use TS as just a sequencing engine. If you keep this in mind then they play very nice together. I have had a few problems in both LV and TS but it was nothing major and was fixed rather easily. I love the two of them together. Keep LV what it is: a programming language (but in this case a user interface) Keep TS what it is: A TEST ENGINE. I would agree with Michael in the fact that you do have to know som C syntax to get the things that you want from teststand.
  18. If it is in a cluster then you will have to get the reference to the cluster. then use a property node to get the controls reference array. index the array to the proper control. (same as tab order in a cluster), then using another property node write an empty array to the value or to the history data. or you could right click on the chart in question and select creat property node/ value or History data and wire an empty array to it.
  19. QUOTE(Neville D @ May 11 2007, 11:17 AM) Thanks for the tip but unfortunately it did not solve the problem, I have played around with the settings but to no avail. I will keep trying and if anyone else has any Ideas please let me know. It really is not a big deal to me. But when you are putting things on the production floor and the manufacturing engineer is pissed off because you actually helped him out but you did not use C++ (hardcore C++ guy). I catch a lot of slack around here for being the only LV programmer, but it is fun. thanks for all of the help.
  20. This is really annoying. I got a complaint from one of my fellow engineers on the floor. His complaint was that when he closed my program it took the program a long time to not be visible in the taskbar (not really a big deal to me). I mean the FP goes away but the taskbar indicator stays up for as long as 30 sec or more. I tried it on my developement machine and sure enough it does the same thing. So I decided to put in the quit LV function, same result. Then I decided to downgrade the program to LV 8.0. I did that and built it into an EXE and it worked perfectly. As soon as I closed the front panel it was removed from the task bar within a second or two. So I then built (using 8.2.1) a really really small app (while loop, random #, Indicator) and built that into an EXE. I ran it and it had the same results. Has anyone seen this type of behavior using LV 8.2.1. I have attached that original problem VI.
  21. QUOTE(jpdrolet @ May 8 2007, 08:14 PM) That probably took a great deal of time. SWEEEEEET Program
  22. QUOTE(Submeg @ Apr 25 2007, 04:04 AM) Look in the example finder under events and you will see a VI called analyze and present. this will get you started.
  23. QUOTE(gustav @ Apr 4 2007, 09:23 AM) All you have to do is tab to the control to give it focus and use the up/down arrow keys.
  24. QUOTE(crelf @ Mar 9 2007, 02:59 PM) I just installed the beta (took forever) and read the release notes and I tried and and love them. Oh and don't forget the new . See you all all on the beta forum because we cannot talk about the new stuff here.
  25. QUOTE(linnx @ Feb 13 2007, 05:29 PM) This is also cross posted http://forums.ni.com/ni/board/message?board.id=170&message.id=229454&jump=true' target="_blank">here.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.