ShaunR

Its more of a reboot than a reset. The state depends on what you have set the power-up states to be from MAX and the position of the DIP switches (refer to the manual)

Told you I get confused as to which propery nodes need closing of the refs

Sweet

You can't help but laugh AT them in this

Try this Although I don't know whenter it will reload the vis if the vis in memory aren't modified. LV might ignore it if it doesn't think anything has changed. But you should really be checking in/out and merging since its really a source control issue.

Not quite sure what your getting at here since the project is just an organiser. You can set a directory to autopopulate which will cause it to react when changes to the organisation take place. Individual vis can be reloaded by selecting "revert" which forces a reload from disk if the vi has changed (you can use an invoke node for this).

Interesting. You don't get any of those when you click on "Code Repository" in the menus at the top (the way I went )

And these " LAVAcr standards" are documented where?

I think it needs to be approved or something. It doesn't appear in my file list but I can see it in the repository and edit/download etc (and its a different colour to the others). If I click on the link its there, so must be just the uploader until its approved.

You'll probably need the "Embedded Module For Blackfin" http://www.ni.com/labview/blackfin/

The short answer is you cannot. You cannot change the text attributes of a single column/row and you cannot embedd child controls into the cells. What you can do is make it look like that is what it is doing. For thee password display, you can replace the text after the cell is edited using the event structure. You will have to keep another copy of this column since you will be overwriting the cell contents. For the combo-box, you can overlay an array of menu-rings or enums. You will have to manage resizing if that is required.

Watch this space insted. PassaMak

Well. Yes and no. It uses .NET so its a bit like saying a vi creates Word documents when, in fact, it is an automation interface to Microsoft Word and Word creates the document. No word, no document. No .NET, no messages.

Well. What can I say. It'd take me a week to figure out whats going on in that spaghetti. I would suggest thet you keep the diagram open while running and when it no longer responds, click the "Highlight Execution" button (the lightbulb). That will show you where it is currently executing. That will at least narrow it down.

Be even better if we could catch windows messages in the event structure!

Can you post an example that demonstrates the problem?

Same here. Watch this space.

Indeed. From the usage point of view it look on the face of it to be nice and easy to access from within the code and you certainly have created a sleek interface. I'm not sure how time consuming it would be to create 5 translations for 300-400 controls though. Also, what if (as in my case) the developer is not the translator?

That'll be the next problem You must be in an earlier timezone from me...lol.

The loop that the release queue comes after never terminates because the boolean is set False. Works for me. After 3 secs I get a flash of the boolean.

Sorry. I've just shown the label and named it "boolean"

Use the "Strings[]" propety instead of the value. The value is the numeric index.

You need to give the value a name.

Looks like your doing it the hard way

I think the UDC2500 uses modbus. You will need a modbus RTU driver. I don't know if Honeywell supply one with their product for Labview, you might have to write it yourself using this http://hpsweb.honeyw...44/51522566.pdf Or if your really lucky, someone else may have written one you could use (try the instrument driver network).