Producer/Consumer pattern executes slow

April 16, 2018, 5:41 pm

≫ Next: Labview 2017， Loop structure crushs after hours with no message or warning

≪ Previous: Wrong Data name after calculating mean ptbypt when saving to excel

$

0

0

Hi all, as you'll see I'am pretty new at using the producer/consumer pattern.

I coded the block diagram shown below and it already does what it is suppossed to do, the only matter is that it executes very slow.

Image may be NSFW.
Clik here to view.Any recomendation or idea about this?

I realised that it turned slow when I added the upper loop (Producer). At the beggining I was running it in a single loop (lower loop) and without the visa read part.

I'd appreciate every comment.

Best regards.

Emmanuel.

PS: Attached below the upper picture. Just in case.

---

Labview 2017， Loop structure crushs after hours with no message or warning

April 16, 2018, 7:00 pm

≫ Next: Creating a Pressure waveform with Labview and DAQ NI USB-6343

≪ Previous: Producer/Consumer pattern executes slow

$

0

0

Greetings.

I wrote a subVI and come across a problem. I hope someone will help me. Here is the problem:
I used the the subVI which can be found in the reference, to show DAQ chart.
I used for loop at first, and copied it twice and changed one of them into while loop structure(just for testing).
I run the subVI and press 3 start buttons and the 3 charts run fluently at first. But after hours (8 ,9 or maybe even longer), some of the loop just stop with no message or anouncement. But other loop still run well.

At the same time. The VI seems crush and i can't stop it use the stop button.

I monitored the memory used by the program. And it did not increase while it was running.

Will it be the bug of Labview2017?

Anyone can help me with this, thanks a lot.

Creating a Pressure waveform with Labview and DAQ NI USB-6343

April 16, 2018, 7:03 pm

≫ Next: Error when build dll LabVIEW Project LV2015

≪ Previous: Labview 2017， Loop structure crushs after hours with no message or warning

$

0

0

Hello CommunityImage may be NSFW.
Clik here to view.

I am trying to generate a sine wave form as a pressure input such that the pressure increases gradually and struggled getting it to work with the DAQ NI USB 6343 and a connected pressure regulator. 

This is the section without the waveform, just a steady pressure value.

Image may be NSFW.
Clik here to view.

This is a screenshot of the "set psi" sub VI:

Image may be NSFW.
Clik here to view.

So I modified the two sections. I tried putting in different waveform generators (Signal Builder, Basic Function Generator, etc.) and they all caused trouble in communicating with the DAQ because of the changed input format (I think). When I changed the “Pressure (psi)” input, it looked something like this (depending on the block I used):

Image may be NSFW.
Clik here to view.

The error messages I got for the two different configurations (with different selections for the DAQ inputss) are attached. I tried different modifications of the DAQ input (single channel/multiple channel and single sample/multiple sample etc.). Even when I managed to get no error message when starting the program and a working waveform as a pressure input (visualized), the conversion from pressure input wave to voltage just didn’t do anything so there was no voltage input to the regulator.

 

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

I would be very happy if anyone could tell me what is going on.

Error when build dll LabVIEW Project LV2015

April 16, 2018, 10:11 pm

≫ Next: How to add controls in a typedef cluster

≪ Previous: Creating a Pressure waveform with Labview and DAQ NI USB-6343

$

0

0

n error occurred compiling the DLL because a function or parameter name is illegal. Please verify that the function and/or parameter names are legal C identifiers and do not conflict with LabVIEW headers.
Additional Information: 9 Project link errors
Error generating type library. Midl.exe failed while compiling the odl file used to create the type library.
Note: The error indicates that the odl file has unknown types. This error is possible when
functions with non-standard types are exported using the export qualifier method from files in
release configuration that have not been recompiled during the build process. You can mark all
files for recompilation and repeat the build. To avoid this situation, it is recommended that
you export these functions using the include file method.
Use the generated odl file "c:\Users\vramalin\AppData\Local\Temp\dlltemp3900.819973\SharedLib.odl" with the command line:
C:\Program Files (x86)\National Instruments\Shared\MSDTRedistributables\BuildTools\8.1\midl.exe "c:\Users\vramalin\AppData\Local\Temp\dlltemp3900.819973\SharedLib.odl" /win32 /mktyplib203 /tlb "SharedLib.tlb" /IC:\Program Files (x86)\National Instruments\Shared\MSDTRedistributables\BuildTools\8.1 /cpp_cmd c:\program files (x86)\national instruments\shared\lvdb 2015\bin\preprocessor.exe
to see what errors midl.exe reported.

