viSci

I am using the ACBR and have noticed that if the UI thread of the parent vi is held up (like with a ring control showing its menu items)then the ABCR will not complete. I presume this is the result of the Set Control Value Method. Is there a way to decouple the threads to avoid this problem. Thanks, Mike Sachs

Hi Nipon, Thanks for the nice mp3 player, good example of clean LV coding style. BTW, pohm cow jai pasa thai nit noy kup. P.S. Carabao is a great group, I saw them 2 years ago at a outdoor restaurant courtyard in Chang Mai.

QUOTE(Aristos Queue @ May 2 2007, 08:28 PM) Ok AQ, thanks for pointing that out. As an aside to this topic I was wondering why the new queues and notifiers do not have an option to return the original reference, thus greatly simplifying things like the msgqueue libraries which internally have to keep track of which previous refnum's have been generated.

I was wondering if there is any plan to update the MsgQueue libraries so that they do not depend on the classic notifiers which one day may become deprecated.

I think we would have seen some pretty outrageous results if google adsense could parse media files for contents keywords? (They probably can already, but have not put it online yet.)

I had a similiar problem and constructed a mechansim using variant attributes to automatically convert cluster variables to named TDMS properties. Here is my example vi. Mike Sachs Intelligent Systems

I am posting a very basic remote debugger for the LuaVIEW scripting environment. I would like to hear some ideas on how to improve this so that it could be embedded in the LuaVIEW core.http://forums.lavag.org/index.php?act=attach&type=post&id=5399

I have some questions: 1. Can you have multiple instances running at the same time? 2. How do you call a LabVIEW vi from the script? Thanks

I just noticed that you can use the Scan from String vi to cast a string to an Enum. The vi will automatically adapt to the enum data type when the output is connected to a enum control. If connecting to a vi input that is an enum, you will need to have a local enum indicator to coerse the data type. Please excuse the post if this was obvious to everyone already.

I encountered the same problem on my machine (Dell Dell Dimension E510) and was not able to fix the problem despite trying for several days. I have never seen an error like this before and would like to know why the IVISION software is sensitive to the DEP mechanism.

The place to see this kind of cool interactive stuff (without the kids) is at: http://www.siggraph.org/s2007/ This year is going to be in San Diego, see you all there...

I also would put my hope in a 3rd party offering, but I would not so completely rule out an open source effort. Anyhow I think a dialog about what a 'OSTE' would be like might be fruitful in itself. I myself have puzzled over whether it would make sense to use an existing scripting engine like Lua or IronPython and add TE api features for managing test specifications, results and reporting as well as common UI components to support intelligent editing, vi template parameter generation, test sequence displays, report display, etc. I would also be interested to explore alternate scripting interfaces that present the user with clickable parameter selections as opposed to text editing. You could still write text based scripts but many use cases could be addressed with a simplified tree like script presentation.

Here is a little snipit from an old thread on LabVIEW sequencing mechanisms: crelf wrote: I know I'm chiming in late on this, but I can't agree more - I could sooooooooooo use something like this! I can't count how many times I've seen LabVIEW developers create their own "TestStand Lite" to do simple sequencing, only to fall on their faces when they need to do anything remotely complex or really reusable. I think that a real NI-produced "TestStand Lite" would be an excellent conduit to get current LabVIEW programmers into TestStand! :thumbup: Anyone from NI like to comment? Pleeeeeeeeeeeeeeease?!? My recent reply: Teststand Lite, that would be an excellent idea. It also makes me wonder what happened to the promising OSTE that was abandoned on SourceForge. I myself use a rewritten Table based version of the original NI Test Executive for basic sequencing and a 'Test Manager' API for managing excel based test specifications, results and report generation. I am looking into creating a new version that would have a better test sequencing API with extended features such as subtests, vi template based parameter editing, script variables and conditional looping. Personally I would rather just buy a 'TestStand Lite' if it was under $1000 with free run-times if using NI hardware.

Teststand Lite, that would be an excellent idea. It also makes me wonder what happened to the promising OSTE that was abandoned on SourceForge. I myself use a rewritten Table based version of the original NI Test Executive for basic sequencing and a 'Test Manager' API for managing excel based test specifications, results and report generation. I am looking into creating a new version that would have a better test sequencing API with extended features such as subtests, vi template based parameter editing, script variables and conditional looping. Personally I would rather just buy a 'TestStand Lite' if it was under $1000 with free run-times if using NI hardware.

