From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Access Violation

Hi !

I have an application that delivers 12 sets of data with 54 items in each
set.
I wanted to build a history presentation VI, 300 , so I initialized a
3-dimensional matrix with 12*54*300 values.
Using extract, and replace array subset I shift the the 300 values 1 step
each time the main application has delivered the data.
At any given time I can access any of the 12*54 arrays with its 300 values
with a little help of some useful VI's.
Any how, The VI works nicely, but the main application that earlier ran for
days in a row, suddenly has started to give access violation errors and the
whole LabView environment shuts down.
I've checked the memory usage with the system manager, and no memory loss.

I'm at loss. Anyone with an idea ?

Yours/
--
Roger Oh
lund, MSc Engineering Physics
Ericsson Erisoft AB
(S?/EPL/J/T) Ph: +46 910 731423
Skelleftehamnsvagen 206 Cell: +46 70 2648301
S-932 83 Ursviken, Sweden Fax:
mailto:Roger.Ohlund@epl.ericsson.se
0 Kudos
Message 1 of 5
(2,855 Views)
Hello Roger,

Could you please provide a bit more detail? In particular, what OS and what version of LabVIEW? If you are running WindowsNT with LabVIEW 6.0, a simple upgrade to LabVIEW 6.0.2 may do the trick.

Other questions:
How is your main (the executable) "delivering" the data to your new program?
Or is the new code an addition to the main VI (ie we're only dealing with one VI)?
Is there any more information you can provide about the error? Any additional message that comes with the error?

Kent
0 Kudos
Message 2 of 5
(2,855 Views)
Ok! From the beginning.

I have built an Image analysis software that can aquire images from 12
cameras and calculate 54 parameters from each of these images. The software
is used to control a process. The source code is about 15 MByte, the
operative system win2k, the computer a dual pIII 1000 MHz with 512 MByte
RAM, the grabbercards are Matrox Meteor II cards, no external DLL's. The
calculations include different Fourier analysis, morphological analysis and
colour analysis, the cycle time per camera is 0.65 seconds. The longest
runtime it's been executed is slightly short of 4 months. The software has
logging abilities, OPC and DDE communication built in, but also (of course)
on screen presentation. Whilst up and running the application allocates
memory for different kinds of images, about 12 MByte. The LabView
environment is LabView 6i with Imaq 5.0. When I tried to include my history
presentation it allocated something like 30 MByte for the 3-D array. Using
extract array subset and replace array subset I shift the the 300 values 1
step each time the main application has delivered the data, data that is put
in as a column in the array filling the first position of the 54 different
300 values long arrays. The procedure is than repeated for each page in the
array as the cameras are switched. At any given time I can access any of the
12*54 arrays with its 300 values with a little help of some useful VI's,
standard NI array VI's. I just extract a desired row from a page and then
inverse it, and it's reday to present in a graph. But since including this
my application has started to give access violation errors and the whole
LabView environment shuts down. I've checked the memory usage with the
system manager, and no memory loss. The error usually occurs within the
first 2 hours.

Yours/
--
Roger Ohlund, MSc Engineering Physics
Ericsson Erisoft AB
(S�/EPL/J/T) Ph: +46 910 731423
Skelleftehamnsvagen 206 Cell: +46 70 2648301
S-932 83 Ursviken, Sweden Fax:
mailto:Roger.Ohlund@epl.ericsson.se


Kent Leung wrote in message
<506500000005000000F25D0000-1012609683000@exchange.ni.com>...
>Hello Roger,
>
>Could you please provide a bit more detail? In particular, what OS
>and what version of LabVIEW? If you are running WindowsNT with
>LabVIEW 6.0, a simple upgrade to LabVIEW 6.0.2 may do the trick.
>
>Other questions:
>How is your main (the executable) "delivering" the data to your new
>program?
>Or is the new code an addition to the main VI (ie we're only dealing
>with one VI)?
>Is there any more information you can provide about the error? Any
>additional message that comes with the error?
>
>Kent
0 Kudos
Message 3 of 5
(2,855 Views)
Oh I forgot, only one application not several.

--
Roger Ohlund, MSc Engineering Physics
Ericsson Erisoft AB
(S�/EPL/J/T) Ph: +46 910 731423
Skelleftehamnsvagen 206 Cell: +46 70 2648301
S-932 83 Ursviken, Sweden Fax:
mailto:Roger.Ohlund@epl.ericsson.se
Roger Ohlund wrote in message ...
>Ok! From the beginning.
>
>I have built an Image analysis software that can aquire images from 12
>cameras and calculate 54 parameters from each of these images. The software
>is used to control a process. The source code is about 15 MByte, the
>operative system win2k, the computer a dual pIII 1000 MHz with 512 MByte
>RAM, the grabbercards are Matrox Meteor II cards, no external DLL's. The
>calculations include different Fourier analysis, morphological analysis
and
>colour analysis, the cycle time per camera is 0.65 seconds. The longest
>runtime it's been executed is slightly short of 4 months. The software has
>logging abilities, OPC and DDE communication built in, but also (of course)
>on screen presentation. Whilst up and running the application allocates
>memory for different kinds of images, about 12 MByte. The LabView
>environment is LabView 6i with Imaq 5.0. When I tried to include my history
>presentation it allocated something like 30 MByte for the 3-D array. Using
>extract array subset and replace array subset I shift the the 300 values 1
>step each time the main application has delivered the data, data that is
put
>in as a column in the array filling the first position of the 54 different
>300 values long arrays. The procedure is than repeated for each page in the
>array as the cameras are switched. At any given time I can access any of
the
>12*54 arrays with its 300 values with a little help of some useful VI's,
>standard NI array VI's. I just extract a desired row from a page and then
>inverse it, and it's reday to present in a graph. But since including this
>my application has started to give access violation errors and the whole
>LabView environment shuts down. I've checked the memory usage with the
>system manager, and no memory loss. The error usually occurs within the
>first 2 hours.
>
>Yours/
>--
>Roger Ohlund, MSc Engineering Physics
>Ericsson Erisoft AB
>(S�/EPL/J/T) Ph: +46 910 731423
>Skelleftehamnsvagen 206 Cell: +46 70 2648301
>S-932 83 Ursviken, Sweden Fax:
>mailto:Roger.Ohlund@epl.ericsson.se
>
>
>Kent Leung wrote in message
><506500000005000000F25D0000-1012609683000@exchange.ni.com>...
>>Hello Roger,
>>
>>Could you please provide a bit more detail? In particular, what OS
>>and what version of LabVIEW? If you are running WindowsNT with
>>LabVIEW 6.0, a simple upgrade to LabVIEW 6.0.2 may do the trick.
>>
>>Other questions:
>>How is your main (the executable) "delivering" the data to your new
>>program?
>>Or is the new code an addition to the main VI (ie we're only dealing
>>with one VI)?
>>Is there any more information you can provide about the error? Any
>>additional message that comes with the error?
>>
>>Kent
>
>
0 Kudos
Message 4 of 5
(2,855 Views)
Ahh, now that's a detailed description. Sounds like a pretty complex application you have there. Since the app runs fine without your array/graph add-on, that must be where your problem lies. Since access violation errors are so vague, I would try isolating the issue further.

Try simply removing the graph and just display your data in array format. If you don't get the crash after removing the graph, the problem must be related to your video card driver. You can then try modifing the acceleration setting in the windows display properties. Set the value to "none".

There are also some issues with arrays in LabVIEW 6.0 that have been fixed in LabVIEW 6.0.2. I've attached the changes.doc file. Take a look at it and see
if any of the changes apply to your program.

Finally, I'd also try isolating your array/graph portion by writing a separate VI and using a dummy 12*54*300 sized array.

These errors can be very tough to troubleshoot. Good luck!

Regards,

Kent
0 Kudos
Message 5 of 5
(2,855 Views)