hooovahh

I don't have those versions installed anymore but you may find more help over on the Version Conversion subforum. http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion

Yeah use the Elapsed Timer express VI and set it to the time you want. The output is "Time Has Elapsed" Then you can use that in a case structure and only do the work when that time is up.

So no one has ever told me this, but from what I've seen child references won't be closed using a close reference, if a parent is forcing them to stay open. Make a new VI, drop down a control of any kind. Right click and create a static reference to that control. Use the Close Reference on that reference, then use a property node to read the label text of the control, passing the error out of the Close Reference into the error in of the property node. Now run the VI. The label is still returned, and the reference is still valid even through you asked to close it. This is because even though you asked to close the reference, it needed to be open because the VI that uses it is still in memory. Reading the detailed help on the close reference function has more information on this. This might also be compounded by the fact that I think this is an example of a "This" reference. So closing the control reference in my mind does nothing, unless you explicitly opened the reference using the Open VI Object Reference. So if you opened a reference to a VI, then used a property node to return the control references on the front panel. Then it is my understanding that you don't need to close the control references, when you are done. All you need to do is ensure the VI reference you opened gets closed. As a fun test I'll usually write a simple VI that does my work and closes the things I think it needs to close, then use the Run Continuous button and look at the task manager and see if memory increases. This is the only time I find myself using this button.

Well I know nothing about EtherCAT but I have some links that you've probably already found. http://www.ni.com/white-paper/7299/en/ http://www.ni.com/white-paper/14140/en/ 80 views isn't that much, there are many lurkers. And there are people like me that opened it up to see if it was something I could help with, then I closed it because I couldn't. Oh an there are some that just read every post so that it is easier to find the unread posts.

What IDs are you reading, what IDs are you missing? You didn't post any code, but even if you did I might recommend contacting Stratom. They likely have an example that is made to just read all data and display it. Is is possible the device is setup to only read standard CAN messages and is missing extended ones?

Sure but a crosspost helps give some context to those unfamiliar with the history of the issue.

Well what toolkits do you have installed? I've never heard of such a screen before, but I'd suggest finding that toolkit and re-installing it, either through VIPM or NI Uninstaller depending on where it came from. You might also get away with forcing a mass compile on the toolkit, again if you can figure out what one it is.

Crosspost

Well they aren't the same, or made by the same company. There are likely features available in one and not the other, and you likely paid for any support you needed. That being said I'm super impressed with the Exaprom one and wouldn't mind paying (a reasonable) fee if I needed it.

Be sure and share it with the community, others may have similar questions.

Michael worked his magic, that he does so well and things should work now. I tested it on a pretty large block diagram and my browser zoomed out, but the image itself wasn't scaled on the server side, so I could still drag the snippet away and then into my blank block diagram.

I think I reproduced the steps you took, but I came to a different result. I posted a reply using the More Reply Options which is also known as the full editor. From there I picked the file by clicking on Choose File. Then I clicked Attach This File. This step might not be needed depending on the version of the uploader that you are using. Then I clicked Add to Post to add it to my reply. I was then able to click the image and get the VI source by dragging the image to my desktop. I wonder if it has to do with the size of the PNG you uploaded. It obviously scaled it which makes me think there is a maximum resolution the uploader accepts. EDIT: Yup just tested it, too large of an image is scaled, I'll let Michael know about his and see if there is something that can be done.

It sounds like you are using the wrong kind of reentrant VI. The NI signal processing VIs uses the Preallocate method of reentrancy which is less efficient than shared clones because a new copy must be created for each copy, instead of reusing already made copies. The benefit is of course things like uninitialized shift registers work as expected because each copy is reserved for that call.

Recently the PDF creating toolkit using ItextSharp by Exaprom has been updated to version 2.0. https://decibel.ni.com/content/docs/DOC-10952 The toolkit is very well put together and I've used it on a couple projects. The example generates the manual for the toolkit, and it is pretty impressive to see all the features of the toolkit demonstrated, by generating the user manual.

