rharmon@sandia.gov

Ok, I understand the need for categories. And maybe this already exists and I haven't figured it out yet... I think it would be useful see all the new postings no mater what category on a single listing, maybe a weeks worth, maybe configurable. Sometimes when I have extra time (almost never!!!!) I look into categories I don't always view and find interesting postings... What do you think?

Ensegre, Thank you... Tried everything but NaN.... Works like a charm...

I need to emphasize a portion of a waveform chart. The only thing I can think of is to make two additional plots with only the values I want to emphasize, but that's not working... Anyone pulled this off before??? Thanks in advance....

Thank you all for the information. I truly appreciate the thoughts. I've written several instrument drivers in the past, but most of the time i'm rushed to get the product out and don't spend the proper time on development. That has come back to haunt me in the past. That said I don't want to waste time (my todo list is always several pages long). This paticular instrument allows me to querry the energy sensor for what parameters are available to be modified, and what the acceptable values are. That allows me to set up the user interface configuration vi for each sensor. That makes adjusting parameters by the user easy from within the software. However I'm using a text based configuration file that users could modify a value that is not supported by a sonsor. Most of the time users are not going to modify a setup configuration file... But they have been know to play around!!! So just ignoring an error message, or correcting it before the user sees it is a bad idea... I'm using Messanger Library, but I'm a baby LVOOP user. a child class is probably a great idea but since the sensor can tell me what parameters are available I think that is the way to go. Although branching out a bit in LVOOP would be very beneficial to me... We're talking baby steps here. So again I want to thank your all for your thoughts... It has been very good for me to see from what angles you guys attack these issues...

Time spent for a diligent implementation is important in the short term, but long term I think time spent up front almost always pays off. There is not a timeout for setting an unnnecessary capability. that said there is of course some small about of bandwidth used. I'm not aware of any risks trying to set an unsupported parameter Good point on the error handling, squelching the errors may infact allow an important real error to be lost. Thanks for the thoughts...

I'm writing software for a laser energy meter. I need to write custom software for two reasons. I need to ensure the energy sensors are always setup the same way, and I need to collect the data in a specific way. That said I have a style question for all you labview pros... The sensors allow me to query the current settings and modify the settings. There are about 11 configurable settings, but not all settings are available on all sensors. When configuring the meter for the attached sensors would you: 1. Query the sensor and only modify the setting that are available on this sensor. Or just deal with the errors created when attempting to change a setting that is not available on a specific sensor.. 2. Query the sensor and only modify the setting if the setting is to change. 3. Just change all the setting on the sensor wether they need to change or not. Or would you take an entirely different tack?

Thanks for the response... I thought the problem was in the parent VI, and couldn't find any sub panel property node to deal with scroll bars. Problem was actually in the vi, changed the vi properties and fixed the problem... Thanks again...

Hope this is the right place to post this... I'm using a sub panel that is sized correctly for the vi to run in it. But I always get vertical and horizontal scroll bars... I don't want them, but can't for the life of me figure out how to get rid of them... I'm sure someone knows the trick... Please help....

Concidering purchase of Wezarp... As you all know this product is expensive... but for me, the time savings from updating current software vs just insert this VI and recompile justifies the cost. I downloaded the demo and tried it... seems to work really good, had small issue, but tech support was awesome (this gives me a comfy feeling about the company) that said, would really appreciate the opinion of other LabVIEW professionals. If you have tried Wezarp, pleased chime in... or if you just have an opinion about this type of software chime it also.... Thanks in advance... Bob