DSC 8.0 : How can I develop a client/server architecture

[HeliosRight]

I've developed a client/server application with DSC 7.1

Now, I'm going to migrate it in DSC 8.0 and I've any problem.

1. How can I load a lvlib from a server at run time ?!

2. How can I get a shared variable list from another computer !?

3. Can I monitor shared variables from differten PCs ?!

Regards

E.G. (Italy - Naples):manvery-happy:

[REM1]

1.  Use the VI 'Deploy Library' to programmatically load an lvlib at runtime.

2.  Does this need to be programmatic, or is user interaction okay?

3.  Yes.  All of the read mechanisms handle reading from remote machines, both for data and alarms/events.

[HeliosRight]

Robert,

1. how can I load different libraries that are in different server/engine ?!

2. I need to be programmatically;

3. Could you transfer me any example ?!

Best regards,

Elio

[REM1]

Elio,

1.  Regrettably, DSC 8 does not provide a simple means for remote process control, only local.  I have attached an untested example (Remote_process_control_example.vi) which should be able to accomplish what you are looking for but it requires that DSC be installed on the target machine.

2.  Regrettably, DSC 8 does not provide a simple means for programmatically determining remote process and variable lists.  I anticipate that this will be added in a future release but I must stress that I am not in a position to be certain of that.  I have not found a reliable way around this yet.

3.  In 7.1, since the tag engine only dealt with a single local process it was sufficient to have only unique tag names.  In 8.0, the shared variable not only has to deal with possibly multiple local processes but remote ones as well.  To accomplish this the shared variable API makes use of URLs much like those associated with the internet, although we rarely have to specify the protocol being used.  Therefore, to read a variable 'baz' in process 'bar' running on machine 'foo' you would construct the following URL \\foo\bar\baz which could then be used by the datasocket read primitive to read the remote value.

Although the DSC development team chose to focus primarily on purely local systems, since this is what all existing customers already had, it is apparent that they, and the LabVIEW team as a whole, have laid the groundwork for further advancements in the remote machine aspects of the product.

I hope this helps.

[HeliosRight]

Thanks Robert,

but these features have not improved the DSC platform, what about it ?!

However, I must to find some solutions for the main problem of my application:

How can I get the "shared variables list" from the remote server/DSC Engine programmatically ?!

Regards

[REM1]

Regrettably, while I suspect this will be available in the future, it cannot be done now.

[REM1]

Ah, never say never.  This VI has undergone only superficial testing.  And I cannot guarantee that it iwll work in future version.  And it is not supported by National Instruments.  And all other possible disclaimers.  But...

The attached VI will allow you to enumerate a remote PCs engine information.

[cs42]

---

@HeliosRight wrote:

Thanks Robert,

but these features have not improved the DSC platform, what about it ?!

However, I must to find some solutions for the main problem of my application:

How can I get the "shared variables list" from the remote server/DSC Engine programmatically ?!

Regards

---

I must agree, that overall the changes to DSC didn't improve it. For us DSC is even unusable now and because of that we can't switch to LV 8!

It has one advantage, though, we can spare the SSPs now, which is quite a bit of money! (But I'd rather have the old DSC Engine for LV 8 including the Runtime-Engine back...)

Cheers,
Carsten

[HeliosRight]

Thanks ... but there is an error : "IterateLevel.vi subVI is missing"

Can you send the complete solution ?!

Best regards

Elio

[REM1]

---

@HeliosRight wrote:

Thanks ... but there is an error : "IterateLevel.vi subVI is missing"

Can you send the complete solution ?!

Best regards

Elio

---

My bad.  Here is the VI.