Can LabVIEW handle fast and large amount of data?

[Brian_Beal]

Hi Ben-

I don't mean to hijack this thread, but I couldn't figure out how to email you directly.  From your comments above, I take it that you think there are issues with the DSC module.  I just want to confirm this, since I did a project a couple of years ago with DSC(8.2), and am still trying to get it to work correctly.  Mainly, it is issues with alarming.  Sometimes they work and sometimes they don't.  Autodeploy doesn't seem to work properly, and I have to redeploy after clearing alarms.  Just let me know if it is me or the product.

Thanks,

Brian

[Ben]

---

Brian Beal wrote:

Hi Ben-

I don't mean to hijack this thread, but I couldn't figure out how to email you directly.  From your comments above, I take it that you think there are issues with the DSC module.  I just want to confirm this, since I did a project a couple of years ago with DSC(8.2), and am still trying to get it to work correctly.  Mainly, it is issues with alarming.  Sometimes they work and sometimes they don't.  Autodeploy doesn't seem to work properly, and I have to redeploy after clearing alarms.  Just let me know if it is me or the product.

Thanks,

Brian

---

THe exact version of LV I can not speak too.

I did see very strange things where values assocaited with an alarm were "stale" and I had to read values twice to get the real alarm value.

Can't speak to clearing alarms.

Running on secure machine (govt) was a nightmare and we resorted to pulling the main network cable to prevent the IT dept from pushing updates while a te4st was running. WE never did figure why but the DSC DB would hang.

AS to performance, I have yet to see a white paper comparing modern SV's access to DS reads of the tags.

I tried reporting the alarm issue but the engineer I talked to thought that was normal.

When DSC was the big thing it had nice features not available in normal LV. These days, it appears to be the red-headed-stepchild. I still support my DSC apps but it has been quite a while since I spec'd DSC for an app.

Ben

[Brian_Beal]

Hi Ben-

Thanks for the info.  I also had to put my alarm value writes into a For Loop and write multiple times for them to take.  I think that I finally determined that 2 times through the loop did it.

As far as performance goes, I can tell you it is sluggish on a modern PC.  I can't give any concrete values, but the operators complained about having to wait for things to happen after selecting a button.  With many other apps going back to LV 6.0, I never had so many problems that could only be attributed to product issues.

Regards,

Brian

[Ben]

---

Brian Beal wrote:

Hi Ben-

Thanks for the info.  I also had to put my alarm value writes into a For Loop and write multiple times for them to take.  I think that I finally determined that 2 times through the loop did it.

As far as performance goes, I can tell you it is sluggish on a modern PC.  I can't give any concrete values, but the operators complained about having to wait for things to happen after selecting a button.  With many other apps going back to LV 6.0, I never had so many problems that could only be attributed to product issues.

Regards,

Brian

---

Sometimes the update rate inside various OPC servers (third party) can be set to improve the update rate as well as the setting for the SV itself.

So I am not alone in this preception....

to contact me remember

"I drive NI Support to drink" >>> bar@dsautomation.com

Ben