I have a LV7.1 application that record ECG signals and produces a visual and auditory display of your heartbeat. I produce the heartbeat sound by playing 2 waveforms for the contraction and release sounds and these are sync'd to the ecg signal. In LV7.1 I can load and start one waveform and then at any point in time after (even if the waveform has not completed) I can load and play the release sound. In LV8.2 the sound vi's have changed and there is no longer a separate waveform load capability. It appears that you must do a simultaneous load and play and it is not tolerant of buffer overwriting, in other words the first buffer must complete before you can write again. The only way I can release the buffer is to do a 'Sound Output Clear' which then requires a Sound Output Config to start things up again. I think it would make more sense if you could just do a Sound Output Stop and then a rewrite.

I have been using the tdms excel plugin and it works well. I was wondering if anyone has constructed a vi that does this same conversion.

I am finding that none of the proposed methods will work in my case. The screen saver in question is apparently network administered and designed not to be foiled. It's purpose is to force a login prompt if the computer is not used for 1800 seconds. The screen saver settings appear to be locked. I have even tried some registry hacks but they do not stick. I had assume there would be some way to fake user activity but ordinary mouse and keyboard events do not work.

Hello all, I would like to have my application generate some sort of windows event that will stop the screensaver from starting up. I have tried generating mouse movements but this does not seems to work. Any ideas?

I have been using LuaVIEW for over a year and it has worked very well for me. I can control all the resources in a PXI chassis (single point and HW timed analog input, AO, DIO, counter PWM) also VISA based instruments such as balance scales, humidity sensors, fluid baths. I have a prototype dialysis machine completely running under LuaVIEW control. All you really need to understand is how to define a LuaVIEW callable LV vi. There is very good documentation on the subject. I am attaching a couple of examples for you to look at. Good Luck! Mike Sachs Intelligent Systems Download File:post-162-1158323291.vi Download File:post-162-1158323357.vi

It seems like a writable simulated resource should be pretty easy to program. You could generalize things by having the resource read from an array of data that is stored in max, similar to scale tables. MAX already provides an interface for creating new scales so it is not outside the scope of what is already there. You would simple select the data source for the simulated resource to be either the default sine wave or an external table.

I do not think this is currently possible but I have a good use case for it. VI Logger lite is a free program from NI that is a fairly good general purpose data logger, except that it can only log analog input channels. It has a API that can be programmatically controlled from labview to start, stop, enable logging, read data, etc. Although all channels must be analog, they can also be simulated channels. If you could setup a writable simulated channel then it would be easy to merge other asynchronous data such as RS232 based instruments, state info, etc. into the HW timed data stream. Any thoughts on the subject?

Greetings All, I am hoping to generate some discussion on the relative merits of these 2 scripting interfaces. I am currently using LuaVIEW and have had some good success with it to model pumping mechanisms for a medical device. I am somewhat concerned about the use of a proprietary CIN and some undocumented vi server methods (set/get tag) that LuaVIEW depends on, since we would like to settle on a tool that we will be able to standardize on for the long term use within our R&D. I am also concerned about the scalability from the simple uses I am doing now to much larger prototyping of complete medical devices that would involve the deployment of a large hierarchy of script modules. Mike Sachs Intelligent Systems

What is wrong with using Datasocket for OPC? I use it all the time and it works great.

I would like to collect some examples of Labview front ends for either scripting language. I would like to develop an interactive scriping vi that would allow me to load new scripts into a table or tree display and see a highlighted execution. (Hey maybe even breakpoints too.) I tried this a few months ago with LabPython and came close but could never get it to work correctly.

I am interested to find out how others are using scripting languages such as Python (LabPython), Lua (LuaView) etc. for applications involving multi-head testing and instrument control. I am particularly interested in hybrid approaches where a script can be invoked by a labview application and that script can also invoke test functions or instrument control vi's. Also where a main vi might have a state machine that is being sequenced by script commands via tcpip messaging. I am very interested in learning from others who have been using LabPython. One area of interest is how to expand the existing LabPython model so that it will work with multiple script threads. I imagine it would be possible for each Labview client to implant an identifier in the server script thread so that the tcpip port or messages could be unique. That way there would not be a fixed port for LabPython.