Jump to content

Search the Community

Showing results for tags 'labview'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • OpenG
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 187 results

  1. I have a requirement that I thought would be SIMPLE, but can't get it to work. I have a 9205 card in a little 9174 cDAQ USB chassis. My *intended* behavior is to wait (block) at the DAQmx Trigger/Start Analog Edge on, say channel ai1, until I get a falling edge thru, say, -0.050V. So I have a little vi (that contains 2 parallel loops) that I want to sit & wait for the trigger to be satisifed. I'm doing "routine" voltage measurements in another AI loop on a different channel. I want this vi to run separately from my "routine" voltage measurements because I want the app to respond "instantly" to input voltage exceeding a limit to prevent expensive damage to load cells. I was afraid that if I used either Finite or Continuous sampling to "catch" an excessive voltage, I might miss it while I'm doing something else. Yes, yes, a cRIO real-time setup would be better for this, but this is a very cost-sensitive task... I just want to "Arm & Forget" this process until it gets triggered, whereupon it fires an event at me. SO... I'm also reading the same voltage on channel ai0 for regular-ole voltage measurements, and just jumpering them together. I did this because I read somewhere that you can't use the same channel for multiple DAQ tasks - I *thought* I would need to set up the tasks differently. {but now that think about it, the setups can be the same...}. I've set up the DAQmx task the same as shipping examples and lots of posts I've seen. I'm supplying a nice clean DC voltage to a 9205 card using a high quality HP variable power supply. Using NI-MAX, I've verified that my 9174 chassis & 9205 are working properly. THE PROBLEM - When I run it, the vi just sails right through to the end, with no error, and an empty data array out. No matter WHAT crazy voltage I give the "DAQmx Trigger.vi" (set up for Start Analog Edge), it never waits for the trigger to be satisfied, just breezes on through as if it weren't there. If I set the Sample Clock for "Finite Samples", the DAQmx Read fails with timeout - makes sense, since the trigger wasn't satisfied. What could I possibly be doing wrong with such a simple task??????? So my fundamental misunderstanding still vexes me - does the DAQmx Trigger vi not block and wait for the trigger condition to be satisfied, like the instructions state - "Configures the task to start acquiring or generating samples when an analog signal crosses the level you specify"? I stripped my requirement down to the bare essentials - see the 1st snippet, the 2nd is my actual vi. Any ideas, anybody?
  2. Can anyone please tell what a DVR [ Data value reference ] is ? I want to know at what situation it will be used and what are the advantages we get by using DVR. I am really confused in this topic . If someone has any code in which they have worked with DVRs. kindly share it to me. Thank you.
  3. Hi everyone, It's all said in the title. I wanna run a .bat file with Labview, i have used the system exec Vi but it didn't work. However when i run the script directly, it works. Can u help me with this issue Attached, my code thanks in advance
  4. Hi, I figured people here may be more interested in this project. I have some cool graph extensions I'm building in an open source project, which make some nice graphical overlays for XY graphs and waveform graphs in LabVIEW. I've got a github page where you can grab the code, support the project or just have a look at some of the same screenshots. Everything updates live in the graph, so you really need to see it, to get how it all works, so here you go: https://github.com/unipsycho/Graph-Extensions-LabVIEW Please star follow the project if you want to see this developed and I'd appreciate any feedback or ideas to extend it further. The markers are very much IN development right now, so no where near finished, but the tools can still be seen working. THANKS!
  5. View File 1-Wire.zip This tool-set gives access to all the 1-wire TMEX functionality. I was able to access 1-wire memory with this library. It has all the basic VI to allow communication with any 1-wire device on the market. It needs to be used in a project so the selection of the .dll 64 bit or 32 bit is done automatically. It works with the usb and the serial 1-wire adapter. Submitter Benoit Submitted 06/01/2018 Category Hardware LabVIEW Version  
  6. Circular Chart Base A flexible and easy way to create high quality circular charts with features such as anti-aliased and translucence, helps you to deal with the boring and time-consuming drawing details. http://sine.ni.com/nips/cds/view/p/lang/en/nid/217432 Features Chart Types : Supports multiple types of charts, e.g. , pie chart, doughnut chart, polar area chart, circular bar chart, circular slide, graduated gauge chart. Chart Elements : Multiple types of chart elements can be added to the chart, e.g. , legend, scale, grid, slider, digital, decoration. Slice Modes : Three modes for different overlapping and connecting relationships between slices. Customizable : Most properties of chart objects are customizable. Reusing & Sharing : Charts can export images for reporting, and their styles can also be saved as files for reusing and sharing. Quick-Start : Easy to use, and you can quick-start your development based on several build-in styles. How to Use Single Control : The Circular Chart Add-On is ultimately defined as a single control. Chart Styles : Being edited or loaded with different styles, the chart can be presented in the different types listed above, or even more. Style Designer : The chart style is configured by the Chart Style Designer dialog box, which can be displayed through the right-click menu of the chart, similar to the Properties dialog box of the LabVIEW controls. Auto Reload : After configured, the style can be saved into the chart instance in your VI and automatically reloaded the next time. Data Type : The data type of the chart is 2-D array of SGL numeric. Each row of the array corresponds to a slice in turn, and each column corresponds to a slice parameter you specify in the Chart Style Designer, the available slice parameters include start angle, end angle, inner radius, and outer radius. http://sine.ni.com/nips/cds/view/p/lang/en/nid/217432
  7. Join us at NIWeek 2019! Contributors of labviewwiki.org, (including future contributors), can add to their ribbon collection by finding an admin during NIWeek or at the LAVA BBQ! See you there!
  8. I'm trying to execute LPR.exe command to print some labels on a printer. However as its normal, problems occur. I could not find answer on any topic conneced with "sytem exec". I already tried all described methods (I think so). That's why I'm asking very kindly for any help. When trying to execute or call the LPR.exe from System exec VI, I'm receiving error: "'C:\Windows\System32\lpr.exe' is not recognized as an internal or external command, operable program or batch file." Generally I would like to call function: "lpr -S 192.168.1.5 -P lp C:\test\do_druku.txt" which works from command window without any problem. print.vi
  9. View File MCP2221A library There it is. The complete library for the MCP2221A. I2c adapter, I/O in a single IC. I love that one. Let me know if any bug is found. I try to make that library as much convenient as possible to use. Two version available 32 bit and 64 bit. little note: to open by serial number, the enumeration need to be activated on the device first. (open by index, enable the enumeration) It needs to be done only once in the life time of the device. PLEASE do not take ownership of this work since it is not yours. You have it for free, but the credit is still mine... I spent many hours of my life to make it works. Submitter Benoit Submitted 05/29/2018 Category *Uncertified* LabVIEW Version 2017 License Type BSD (Most common)  
  10. It's nothing to fancy. I added a few things to the UI to support more features and in preparation of adding the VI renamining/relinking step that was done seperately in the OpenG DEAB tool before calling the OpenG package builder. But I never got around to really add the deab part into the package builder. It's kind of extra difficult as the DEAB compononent doesn't currently support newer features like lvclass and lvlib at all and of course no mallable VIs etc. I can post what I have somewhere, but don't get to excited.
  11. 15. FIFTEEN. That's the number of current job postings in my group. We're hiring! This is the most fulfilling, challenging, and rewarding position I've held. Job specific requirements listed on the website. https://www.lockheedmartinjobs.com/search-jobs/Test%20Engineer/Grand%20Prairie%2C%20TX/694/1/4/6252001-4736286-4684904-4694482/32x74596/-96x99778/15/2
  12. View File GRBL 1.1 Hi everyone, Since GRBL standard is open source, I decided to post my Library that I used in LabVIEW to interface a standard GRBL version 1.1 controller. Not all GRBL function has been integrated, but this is a very good start. Enjoy and let me know your comments. Benoit Submitter Benoit Submitted 07/26/2018 Category Hardware LabVIEW Version  
  13. lEver wanted to communicate with VI which are across context boundaries? Those typical boundaries, are different LabVIEW project LabVIEW into LabVIEW EXE, EXE to EXE PC to PC across a network or even the internet Usually to get around these boundaries, we have to flatten to some easier transport mechanism like a string and then unflatten on the other end. There are a whole other host of situations and and reasons why cross context boundary communication is useful and not just a simple slam dunk using existing primitives in LabVIEW REx (Remote Export Framework) is a useful framework that you can take advantage of to eliminate the typical boundaries Instead of spend 45 minutes trying to describe it, see the linked videos below, (also in the PPT) until more written content gets made. Basic Demo - Current App http://screencast.com/t/JbW2mM3jx Creating & Using a New Command http://screencast.com/t/GhkE2CEx4Ip Send into EXE http://screencast.com/t/bxbI0B4l8Xs EXE to EXE http://screencast.com/t/xCJw2B39mFQr Debugging Ports / Services http://screencast.com/t/E0RXrgM3Yex Using Service Dump Info http://screencast.com/t/oTUSH5aFqo9S Network Communication http://screencast.com/t/KuTPTKA8rmC1 Rebuild of EXE (addendum) http://screencast.com/t/36oWmrybjRMj ******************* 1/12/15 Update: attached new VIPC which upgrades REx to 1.14.0.31 to address the issues w/ things not moving into the tools menu properly Remote Export – REx Framework.pptx REx Installation Full.vipc
  14. My project involves designing a front end for a synchronous generator using LabVIEW. It is actually data acquisition and display of signals in a file. The problem I face when building a program is that: 1)the sampling rate is set to 100 samples with 1 kHz sampling frequency.These signals are generated by daq assistant and i have used merge signals to merge these signals from daq assistant as well as signals from other radio buttons and Boolean as well. The problem is that when written on a file I am able to see only one instance of Boolean status for every 100 samples daq assistant creates. 2) now iam able to write only 0/1 as status of Boolean in the file.How will I write on /off into file?
  15. With exciting projects in oil and gas, aerospace, utilities, and other industries, Vertical AIT is looking to hire skilled LabVIEW developers and architects in the Houston area. We are an Alliance Partner, and we specialize in embedded development. Requirements: - US citizenship (required by our contracts) - Industry experience in production software development - Embedded cRIO development experience (Real-time and FPGA) - Certification (CLD, CLA, and/or CLED) preferred - Must be meticulous and detail-oriented We offer great benefits, and we prioritize a healthy work/life balance. Learn more about Vertical AIT at www.VerticalAIT.com, and please send resumes to jobs@verticalait.com.
  16. Hello, I'm trying to send data from my RPI b+ to labview and store the information in a spreadsheet, right now the data I'm using is just a sawtooth generated in the python code but eventually it will be sensor data adquired via spi, the data comes at =~ 6-7khz but the time it takes to send the data to labview is much greater, I fear the circular buffer I intended to use to store the data before sending it via tcp will get filled pretty fast. I'm not very experienced in either python nor Labview, I was wondering if i could get some advice in the optimization of the code. I attached the VI of the client and a VI that graphs the data on the spreadsheet, also the python code. Thanks in advance, sorry for the mess. Waveform Grapher.vi Client.vi serverSerial.py
  17. Version 1.0.0

    120 downloads

    There it is. The complete library for the MCP2221A. I2c adapter, I/O in a single IC. I love that one. Let me know if any bug is found. I try to make that library as much convenient as possible to use. Two version available 32 bit and 64 bit. little note: to open by serial number, the enumeration need to be activated on the device first. (open by index, enable the enumeration) It needs to be done only once in the life time of the device. PLEASE do not take ownership of this work since it is not yours. You have it for free, but the credit is still mine... I spent many hours of my life to make it works.
  18. hello there i'm stuck with my assignment. i have made a VI that generates random number and writes the data to CSV file I have added a timer stamp in the first column now i want to get the data for every 5 seconds using wait function how do i do it ? Thanks in advance 2d array random no v2.vi
  19. Hi All Apologies if this isn't the correct forum to post this on but I wanted to let the community know about a new LabVIEW podcast series I am running - The Quick Drop Podcast QDP LogoQDP is a community driven podcast that I want to use to talk about LabVIEW and engineering/Science in general via a medium that I don't think we currently make the most of. So far we have 2 episodes which are available on most podcast platforms (i'll link some below too): Ep 0.1 - Intro: A brief intro to me & rasons behind the podcast Ep 1.0 - NI Linux Real-Time Controllers with Neil Crossan: I am Joined by Neil Crossan, a Certified LabVIEW Architect, TestStand Developer & Certified Professional Instructor who works in ATE development. Neil shares his experiences with the cRIO platform & some headwinds he's had using the current platform as well as addressing some of the ways he's customised and optimised the NI Linux Real-Time OS. I am actively looking for more people to do episodes on, so if you have an idea please contact me: E-mail: info@tthequickdroppodcast.com Twitter: @quickdroppod Links: Apple Podcasts Spotify Anchor Stitcher Thanks! Jono J Hobson Certified LabVIEW Architect
  20. Manufacturing a satellite or a simple pen require to test the quality of the product before delivery to the customer. LabVIEW is widely used for that purpose. Since 20 years of LabVIEW development I saw numerous test framework. I was wondering if people where interested to work in a collective and open source test framework. Per example the following feature can be included: HAL (hardware abstraction layer) Database to record test results with the data viewer (PostgreSQL) single/asynchronous/batch/debug mode multi-language support Image analysis (open CV) + bar code reader User access level Remote monitoring Jig identification to prevent user error (testing the wrong product with the wrong jig/test sequence) HTML/xml/txt report and so on.... Benoit
  21. One of the main topics of the 2018 CLA Summit was the need to improve access to open source code in the LabVIEW community. This is something that I have tried to do in the past with limited success. After hearing what others are doing and discussing the issues, I am inspired to take on the task of getting as much of my code that is shareable out into the open for others to use, improve, learn from and critique. So, the point of this thread is to figure out how best to do that. I have tried posting code to forums in the past. I have even posted to the code repository here on LAVA. I have used code posted here and via the tools network and VIPM in my own projects. But I am not sure if any of those avenues are the right path forward for me. There was much discussion about different open source repositories on the interwebs that we could leverage. There was also some discussion about how to help others discover the code you shared. What I did not hear was any definitive conclusions on how best to do this. So, the point of this thread is to try to solicit feedback on code sharing and come to some sort of consensus on the best options out there. If you have an opinion on this please join the conversation and share what you think is the best solution. Here are some questions I am trying to answer: 1. Where should we share code? What system works best for LabVIEW code and is user friendly enough to not discourage people from using it? Please share links and how-to documents for your preferred site/system. 2. How should we license code? I heard some discussion about the various type of licenses. I am not interested in retaining any rights to code I share and do not want to put any burdens on those who want to use and learn from any code I share. What licence is accepted in the open source community that supports this kind of sharing? 3. Once we post, how do we make our code discoverable? Do we need to post links all over the place or is there a better way? Here is one attempt at making that better you should check out if you have not already: I am not just interested in putting the code out there, but also trying to explain why I think it is worth your time to take a look. I am willing to post on forums, create a blog, even produce some vlogs on YouTube if it is the best option. Please let me know what format would motivate you to take the time to learn about the open source code out there. Either way, thanks for taking the time to read this thread and contribute what you can, even if it is just to follow the discussion and learn from others like I am trying to do. -John
  22. Hello, everyone! I am studying a LabVIEW for my research. And I have a really curious question. Can I check my LabVIEW bit (ex 32bit or 64bit) through the code? I searched the property node and Invoke node to find the function which shows the LabVIEW bit. But I was not able to find it. If there is someone who knows the function, could you let me know about it? Or if I have to use the .dll to check LabVIEW bit on the code, could you announce me the .dll name? Thank you for spending your time for me !!!!
  23. Hello I am looking for a functional MQTT server client implementation for Labview. I have been doing some search, and found something, but they all seem to be unsupported. Does anyone have any pointers to a fully functional one? Is NI developing any stuff on this? Thanks Edited for correct content
  24. Benoit

    GRBL 1.1

    Version 1.0.0

    411 downloads

    Hi everyone, Since GRBL standard is open source, I decided to post my Library that I used in LabVIEW to interface a standard GRBL version 1.1 controller. Not all GRBL function has been integrated, but this is a very good start. Enjoy and let me know your comments. Benoit
  25. Started some work on a simple C code generator for LabVIEW. https://github.com/taylorh140/LabVIEWCGen I was working on some ideas to handle some more complex Items. Had some thought about using https://github.com/rxi/vec To handle strings and other arrays/vectors, I would like to pass these more complex data types by pointer. However I am looking for some ideas as to when to make a copy. I know LabVIEW has some internal item that manages this but I haven't found a way of accessing it quite yet. Let me know if you think this is worth some effort. Or if you have any ideas about the architecture that you think would be helpful. Also i imagine that this will still only ever support a small subset of LabVIEW, the languages are quite a bit different, and i prefer that the code be as clean as possible.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.