Quantcast
Channel: All LabVIEW posts
Viewing all 202447 articles
Browse latest View live

Re: Connectivity issue from a server to Client OPC

$
0
0

RDA stands for Residual Gas Analyzer, or QMG - 220 Prisma Plus device which basically works as a server I set its IP address 192.168.10.110 with the device name and Mac address. On visual basic, I created a client program after that I make Labview as my client with IP address 127.0.0.1 over port 2080 and my PC Ip is 192.168.10.10 with DNS 192.168.10.1

When I am trying to make an attempt for connecting Server(QMG 220)  with LabVIEW that time Server shown its connectivity but LabVIEW main program or client not giving any response.

 

https://pfeiffer-vacuum.com/en/download-center/

 

Regards,

Taufeey


Re: Overlay motion vectors

$
0
0

I can't open the file that you bring "Here is a gooh vi", can you share to me on email qolbusaharuddin@gmail.com, thankyou


 wrote:

Hello! Unfortunately, the method of optical flow I is not adapted to download the video. For it to work I used the convert video in a series of images.  Here is a good vi.


 

Re: SD card

$
0
0

Thank you for your answer but it's not resolve my issue.

I have the sbRIO9607. I want to implement SDIO peripheral interface. For this, I need to do a socketed CLIP (cf picture SDIO 1).  I did it. But I have the error code 65010. And in the line command I have this error (cf picture dmesg).

 

Help me please

Guidance for the below mention commands

$
0
0

Hello everyone, 

 

I attached a couple of pictures if anyone please guide me in its understanding how its working.

 

 

Regards,

Taufeey

 

Re: How to call dll function with the double asterix parameter

$
0
0

 wrote:

Can I please ask you for some additional information : Why void ** ppHandle should be of a Data Type: Unsigned Pointer-sized Integer? And if I would have only one asterisk like this: void * pHandle should I also use Unsigned Pointer-sized Integer for data type?


Basically because the asterix indicates that it IS a pointer. And pointers have different sizes depending if the application is 32 bit or 64 bit. A double asterix simply means that it is a pointer sized integer passed by reference (in other words "Pass: Pointer to value").

As long as you work in LabVIEW 32 bit your configuration works too, but why limit it to only work in LabVIEW 32 bit? Sooner or later everyone will only work in 64 bit.

 

And yes if it is only void *pHandle it would still be a pointer sized integer but this time Pass: by Value.

 

The real problem you had is the second misconfiguration. You have to always make sure that any output buffer is preallocated. That is mandatory for C function calls, unlike what you are used in LabVIEW where a LabVIEW node automatically adjusts array and string buffers to the necessary size.

Re: How to hide a single tab in tabcontrol

$
0
0

OK old thread, but I think it worth to share.

This VI can be used as a template.

I strongly suggest to create a type def with the same element number as your tab or create your tab control as a typedef. Of make it generic by changing the list into string.

Benoit

Re: 10 G communication and LabVIEW

$
0
0

If the 10GB network interface is fully supported by the OS as a TCP/IP interface it will certainly work. But don't expect to get 10GB/s data throughput. That is pretty impossible to do without very special application support with direct access to the network interface driver, which the standard Windows socket interface is anything but that.

Re: Best Practice: Is it better to write to a front panel object via a Reference>Property Node combination, or directly via a Constant>Duplicate Terminal

$
0
0

 wrote:

This thread  prompts a new question.

 

As mentioned previously the  current gen involves a thread swap for the property nodes to use the UI thread and prevent race conditions blah blah blah. I had understood that as being a hack. So on to the question...

 


I wouldn't say this is a hack. It's a fairly cheap way to make synchonization between multithreaded code and a single threaded UI. The alternative would have been to add a mutex to every possible UI object in LabVIEW and rewrite every part of LabVIEW to make sure to go through this mutex when accessing the object. This approach would have been a lot more work (several 100 sites in the code would have had to be visited, revised, tested and countertested) and very error prone as it is extremely easy to miss some instances where this mutex needs to be used. One single missed mutex access can make the difference between an application that simply runs and one that more or less frequently crashes at seemingly random moments.

 

As LabVIEW NXG is pretty much a complete rewrite for the entire UI part of LabVIEW, with a high potential to never work on other platforms than Windows aside from the headless operation on realtime targets, I'm sure they changed that part in the process too.


Re: Guidance for the below mention commands

$
0
0

What do you expect us to tell you? That it seems to be a TCP based communication with a STX byte as start of message indication, then a text string containing some command and then an ETX byte to indicate the end of the message?

Did you notice the little prefix on the left border of the string constants? x means that it is in binary display mode while n indicates normal text mode.

