viSci

More info on the subject... http://zone.ni.com/reference/en-XX/help/370051P-01/cvi/libref/cvicnvcreatesubscriber/

Amazing NI is still trying so hard to sell the DSC. From what I can tell NSV events are possible in CVI without the DSC. Here is an old thread that ends in some CVI code that show how to register NSV change callbacks. Now all you have to figure out it how to trigger LV user events from CVI, which I believe is possible. http://forums.ni.com/t5/LabWindows-CVI/NSV-Async-Read-Callbacks/td-p/1329994

You might also try the AIT Stimulizer software to see if you can talk to the board.

I found that sometimes the AIT 1553 boards do not play well with other 1553 boards...

Here is a pi in the sky question... Will there be any support for acquiring images over the MIPI interface?

Quite a few years in the making..many thanks for your dedication! I especially like the new script event feature with line number status.

Thanks for the replies. I went with a tool called FireDaemon, it is low cost $50 and works very well! Of course I also refashioned my app to remove any nasty popup's or dialogs that could occur. I also added a command line interface and a comprehensive log file which was essential to debug various issues with my new LV service.

Nice, thanks! I think this would be a good starting point. Perhaps add auto ref level based on the measured amplitude and offset. Also could add interpolated indexes since there is a small error between the thresholded index and the actual fractional index that would correspond to the precise point where the signal crossings occur.

Does anyone remember if there was an older version of this vi written in pure G? I would like to have a version that I can modify to return all pulse measurements in a waveform instead of just the one specified. It seems like much of the work in finding one pulse could be applied for finding all pulses. My interest comes from a requirement for real-time processing of a 32 channel AI at 100kHz with each ch containing ~ 500 pulses/s. The current Pulse Measurement vi is about 10x too slow to keep up. I am on my way to creating my own from scratch but still would be useful to have on hand for comparison.

Just curious to know if any capability has been added to allow Lua to call multiple LV vi's within a single script. Also is it possible from within LV to single step a Lua script?

Greetings all - I have a LabVIEW 2014 executable that I am trying to put into a form that can be run as or from a Windows Service. Of course I removed all possible dialog windows and any need for UI interaction. I did my testing using a program called FireDaemon which can wrap any window exe as a Windows Service. I found that I could not get it working until I included the NI Authentication Service (NIAuth) as a dependency within FireDaemon. If I do not do this my application (which does not use any web services as far as I know) just hangs when the Windows Service activates. Does anyone have a clue about this? I would like to create a version of my app that does not require this dependency.

Just wondering if anyone has had any luck using the vision toolkit to decode the ubiquitous IMB barcode that is virtually on all USPS letters. As of LV2014 it does not appear to be built-in to the barcode vi's. I have found some third party .net toolkits that work well but are costly. Here is one that works particularly well... http://online-barcode-reader.inliteresearch.com/

Thanks folks, it does look like Gige is workable. The next issue is streaming to disk. I have tested out the IMAQ AVI vi's and they work nicely but performance is highly dependent on the codec selected. So far it looks like the FF Video Codec 1, a mpeg derivative, is working well. It allows me to achieve a 30 fps rate with 640x480 B&W frames and has impressive compression. I will have to do more testing at my target resolution of 1024 x 768 and may need to further optimize my codec or try out a straight binary file instead of avi.

Just curious about the Gige interface. I have a Bassler 2048 pixel Line scan camera running at 48kHz. That's something like a 2048x4096 image @ 10Hz. Is that doable with the PCIe framegrabber? Do you guys have any other benchmarks?

I was wondering if anyone knew how this tool works its magic. I would like to investigate if it may be possible to modify the tool to work with WADL web services rather than the older WSDL Soap Services currently implemented. I looked around and could not find any NI vi's associated with this tool.

Curious to know if anyone has created a way for LabVIEW or TestStand to interact with a Instrumented Android APK file or 'App'. The Standard Android Development environment includes tools like Robotium or Monkeyrunner which are great if you are using Java or Python. In my case we already have LabVIEW in place for testing the embedded HW and subsystems but would like automated Android UI interaction as well.

One thing that I found to be very helpful is a little utility call Process Tamer. It does just what it says and immediately slowed down annoying windows background tasks. I was going to revert back to Windows 7 but now everything is just groovy!

I took the plunge myself and was wondering how others are fairing on Windows10. Most of the issues I encountered have to do with default settings in W10 that allow background processes (like anti-malware) to just pop into memory at any time and suck the cpu dry. I spent a whole day disabling and tweaking things to prevent thoughtless cpu hogging.

In this case would the read variable with timeout help? Or should the warning be to always try opening the connection first?

For all of us who could not make it this year...thank you, thank you, thank you!

Ok, answered my own question. It does work if I use a classic simple numeric instead of a system numeric and set the foreground color to transparent.

I have hear of the zero pixel cluster boarder but could not find something similar for an array. My objective is to build a numeric table-like array. So far the best I can do is:

Go to the PID Tank Simulation example as a good starting point.

Yes that is the way it works in DAQmx. It makes sense that the task would start directly and then the acquiring of data into the buffer is inhibited until the trigger occurs. I believe you can check the state of a task to determine if it is still waiting for a trigger or not.

Sounds like a database application. You could develop in Microsoft Access and then wrap your stored procedures in LabVIEW. There are some good examples in the Database toolkit for that.