by
shaun78 » Tue Sep 10, 2013 12:07 pm
I can't believe that this software can be validated.
Don't worry; it can't be validated.
Several years ago I worked for a company that purchased the validation scripts from PE. PE's scripts, executed internally because they wanted something like $30,000 to simply execute the scripts.
I am very competent when it comes to software validation. I am also a chemist that has been performing method development and validation activities for the past 10+ years. The point being, I know how to validate software and how to use a CDS.
There was barely a validation script from PE that I did not have a significant deviation to. Some scripts required extensive modification of both PE and Windows *.ini files in order to get them to execute properly. The modification of these files then had to be reverted back to the original state otherwise other portions of the software would not function properly. Other scripts simply outright failed. Others could not be verified at all. Finally, a handful can not be executed as written otherwise they will fail; all techs know this, deviate from the script, and don't document it.
As a result of what I discovered from this, we started purchasing another manufacturer's equipment and CDS.
I really hate blatantly speaking badly about another company in this manner, but PE simply is not worth any amount of time you have to invest into their products.
Your comment about on-screen results and printed results being different makes me laugh; Or reprocessing generates different results. Can't tell you how many times that little problem drove me up a wall. Yeah, it's a real problem and it is not unique to you or your setup.
Someone here also mentioned about not being able to open a data file due to invalid data points. I can't tell you how many hours I spent on the phone with PE tech support trying to resolve this one. The bottom line is if a data file ends in odd number of data points, this causes some sort of magical catastrophic division by zero, which produces the invalid data point error. The "fix" is to simply add a fake data point to the file via a text editor ... or delete a data point from a file.
The lack of of speed with TCCS is mostly likely because, at the end of the day, all your communication is running through a telephony Lantronix terminal server, which uses a data rate of 9600 baud. It simply will not be fast; it can not be fast.