LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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



@cs42 wrote:


@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...) Smiley Sad

Cheers,
Carsten


Can you tell me why you think DSC is unusable?  Maybe I can help you with something.
Regards,
Robert
Message 11 of 32
(5,236 Views)

There is another warning when I launch it:

GetRemoteEngineInfo.vi
    - The shared library expected to be at "C:\WINNT\system32\lksock.dll" was loaded from "lksock.dll".

Robert,

could you send the un-protected version, if there are not any problem ?!

Thanks

Bye

Elio

0 Kudos
Message 12 of 32
(5,229 Views)


@HeliosRight wrote:

There is another warning when I launch it:

GetRemoteEngineInfo.vi
    - The shared library expected to be at "C:\WINNT\system32\lksock.dll" was loaded from "lksock.dll".

Robert,

could you send the un-protected version, if there are not any problem ?!

Thanks

Bye

Elio



Saving the VI should get rid of the warning (I wrote this on an old test machine) so some of the paths may be off.  Although I accidentally uploaded IterateLevel.vi unlocked I would prefer to leave the main VI locked.  It contains some priviledged information.  I will be happy to look into any issues you find (time permitting.)

 

Regards,
Robert
Message 13 of 32
(5,221 Views)

REM1 wrote:

Can you tell me why you think DSC is unusable?  Maybe I can help you with something.
Sure I can: with the LV DSC 8.0 Run Time System I don't have a tool like the Tag Engine Editor anymore, where I can setup logging to a database without ever editing/writing an application in LV! That I need a process name now to access a Tag is no problem (I have some workarounds in mind) but the missing Tag Engine Editor is (and currently I don't have much time to write my own!).

I know that this is a quite "harsh" statement, but we really looked forward to LV 8 and now we're quite a bit dissapointed, that it isn't easy to use for us in the lab!

Cheers,
    Carsten

Message Edited by cs42 on 03-21-2006 08:21 AM

0 Kudos
Message 14 of 32
(5,212 Views)


@cs42 wrote:

REM1 wrote:

Can you tell me why you think DSC is unusable?  Maybe I can help you with something.
Sure I can: with the LV DSC 8.0 Run Time System I don't have a tool like the Tag Engine Editor anymore, where I can setup logging to a database without ever editing/writing an application in LV! That I need a process name now to access a Tag is no problem (I have some workarounds in mind) but the missing Tag Engine Editor is (and currently I don't have much time to write my own!).

I know that this is a quite "harsh" statement, but we really looked forward to LV 8 and now we're quite a bit dissapointed, that it isn't easy to use for us in the lab!

Cheers,
    Carsten

Message Edited by cs42 on 03-21-2006 08:21 AM


I don't consider your statement to be particularly harsh.  While I am not on the DSC development team I have a soft spot in my heart for the product and want to ensure it's success.  With that in mind, and understanding that the user-friendliness may not be all that was hoped for, are you familiar with the Variable Manager in LabVIEW 8.0?

This utility is available with the DSC 8.0 Run-Time, although not friendly to find.  It can be located at <installation directory>\National Instruments\Shared\Variable Manager\8.0.  This utility can be used to create and configure shared variables in the run-time.  This includes configuring all the DSC related functionality such as logging.

To create a new process use the menu item 'Edit>>New Library'.  Then you can highlight that process and use the menu item 'Edit>>New Variable' to create a new variable.

There are issues dealing with library files (the things that replace scf files) but these are being loooked at.

I don't know if this helps you at all but I wanted to make sure you knew about it.

Regards,
Robert
Message 15 of 32
(5,201 Views)

REM1 wrote:

This utility is available with the DSC 8.0 Run-Time, although not friendly to find.  It can be located at \National Instruments\Shared\Variable Manager\8.0.  This utility can be used to create and configure shared variables in the run-time.  This includes configuring all the DSC related functionality such as logging.

To create a new process use the menu item 'Edit>>New Library'.  Then you can highlight that process and use the menu item 'Edit>>New Variable' to create a new variable.

There are issues dealing with library files (the things that replace scf files) but these are being loooked at.

I don't know if this helps you at all but I wanted to make sure you knew about it.



That's good news! Smiley Very Happy Unfortunately in former threads nobody mentioned this... Smiley Mad

I'll have a look into it and maybe then we'll be able to switch to LV 8.

Thanks a lot!

Cheers,
    Carsten
0 Kudos
Message 16 of 32
(5,188 Views)
One problem: I can't find a way to define a database to log to in the Variable Manager! Where do I define where to log to?

Carsten
0 Kudos
Message 17 of 32
(5,189 Views)


@cs42 wrote:
One problem: I can't find a way to define a database to log to in the Variable Manager! Where do I define where to log to?

Carsten



Gaaaaaah!  You can't.  I'll look into this and post something in a day or so.
Regards,
Robert
0 Kudos
Message 18 of 32
(5,162 Views)

Do you have your configuration saved in a library file?  I know you said you didn't want to do any programming in LV, but I have a work-around if the configuration is saved to a library file and I don't if it is not.

Message Edited by REM1 on 03-27-2006 02:41 PM

Regards,
Robert
0 Kudos
Message 19 of 32
(5,158 Views)


@REM1 wrote:

Do you have your configuration saved in a library file?  I know you said you didn't want to do any programming in LV, but I have a work-around if the configuration is saved to a library file and I don't if it is not.

Message Edited by REM1 on 03-27-2006 02:41 PM


Not yet! I just looked at the Run Time Engine to decide whether we can work with it. So once we decide to move to LV 8 I might save the configuration in a library file. I think the most important thing is, not to have to use the development environment to configure tags and to change the DB to be logged to! If I have to do a basic configuration in the development environment which I can change later use the RTE, I think we could live with that...

But maybe it's much easier to write a small application which attaches a database to a process? I can tell a shared variable to be logged in the variable manager at least, as far as I see...

Thanks for your help. It's greatly appreciated!

Cheers,
    Carsten
0 Kudos
Message 20 of 32
(5,145 Views)