george seifert

I have an ActiveX interface that's giving me some problems. I'm able to create a reference where I can select the ActiveX class. I can also create properties and methods. When I run my code I get the follow error when I try to set a property. Error 97 Null Refnum was passed in as input If I put a probe on the reference it shows the value as 0. Any ideas what's going on? I've programmed ActiveX interfaces before but haven't run into this. George

Thanks guys. I didn't even consider Wikipedia for this problem. George

Slightly off topic I suppose, but somebody here must know this. I have a Bruel & Kjaer (2250) sound level meter. I want to convert the raw data signal from it to dB(A). The company wasn't much help. It has an option to A weight the input signal (from the built in microphone). I can get a waveform from the device and am converting it with a DAQ card, but have no idea how to convert to dB(A). Unfortunately I don't have the Sound and Vibration toolkit. Can anybody help with the conversion or suggest a place to look? Thanks, George

I have one PC running an LV app (LV 8.6, DAQmx 8.7.2). After a system reboot, the readings from my DAQ card (PCI-6251) are garbage. If I stop and restart my application (but don't reboot the PC) the readings are fine. I have the same app running on a couple of identical setups and it runs fine. So that would seem to point to a hardware issue. My app resets the DAQ card before setting up all my tasks. I tried reloading my app and DAQmx. I haven't been able to try a new DAQ card yet. Can anybody think of an explanation for this odd behavior? Does it seem to indicate a problem with the DAQ card? George

QUOTE (dong1 @ Nov 10 2008, 07:16 AM) NI has told me that there's a problem with the Wavelet peak detection VI so I really wouldn't recommend using it. My VI was just an example that used NI's VI to illustrate the problem I was having. George

Thanks for the help. I decided to go another route. In the VI with the Path control (destination) I monitor the Listbox for a double-click via a dynamic event. Then I just grab the clicked line and put it in the Path. I think it's even easier for the use than the drag and drop I wanted originally. George

I'm just wondering if this is possible before I spend a lot of time on it. A quick trial and a search got me nowhere. I'd like to drag a filename from a Listbox in one VI and drop it in a Path control in another VI. Is it possible? As a backup I tried to copy the line from the listbox and paste it into the path control, but it wouldn't let me paste into the path control. Any hints to get me going? George

QUOTE (Aristos Queue @ Oct 16 2008, 03:50 PM) Bummer. There should be.

QUOTE (Aristos Queue @ Oct 16 2008, 01:31 PM) I've looked through all the settings and I must be missing it. There's one that says "Configure Express VIs immediately", but that doesn't do what I want. There's another one that says "Place subVIs as expandable", but that also doesn't work. The help for Express VIs doesn't help me either. George

Is there a way to get an express VI such as Time Delay to show up as an icon when first dropped on the BD? I hate having to go to the menu to switch it over all the time. George

QUOTE (Ton @ Sep 30 2008, 07:11 AM) Unfortunately I couldn't load the probe because I don't have OpenG. But I was able to navigate to the Refnum case in your browse variant VI and saw where you use the Variant to Data VI with a Generic type that feeds a property node that gets the ClassName. That's pretty much what I had tried before and didn't work. I've also tried all the NI Variant tools. I've inlcuded a quick and dirty VI in case someone has time to look at it. Forget about how I get the variant value (it simulates how I do it in my real VI). I generated the Variant value and then made it a control to make it easier to use. The VI wouldn't work if you don't have the PXI hardware (or have it simulated). It bugs me that I can see the className right there in the variant value control, but can't figure out how to extract it. Any ideas would be welcome. Download File:post-2786-1222782130.vi George

I'm trying to figure out how to get the className of an IVI I/O control. See the enclosed picture that shows the variant value I get when I use a CTL property node to return the value. Download File:post-2786-1222711224.bmp The variant value shows the className that I'm trying to retrieve (in this case niDCPower). This className is what shows up if you right click on an IVI I/O control and then select Select IVI Class. I tried converting to an XML string, but that doesn't return the value I need. Any ideas on how to return this name? George

QUOTE (JustinThomas @ Sep 18 2008, 09:43 AM) Perfect. I never would have thought to try that. George

Does anyone know if there's a way to read all the properties within a channel in a TDMS file? I know how to read one property at a time using the TDMS Get Properties VI, but you have to know the property name ahead of time. Even if there was a way to list all the property names within a channel that would help, but the TDMS List Contents VI only lets you supply a Group name. George

QUOTE (gleichman @ Sep 16 2008, 03:21 PM) That's what I meant. I believe it works for things other than Word, but I understand not wanting to use non-standard updates. I don't know of another good way to get around it. I agree that NI didn't handle this update right. George

QUOTE (gleichman @ Sep 16 2008, 02:22 PM) I just went through this. I don't know how to send you to the thread but look for this title Can't get Word.Tables in Report Generation Toolkit in LV 8.6 George

QUOTE (daal @ Sep 15 2008, 02:18 PM) I finally got it going. All I needed was some really simple instructions. The KB on this is really confusing. If it just said copy these files to these locations I would have been done two days ago. Anyway, thanks for the help. George

QUOTE (daal @ Sep 15 2008, 12:22 PM) Thanks for the help. I downloaded your example and the Word-GetTableCount VI is broken. Where am I supposed to copy the "NIReport.llb" folder to? George

QUOTE (Doug Norman @ Sep 10 2008, 02:28 PM) I downloaded the example, but it's broken. I can't figure out how to get it to work. I've been messing with it for quite a while now and am feeling really stupid. I just can't understand how to get the correct Get Report Type VI in there. When I double click on the Get Report Type VI in the example VI it brings up a dialog asking which implementation to load. I figured that the NI_Word one makes the most sense. That VI comes up broken with this explanation "This VI doesn't match other VIs in the method, Connector Pane Terminal(s) are different. All VIs that implement a method of a LabVIEW class must match Connector Panes. To correct this, compare Connector Pane of both this VI and the VI of an ancestor class that implements this method." What the heck does that mean? Maybe I'm making this too hard. Sure seems like I need a knowledge of LVOOP to get this going. Any help to get me further along would be appreciated. George

QUOTE (mross @ Sep 10 2008, 11:28 AM) I'm using Word 2003. I'm pretty sure the Word version isn't an immediate problem here. It's more that they introduced objects into play here where there weren't any before. I figured I had no real use for OOP since I don't do multiperson projects and most of my apps aren't all that big. I don't think it's fair that they expect me to program in OOP just to fix a VI that they broke. George

I got a nasty surprise when I tried to open a VI that uses the Report Generation Toolkit to access a table in Word. The Generate Report Get Data to Modify and Generate Report Set Modified Data aren't part of the toolkit anymore. The NI site has some info and I've tried to follow their examples, but I'm just not getting it. Supposedly now I have to use LVclass stuff to access what I need. I haven't tried to use LVclasses yet, and don't have a lot of time to learn a whole new set of tools. Could someone show me how to modify the attached really simple VI that counts the number of tables in a Word doc? Mostly I just need to know how to get access to Word.Tables. Download File:post-2786-1221055973.vi Thanks, George

QUOTE (Ton @ Sep 4 2008, 04:16 PM) Thanks for checking it out. I'll contact NI. George

I'm using the WA Multiscale Peak Detection VI to do some peak detection. I've enclosed my VI that does this. On the block diagram I have to sets of data (far left) labeled "Works" and "Misses first peak". The data looks very similar, but as the labels imply, one finds the peaks correctly and the other misses the first very obvious peak. If I change the "Width" input to the VI down to 2 then it will work with the second set of data. Unfortunately then it detects too many peaks. Even so, with the data sets being so similar it seems it should detect the first peak on both sets of data. I'd really appreciate it if someone could run the VI and tell me what I'm missing. Download File:post-2786-1220546637.vi Thanks, George

I just noticed that there's still a LV process running (in Windows Task Manager) after I exit LV. There's nothing else associated with NI running either. Once I noticed that there were 5 of them running. I don't remember this happening with LV 8.5. I'm assuming this isn't normal is it? George I think I should add that I believe this happens after a crash. I keep getting this error I described elsewhere that implicates Visual C++ when I try to write to a TDMS file. LV crashes after that. Could that leave a process running?

I'm getting the following runtime error when my LV 8.6 code encounters a TDMS Write VI. The error makes no sense to me. The odd thing is that I have other TDMS Write VIs in my code that work fine. It's only when it encounters this VI in a particular place (I put a breakpoint right before it and the error pops up when I single step). I've tried replacing the VI, but that didn't help. Does anyone have any clue what this error means? Why the heck is MS Visual C++ involved? George I figured it out. I was feeding the VI a bad file reference. The error still seems all wrong to me though. Plus it shut down LV which seems totally unnecessary.