Jump to content

rkesmodel

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

0

About rkesmodel

  • Rank
    More Active
  • Birthday 01/18/1952

Profile Information

  • Gender
    Male
  • Location
    Huntsville, Al

LabVIEW Information

  • Version
    LabVIEW 8.6
  • Since
    1996

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Actually, it will be a little slower than that. The rule of thumb I have always been given by NI tech support for all NI mutiplexed devices is (Max samle rate/# of channels*0.8). So, it would be 200/16*0.8=10KS/sec per channel. If you need faster sampling you will either have to buy a faster module, or one that will do simultaneously sampling. For multiplexing at 200K across 16 channels you would need a module with a 200/0.8*16=4MS/sec capability (at least). Roy
  2. Oops, my bad. I meant the NI-9234, four-channel C Series dynamic signal acquisition module for making high-accuracy audio frequency measurements from integrated electronic piezoelectric (IEPE) and non-IEPE sensors with NI CompactDAQ or CompactRIO systems. http://sine.ni.com/nips/cds/view/p/lang/en/nid/208802 The other numbers are correct. We want one of the stand alone USB, single module chassis for it. Roy
  3. Does anyone out there have a used or discounted NI-9134 and NI-USB-9162 or NI cDAQ-9171 for sale? We have a need for one of these, but new ones are a bit beyond our contract budget. Thanks.
  4. Great work Kelly. I have used your earlier version (before the cluster and tab controls were added. However, how do you generate the list of controls? Roy
  5. My customer is about to purchase a laptop to run our PXIe-1062Q chassis through the PXIe-8360 kit (PXIe-8360 in chassis to ExpressCard-8360 in laptop). He is looking at either an HP EliteBook 8530W or DELL Precision M4000 running Windows XP Pro. Any stories greatly appreciated. Roy
  6. I would like to be able to set up a default VI that would be AUTOMATICALLY used as a template for all new VIs, ESPECIALLY when I "Create SubVI" on the BD. The way AutoCAD used to do this comes to mind. I could create a drawing with all of my usual default choices and save it as "acad.dwg" in a specific location. Any new drawing would then be created from that template. Currently, as far as I know, you have to open a new drawing from a saved template to do this and there is NO way to control the choices when you "Create SubVI", you have to manually change them every time. Roy
  7. I would like to see the wish list set up with searchable sections, like "FP wishes", "BD wishes", "Project wishes", etc. We could then search for previuos wishes at top level or within levels and VOTE on them. This would save typing in previously submitted wishes and give an easy tally of how many would like the feature. POWERFUL tool to ghet features we want. I have submitted this to NI and mention it to every support tech I talk to so they will submit it. Roy
  8. QUOTE (Michael_Aivaliotis @ Aug 22 2007, 01:39 PM) Great idea, Michael. I would like to see the reverse functionality. Right click on the vi name or icon (yes, I'd like to see small versions of the ACTUAL icons) in the project tree (Items or Files view) and "Find all instances" just like we can in VI Hierarchy view. We can "Find - Callers" and "Find - SubVIs". Why not "Find - All Instances"? I have not only submitted this to NI, but also mention it to every support tech I talk to, so they will submit it. Roy
  9. Does anyone have a working vi to write LabVIEW data to a MatLAB binary file (.mat)? I found this: http://digital.ni.com/public.nsf/allkb/562...62570D10074E3CC but when I try giving it an array name and 2D array of data MatLAB says it cannot read the file ("File may be corrupted"). Any assistance greatly appreciated.
  10. QUOTE (dnt @ May 2 2008, 05:00 PM) Thanks for the suggestion, but I can already get the files in csv format. The problem is that these files can be a big as 103Mb. It takes quite a while to read in that large a file. That is why I was looking for a way to read the bin files.
  11. Test engineers are sending me large (1Mb) .bin files of data saved from an Agilent DSO6104A Oscilloscope. I need to read the files into LabVIEW. Has anyone done this? Thanx
  12. How about a format 'paintbrush' that would copy ALL of the format (text, color, size, etc.) from a control/indicator to another like Word and EXCEL have? I have had a situation where I had what I thought was a perfectly good FP with multiple LEDs, BOOLEANS, etc. and the cutomer came along and said things like, "Make them all bigger", or "I don't like those colors" (and yes, I thought I had prior approval). It would be nice if you could change just one of each item and then 'paint' the others. Roy
  13. How about a format 'paintbrush' that would copy ALL of the format (text, color, size, etc.) from a control/indicator to another like Word and EXCEL have? I have had a situation where I had what I thought was a perfectly good FP with multiple LEDs, BOOLEANS, etc. and the cutomer came along and said things like, "Make them all bigger", or "I don't like those colors" (and yes, I thought I had prior approval). It would be nice if you could change just one of each item and then 'paint' the others. Roy
  14. Hello all, Thanks to an increased Capital Equipment budget, I am now able to put together a 'portable' lab measurement system. We already have a PXI chassis with MXI-3 interface in a desktop PC and want to upgrade to PXI-ExpressCard8360 and a laptop. I am looking for recommendations (both pro and, especially, con) on what laptop I should use. I have a fairly generous budget for the laptop (about 5 grand). I want to stay with a Windows machine. It will also probably become my general use and LabVIEW development machine, so I don't want it to be too massive. I have already printed the list from NI. I am looking for real-life experience. Thanks for any assistance. Roy
  15. QUOTE(David Boyd @ Mar 17 2005, 08:47 AM) Dave, Interesting link. However, the main problem that Paulo will have is that when LabVIEW accesses a flash drive it keeps a reference open to the drive until LV is completely shut down. There are several programs that will do this (even some MS ones). They will keep a reference open to the last drive they accessed. The only way I have found around this behaviour is to either shut down the offending program or access a different drive (do not know if this works w/LV). Aslo, many of us are CLN 'challenged' and the article is so much Greek . Anyone have a solution out there?
×
×
  • Create New...

Important Information

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