Jump to content

Neville D

Members
  • Posts

    752
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Neville D

  1. Hi Abe, Use the "active plot" property to select which plot you are working with, then change the name of that plot. Active plot just accepts plots numbered 0,1,... etc. Neville.
  2. There is something on the NI website.. search for Icon Art Glossary or something like that.. they have an html doc that can pull up a whole bunch of icons which you can then modify to your taste. Neville. PS Let me know if you can't find it.. I downloaded it a while back, and I can dig it up from my stuff if required.
  3. Is the Hard drive formatted for FAT32? How about the boot sequence? Is it set to A drive and then C drive? I think the chipset might be a problem. As far as I remember they support a chipset that is not commercially available anymore. You should check with NI on this. Also if you are using LV-RT 7x, you need to download lvalarms.dll from your Desktop using the FTP tool in NI-MAX. There is a bug in the lvalarms.dll that gets built in. <<Check the knowledgebase for detailed info about where to find the lvalarms.dll file on your pc and where to place it on your target.
  4. I stand corrected! Sorry. Neville. In my opinion, throwing in a write or a read DS function is a lot easier & quicker than writing a TCP/IP client server. That is the idea behind the Datsocket stuff. Unless, you have the TCP/IP Client Server already written from another project.. N.
  5. Looks like NI just swallowed another little fish! T&M World article
  6. Hi Khalid, I realized that, and my utility will save the changed VI by invoking the "Save instrument" method. Try it out! Regards, Neville
  7. Very strange. I don't believe it has anything to do with the exe specifically. Try switching off one of the instruments and seeing if your code generates an error. It HAS to. What does it do when it "runs right through"? If it runs through without generating any errors, I am wondering what your code actually does. Neville.
  8. Are you getting any error message from your code? Where is it hanging? Is your interface GPIB0 or is it GPIB1 (plugging or replugging the USB device might cause it to use another device number perhaps). It has got to be something simple.. its not a big deal to build/install/run exe's. Neville.
  9. Is your VISA alias on the new machine correctly set up? i.e. if you are accessing com port 1 as "COM1", then on the new system COM1 needs to be linked to Serial port#1. Same concept applies to the VISA aliases. If your DMM is accessed as "DMM", define it to be the instrument you require. Or else just use "GPIB::5" in the VISA control or constant. Try to put an indicator on the front panel that shows you what the VISA string being used by the exe is. Remember, once you have built the exe and installed the RTE, on the next iteration, simply copy over the new exe and it should run (you don't have to go through the install process again). Neville.
  10. Thanks guys, I wasn't sure if that property would overwrite an existing VI, but it seems to work. Here is a utility that I wrote to get rid of breakpoints and then save the resulting project. http://forums.lavausergroup.org/index.php?...findpost&p=7003 Enjoy! Neville.
  11. Hi Khalid, and Lavezza, I took the liberty of adding Lavezza's code with a few mods to an existing tool that I had worked on with E. Blasberg. It helps you to find used and unused VI's in a project, kill unused VI's that you select, and now, remove all breakpoints in the project. Throw this llb in your /projects folder and then restart LV. Use from the Tools menu (Find used & unused VI's) Thanks to all who participated. Here it is! Neville Download File:post-2680-1129654122.llb
  12. Hi All, I am trying to write a utility that finds all breakpoints, removes them and then saves the changes. Anybody know how I can programmatically saved the changed VI? I already got the breakpoint stuff working. Thanks, Neville.
  13. No, it looks like everything closed out pretty fast. Just a comment, publishing data (Real or booleans) is a more efficient (faster) way to go than the simple method of right-clicking on a control & publishing it to the DS server. Neville.
  14. The NI Web server only supports Internet Explorer. Datasocket is the way to go. I have communicated with about 16RT targets with buffered data using Datasockets. Usually works well, though sometimes the Datasocket server inexplicably crashes at startup. Neville.
  15. I tried your VI and everything works pretty fast. Close < 1s. Do you have enough memory in your PC? I have a laptop with 1Gig of RAM (just for comparison). Neville.
  16. You can also define a constant 2d array by putting an array object on your block diagram then placing an I32 number in it. Drag the index control downwards to make it 2d, then drag the edges of the array to increase the number of visible elements, then type in your values. Neville.
  17. Hi Rohit, The listbox has a property whereby you can display a little symbol next to each entry. Instead of having a complicated series of moving boolean arrays, just display a "check" symbol for true and a "x" for false. Right-click on an item in the listbox and visible items>symbols. You can also access this property through the property nodes. And yes, you can add a scroll-bar to the array by right-clicking on the array>Advanced>Customize and then edit the array control to replace the up and down arrows with a scrollbar. Neville.
  18. Use the Text & Pict Ring control from the Ring & Enum Pallet. Neville.
  19. I think it helps to know the limitations of the tools you have at hand. The idea of the references etc. is to clean up your top-level diagram, and bury property manipulations in a sub-VI.. a VERY useful function, but it has its cost. Neville.
  20. What do you mean by Timer loop? You can use the "timed loop" structure which can be stopped and restarted as well. Neville.
  21. Yes, the executable will run slightly faster, since diagrams are not saved, and Front panels of lower level VI's are not saved, and debugging functions are disabled. I doubt if you will get an order of magnitude speed improvement though... The VI is also "compiled". Every time you save a VI, it does a quick compile.. you will see the compile message only if you have a large number of VI's you are saving at the same time. N.
  22. Hi Ayumi, After digging around in the NI Knowledge Base (www.ni.com/kb), I found some answers. Check out these links: http://digital.ni.com/public.nsf/allkb/4FC...6256D8900563E45 http://digital.ni.com/public.nsf/websearch...6256b3a0062bff6 http://digital.ni.com/public.nsf/allkb/7DF...6256DF900785211 http://digital.ni.com/public.nsf/allkb/560...6256C5500711C2B http://digital.ni.com/public.nsf/allkb/D41...6256FE8000F28FD http://digital.ni.com/public.nsf/allkb/CE8...6256AE600663BD3 http://digital.ni.com/public.nsf/allkb/AB4...6256C010061EA7B http://digital.ni.com/public.nsf/allkb/5D2...62565D7005DEA42 http://digital.ni.com/public.nsf/allkb/23F...6256CD70055095E Bottom line is the speed of your computer is also an issue when trying to do high-speed DIO. Another thing is the speed and efficiency of the DAQ driver. Looks like you are using the "traditional NI-DAQ". DAQ-Mx the new driver is far faster & it uses a multi-threaded architecture. This might buy you further speed as well. But it can't be used with LV 6.1 You would have to upgrade to LV 7.0 or later (7.1.1 is the latest version). Take a look at the speed benchmarks in the above links. Hope this helps. Neville.
  23. That would help too..!! Sometimes you can't see the forest for the trees! :headbang: N.
  24. If the time taken to execute the code is very small (<10ms), the overhead required to call the counters might affect your readings. In this case, 1 Get start time from tick counter. 2 Perform a known number of operations in a loop 3 Get stop time from another tick counter 4 Calculate the avg. time for the operation using the #operations and the elapsed time. Neville.
  25. Ayumi, can you PLEASE provide more complete information. It is impossible to follow what you are doing with little bits and pieces. 1 Explain your application 2 State your Software Version (including DAQ driver) 3 Describe your hardware & setup (triggering etc.) 3 Post your example code 4 State your exact problem I cannot find your particular example in my LV version 7.1.1. Neville.
×
×
  • Create New...

Important Information

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