sassos

I feel your pain, I had a somewhat brutal education process with DSC a few years ago. It's an amazing tool, but it can be difficult to learn.

You might be using an old version, since you bring up BVE. DSC is an ancestor of BridgeVIEW, and if you're using an old version you might see artifacts. I don't know for sure what BVE is, but there's a chance it has something to do with Bridgeview, since it was often referred to as BV.

You might find it easier to deal with if you upgrade an old version to the latest. Shared variables made DSC far far easier to use. And the latest version of LV allowed you to search for all instances of a shared variable, which is something I did not have when acquiring a huge DSC project with many floating shared variables. Might sound trivial, but being able to see all instances where a global is written is killer on a huge legacy app.

If you are only going to slightly modify it, you need to weigh the various costs of an upgrade. If on the other hand you think you are going to spend more than a couple weeks of full time programming on this, spending the time & money to upgrade to latest LV & DSC will probably be worth it. You'll most likely break the program and need to recode a few things, but the day or two it takes to do that will be worth mountains of saved debugging time.

You are wright, but unfortunately it's not my business to decide for the software upgrade!!

What I need, you say...first of all I need to understand!!

Someone else developed a DSC application which monitors a lot of instruments being part of a complex system, such as demodulators, spectrum analyzers and other exotic machines most communicating via TCP/IP or RS232.

Well, now I need to expand and modify it. I need to understand how the various software components are (necessarily) linked together: which is the role of "BVE", items, channels? and how are they related with the Tag Engine?...

...obviously it's impossible at the moment to ask developer questions!

Hi all,

does anybody know where I can find documentation about DSC? Somethig which explains deelpy concepts like items, channels, I/O points, BVE refnum (what is a BVE???!!!)... and stuff like that!

Thanks.

sassos

Problem solved.

With the DSC Run-Time System on the target PC it works fine.

Bye!

Already done, but trying that I received errors connecting data in input.

Hi Sassos

I mean that: in your source code, instead of using the Polymorphic VI [i.e. Read Traces.vi], use the Polymorphic Member VI [i.e. Read Traces (numeric).vi] instead.

First of all thanks for the answer!

Then, yes, I'm trying to export some data from a Citadel DB and the VI will work on a machine with the labview runtime...and how can I link the VI?

I noticed that in the "VI setting" tab (in the Build Application windows) I can find any VI utilized in the top level VI but the Read Traces.vi is absent.

Furthermore, if at the end of the building process I run the exe and then insert the missing's VI path, it asks me for other stuff in the historical library...

Bye.

-sassos.

Hey Sassos - is that a DSC vi (I haven't used DSC in 7.1)?

I lodged CAR # 243120 for a missing polymorphic in Open Traces.vi.

You can read about it here - its the second issue I raised in the thread - about mid-way down.

Anyways the workaround was to link the actual VI in the code and remove any calls to the polymorphic VI.

Hope that helps?

Cheers

-JG

Hi all,

I'm trying compiling a VI in Labview 7.1 selecting option "Single target file containing all VIs".

The process ends correctly, but when I try to execute the .exe (from runtime folder) it asks me where to find the ReadTreaces(numeric).vi (it is a polymorphic vi).

How do I can fix that?

Thanks!