LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

RSLinx OPC Buffer?

I am collecting data from a AB plc via and OPC link in RSLinx.  When manipulating just a few points, I see all the values come in fine.  However, if it is rolling through events (e.g. events 1 through 16), it seems to be missing some.  I have the topic configuration with data collection at 100ms and my VI running at 100ms.  Is there perhaps a way to buffer the OPC data so that I do not miss some of these events?  I also got a "Memory is Full" message, which I am not sure if it is related.
0 Kudos
Message 1 of 3
(3,411 Views)
Where does the "memory is full" message come from, Windows or LabVIEW?  How much RAM does your system contain?

Also, if you slow down the program and server, are you able to retrieve the all of the data?  Are you using Polled or Unsolicited data collection mode?  The differences are mentioned here, just click on the Data Collection Mode link.  I haven't found any options for buffering.  Sounds to me that buffering would probably just prolong the inevitable.  If you are unable to read from the OPC server as fast as data is being generated, a buffer will eventually build until it overflows. 

Cheers,
Spex
National Instruments

To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be has a 2x safety factor...
Message 2 of 3
(3,389 Views)
The message comes from LabView.  There is 1GB of RAM on this PC.  I am doing Polled messages @ 100ms.  We are ringing in 12 16-bit integer values into LabView and separting the values into the individual bits and combined into boolean array for each integer value.  These arrays (6 each on 2 machines) are brought into basically an array of arrays.  I'm doing this mainly to more easily perform one-shot functionality on all the boolean values (96 bits per machine).  We don't write any values to the PLC. We were getting this at the startup of the machine, as it was rolling through a lot of different values, however the values were somewhat bogus.  Changes were made to the PLC program to ignore these startup values and it seems to have alleviated the issue.  Thanks for your help though.
0 Kudos
Message 3 of 3
(3,384 Views)