The OPC server in Window 2000. Can't browse the items.

[JYC]

Hello, I have some confusion about the FieldPoint OPC server in Window 2000.

I am using FieldPoints 3.0 OPC server and Wintech' OPC client from www.win-tech.com.

1. I have both work together as expected in Window NT4.0

2. In Window 2000, my Win-Tech based OPC client can connect to the OPC and I also can add a group. But I can see any items in my OPC client.

Here I tried something and the results make me more frustrated.

. My Win-tech based OPC client can browse some other OPC servers correctly,
. Some other OPC browsers like ICONICS's tag browser can browse the FieldPoint OPC items.

I know there will be lots of figure-pointing here. I wonder if there is a tool out there can help me
out.

Jim

[steven@ni]

Jim,

When you install Fieldpoint Explorer 3.0, there are several other software programs installed:

Fieldpoint OPCServer
Logos (a proprietary protocol) which includes:
-time services
-citadel services
-classified services

The Fieldpoint OPCServer uses standard OPC protocol. If you have any type of client (that is OPC 1 or 2 compliant), then you can communicate with the OPC Server.

If you are unable to browse the server, please make sure that the client is OPC compatible.

If you have any other questions, please let us know. Thanks.

[JYC]

Steven,

Thanks for the response. But is there any tool of testing OPC lient whether or not it is OPC compatible ?

Jim

[steven@ni]

The best way to determine OPC compatibility is to contact the vendor of the software. I have looked at the win-tech site and the opc client that they offer is OPC 1 and 2 compliant. It even supports browsing and any other necessary capabilities. It should support the functions you are trying to implement.

[Aaron_G]

Jim,

Obviously finger pointing does not get us anywhere and does not get you up and running, so let's look at the facts.

1) The Wintech OPC Server with FieldPoint Explorer 3.0 works correctly under Windows NT.
2) The Wintech OPC Server with FieldPoint Explorer 3.0 does not work correctly under Windows 2000.
3) The Iconics Browser works correctly with FieldPoint Explorer 3.0 under Windows 2000.
4) The Wintech Client can browse some but not all other OPC Servers correctly under Windows 2000.

Taking a look at the facts above, the probable assumption is that the cause for the failure is from the Wintech OPC client.

Some additional things to consider:
1) There is a test client availble from National Instruments for downloading. I do not remember wh
ere the software is on the ftp site but if you email National Instruments Tech Support, they should be able to tell you.
2) The OPC Foundation (www.opcfoundation.org) has a OPC Server test tool (and maybe a client test tool as well). I do not know if there is any cost for these tools.
3) Try different permission settings while testing (e.g. admin vs power user vs regular user). On Windows 2000/NT machines there are sometimes problems with permissions.
4) Run DCOMCNFG to make sure that the permissions for the OPC Server are set-up properly.
5) The names do not change when you are on Windows NT vs Windows 2000, even though you may not be able to browse, you should still be able to manually enter the name of the tag and link to it.

Regards,
Aaron

[JYC]

Aaron,

Thanks for the tips. Unforunately, there is no Standard Client test tool at OPC Foundation site.

And I think that FieldPoint OPC must have something different from the other OPC servers since the Win-tech OPC client can browse all of them ( as I tested ).

Can NI do some investigation on this ?

Actually, you only need to download the demo from Win tech. You can try on both NT and the 2000. You will be surprised.

[Aaron_G]

Jim,

There is a freeware OPC Client at www.matrikon.com. They also have a utility called the OPC Delegator that will insert itself between the OPC Client and OPC Server and pump out a log file of all the calls.

I used the OPCDelegator program to log the calls from the WinTech OPC Client, LabVIEW and the Matrikon OPC Explorer program. Comparing the log files, I was able to find the problem and it is in the WinTech OPC Client. The WinTech client is using the function ChangeBrowsePosition(), setting the direction as down (3 options; up, down or goto), and passing the szString parameter of [FP Res\FP-AI-110 @2]. The problem with this is that is previous called the ChangeBrowsePosition(O with [FP Res], this means that it is now in the [FP Res] brach and the
next branch would be [FP-AI-110 @1]. Instead, the FieldPoint OPC Server thinks that they are trying to connect to [FP Res\FP Res\FP-AI-110 @1]. Their client should either a) use dwBrowseDirection=3 (goto)
b) do a dwBrowse with direction=2 and szString [FP-AI-110 @1]
c) do a dwBrowse to the root (direction=1) and then a dwbrowse down (direction=2) to the szString [FP Res\FP-AI-110 @1].

So in conclusion, talk to WinTech regarding their browse as it is not conforming with the specs. If they provide contact information, I can send the log files highlighting the problem.

Regards,
Aaron

[JYC]

Aaron,

Thanks. Evetually, we found the evidence. Their contact information is support@win-tech.com. By the way, can you send me the log file ?

[Aaron_G]

Jim,

I sent the appropriate information to Win-tech. Here are the 2 log files.

Regards,
Aaron

[??]

sir:
I meet the same problem as you described,would you be
so kind to let me know your solution to that problem in the end? my e_mail is yue_qi_qi@sohu.com.
thank you.