ERROR_REPORTED_TO_USER

How to add controls in a typedef cluster

April 17, 2018, 1:36 am

≫ Next: TDMS driver error doubt of version in 2017?

≪ Previous: Error when build dll LabVIEW Project LV2015

$

0

0

Hi,

I need to add controls to a typedef cluster of 30 elt 

any help please ?

i'm using LabView 2015

Thanks 

TDMS driver error doubt of version in 2017?

April 17, 2018, 1:39 am

≫ Next: cannot install PB module on cRIO 9074

≪ Previous: How to add controls in a typedef cluster

$

0

0

I did a try in Labview 2017 and there is a standrd program structure as below:

Image may be NSFW.
Clik here to view.

In one loop, the above structure could work well in Labview2015, cause of the synchronized data acqusition and storage, but in the latest version of 2017, the "TDMS close" will be instabled to affact the normal loop work,  while you put your data path out of the C:, such as in D:\data\1.tdms ....

you will see the loop goes lower.  I do just doubt this is the version error between 2015-2017, but more possbile will be the errors in the "TDMS write" /"TDMS close"   themselves. Because "TDMS write" include  the buffer memory and feel hard to be released by "TDMS close". So, this trouble may be a big problem!  If anyone knows how it is sloved pls try your best to let me know, thanks a lot.

 

cannot install PB module on cRIO 9074

April 17, 2018, 3:26 am

≫ Next: code:66 tcp write change password error.

≪ Previous: TDMS driver error doubt of version in 2017?

$

0

0

Hello,

another problem. I am trying to upload a new profibus configuration onto a Kunbus ex Comsoft PB module. Labview 2014, NI Visa 14.0, MAX 14.5. So thats more than the minimum required. PB module in slot 1. Made all the settings as per the users manual. But I cannot upload the configuration onto the PB module. The errors look as if the Kunbus configurator does not find the module.

The error log file stays 0 byte, so not much help.

 

Cheers,

 

Steffen

 

Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

code:66 tcp write change password error.

April 17, 2018, 3:42 am

≫ Next: Need of VISA driver

≪ Previous: cannot install PB module on cRIO 9074

$

0

0

Good morning, 

I apologize if any key information is missing, I am not very familiar with LabView.

 

I am currently troubleshooting an intermittent error that I am being told is a network error however I don't believe this is true.  We currently utilize software written in LabView by vendor that is used on several test locations.  The configuration is the same: through a secondary NIC on a private VLAN there are 2 other devices that the software uses, a signal conditioner and a gps clock.  There are periods where,when bringing up the software it will not see the GPS clock (which is also the timing source for the associated digitizers that are connected to the signal conditioner).  The GPS clock and signal conditioner both run through a managed switch.  As stated, the software will, at various locations, intermittently not see the GPS clock or lose it while connected.  As I was being told this was a network issue from the lead technician I thought this might be a duplex mismatch or a firewall that might have been recently implemented.  However, the network switch and the NIC are both set to auto-negotiate, the GPS clock, when speaking with the networking personnel, is transmitting at 100mb/full duplex (as per the device documentation) and they see no conflicts on their side.  All cables were checked and determined to be good.  There are no firewalls in place.  This device communicates via telnet and there are currently no policies implemented preventing this.  I also, under ethernet properties, disabled all but IPv4 as this fixed a similar issue on an unrelated system elsewhere.  

 

Yesterday I was able to run wireshark while bringing up the system in question and during the initial communication with the device there was a reset packet which i then received a message from the software that it could not find the GPS clock.  After a few attempts I was able to bring up the software with communication to all devices.  In Wireshark I was able to see several retransmissions and eventually it stopped retransmitting and the software in question was locked up.  Upon closing the software I received this message "

