DSC Engine

[Margolin Igor]

Hi!
I have project with 1500 tags in Labview DSC 6.1 I have problem with DSC Engine.exe After two day work, the memory usage of DSC Engine increase up to +5 Mb, after 7 days - +15 Mb. From the engineer of NI I got recommendation: increase parameters of Engine in the tag configuration on 2000 while my problem isn't disappearance. At fact, now I am having 450000, 450000, 450000, 450000 and 60 second for the close Engine.
Please, advise how can I resolve this issue?

[unclebump]

Have you applied the latest fixes for that version??

http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/513aa4a0bb60d10086256b48006d44b5?OpenDocument

[Ricardo_SR]

Hello,

Does this happen with only this VI or does it happens even with the shipping examples at a lower scale?
Are you opening multiple times the tag monitor?


Ricardo S.
National Instruments

[Margolin Igor]

Hello!
Of course, I apply the latest fixes for that version before started work. Labview is installing on the OS Windows XP with Service park 1.
I tried turn off Labview application without turn off DSC Engine.exe, so the situation is repeat. I realized some experiments in the tag configuration such as: disable log events and log data some tags, absolute disable log events. In fact, I’m having a group in the project which has update rate 1 sec. At last, I tried created a few groups with difference update rate (1,2,5,10 seconds), unfortunately situation with DSC Engine isn’t change. Maybe DSC Engine have installation-specific setting, but I don’t know, how is parameters of DSC Engine dependences from the numbers tags or update rate. Well, in this case I can’t define the numbers tags which I can poll with 1 sec or high zone of deadband. In the documentation I read that DSC Engine is working in the poll mode, but I certainly know that my OPC server is working in event mode, so the numbers tags which are changing little.
What do you think about my problem?

[unclebump]

Can you post your .scf file and your vi??

[Margolin Igor]

Hi!
Well, I'll try to send vi, but there are 63 vi in my project, which VI I must send to you?

[unclebump]

I looked at your vi for a bit. You have several loops with about 25 sets of code that do the same thing and all of the use the build array command. This will use new memory each time it builds the array. At a minimum, try to initialize the array outside the while loops. Feed it into a shift register, and use the replace array subset inside the while loops. Many of the individual cases have the same structure. Could you rearrange the vi to have one piece of code inside a for loop and feed it with several arrays. Also, all of the constant declarations inside the sequences could be done once outside the while loop. One set could be used for most of the sequences.

[Margolin Igor]

Thank you for your reply, but unfortunately I don’t know, how should I do it!
Well, in fact, this is a main (mozhno i general) vi in my project. In this vi operator watch for the work of all system of the building and he can see any parameters of the subsystem. So, I don’t know, how to build code with initialize of the array outside the "while" loop, if in my case the pool of parameters are constantly.
If it's possible, please write an example, that solves this problem or correct my code.
Could you explain me, how do my errors depend from increasing of using of memory by DSC Engine.exe?

[unclebump]

Here is an example of what could be done with all of the write tag vi's outside the while loops. Tag naming with index numbers in the format xxx (tag001, tag002, tag003) and tag groups can help create a block of tags to be written or read. I'll work on some of the other sections, but I'm using 7.0.

[unclebump]

Here is an example of what could be done with the color selection for the round LED's on the front panel. I couldn't find where you set the indicator to true or false. If you only want to change the color, you can use a color box indicator. Normally the color box indicator is square, but it can be customized to make it round. These color boxes can be put inside an array. this would make it very easy to cycle through all 24 of the sequence frames.