LabVIEW
DSC module
Chances for a DSC 64-bit version are practically nihil. Many of the components in the DSC Toolkit are very old and completely legacy technology by modern standards. Some also are pretty much impossible to run securely on modern OSes, and I'm sure you would not be happy to have to run an old version of Windows 10 in order to use several of the features in the DSC Toolkit.
Making the DSC Toolkit fully secure and compatible to the latest and greatest standards would pretty much require a total rewrite of large parts of that toolkit and use of various new components that require additional license deals with parties like Microsoft and many others. It would mean that the Toolkit would need to cost a manifold of what it cost in the past to be even close to covering its development and maintenance costs. Basically it's a proposal already dead on arrival.
If you feel that LabVIEW is only usable for you with a modern DSC Toolkit, that is your personal right. Many users including me haven't looked at the DSC Toolkit in at least 15 years, so everyone's mileage varies.
@rino.stringola wrote:
Is there an alternative to DSC? I mean I/O scaling, automatic data logging, and trending of variables from historical and real-time databases.
As santo said, it would probably turn into creating something yourself. The issue with the DSC Toolkit is that attempts to be an "egg-laying wool-milk-pig" (to translate a German noun) by doing a myriad of things but non really in a very perfect way. For most applications it ends up cheaper to reimplement the few things that the application needs than paying for the DSC Toolkit in the long run. And the DSC Toolkit is not easy at all. It comes with a significant effort to configure everything in a way that is often hidden and hard to figure out later. It is based on the Lookout technology that NI acquired back in a far away past and adapted to the LabVIEW workflow without the pretty amazing philosophy of Lookout. But Lookout didn't make it either and was eventually gutted by NI as they considered it a support burden with to small market to pay for its maintenance and further development.
Basically, if the application is fairly simple, implementing it directly in LabVIEW is usually quicker. If it is really complicated, keeping the overview in a LabVIEW DSC system is going to be a nightmare compared to implementing it from scratch, provided the developer has some good LabVIEW experience.
