Rif.: DSC module: crash with OPC UA client il LV 2012

[Tonch]

Hello,

I'm working on OPC UA project in LV 2012. In the client side, under windows 7, I had a crash registering a byte array tag with the "Add Monitored Nodes VI". When the tag was updated, labiew crashed with teh following error:

I discovered the problem: in the server the tag was ByteString instead of Byte Array and I solved in my application. The question of solidity of the software for a common mistake is still present.

Thanks in advance.

Sandro

[FatBoyMonchi]

Hi Tonch,

are you correctly managing the error wire?

Usually a correct error management will make the application more stable.

Hope it helps,

FBM

[Tonch]

For better understanding I attach the example (client windows, server RT). The problem occours when a generic byte array is written into a ByteString type at the server side. Then at the client side a crash happens when the event structure traps the data change.

It is not possible trap the erro before the crash. On my system it crashes any time the array is wrong.

Sandro

[FatBoyMonchi]

Hi Sandro,

in my opinion the first thing to do is to investigate in the error log.

To open it, follow the steps explained at this link:

http://digital.ni.com/public.nsf/allkb/7E9EBE4CA3B6DCE786257633005E7121?OpenDocument

Hope this helps, let me know.

Bye

FBM

[Tonch]

Hello,

I don't know why, but LV last time didn't propose me the error pop-up and the error log folder was empty. May be because I was targetted to the RT environment also?

Now, with the RT server deployed I was able to retrieve the errors.

The MS Win error report:

Problem signature:

  Problem Event Name: APPCRASH

Application Name: LabVIEW.exe

  Application Version: 12.0.0.4027

  Application Timestamp: 50574342

  Fault Module Name: LabVIEW.exe

Fault Module Version: 12.0.0.4027

  Fault Module Timestamp: 50574342

  Exception Code: c0000005

  Exception Offset: 005d1761

  OS Version: 6.1.7601.2.1.0.256.48

  Locale ID: 1033

  Additional Information 1: 4c07

  Additional Information 2: 4c07d344758da30e0b739df670ed1b50

  Additional Information 3: 7dc2

  Additional Information 4: 7dc271b289155588ff44180592900811

The LV error report is attached. I sent it with the automatic sender as report e2d8cb76-200e-467d-8b7b-c64ee1c18893

I discovered that the error occours sending empty regular byte array also.

sandro

[FatBoyMonchi]

Hi Sandro,

looking in the client.vi of the LV example I saw that after the delete monitored nodes.vi, also delete subscriptions.vi and disconnect.vi must be used, linking also the error wire 'till the end and to a simple error handler or an error out indicator.

Maybe that's the reason why you had an unexpected crash.

Let me know if it works! 🙂

Bye

FBM