Jump to content

massi1970

Members
  • Posts

    4
  • Joined

  • Last visited

    Never

massi1970's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi people, in order to automatically recognize wich com port is connected to a device I've used the "Visa Find Resource" with this string ASRL?*INSTR{VI_ATTR_ASRL_BAUD ==19200} to check only com devide with baude rate at 19200. After the research I try to write to all (in sequence) the serial port found a command ($A) waiting for 4 bytes returned or time exceding. In fact the device connected answers only with command "$A" (with 2 bytes). If time is exceeded (2000 ms) and 4 bytes are not present on serial port the vi goes to the next port found. If on none of the port found 4 byte are present the device is non tonnected. This vi runs fine if it is launched into labview (7.1), but if it is compiled and I use the exe program I never find the device. Otherwise it seems to run too fast as expected (few ms). Have you any idea of which tipe of error I made? Thanks Massimiliano.
  2. Hi people, does anyone know how is possible to read the name of the running vi in the running vi? thanks Massimiliano
  3. Hi. I encountered this problem. Modifying the example "continuous generation" by inserting a subVi that returns part of a vector of data (previously generated), with number of data corresponding to the whole daq channel buffer (which size is setted to 100 samples) in the first step of the loop, and the half buffer every other step, and setting the sample rate to 100 S/s. I expect to obtain an output continuous signal , representing my data vector. If, as suggested by National, I set regeneration mode allowed and inspecting the output signal with an oscilloscope I can see only the first cycle continuously reproduced. Even if I not allow the regeneration after the first step I obtain an error. I also sure that the correct number of data are fed in the correct way and number, by a direct visualization of them in labview. I use traditional daq because I use an AT-MIO-16XE-10 and it is impossible to change the FIFO buffer of this device. I cannot use yhe whole FIFO cause the excessive elapsing time in every step of the continuous loop (more than 20 seconds, given the FIFO dimension of 2048 samples), and I hve the necessity of stop (or change) the data generation almost immediately (or in one second). Have anyone an idea of which is my error? Thanks Massimiliano
  4. Hi people. I've the necessity of change my data output during the generation. In particular I've to stop the generation after tha data smooth to zero after push a stop button, but I previous don't know when I'll stop the process. So I don't use the generation all at once, but I use a buffered generation in a loop and in the same loop I put a packet of data ( a vector of 100 elements) in the buffer, then the program generates in daq (at 100 sample/sec). Even if in the first step of loop I set the "AO config" (whit buffer to 100) and put 100 or more than 100 (in particular 200 or 400) elements in the buffer to write , writing data with "AO write" followed by "AO start" and in the other steps I write ("AO write") 100 elements, I obtain always this error: "The on-going transfer has been stopped. This is to prevent regeneration for output operations, or to reallocate resources for input operations." I'm sure of low rate generation for my hardware so I don't understand where changing the vi to obtain my target. Have any idea. Thanks. Massimiliano In attachment the vi
×
×
  • Create New...

Important Information

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