Code:66, Source: TCP Write in 6115G-TSM Change Password - Logoff.vi->6115G-TSM Close Connection.vi->Shutdown_Close Refnums.vi->Shutdown Main VI.vi->Top Level GUI.vi" where the TSM is the gps device in question.  I have seen the code 66 before however never this message.  I am unsure if this is stating the device suddenly lost it's password or if it's indicating something else.  This device has been used at the various test sites for several years and this issue of intermittent comms seems to be within the last year.  

 

If I am missing any key information or more is required please let me know.  Thank you

---

Need of VISA driver

April 17, 2018, 4:55 am

≫ Next: Board is not detected

≪ Previous: code:66 tcp write change password error.

$

0

0

Hi All,

We have following driver for following devices.

DAQmx driver : DAQmx devices

NI-488.2 Runtime : GPIB devices

NI-DMM: NI DMM devices.

 

can anyone let me know why we need VISA library when we have above device drivers.

 

Regards,

Anand

Board is not detected

April 17, 2018, 4:55 am

≫ Next: Building shared library for simple add function labview VI

≪ Previous: Need of VISA driver

$

0

0

Hello everyone,

I am using Labview 2017 with NI MAX version 17.0.I have installed NI DAQ version 17.0.I  am using signal ranger mk3 board as my hardware platform.I want to use Analog Output block from DAQ Assistant.But when I clicked on Voltage from Analog Output block of Generate Signals tab of DAQ Assistant window.I got a message "No supported devices found".

 

So I checked in NI MAX and my board was detected.I have attached the figure below.

 Can anyone help me to resolve this issue?

 

 

Building shared library for simple add function labview VI

April 17, 2018, 5:02 am

≫ Next: Timestamp Formatting Truncates Instead of Rounds

≪ Previous: Board is not detected

$

0

0

Hi ,

I am trying to build a shared library for simple add function in labview .But getting error as attached snapshot.

 

Regards,

Anand

 

 

Timestamp Formatting Truncates Instead of Rounds

April 17, 2018, 5:35 am

≫ Next: Board is not detected

≪ Previous: Building shared library for simple add function labview VI

$

0

0

While testing some code that displays timestamps, I noticed that Timestamp indicators (and the format into string options) truncate timestamps instead of round.  This leads to minor rounding errors in floating-point math causing your result to be off by a much larger amount (in the attached vi, 1ms).  The attached vi gives the same results in LabVIEW 2015 and LabVIEW 2017 - in case it affects the results, I tested this in Eastern Daylight Time using United States time format conventions.

 

 

Does anyone know if this truncation is intended behavior?  If it is, I might add an idea exchange entry suggesting a rounding version of the %u time format code.

Board is not detected

April 17, 2018, 4:02 am

≫ Next: Does the LabVIEW Student Version feature data aquisition with a USB DAQ device?

≪ Previous: Timestamp Formatting Truncates Instead of Rounds

$

0

0

Hello everyone,

I am working on LabView version 2017.I have signal ranger mk3 board as my hardware platform.In order to use Analog Output block I downloaded NI DAQ version 17.0.I am using MAX explorer version 17.0.When I clicked Analog Output from Generate Signals tab of NI DAQ Assistant window,I got a message "No supported devices found".

 

So I checked into MAX explorer window and my device got detected.I have attached the figure as follows.

 

Can anyone help me to resolve this issue?

Does the LabVIEW Student Version feature data aquisition with a USB DAQ device?

April 17, 2018, 7:06 am

≫ Next: While Loop time slowing down?

≪ Previous: Board is not detected

$

0

0

I will purchase a Student version of LabView. It comes with the folliwing modules:

• LabVIEW Student Development Environment
• LabVIEW Control Design and Simulation Module
• LabVIEW MathScript RT Module

Will it feature working with a NI USB DAQ 6001? If not, which version/moduels would be necessary?

Thanks,

Tobi

While Loop time slowing down?

April 17, 2018, 8:00 am

≫ Next: LabVIEW and "Contact ID" protocol from Adenco

≪ Previous: Does the LabVIEW Student Version feature data aquisition with a USB DAQ device?

$

0

0

Greetings,

I am getting the common Labview error where it states -

 

