labview

I would like to know what is the content of a tdms file, which is produced by Labview. Following this site , I write in Python: import numpy as np from nptdms import TdmsFile from nptdms import tdms #read a tdms file filenameS = "RESULTS.tdms" tdms_file = TdmsFile(filenameS) tdmsinfo [--properties] tdms_file I receive the following error: tdmsinfo [--properties] tdms_file ^ SyntaxError: invalid syntax I do not how to fix it. Thank you for your help :) What you are looking for is: First create a TMDS objet from file: tdms_file = TdmsFile("C:\\Users\\XXXX\\Desktop\\xx Python\\XXXX.tdms") then

Our project is LIDAR which is based on physics. The total equipment is connected to server which consists of various sensors. Server gives total information about the equipment like temperature, humidity etc. Server and laptop are connected through LAN. Our work is to develop a software using labview which interfaces the equipment with the laptop. To achieve that first we have to connect the server to the laptop. We have tried in so many ways using TCP/IP vi in labview. Both server and client programs are required to do this. In the server program we are using TCP Listen and in the client

I wrote a rather complicated piece of code in Labview (with many loops and other sequences). Therefore I want to create many subVIs to make my code more clear. When I have a loop in the code I want to have in a subVI, the icon of the newly created subVI appears far away form my original piece of code, causing my Block Diagram to expand. Why does it happen and how can I avoid it? The piece of code I want to turn into a subVI: The same fragment of my Block Diagram after I created the subVI: And here is my newly created subVI - approximately 1 m to the right at 1 m down in comparison with the

I'm just getting started on developing in LabView, it's all new to me. And i'd like to use git extensions to handle my versioning. Since the source is in a *.vi format, I can't use the normal diff tools, the source is binary. Fortunately, LabView comes with dedicated diff and merge tools which seems to be very helpful. And I can setup TortoiseGit to use these tools on all *.vi files. It's from this how-to: https://www.labviewhacker.com/doku.php?id=learn:software:github:getting_started Is there a way to do the same in Git Extensions? I much prefer git extensions over TortoiseGit.. So I'd rather

I am developing a data acquisition program in Labview that uses multiple translation stages, cameras, a high speed digitizer, and other instrumentation. I'm developing the application on one computer, and will be deploying it to another computer. The development computer has labview 2013, and computer the application will be deployed on currently has Labview 2012, but we will be upgrading it to Labview 2013 when we move the application over there. Some of the drivers need different versions of the driver to function under Labview 2012 than they do for Labview 2013. I'm trying to keep all of

I have a data acquisition program written in C++ (Visual Studio 6.0). Some clients would like to control the software from their own custom software or LabView. I would like to come up with a simple API with a dll I can distribute to them and would like some tips on how to get started. This is going to be VERY basic, maybe 4 or 5 commands. My DAQ program will still be running in its own window on the same machine, I would just like to set it up to be controlled from another program. You are on the right track with a DLL. The real trick, it sounds like, will be deciding what sort of inter

I have written a standalone app that controls a device through RS-232 port and some customers want to be able to use the device with LabVIEW. I have seen some threads describing where to start when learning to use LabVIEW, but I was wondering if anyone has experience with writing a plugin/driver (is that the right word?) for LabVIEW and perhaps point me in the right direction. The existing app is GUI that allows people to control the device with higher level concepts - rather than have to know the syntax and protocol of the serial port comms stuff. I want to abstract that away as well so that