I have seen that link before posting the query. That property node will work only for 32-bit MS-Office.
Thanks,
S Nagaraju
↧
Re: Data formatting in Ms Word
↧
Re: Time record
Hi resgin,
store the current value of your"time record" in a file. Upon start of your program you just load the file...
↧
↧
Re: Creating .net assembly with malleable VIs
raceybe wrote:Experimentation has shown that if you create a .net assembly with a malleable vi, only the implemented solution is available in the resulting assembly. Can anyone confirm that this is the expected behavior?
The behavior I was hoping for from the resulting assembly was to have the resulting function support multiple data types (such as scalar and array).
I'm not surprised! Mallable VIs make their magic happen by basically recreating the VI on the fly according to the datatype wired to it. This is definitely an edit time feature. Once you hit the run button the whole code is recompiled into machine executable instructions according to the datatypes wired to the mallable VI at edit time. The same happens when you build an application, DLL or .Net assembly and accordingly only the code for the specific datatype at compile time is generated.
Someone would have to add support for generic datatypes to the .Net implemenation in LabVIEW, device a runtime rather than an edit time adaptive datatype too and make this all work together. Without knowing all the details of LabVIEW interna I still expect such a project to be a major investment that is unlikely to happen in the current LabVIEW version. It may be on the roadmap for NextGen LabVIEW (LabVIEW NXG) but that has to tackle a lot of other things first to be fully feature comparable to current Gen LabVIEW.
↧
Re: Creating .net assembly with malleable VIs
raceybe wrote:Experimentation has shown that if you create a .net assembly with a malleable vi, only the implemented solution is available in the resulting assembly. Can anyone confirm that this is the expected behavior?
The behavior I was hoping for from the resulting assembly was to have the resulting function support multiple data types (such as scalar and array).
I'm not surprised! Rather, I would be extremely surprised if it worked like you hoped for! Mallable VIs make their magic happen by basically recreating the VI on the fly according to the datatype wired to it. This is definitely an edit time feature. Once you hit the run button the whole code is recompiled into machine executable instructions according to the datatypes wired to the mallable VI at edit time. The same happens when you build an application, DLL or .Net assembly and accordingly only the code for the specific datatype at compile time is generated.
Someone would have to add support for generic datatypes to the .Net implemenation in LabVIEW, device a runtime rather than an edit time adaptive datatype too and make this all work together. Without knowing all the details of LabVIEW interna I still expect such a project to be a major investment that is unlikely to happen in the current LabVIEW version. It may be on the roadmap for NextGen LabVIEW (LabVIEW NXG) but that has to tackle a lot of other things first to be fully feature comparable to current Gen LabVIEW.
↧
Re: Labview with fuji PLC by modbus
Another good place to ask is Google -- typing "Siemens plc LabVIEW" gives quite a few suggestions. You are probably the best judge of which is the most useful ...
Bob Schor
↧
↧
Re: Data formatting in Ms Word
Sonti_11532 a écrit :And how to remove the empty lines in between table and picture??
Regards,
S Nagaraju
This is not something easy to do, is it that important to remove them?
To remove them you will have to get the Word._Document ActiveX reference to delete the last two empty paragraphs (carriage returns are delimiting paragraphs in Word) before adding the picture. Sounds easy to do but it's not, you need to be familiar with ActiveX and the Word object model.
Ben64
↧
Re: Fill data in multicolumn list box
Hi Gred,
Thanks for the input i was trying with insert into array instead replace array element.
I have worked out and attached the concept VI which is that am trying to accomplish for all my queries related to tab control and the MCLB. But which is not successful.
Main VI consist of Tab control and MCLB. The MCLB data will be updated in a sub VI with different loop functionality sequentially for various purpose which in turn continuously updated in the MCLB on the main VI through Global variable (which am not satisfied since I feel and based on NI recommendation (http://zone.ni.com/reference/en-XX/help/371361H-01/lvconcepts/using_local_and_global/) use of global variable will be inefficient with array and more memory wil be occupied. Kindly Comment on using global variable for this case or any alternate solution is recommended).
Note:At the same time in the main VI i need to see the current data which being updated on the subVI for the respective page. Also when i switch the page need to see the previously completed page data during that time the data fo the other page to be recorded in background and when the page is switched the data to be seen.
hope i have clearly told about my doubt
↧
Re: About calling dll
thanks a lot !
↧
Re: Fill data in multicolumn list box
This would be a great candidate for a class. The init stores the reference, and the methods update the control by that reference. You'll still need a shift register... Re-useability being the advantage.
↧
↧
Re: Image Acquisition and Line Profile
I've written two VIs that might work. The IMAQdx version will definitely work if you defined the ROI. I've modified a LL Grab example and used your ROI code to try and do this in IMAQ. As I have no IMAQ camera I can't test it, but it looks about right to me. The important factor in both examples is that the line profile VI is placed inside the while loop so that the profile is updated every time an image is acquired.
↧
Re: Question about the latency of high throughput function in LabVIEW FPGA.
I'd go for a predefined look up table or an approximation. Usually, a full out can be avoided, since there are symmetries, reducing the lut to 1/4 and some logic.
zyb1003 wrote:So is there anyway to make from 1-16 cycle, the setpoint use the first valid data, then on the 17th cycle use the second valid data?
You'll have to push the values on a fifo every 16th cycle, and do the calculation in a separate loop. The results need another fifo.
↧
Re: graph that outputs NaNs and 1s based on conditions
The loop in the bottom right makes no sense without 3 shift registers. As it is, each loop iteration modifies the original data, so only the last iteration is on the output of the loop.
If this needs to grow, you might consider cleaning up a bit.
↧
Re: graph that outputs NaNs and 1s based on conditions
The VI you have attached has very little resemblance to the code in the first picture. Please reduce the problem to a small simplified example that demonstrates what you want to do. Make sure it contains (or simulates) typical data.
Also, please don't over-customized the front panel appearance when you attach VIs. Things like disallowing resizing and hiding the scrollbars is not very nice to us, especially if the front panel has an odd size and objects are partially clipped. If you think you need these restrictions, they should be the very last thing before distribution.
↧
↧
Re: Temperature Control using labview
State machines are extremely useful, but may be an over-complication for a simple temperature threshold evaluation. Unless you are planning to add more complex functionality, something like this may work:
↧
Re: how to make a RESET button in labview ?
how to make a RESET button in labview ?
↧
Re: how to make a RESET button in labview ?
HARRY78 wrote:how to make a RESET button in labview ?
It does not make a lot of sense to add to an old thread and just repeat the subject line in the body of the post. (You did the same here). Since the question has been discussed in detail, please clarify what else you need.
↧
Re: Scripting: Set connector pane – error 1 if source terminals are connected
Thank you wiebe@CARYA,
SetConPane is available when property is selected for VI Property Node:
Connector Pane > Set
I do not know how should it be used correctly. It is interesting but not in my high priority list (thanks to your hints 
)
↧
↧
Re: Creating .net assembly with malleable VIs
Okay, I guess that wasn't clear to me that it was an edit or compile time behavior, but I guess it makes sense.
↧
Re: exe crashed with Exception code 0xC0000005
Posting the code for your executable would be more helpful than this error log. It only shows the same thing you have already described - the call stack ends at the internal save workbook VI (a wrapper around the COM Interop presumably). I don't see much else there of value unfortunately.
Maybe someone else who has had the same issue could provide more pointers.
↧
Re: Hiring Developers and Licensing
Dear rolfk
1. No i dont have any NI software licenses, and i dont intend to purchase them in the future.
2. It indeed would be wise to have the source code.
I am actually wanting the system wrote a tdms streaming from their pick ups continuously 24/7, without any specific case.
Besides, where should i find a proper developer able to perform this work?
↧
