Similar Questions

• TestStand do not call a Labview DLL copied to a new location.

  TestStand v4.2 & v8.6.1 LabVIEW: I have a problem with TestStand calling a Labview project DLL. It will call the DLL successfully if it points its record source (the directory where the DLL was built. However if the DLL is copied to the clients working directory and the appellant TestStand step points to the copied DLL, the problem occurs. The TestStand calls the DLL from the working directory of the client, but does not execute the DLL, simply set the status of the step to "Done" where he clearly didn't.

  The vi named in the DLL has correctly, all handles error clusters such that if there is an error in the vi running, the error would be forwarded to TestStand.

  Any ideas please?

  Update: the original problem was never solved, but another method was used successfully to generate an Excel results worksheet. This used controls Active-X to open a file, import a model, write the data, close the file, and then make the new file read-only. It now everything works fine.

• TestStand 2014 freezes when I select a path from the project during an Action LabVIEW using LabVIEW TERM 2014

  In the company that I work, we have a solution that uses the two TestStand 2014 and 2014 LabVIEW.

  We work with the development version of the two, but we are deploying our automation using TestStand and Labview Runtime engine 2014.

  We tried to deploy a new station, but during the analysis of our project, the User Interface for Teststand (version Deploy) froze.

  I tried several things and decided to install a full version of TestStand 2014 and 2014 LabVIEW to try to debug the problem.

  What I've discovered is that when I create a new sequence in TestStand, add a VI Action and try to load the path to the project, the TestStand freezes if I use the adapter Runtime.

  If I go to the LabVIEW development system adapter in TestStand, it works. However, I need to use the Runtime since it's free while the LabVIEW Development is paid.

  We already use our solution in other places, and this is the first time, it never happened. The only post I found online that had something to do with this issue is this.

  If I remove the path of the project and call the VI himself, as "dvu", said in his second post, it works.

  However, it is something not good to do in our automation together, since we have several calls from LabVIEW.

  Any ideas on how to do this only works with 2014 DURATION and 2014 Runtime LabVIEW TestStand?

  Thank you!

  Thanks a lot Stop_Luke_and_Listen, but the guy where the deployment was made called the support NEITHER and they couldn't find the problem, so they formatted the PC.

  Now it works very well, so I won't be able to generate the report. It would have been a great idea.

  Thank you!

  SOLUTION: Format the PC and reinstall.

• TestStand deployment error Code 1055 when using LabVIEW storage VIs

  After a few days of playing with TestStand deployment. I have final stalked the VI which was the origin of this error.

  He was using the LabVIEW storage screw to save data in a TDM file.

  My work around at the moment is to use a Wrapper VI and call this VI by reference.

  In this way the deployment TestStand cannot detect the Sie of storage.

  I'm using LabVIEW 8.6.1 and TestStand 4.1.1 does anyone know if this issue was address TestStand 4.2?

  It seems that the upgrade can be worth it.

  Simon,

  After investigating the matter further, I found that we had already encountered this bug. It has been fixed in 4.2 TestStand and LabVIEW 2009 I tested your files with 4.2 TestStand, LabVIEW 2009 and everything built successfully without any hiccups on the way.

• From the telnet session between calls of LabVIEW, TestStand

  TestStand, I'll call telnet.llb VI.

  In a step TestStand am opening a telnet session to IP address and the collection of the telnet (U32) connection. In the next step of TestStand, I pass the telnet connection to a telnet writing VI, but this error occurs.

  "Dequeue item to acquire Semaphore.vi:1-> Write.vi:1-> Telnet Write.vi.ProxyCaller Telnet"

  The telnet open, write, read and close the excellent work if I get the number of telnet in the same VI session. But I need to keep the session open between TestStand calls because a huge VI is not possible.

  Thank you

  Josh

  Verify that your adapter for LabVIEW has reserved the execution. If it is already, I don't know, you may need to create a parallel thread that keeps the session active.

  CC

• Call a visual basic executable file with arguments command line using LABView

  Hi all

  I try to call a visual basic executable file with a command line using LABView 2014 argument. What I'm trying to accomplish executes an executable file that communicates with a device via a COM port. So, I would open the .exe with a command line argument to communicate via com 3 using the SYSTEM Exec VI. It seems that the command prompt window flashes and closes and then nothing happens. Not a lot of discussions about this on the forum. Any help would be greatly appreciated. Thank you.

  With some programs, instead of passing in the string:

  Somefile.exe

  Instead, you can use:

  cmd /c "C:\Full Path\to the EXE\Somefile.exe"

  Can you tell us what exactly you are trying to run?

• Retrieve the names of the measures of the stage using LabVIEW

  How retrieve you the names of the measures a digital multiple of the step using LabVIEW?

  I have built a vi to be called TestStand and will pass the "ThisContext', but the vi is not complie.  That's how far I got.  The vi is attached.  The error message is:

  "The method selected in the invoke node is invalid or no method has been chosen.  Click on the invoke node and select a method. »

  My vi is an attempt to write the code of

  Normal
  0

  fake
  fake
  fake

  MicrosoftInternetExplorer4

  / * Style definitions * /.
  table. MsoNormalTable
  {mso-style-name: "Table Normal";}
  MSO-knew-rowband-size: 0;
  MSO-knew-colband-size: 0;
  MSO-style - noshow:yes;
  "mso-style-parent:" ";" "
  MSO-padding-alt: 0 to 5.4pt 0 to 5.4pt;
  MSO-para-margin: 0;
  MSO-para-margin-bottom: .0001pt;
  MSO-pagination: widow-orphan;
  do-size: 10.0pt;
  do-family: "Times New Roman";
  MSO-ansi-language: #0400;
  mso-fareast-language: #0400;
  mso-bidi-language: #0400 ;}

  message.ID = 10653 in LabVIEW.  More precisely:

  Normal
  0

  fake
  fake
  fake

  MicrosoftInternetExplorer4

  / * Style definitions * /.
  table. MsoNormalTable
  {mso-style-name: "Table Normal";}
  MSO-knew-rowband-size: 0;
  MSO-knew-colband-size: 0;
  MSO-style - noshow:yes;
  "mso-style-parent:" ";" "
  MSO-padding-alt: 0 to 5.4pt 0 to 5.4pt;
  MSO-para-margin: 0;
  MSO-para-margin-bottom: .0001pt;
  MSO-pagination: widow-orphan;
  do-size: 10.0pt;
  do-family: "Times New Roman";
  MSO-ansi-language: #0400;
  mso-fareast-language: #0400;
  mso-bidi-language: #0400 ;}

  Dim MyStep ACE [step]
  Dim MyMeasurement As PropertyObject

  MyStep =
  seqContext.AsPropertyObject.GetPropertyObject ("Step", 0)
  MyMeasurement =
  MyStep.AsPropertyObject.GetPropertyObject ("Result.Measurement [0]", 0 ")

  MsgBox (MyMeasurement.Name)

  Can someone help me complete the vi?

  Thank you

  Thank you very much.

  A small change to the vi required.

• How to check if the exe called by labview does not respond?

  Hi all

  Here's the situation:

  I have a main executable VI which calls on several other screws which are all in the form of exe.  Sometimes, when these other .exe are called, they open reduced as they are supposed to, but they begin the desired process because they become inadmissible.

  Basically, I wonder if there is a way to check if a window responds or not.  I'm using LabVIEW 2010 on a computer with Windows 7.  All the subVIs called by this VI have this problem but to different degrees.

  I thought that I might be able to do this through a reference application and research somehow the title of the window for "(ne répond pas) ', but I have not found a way to implement it."

  Thank you

  M

  I sometimes use a library of 3rd party called AutoIT to do things like move windows and check names, window titles.  Related download installs an ActiveX control that allows you to do.

  See here for a list of the supported control functions.  Look at the end (all functions starting with "Win").

• Programmatically insert step of ActiveX/COM using LabVIEW

  Hello

  I would like to be able to create sequences like the one set using LabVIEW.

  This sequence has only 2 steps, a LabVIEW VI call and an adapter of ActiveX/COM call.

  I was able to do using an adaptation of the code here: https://decibel.ni.com/content/docs/DOC-36337

  However, I am struggling to add the step of the ActiveX/COM.

  Any help would be welcome.

  Thank you

  Of course, there is a way, if you look for it

  Since you have an existing 'Step' class object, you can also get a 'Module' object for her. Subsequently, you will need to specify that it is an ActiveX module. If you do not know which - probably you need to get the object 'map' somehow... Our case is simpler, so just cast to the ActiveX module and... to set certain properties like ServerId, ActiveXReferenceExpr and so on.

  I've attached an example for you. Interesting thing is the ServerId - I just read this chain of the TS for similar action and reused it here so do not ask me how to get automatically

  You will need to complete your 'properties' as 'file' - but I'll gracefully leave this work for you =.

  Best regards

• How to view mdsplus data using labview

  I posted this question in the Council of Labview, but seems that nobody does it so far. I don't know what is the best place to ask this question. So I reposted here.  Thank you very much.

  I am a newbie to Labview. I'm writing a few vi to display and write data to Mdsplus.  I downloaded Mdsplus(labview) can discover Mdsplus functions, like mdsconnect, mdsput, ect, in vi to call a library function. But I have no ideal how to use it. I tried to use the Mdsconnect function to connect to a machine, but it still gives me an error like: Labview: an exception occurred in the external code that is called by a call library function node...  I was looking for help on the internet documents, but could not find anything useful. Could you please help me with this problem?  If you have examples of these vi, or teach me how it, it would be very useful. I'm using Labview 8 (windows). I would appreciate your help!  Looking forward for your reply.

  Oops,

  I attached properly in the previous post.

  Greg

• How to program using Labview to an accelerometer

  Hello:

  I got an accelerometer which has digital I2C/SPI serial interface, so I bought a USB - I2C converter for data acquisition. I would like to know if I can use Labview to acquire data of com port and also program for the accelerometer to capture the data of the axis z. I have a box of white myDAQ NOR but SB. says that it is not an appropriate device to acquire before I2C/SPI signals. The datasheet of the accelerometer is in the accessory and the specification of the converter is this link: http://www.robot-electronics.co.uk/htm/usb_iss_tech.htm .

  I hope someone can solve the problem for me. It is best to use the software labview for me because most of my project work is based on that.

  Best regards

  The f

  Good and bad news.  You have an accelerometer that 'speaks' I2C or USB to I2C converter, so if you connect both of them, you can send 'orders' of your accelerometer easily of LabVIEW by using communication series live that's the good news.  The bad news is that it seems that you need to address your accelerometer using calls very low level, a work, I certainly don't want to face!  This crys on a 'pilot', a middle piece of equipment that does all the "hard work" to take a high level order ("Please tell me the acceleration") and he translates things your device includes (including the Setup program, records, calendar, packing and unpacking of the bits and bytes, etc.).

  Bob Schor

• Deal with failure when using LabVIEW 2011 and DSC MODBUS communication

  I'm currently reading from operating records a PLC with MODBUS/TCP. I confirmed that the PLC will update the values and in response to a MODBUS communication correctly by using a third-party program called Modbus Poll. However, when I try to query the PLC using the LabVIEW shared variable engine, I am unable to read the values of the same addresses that I consult with Modbus Poll.

  My installation is simply to a PC directly connected to the controller via Ethernet without a router between the two. I'm using LabVIEW 2011 SP1 with the DSC module.

  I opened the Manager of distributed systems OR to display the State of all variables in the Modbus Library that I created, and I noticed that the ILO CommFail permanently the value 'true '. All other variables with a 'read' access mode signal "failure of process". I tried to restart the process and stop and start the local variable engine without success. I also restarted my computer several times to see if any services did not exist, but this does not appear to have solved the problem.

  Finally, I resorted to listening to communications on the network card I have the PLC connected via Ethernet using Wireshark and found that while Modbus Poll communicates with PLC, number of MODBUS and TCP packet is sent and received. However, when using only LabVIEW or the DSM OR communicate with the controller, there don't seem to be any communication on the network card.

  Something that may be interesting to note is that I could communicate with the PLC and to read values with the DSM just once, when I understood everything first what address I should be reading of. All of this has stopped working shortly after. Prior to this, 'CommFail' was not generally set to 'true' with my current setup. Thinking it was my firewall, I have since disabled my firewall, but this seems to have had no effect on the problem either.

  Any help on this would be appreciated.

  So, I thought about it. It turns out that the IP address of the server i/o MODBUS must be set to the address of the MODBUS slave, not the local computer. The address of the i/o MODBUS server is defined by the navigation in the Explorer window projects, expanding the variable engine shared library for MODBUS and right click on the server MODBUS (for example Modbus1) item and select Properties.

  In addition, the addresses seem to be shifted by + 1.

  Thanks for the tip so.

• Go to the PHP website using Labview 8

  Hi people,

  I'm writing a vi LV8 to retrieve data from a Web site. The first site I've played with just had a text output so a simple:

  -OpenTCPConnection (for 'www.hpc.ncep.noaa.gov')

  -WriteTCP:

  -line 1: 'GET heat_index_MEAN/hitable_east.txt '.

  -line 2: "" Host: www.hpc.ncep.noaa.gov".

  -line 3:

  -ReadTCP

  It worked perfectly fine.

  But this isn't really the data I want. I want the data displayed on the Web site:

  http://forecast.weather.gov/MapClick.php?W0=t&W1=TD&W2=Hi&w3=sfcwind&w3u=1&W4=sky&W5=pop&W6=RH&W7=th... 96 & textField2 =-77.48167 & site = all & unit = 0 & dd = 0 & bw = 0

  But, when I try the same calls I get the error messages like:

  Query HTTP/1.0 400 Bad server: AkamaiGHost Mime-Version: 1.0 Content-Type: text/html Content-Length: 216 Expires: Sunday 12 August 2012 17:40:25 GMT Date: Sunday 12 August 2012 17:40:25 GMT connection: close

  Bad request

  Your browser has requested that this server could not understand.

  Reference #7.9f931160.1344793225.0

  I don't know enough about HTML or PHP to tell if I have a HTML or PHP problem; and what I have to understand to move forward. More precisely:

  -can you tell if it is a PHP or HTML problem in my code?

  -If Yes, which?

  -I can access a Web site (which uses PHP) LabVIEW?

  -what I have to learn more about PHP to proceed?

  -J' tried to send a command "OPTIONS" of HTML, but I received very similar eror messages (not a quesstion)

  -the site has an XML option that displays data as text/XML, but it also seems to use PHP, if I get the same errors with my code (not an issue)

  -any ideas on how to use labview to read data from this site?

  Thank you, in advance...

  
  

• Interfacing Ensenso SDK using labview

  I am trying to Ensenso SDK interface using labview. The company provides a .net dll, however, all available functions are not accessible from labview. They also said that labview is not yet officially support for interface with the Ensenso SDK. But C, C++ are officially supported. Now my question is, is it possible to write code c or c++ to control the Ensenso SDK and then access the C or C++ works using labview? If so can you help me how can I do? Thank you very much for your support.

  With sincere friendships.

  Sewyew

  If you can not get the .NET DLL to work with LabVIEW (for example the use of the call library function node), you could create a C/C++ DLL wrapper that allows you to access the functions you need. I don't know too much about the details, but it is certainly possible.

• Printing of barcode using LabVIEW in Zebra GT800

  Hello

  I GT800 Zebra printer and I am trying to print a barcode 1 d with label using LabVIEW. I connected my printer via a USB port. What commands EPL must I give in order to print the bar code?

  Well, before I was using .net and a printer connected in series, and we just called a shell command to copy the file on the com port with a command like "COPY /B PRINT. PRN, COM1.

  I don't know which would be too much work to LabView, but there may be more elegant ways. I've never done no direct printing of labview so I don't know, but a quick bit of Googling (which I'm sure you can do it yourself as well as I can) seems to suggest that using the exec command vi system is the way to go.

  To access a port USB printer can be more complicated. One way is to share the printer on the network and then map to an LPT port with a command like somethng "net use LPT1-" from a command prompt (you can view the help on this command, because it comes just from memory) - then it becomes directly available on the back and you can use the COPY /B LPT1 command to send your file to him. ".

  If someone has a better suggestion for sending data to Labview to a printer, then I would like to know.