dsc write tag.vi no working to update the tag -6553600 status

[RVallieu]

I can not find any information on this status message -6553600.

The tag exists in the .scf file and the engine is running.

Can anyone tell me what this status means? 

Dropping the Tag Status VI does not yield any information - it just says "No Error"

[Robbob]

What version of DSC are you using? It is odd that the Tag Status will not yield any information on the error.  -6553600 is a general error that can mean many things, it must not be related to that specific tag.

[RVallieu]

Customer has LabVIEW 7 and DSC 7.0 I believe.

[unclebump]

Download a demo of kepware to see if another opc client can see the same tag.

www.kepware.com

Also try the NI tag monitor inside the DSC module. Might show some more info.

[RVallieu]

We did run the tag monitor and were able to see values stored there...

What else might this show me?  We know it is not updating.

[RVallieu]

I should also add that the previous system was running BridgeView and this round of upgrades is trying to convert to DSC Toolkit to connect to remote modbus, and FieldPoint devices.

Locally we try to write to a tag and read back the value to make sure we have access to the Server and tags, if this is a go then we initiate a call to a remote system (which seems to be working, as we can call the device and it answers).

Is there an article, etc. that gives recommendations when upgrading from the BridgeView to DSC?

[Robbob]

Take a look at LabVIEW Datalogging and Supervisory Control Module Notes for BridgeVIEW Users

[Ben]

Hi Rob,

I have been asked to help out Ryan with this challenge since I was one of the original developers.

Its a littel complicated but here goes.

In BV 2.1 NI develop a specail version of the Lookout OPC server that exposed "Off-hook" Phone number" and "Poll" which were then mapable to BV tags.

In our app we set Off--hook false, set the phone number tag then wrote a true to the off-hook. This would intiate a dial seq by lookout that would query the widget. This process repeates 24 X 7 for all of the custmers being monitored.

As I understand it, sometime after BV 2.1 NI incorporated these specail changes (off-hook" etc) into Lookout. I don't know which version these function got introduced as part of teh core software dist.

When we watch the tags using server explorer and the tag monitor, there status appears to come up good and the first write to the phone number looks OK along with the first "off-hook=T" starting the dial. But then a check of the "Comm Fail" tag afterwards shows it is true (indicating a problem) and then we see the quality of the tags all go bad in the tag monitor as weel as server explorer.

Those observations were made using LV 7.0 (customer is taking small steps to upgrade).

So what I really need is to contact someone who can help me get the right versions of the Lookout drivers in place taht support the dialing functions.

I'll probably call in thsi AM and log a new call but direct them at this thread so someone may be looking for you.

This app really isn't that complicated aside from its heavy reliance on Lookout to talk to a bunch of widgets. Just reads some tags and right a DB every now and then.

Ben