hooovahh

I like how you actually handle window resize properly where a very large majority of the custom probes do not. I also like the ms timer column. Have you ever thought about having a dt column? Or replacing the ms timer with a dt column? I only ask because it isn't too important to me that case A was handled at 3946013 and case B was handled at 3959319. What is useful is how much time went between the two cases, which can tell me how long it took to execute case A. I can of course get that information if I do math but it would be nicer if the probe did it for me. At the moment I'm using VIBox Probes by SAPHIR which has a History Probe for strings. This has a few features yours doesn't like being able to set the history length to a number (not window size), and being able to pause based on the string value. One feature neither you nor the History Probe has that I've thought about is the ability to Pause the probe. I haven't needed to use this feature yet so maybe it is stupid, but I wonder if it would be useful if you could press a button and then have it no longer update the probe with new values but have the VI run like normal. My use case is what if my VI is running like normal, and then I see some case happen that wasn't expected. The probe will overwrite its values if the VI keeps running and handling cases but I may want to see a snapshot of the cases that were handled to figure out what led up to going into that case.

Yup that was what I was thinking. Possibly a ring with the string values in a look up table or something so you don't need to read the string values with a property node every time you want to know which item was selected. Although that gets me thinking. So with an Enum we can read what all the possible values are using the OpenG Get Strings from Enum function. Is it not possible to read the string values of a ring control the same way because that information is not contained in the wire, only the numeric representation is?

When ever I think comedy and LabVIEW/Technology, the LAVA Lounge is a good place for it. Over at NI they have the Break Point board: http://forums.ni.com/t5/BreakPoint/bd-p/BreakPoint

Yup, I'd say this is one of those "Everyone makes that mistake the first time" type is situations. I just want to know if my number is NaN so I wire it to an equal and put a constant of NaN right? Nope use the primitive under the comparison palette "Not a Number/Path/Refnum"

I have not used it on a real project yet, but what work I have done with it appears to show it as being stable. I also agree that we probably won't be using it on large projects until the SP1 release. We also have some Veristand guys and we try to all upgrade at once. Veristand 2013 came out a few weeks ago so hopefully we can all just wait until the SP1 release of LabVIEW and upgrade together.

Okay maybe this mythical cluster never really existed and it was a dream. I must have been thinking of the Left and Top cluster I already posted, and can be found in the thread you linked to.

Nope, also 1px on each border.

This is still not the borderless one posted by AQ years ago. This is also a 1px border. If you put a numeric in the cluster then the cluster in an array, the size of the array will be 2 pixels larger in width and height when compared to just an array of the numeric. The cluster I posted will be 1 pixel larger in height and width. The one originally posted would be the exact same size because it was truly borerless.

I don't remember if there were other ways to select the cluster and move it. You may have been able to double click it from the block diagram, get its selection, then use the arrow keys to move around I don't remember if that worked or not. Even if it did work any engineer taking over a project would get quite frustrated when they couldn't find out a simple thing like "Is this an array or a cluster?" and "how do I select the stupid thing?"

Okay so I don't have the original post of the 0px cluster. But to me it was a little useless because it was 0px and you couldn't actually click it to select it. This broke work flow every time you needed to move it on the front panel. But what I do have that I don't see here is a 0.5px cluster. It has 1px on the left and top border, but 0px on the right and bottom. This means you cannot select the cluster by clicking the right or bottom, only on the left and top. Top Left Border Only Cluster.ctl

With that piece of information I'm guessing it is a real bug. LabVIEW is likely writing the same exact string to the file so that bit for bit it doesn't change at all. So why does it think it has changed? i too have felt the pain of remote graphical development. I just can't bring my self to do it. I then deal with the changes between machines, but luckily the changes have been mostly slight changes because development machines are loaded with similar software.

It's not wrong. The two forums share alot of the same knowledge but sometimes someone at NI's forums may have an idea that someone here did not. When making a post that you want to involve both communities in, generally people will have a link to the same post on the other forum, so that anyone can get a more complete picture of the things you've tried, and suggestions others have made.

Here is the description for that error. I'm guessing you don't have some VISA run-time installed properly.

