LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ABB SattLine OPC

Hi Kabul,

Still have not found any solutin to this. I attached the image, something is wrong with the

website configuration on our sever i guess, why it cannot be accessed.

Here is another link, hope this works. In the background you can see

how nicely the Server Explorer is connected and reads the data from the ABB server

while in the front Lanview crashes....

regards

Zoltan

http://www.flickr.com/photos/13534209@N02/1381389959/

 

0 Kudos
Message 11 of 20
(7,279 Views)
Hi Zoltan,

Is is possible for you to get in touch with the Field Engineer of your area and request of a copy of DSC 8.5 for evaluation purposes? If not, give me your first, last name and the name of your organization and I will try to get in touch with the Field Engineer.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 12 of 20
(7,206 Views)

Hi Adnan,

thanks for the reply. I have requested already for evaluation a copy of DSC 8.5. In principle as far as I know

our university has a continuing license with NI. Hope to have access to this soon, and see if this solves my problem...

I am afraid though that I could still miss something in the OPC syntax too, since althoug with some of the OPC clients

I have no access to communicate with the ABB server (MAtrikon, NI Server Explorer) I also have problem to access

it from Matlab, too...

Regards

Zoltan

0 Kudos
Message 13 of 20
(7,195 Views)
Hi Zoltan,

I am not able to understand this correctly. Are you able to access the ABB OPC server from other clients? I have seen the image where you were able to access it from the NI Server Explorer. What exactly do you mean when you say you have no access to communicate with the ABB server with some OPC clients?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 14 of 20
(7,110 Views)

Hi Adnan,

Sorry for the confusion. Yes I am able to access the ABB server if I use

developed clients, e.g. NI Server Explorer and Matrikon OPC Explorer.

With these two I have no problem communicating with the ABB server.

When I try to develop my own code based on the Labview opc.dll examples

or the procudere using the DSC module (via shared variables) then the problems appear.

What I meant last time is that if I try to access the ABB server in MAtlab for example using

the basic matlab OPC toolbox, I cannot do that either, which makes me believe that

there could be some special syntax issue in this case, which obviously does not

creat any problem however for the standard clients (NI Server explorer/Matrikon).

This could be a second issue, however what is clear now If I use the labview examples from

the opc.dll labview crashes or if i use the DSC 8.0 I do not see the tags...

I am still trying to get DSC 8.5 and see how that will behave.

Regards

Zoltan

 

 

 

0 Kudos
Message 15 of 20
(7,097 Views)

Hi,

I have now Labview 8.5 and DSC 8.5 installed, but unfortunatelly despite all my hope

everything behaves the same as I desctibed before when I used labview and DSC 8.0, that is

1. NI Server explorer works perfectly I can connect read and write data.

2. If I try the datasocket VIs, I can see the server, see even the tags but when

I click on the tag Labview crashes (both 8.0 and 8.5)

3. With the DSC (both 8.0 or 8.5) using the shared variable method, I can see the server when

I add the new OPC client (this is the ADS.OPC.2 server on the figure below: error 10).

But when I add the new variable and want to browse the server I cannot see anything.

The second figure below (error 12) shows how the browse widow looks like. The untitled library 2 is

the one corresponding when I added the ADS.OPC.2 server. This is empty, nothing is showing

just the default staff from Labview, but no tags from the actual server, whereas when I did

the same procedure with the Matrikon server I can nicely see the tags (Untitled libray 3 --> simulated itemst).


http://www.flickr.com/photos/13534209@N02/?saved=1


Any suggestions would be very highly appreciated at this point.

 


Thanks

Zoltan

 

 


 

0 Kudos
Message 16 of 20
(6,707 Views)
Hi Zoltan,

I am not trying to sound obtuse over here but I notice that you have kept the Server Explorer open in all your images while trying to interact with LabVIEW. Can you try closing the Server Explorer (and any other OPC Explorer) before you use LabVIEW. Do you still get the errors?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 17 of 20
(6,620 Views)
Hi Zoltan,

Do you have any updates on this? If you are still facing issues, please be sure to let me know.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 18 of 20
(6,059 Views)
Hi,
 
Thanks for everyone who helped. After a few weeks of tests finally it seems
that the problem was a "simple" configuration problem in the ABB OPC sever
side. I still do not understand how the NI Server Explorer and the Matrikon OPC
Explorer were able to communicate without any problem when the Labview VIs
were not. But what is important that my original code works now very robustly.
And the error clearly and reproducably were in the configuration file for the server.
I use the Datasocket vis, but it appeared that the DSC worked as well both in
8.0 and 8.5 (have not done extensive tests yet since I am happy with datasocket).
 
Thanks again for the help
Zoltan
0 Kudos
Message 19 of 20
(5,627 Views)

Hi Zoltan,

 

Do you recall what changes were necessary in the ABB configuration to resolve this issue?  I am working with a similar problem with ABB OPC.

 

Regards,

 

Steve

0 Kudos
Message 20 of 20
(1,711 Views)