So you have a 2D array of numbers, and you want to find the perimeter around an object outlined by values of 1? There are probably tons of ways to achieve this. Look on the array palette and see what you can come up with. I'd suggest reshaping the array into a 1D, and use the search 1D array looking for 1, then that used with the quotient and remainder can give you the upper left edge. Similar functions where reversing the 1D array could get the lower right edge. If you get stuck post what code you've come up with.

Hey that's pretty neat. It remind me of one of my favorite XControls the Variant Probe, where a variant can be displayed in a colored tree.

In many cases a private method was made public, so there is no reason to password protect a VI. But in some cases these methods have new inputs or outputs between versions, so back saving would break the code. You'll then need private methods enabled so you can pick the older version if this is the case. If we just made all private methods public it would take care of this problem...and create many more.

Then using a DAQ card is going to be a problem. If you install DAQmx you're going to be required to install MAX. Then you can import your MAX NCE and use the tasks and channels in MAX, or use DAQmx VIs to programatically make your tasks at run time. Oh or the third option I don't usually do is you can have the tasks be in the project which then get deployed to the EXE when it is built. If you are really insisting on using LabVIEW 7.1, which is something like 11 years old then I'm unsure how much of what I said is going to be true for you.

I understand where you are coming from, but even when I was in that type of industry, explaining that things get done faster, and cheaper when trusted toolkits are used instead of reinventing the wheel, usually persuades the customer. It sounds like you are in a culture that doesn't use OpenG and it would be difficult to bring that in. I'm in a culture where using OpenG is expected, so taking that away would be difficult. Our applications are dependent on it, and so we always trying to make using and installing it as easy as possible. Same with other trusted toolkits like JKI, WireFlow, MGI, and others from LAVA. Again IANAL but I don't know if attributing OpenG as a consortium meets the needs or not. For now I think that is what I will try doing, but in the back of my mind I'd like to scan installed packages, and generate a license text file.

I am not a lawyer (IANAL), but I was using the following definition for Credit Publicly acknowledge someone as a participant in the production of (something published or broadcast). If we are trying to disclaim liability, I'd suspect leaving someones name off of a list of developers who influence the creation of the product would be what is desired. If that is the purpose couldn't I just say any code developed by someone other than me, used in this product are not responsible. Same here actually for some of my Code Repository stuff on LAVA.

Probably this. You'll probably need to use some kind of system function to get the origin path of the junction point, and then get the free space on that path.

While I think this is the easiest solution, and probably something similar that I'll adopt, what if you only used on subVI made by one guy in your build? You are crediting a few dozen people when really it should be one guy. Could I take this to the extreme and credit every human on the planet, and then never need to worry about forgetting to credit someone?

Okay attached is a VI that can be used to parse the arguments into multiple arguments. By default the delimiter is && but another one can be provided. Saved in 2013. Parse Multiple Arguments.vi

Whatever I guess, I just assumed that you'd continue to use the JKI delimiter of >> Something like: Enable Control >> Save Button >> Exit Button Where this case "Enable Control" could enable a set of controls, but I suppose && could be used just as long as it is clear that is how this N arguments works.

Feedback on the JKI State Machine would probably be better heard on the JKI forum. As for your comments 1. I think the "Default" case could be made to exit. The only time you should see that error is during initial development, when you try to go to a case that you haven't written yet. In this case going to exit is not a bad thing because I'm going to want to stop my software anyway to fix the typo or write the case that I meant to have. 2. The JKI State Machine already has several sections, for Core, Data, Macro, UI, and even has a template category. I've seen some others add a "Decision" category and try to limit decision making to go in those types of cases. After re-reading your comment I see you are talking about cases in cases. I think this could get confusing. But honestly I have done it in the past for a group of cases that are similar like "Defer Panel" and "Undefer Panel" but really arguments could be used here.. 3. This is probably a good idea, but I'd argue that the majority of the time a case has no arguments, let alone N arguments. The extra overhead of using something like Spreadsheet String to Array on every call of Parse States seems unnecessary. I'd recommend making a subVI that just takes the scalar string of arguments, then uses Spreadsheet String to Array with the delimeter being ">>" then return the array with white space removed. Then you can call this VI in the cases where you know you entered more than one argument.