"The application is not able to keep up with the hardware acquisition.  Increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all samples available may fix the problem"

 

I've tried all of the above to include setting the recommended samples to read to 1/10th the sampling rate, but still eventually the application crashes for the aforementioned error.  I can delay the inevitable error, but can't seem to prevent it completely.  I put in some timing code that I copied from a NI help to determine the duration of my While Loop as that time is a factor on how frequently I'm reading data from the hardware.  The While Loop duration is slowly creeping up for some reason, which in turn is decreasing the read rate.  Perhaps the reason why the loop duration is creeping up is obvious?  Is it still something to do with how the timing and read VI's are configured, or is it something in my code slowing down the loop??  For starters, I'd like to just run the application at 1000Hz sampling rate.  I require this application to run continuously for an indefinite duration of time.  I'm obviously not a polished LabVIEW programmer, so be nice please.  Thank you.

---

LabVIEW and "Contact ID" protocol from Adenco

April 17, 2018, 8:16 am

≫ Next: Numerical integration of Force and Velocity graphs to obtain energy.

≪ Previous: While Loop time slowing down?

$

0

0

Hello Friends!
I need to connect a residential alarm switch via Ethernet using Adenco's "Contact ID" protocol.
Has anyone done this yet?
Thank you!

Numerical integration of Force and Velocity graphs to obtain energy.

April 16, 2018, 11:13 am

≫ Next: Drivers and VI for ANRITSU MS46122B

≪ Previous: LabVIEW and "Contact ID" protocol from Adenco

$

0

0

Hello Respected Members!

I am presently working on Force Velocity integration to obtain energy of a falling hammer. I have attached two accelerometers and two strain guages to a rod, on which the hammer shall fall. I have attached the pictures which better explain the problems.
i m using Ni-cDaq 9172 and NI9237 ( accelerometers are piezoresistive) 

Please advise how to go about it.

Drivers and VI for ANRITSU MS46122B

April 17, 2018, 9:17 am

≫ Next: FPGA loop time optimization - CRIO 9082 - 9224 analog input module

≪ Previous: Numerical integration of Force and Velocity graphs to obtain energy.

$

0

0

Hi all,

 

I am trying to communicate an ANRITSU MS46122B VNA through LabVIEW, and I need the VI's to configurate it directly from the block diagram. So far I have been using some modules from MS464X and MS37XX that were in the folder by default, but some of them work and others don't. Where could I download the specific VI's for the MS46122B model?

Thank you so much.

Kind regards,

FPGA loop time optimization - CRIO 9082 - 9224 analog input module

April 17, 2018, 9:47 am

≫ Next: Write to Measurement File does not pass my string name along

≪ Previous: Drivers and VI for ANRITSU MS46122B

$

0

0

Hello,

 

I'm fairly new and unexperienced on FPGA.

I'm using a cRIO 9082, with some high speed data acquisition module, like 9224, which is supposed to operate at 1 MHz sampling rate.

I need to read data on some analog input of the 9224 and react within microseconds, based on a fairly simple algorithm.

I have isolated the communication with the 9224 module is a separate loop, focusing only on this task, and storing the read value in an indicator. (see annexed picture)

But just this loop, seems to run at maximum 3 us per loop. It seems it does not approach the 1 us per loop I was expecting. 

what is the reason why this loop does not run faster than 3 us per loop ? What are the ways to bring it to 1 us per loop, as the 9224 module is supposed to run at 1 MHz ? I'm probably missing something because I'm not experienced enough on FPGA. Any help will be very appreciated.

 

J.F.

Write to Measurement File does not pass my string name along

April 17, 2018, 10:01 am

≫ Next: OPC automation active-x help

≪ Previous: FPGA loop time optimization - CRIO 9082 - 9224 analog input module

$

0

0

I have a write to measurement file that collects data from a "set dynamic data attributes". The problem is that it doesn't update all the signal name but only the last in the iteration. I really do not want to use a shift register to correct this problem as the shift register causes an error "2553" after a long period of data collection, along with stopping problems.

 I have attached the section of the VI so you can see what i am talking about. Again, I would appreciate a fix that doesn't involve the shift register. Note also, all other parts of the code are functioning correctly.