R
Dear List, We have two customers with a bug in FactoryLink ECS 6.5.0. The FactoryLink clock does not correctly recognise the North American spring-ahead time change that occurred on 2001-04-01, i.e., EST to EDT. The FactoryLink clock is one hour behind (even though the underlying Windows NT PC clock is correct). The temporary workaround is to set the PC's clock one hour ahead. This is not a satisfactory fix, since other applications on the PC may be out of synchronisation and also the bug disappears sooner or later, at which time the clock must be reset. We have customers who have critical systems that require an accurate SCADA clock for data logging and alarm logging to name but two. I think that going into each application and hacking the date / time handling is not a good solution. Is anyone out there a big enough end-user of FactoryLink ECS 6.5.0 to lean on USData to provide a free patch? Does anyone else have a suggestion for an elegant solution with little or no overhead that means I do not have to modify the FactoryLink applications? The solution must not interfere with other programmes' access to the PC clock. Apparently USData does not support version 6.5.0. Their "patch" at this time is to upgrade to 6.6.0 (or 7.0 for that matter). The upgrade to 6.6.0 is free for customers with a support agreement. However, systems would have to be re-validated with a version change. Regards RJ