Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by FJ_Sanchez

  1. Can you explain the utility of the reset function? I don't understand this parameter of the VI...
  2. Hello, I am trying a very simple example using "Basic Level Trigger Detection.vi" and it is not working as expected. I want to get the first 3 rising edges (even without hysteresis) but I always get the first one. The help says that this VI internally stores the status (I have also check that in the code) but I see when debugging that it always returns 0 in the terminal where the history should be stored. I can workaround with my own VI or using subsets of the input signal, but is it a bug? Thank you.
  3. Ok, few days ago a NI engineer tried to solve the problem comming to my office, but failed to find a solution. After some trial and error and some research I found the problem. I have to enable the Intel C-STATE technology in the BIOS settings under the CPU options. It looked like it was a problem related to energy and power states... Thank you anyway.
  4. Hello, I've been struggling with this problem for months now... I want to use a cDAQ9171+NI-9234 with an Advantech PC (AIMB-580). I have 3 computers like this and all with the same problem. I plug the USB cDAQ-9171, Windows detect the device and loads the proper driver (cDAQ-9171), it is displayed in MAX but self-test or reset always fails with error. At the same time, NI Devive Loader service hangs up. If I try to restart or stop this service it cannot complete the operation, the only way to finish this operation is to unplug the usb cable from the PC, then the service restarts correctly.
  5. Hello, I'm developing an application that uses some PCIe hardware. My daily developing computer is a laptop docked to a dock station. Now, I would like to develop testing my subVIs in the remote desktop that has installed the PCIe hardware. I know I can enable remote debugging, compile and transfer the executable, then execute and connect from my laptop, but this is very inefficient and slow process to test subVIs. I could install the full development environment in the remote desktop, develop in this machine with remote connection (or even directly on this computer, as it's next to my
  6. I agree with you, I think that flatten to string is appending some useless information in this case. Thank you.
  7. Hello, I've been using Snap7 library for a while in the client role, so I can communicate with SIEMENS PLCs There is specific LabVIEW info here: http://snap7.sourceforge.net/labview.html I can successfully use the Cli VIs to read/write from PLCs DBs (a DB is just a memory block). For reading I pre-allocate a buffer, but I'm not sure if I'm doing it properly. My main concern is about memory leakage, I don't know if the memory will be freed after the VI exits or it will not be freed as long as the VI is in memory. Attached is what I have just now for reading. I define a typedef for each
  8. Hello, finally I got the solution to my problem but I didn't post it here, so I do now to help anyone that could encounter this problem. I'm not sure if the COM object is non-thread safe, but the fact is that if I mark the VI to run in UI thread everything goes smooth... Regards.
  9. Hello everyone, I have a front panel with a lot of indicators in different tabs (total about 100). I would like to know what is the best way to manage such huge amount of indicators... Usually I don't have so much, but in this case I have 5 tabs, so the amount of indicators in the VI gets high. After I've acquired data from the acquisition device, I should update most of them. My acquired/processed data is stored in an array. Any recommendations? Thank you!
  10. Thank you to everyone, much clearer now
  11. Hello, I have a project that I've modified in 2 different computers apparently with the same development environment (LV2013 SP1 + Database connectivity toolkit among others). When I moved the project from one computer to the other and closed the main VI (without any changes, just open and close) the "save files" dialog showed that some files from Database connectivity toolkit needed to be saved. I have a subvi calling "DB tools select data", if I remove this VI, labVIEW ask a last time to save or don't these files. If I dismiss any changes I can open and close the main VI and LV doesn't a
  12. Forget about this... now it's working, it was something related to the #defines that it generates by default. Anyway, I really recommend the mentioned post to anyone with problems with C++ dll and LabVIEW.
  13. Hello, I'm trying to compile the code from this thread http://lavag.org/topic/9232-c-classes-from-lv/ and load it in LV. I can compile it without errors, but when I try to load the DLL in Lv using the Call Library Function Node, it throws an error: Error loading "mydll.dll" Invalid access to memory location. If I use the dll provided in the zip it works great, so I think that I should change something in Dev-C++ to make it compatible with LV Call Library Funcion Node. Any ideas?
  14. After some time trying still stuck with this, even NI support couldn't give me a solution, probably the COM object isn't fully ActiveX compliant or compatible with LabVIEW implementation of ActiveX... I'm going to make a wrapper DLL in C++ that handles the COM calls and pass data into LabVIEW, but I've never done it before and I'm struggling to make it work.
  15. Hi, it's not commented out in VBA, it's just wrong syntax highlight. I think I'm doing exactly the same, but something should be wrong or I would get same result.
  16. Hello, I'm trying to use a library to interface some LVDT gauges from Marposs. It's implemented through COM objects and I have it working in Excel with VBA with this code: Private Sub CommandButton1_Click()Dim oSmaoMain As SMAO.SMaoMainDim clsInfo As SMAO.InfoDim sInfo As String'Initialize the SMAOMain ObjectSet oSmaoMain = New SMAO.SMaoMainoSmaoMain.Initialize'List all the Installed DriversFor i = 1 To oSmaoMain.DriversCount sInfo = sInfo & "Driver Name : " & oSmaoMain.Driver(i) & " " & oSmaoMain.DriverDesc(i) & vbNewLineNextMsgBox sInfo, vbOKOnly, "Installed Dri
  • Create New...

Important Information

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