We are not a service. You are not paying us. We are here to answer questions and assist those who need help, and to those who put in an effort to learn and do their own work. You have not posted anything useful or any code that you have tried or described where the issue is only that it doesn't work. That's great what is the error? Did you search for it on NI's site? Did you look at any of the many examples shipped with LabVIEW? What worked and didn't work? If you are not getting a response (which you haven't said is true or not) I would make sure that you can get the module to respond with a more low level application like hyper terminal to ensure your setup is not the issue.

Please do not create duplicate posts. I deleted the other one because that one was in an incorrect topic section. In the future if you want a topic moved click the Report to Moderator button and request a move. Here is what I said in the other topic before deleting it: Looks like there is some good information in there about how to communicate over RS-485. What part of your task are you having problems with? LabVIEW ships with many examples on using VISA to communicate to serial and GPIB. Go to Help >> Find Examples and search RS-485 to find the relevant ones.

How about this. Get a list of all front panel controls, and then register for a Value Change on any of them, or shortcut menu activation on any of them. There will of course need to be code to understand what to do with the event after it is generated but you can have it be semi-automatic in that it finds all the controls on the front panel. Register All Controls.vi

This is a recent change to the forums to combat the recent influx of spam. Sorry for the inconvenience. Admins at LAVA did not make the decision lightly and are trying their best to keep a community as free from spam as possible.

So at NI Week the pricing mentioned was $500 for full version $400 for board only. Since then a NI rep has said $250 student, $500 University, and $1,000 for non-academic use. (all prices I assumed were US dollars). I've been keeping my eye on the MyRIO page, and signed up for updates but haven't seen or heard anything so I just emailed my sales rep to see what my options are. The detailed spec looks less impressive then I was hoping but still cool. One thing I noticed is the AO rate on the FPGA is the slowest that NI offers. Analog Input rate 500KS/s (aggregate?) and Analog Output 345KS/s. What is odd to me is I have never seen aggregate sampling rate on an FPGA before. Still I want to see what I can do with it. Add an LCD display, and a keypad and you have a good platform for making something.

I think your speed test is a little flawed. You shouldn't be updating any UI indicators in states that you want to know how long it takes to execute, because these operations like updating the UI happen asynchronously and can effect the time a state takes to execute in an unpredictable way. I would also recommend removing debugging, and automatic error handling. That being said I still saw a large improvement using the example class you had. I don't have any other classes to test it with at the moment.

I couldn't get your snippet to work, can someone else confirm that something was lost in the upload?

It's low brow when compared to the sophisticated British humor. (I meant to link to the Simpsons episode that made fun of Benny Hill but I can't find it)

To add to this, when a quick drop function runs, it runs in a different application instance. This may make debugging slightly more difficult. Once you get a break point to trigger you don't really need to worry about it but I'm guessing what the issue was is that you set a break point, but it was for the main application instance, and hasn't been resaved, so when the quick drop ran the break point wasn't called in the new application instance.

I think you need to learn to ask questions a little clearer, but I think I see you problem and I would consider it a bug. In LabVIEW 2011 SP1 I made a button, then set it to Switch Until Released. In this state the user should will click the button, and when they release it it will return to the state it was in. So a user should only ever have a True state when the button is down, and when the mouse button is up it should always be False. What mojalan was trying to say is if you press and hold the center mouse button (button 3) the button will change to True as if the left mouse button had been used. Then while holding the center mouse button, hold the left mouse button. Now the button will change to False. Then release the center mouse button. Now the button will change to True. Now release the left mouse button, but this time the button remains True. There are many work arounds. The first that comes to mind is use an event structure and select the "Mouse Down?" event, and if the mouse button is button 3 then discard the request for a mouse down (wire a True to the discard terminal). This will then prevent the center button from doing anything.

I often rename when a VI no longer means what the file name may suggest. I may have a VI that determines the pass/fail status of some DAQ measurements so I name it "Determine DAQ Pass Fail.vi", then I realize my software needs change and I now need to determine pass and fail status for many other mixed signals like CAN, I2C, calculated information, and other data, so I modify my VI to now handle determining Pass or Fail status for any data type but the VI name just states it works with DAQ. So I rename the VI to be "Determine Pass Fail.vi".

Yeah you were a little unclear on what you wanted. What you want can be done with Invoke or Property Nodes. I've never done it before but it wasn't too hard. Attached is a VI that will make a VI, drop in an Invoke Node, change it to the VI type, then set it to Abort VI. Saved in 2010. Create VI With Abort Invoke Node.vi Create VI With Abort Invoke Node.vi