How can i configure bridgeview and lookout when time response from device is too long?

[PavelRucka]

Hi, every one.
For example when i'm push button to start motor in my lookout application the motor is really started after five minutes.
Which thing or .ini-file can i config when time response from device is too long?
Lookout 5.1 + fixies, logos 4.5, bridgeview 2.1.1.
Bridgeview configure about 2500 tags from ETM - OPC server(ETM OPC Data Access Server, EDV systeme it's a older OPC server from Rittmeyer).
Because this server have too long time response when number of tags is around 1000 and on one computer can be run only one ETM.OPC server a have three computers and import networks tags from two remote computers(when run ETM.OPC server).
Thank for all answers.

Pavel

[Vineet_A.]

Hello Pavel,

How is your Lookout OPC Client object configured? Have you checked the options for "Use Asynchronous I/O" and "Force Refresh After Write"?. Does that seem to make any difference. Have you noticed this large delay with any other data members?

Is it possible to use some other OPC client software to monitor the BridgeVIEW OPC server items? This would be a way of seeing where the delay is taking place. Try to start the motor using the other client software and see if the delay is still around 5 minutes. That will help to point you in the right direction for troubleshooting your code.

One option is to use the NI Server Explorer to monitor OPC items without any programming.

Here's the link: http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/34e67fa9f8ff7a0686256ae60054198c?OpenDocument

If you have any other questions about this, please let me know.

Regards,
Vineet A.

[PavelRucka]

Hello, thanks for your reply.
OPC client read all tags succefly without time delay but when i use write tags (write some number to the device)time delay is too long.

My OPC client is OPC1 type.
I'm now use synchronous I/O and next check box (reconnect automatically is check).
I don't now where i'm looking for "Force Refresh After Write"? This options isn't in OPC client windows.
There are this options too:update rate (100milisec), deadband 1%, poll device, defaul access.
I'm trying use Asynchronous I/O.
I'm use NI server explorer. Server explorer read all tags (quality good) but write tags quality : out of service!
Bridgeview getting error "Output qeueue Overflow". I'm change value in BV engine configuration:"Output queue size from default 2000 to 6000(input qeueu size too) but no efect.
Pavel

[PavelRucka]

Hello,
i'm test device from server explorer.
When i'm OPCETM server device run without delay, but when i'm use bridgeview which read tags from remote bridgeview (use import network tags and open remote sharing file .scf delay is too long.
On remote computer is bridgeview use configurate wizard and import tags from ETM.OPC server.
Pavel

[Vineet_A.]

Hello Pavel,

It sounds like this directly related to your BridgeVIEW software. There were many improvements made to BridgeVIEW since version 2.1.1, and since it's also no longer supported, I highly recommend upgrading to LabVIEW DSC.

I'm a little unclear about your last post. Does it mean that you were able to successfully write directly to the ETM OPC server from Server Explorer, and there weren't any problems with delays or errors?

If this is the case, why not use the Lookout OPC client to directly access the ETM server tags and see if you can start the motor that way.

Is there any reason why you need to go through the BridgeVIEW OPC server at all?

Regards,
Vineet A.

[PavelRucka]

Hello,
i'm must use Bridgeview because ETMOPC server don't work corectly with device through wsr3000 system when system is breakdown or lookout crashed.
Lookout don't see tags from opc server.
When i'm use bridgeview upper the ETMOPC server is everything ok.

Pavel

[Vineet_A.]

Hello Pavel,

You should be able to access your ETMOPC tags from the Lookout OPC client object. Is there any reason why you're unable to do that? It's surprising that Sever Explorer can access them, but Lookout can't.

In Server Explorer, do you still get delays when writing to Bridgeview tags?

Regards,
Vineet A.

[PavelRucka]

Hello,
i'm configurate OPC client in lookout this way:
use asynchronus I/O non check and update rate set to 2000 minisecond.
After this change is delay 2-4 second.
So problem was in setup OPC client in lookout.
When configure bridgeView this way: about 1000tags on server and 700 import network tags on client1 and 600 import network tags on client2. Then read from the device is ok but write some number to the device have delay when update rate is <100 milisecond.
But i'm use:
my OPC server insn't very good.
segment A device 1000points > ETMOPC server > Bridgeview > opc client in lookout
segment B device 700points > ETMOPC server > Bridgeview > BV_import net tags > opc client in lookout
segment A device 600points > ETMOPC server > Bridgeview > BV_import net tags > opc client in lookout

Thank you for your help.
Pavel

[Vineet_A.]

Hello Pavel,

I'm glad everything is working better now.

Regards,
Vineet