Labview visa write and read

To minimise the time "wasted" by transferring data between the instruments and the PC I would like to query them in parallel.

labview serial port monitor

All my instrument drivers are separate objects. While none of the standard drivers that come with the SDK for such chips is really meant to be distributed by OEMs to their clients, most especially no-name manufacturers do so anyhow as you really can't hire a programmer to improve a driver when you earn basically nothing on the sale of a product already and from the ones I've seen only the FTDI driver works reasonably well enough to not crash under any but very ideal situations.

This only can happen if a kernel driver is violating some critical system integrity while being called by the process directly or indirectly.

Labview read buffer

I can ensure that communication to a single type of instrument is done in series by making the vi that does the communication non-reentrant. Has anyone had similar experiences? To minimise the time "wasted" by transferring data between the instruments and the PC I would like to query them in parallel. And what function I have to use for it? I don't even have to read the answer back doing so won't make a difference : This will kill LabVIEW and , both 64bit without even popping up the "We apologize for the inconvenience" crash reporter dialog. Tom Depends what instruments that were. This only can happen if a kernel driver is violating some critical system integrity while being called by the process directly or indirectly. Basically your instrument is pretty much the same as any of those RS to USB converter dongles, and there it makes a big difference if one uses a noname product with unknown internal controller or one based on for instance the FTDI solution. This really only leaves two options for the cause of this crash: A buggy chipset driver for your system itself or a buggy USB virtual comm driver for your instruments. While none of the standard drivers that come with the SDK for such chips is really meant to be distributed by OEMs to their clients, most especially no-name manufacturers do so anyhow as you really can't hire a programmer to improve a driver when you earn basically nothing on the sale of a product already and from the ones I've seen only the FTDI driver works reasonably well enough to not crash under any but very ideal situations. I want that because when I set temperature that does not have to run continuously because this is one time command to read temperature value this section run continuously because temperature on the experimental set up is changing an I have to see this changing, for example I set temperature F and than controller heat up device F but this command is one time command, but reading temperature command should work continuously because temperature is changing and I need to read temperature for each 60 sec and I can do that part.

Is it outrageous to assume that communication to separate instruments via different VISA references should work in parallel? Report to a Moderator I am using basic visa read and write example to control my temperature controller actually it works perfect but I want something else.

And what function I have to use for it?

labview read serial port continuously

I want that because when I set temperature that does not have to run continuously because this is one time command to read temperature value this section run continuously because temperature on the experimental set up is changing an I have to see this changing, for example I set temperature F and than controller heat up device F but this command is one time command, but reading temperature command should work continuously because temperature is changing and I need to read temperature for each 60 sec and I can do that part.

Am I just lucky that I haven't had more crashes when I'm talking to a lot of instruments? This really only leaves two options for the cause of this crash: A buggy chipset driver for your system itself or a buggy USB virtual comm driver for your instruments.

labview serial terminal

Which one it is I have no idea.

Rated 5/10 based on 34 review
Download
Serial Communication