Saverio

Why are you trying to pass a pointer to a structure? The function prototype uint32 Function_name(struct OutData) clearly does not indicate that you're supposed to pass a pointer to a structure! Also, you seem to be dealing with a C++ DLL, as the name mangling shows. Please review the articles on the NI site and in the LabVIEW Help regarding calling C++ DLLs and name-mangling issues. If you are trying to call other functions you may not be able to see them due to the name mangling that occurs with C++ DLLs.

You have to be careful about what you're actually referring to. The Microsoft Office Spreadsheet is an ActiveX control, which is not the same as the ActiveX interface for Excel. Two different things. If your front panel control looks like this: then you're talking about the ActiveX control, not the Excel ActiveX interface. Is this what you are using?

Your data cluster contains 9 elements, but the prototype indicates it's only 8 elements. So, you've got one too many elements in your cluster. Also, have you changed the datatype for the NType element to U8, as well as the individual elements of the data cluster?

Other than the fact that a serial connection will be slower than a USB DAQ I'm not sure what you're really expecting in terms of an answer. Which USB DAQ device were you using? What's your instrument? What's your baud rate? Have you configured the VISA Read to end its read on a termination character? If not, are you accumulating the serial port reads in a loop? What's your loop rate?

cross-posted at the NI site in MULTIPLE places: http://forums.ni.com/t5/LabVIEW/buying-labview-programme-on-sensor/td-p/1179075 http://forums.ni.com/t5/LabVIEW/how-to-read-sensor-digital-input-and-output-using-labview/m-p/1178945#M511703 http://forums.ni.com/t5/LabVIEW/URGENT-pls-help-me/td-p/1184101

Well, yeah, I figured as much. I was being facetious. After all, I know he frequents the site you folks like to refer as to the "Dark Side".

Gee, thanks.

QUOTE(Gavin Burnell @ Jan 22 2008, 03:19 PM) There's actually two versions available. One that uses libxml and the other that uses the MS XML parser. I happen to use the one that uses the MS XML parser.

One of the options in the poll is LabXML, which is what I use. It inherently uses the MSXML parser, so I'm not sure which poll answer to choose in this case (went for LabXML). The earlier comment regarding using .NET is interesting because I actually tried to use it and I found it to be abhorently slow, as compared to LabXML. I essentially duplicated the operations that were being performed in LabXML in reading an XML node, so as not to hard-code the schema, as mentioned in the post. I found that the same operation was an order of magnitude slower with the .NET XML interface.

QUOTE(Aitor Solar @ Jan 7 2008, 03:11 PM) No. I just changed one hex value at a specific location in the file. That changed the behavior of the output to "required". It did not corrupt the VI, as far as I could tell. There was the side-effect that I mentioned, but I don't know if that's because LabVIEW inherently doesn't deal with required outputs, or what.

Back to original question: Does changing it by means of a hex editor count? 'Cause that's how I did it. Odd side-effect is that the Info window shows the correct display in terms of its wiring property, but when you right-click on the indicator it doesn't.