Re: VISA Read continuous serial data drops packets...

Re: Best PING, one that understands "TTL expired in transit"?

$
0
0

Although your answers seem to contradict, all of you are correct. ping is the correct tool to generally check if there is a route to a host. It can also do some metrics, but it cannot assess if a route makes sense:

 

$ ping -i 1 8.8.8.8

Here I expect my TTL to expire in transit. However, this message still means there is a route to that remote host found (no evidence about if it actually works).

-> everything is fine, despite the message

 

$ ping -i 128 8.8.8.8

(same as ping 8.8.8.8)

Here I'd expect a full round-trip of the icmp packet. If you see "TTL expired in transit", you most likely have a looped route or are missing a vlan configuration one side of a trunk port. The remote host will never be reached.

-> you need some network troubleshooting

NI visa read serial looses a lot of data

$
0
0

Hi,

I am sending a continuous serial data from a micro-controller to the PC via serial port at a baud rate of 1562500.

I noticed that my lab-view read vi attached below looses lots of the data packets that I am sending. When I went through the saved data I notice that the data in the receive buffer has been flashed in the middle of the transmission and all the synchronization is lost.I tried using various buffer sizes but it seems the program behaves the same.

The problem I have is quite similar to the following.

https://forums.ni.com/t5/LabVIEW/VISA-Read-continuous-serial-data-drops-packets/td-p/3580333

 

Here I have attached the vi I am using at the moment.

Re: NI visa read serial looses a lot of data

$
0
0

I think you read too slow.
you get only 1+2+18 bytes and write it into file with expressVI. In this case every iteration you open and close file. That takes much time.
try to measure loop period, I think it will less than need.
Or remove "Write to file " vi and check speed

Re: Best PING, one that understands "TTL expired in transit"?

$
0
0

Ok, I'll improve the parsing of the resulting text then. But if feels a little to hacky to be good practise.

I remember a similar case when I did something clever that broke since the output in command line was different in windows xp/7 or different in swedish/english/japanese or whatever.

But this tool is only for my personal use, so that should be ok.

 

ikaiser, you are correct that it exist some network loops or something, and I try to figure out when and why it happens.

 

Thanks for all answers!

Re: How to Save Array and Calculations even if I close the VI


Re: NI visa read serial looses a lot of data

$
0
0

Hi,

Thanks for the reply. The problem is I need to log the data into a file, how can I log the data into file without slowing the read?

 

Can Communication lag

$
0
0

Hey everyone :-) Me again!

 

right now I develop a Labview Software using the CAN BUS protocol.

I use a PCAN adapter that is connected via USB. Communication works via PCAN_Driver_LV2010 v1.0.0

https://lavag.org/files/file/211-pcan-driver_lv2009/, I can send and receive and control the device.

 

BUT: I do have a strange time lag reading. An example: I read the can message for voltage and display them in a diagram. The device is continuously sending the voltage can message. If I switch off the device, data continues to be displayed for a minute or so, unless the device is already turned off and stopped to send data some time ago. I verified it with PCAN viewer, that uses the same connection and immediately stops to receive data when I switch off the device... So - principally it is possible.

 

I posted a screenshot to clarify what happenes and I posted my reading vi. If you need further information please let me know.

 

Precise questions:

 

1) Is there a buffer, the driver is reading from?

2) Do I read too slow (not often enough)?

 

 

If anyone has experience with the use of the PCAN Dongle and the driver mentioned or an idea, please let me know :-)

Best regards

Anna

Re: NI visa read serial looses a lot of data

$
0
0

You should use open-save-close functions

file.png

 

Also you have 1000 bytes buffer. You can read longer data packets, but rare

Lost connection to OPC client

$
0
0

Hi there,

I'm using LabVIEW 2013 on Windows 7.

 

I've a problem with a LabVIEW project. I've created a I/O server (type OPC client) in the project explorer. I make the code and I run the simulation. Sometimes it works and sometimes doesn't works.

When it doesn't works, if I browse to look for the variable I have to read, I even didn't see the variables.

I also open the "NI Distributed System Manager" and also with this tool I can't see the variables and it says that the connection was cutted. So that if I run the simulation, LabVIEW give me the error -1950679035 (image attached), because it can't reach the variable.

 

Someone has a solution? Someone already had this problem?

 

Thank you very much 

 

Re: Open file in LVOO

$
0
0

Hi,

 

thanks for the support.

The reason to use shared clone if permit the use of the functionality in different point.

Let me explain,better.

I want use the logfile utility in different part of my project on different file for different Subsystem, so the Subsystem 1 produce logfile1, etc. etc.

Viewing all 202447 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>