800xA sv6.0.3.1 Windows 10 Engineering Station Freezing at Login Screen
Has anyone experienced a Windows 10 Engineering Station freezing at the windows login screen. The customer is aware that the hardware is not on the supported list. The solution for them is to restart the machine, but it seems to happen on a daily bases. The machine is used to print (through its serial port) the Events to a collection server or Level 3 and so the plant's Level 3 Corporate view is missing events until the restarting of the Engineering station. They are in the process of changing to an OPC connection.
Operator Stations are Thin Clients connecting to an RDS Server and so is not experiencing the problem. All servers are virtualized using VMware ESXi
800xA System version:
6.0.3.1
PC Hardware:
Desktop PC, Acer DT VM2640G, Intel Pentium G4400 , 8GB RAM , 1Tb HDD, Keyboard & Mouse included, Win 7/10 Pro 64-Bit (Acer Part : DT.VMSEA.011)
Operator Stations are Thin Clients connecting to an RDS Server and so is not experiencing the problem. All servers are virtualized using VMware ESXi
800xA System version:
6.0.3.1
PC Hardware:
Desktop PC, Acer DT VM2640G, Intel Pentium G4400 , 8GB RAM , 1Tb HDD, Keyboard & Mouse included, Win 7/10 Pro 64-Bit (Acer Part : DT.VMSEA.011)
Asked 1 year ago
Answers
0
ACER is not a certified computer for 800xA:
https://new.abb.com/control-systems/s...
https://new.abb.com/control-systems/s...
Answered 1 year ago
0
Tbh, 99% of the time its not a major issue if client hardware isn't certified - everything works - but it does mean that no-one is going to spend much time to help track down anything remotely obscure that may or may not be caused by the 800xA software rather than anything else. I would suspect that this is a generic windows / hardware issue rather than an 800xA problem, and a 50/50 guess would point at the serial port unless this is an absolutely standard part of the PC hardware and is fully supported by the PC manufacturer.
I suspect in any case you should be getting rid of the serial port entirely. To capture events through an ethernet port, configure a Windows Printer Ethernet Port and attach a "Generic Text" printer driver to that port. Configure the Alarm Logger Service in 800xA to point at the "Generic Text" printer. The remote system should then be able to read the TCP data stream directly without needing a physical cable or physical serial port.
I suspect in any case you should be getting rid of the serial port entirely. To capture events through an ethernet port, configure a Windows Printer Ethernet Port and attach a "Generic Text" printer driver to that port. Configure the Alarm Logger Service in 800xA to point at the "Generic Text" printer. The remote system should then be able to read the TCP data stream directly without needing a physical cable or physical serial port.
Answered 1 year ago
by backdraft
What means freezing? Can it still be accessed from Network e.g. RNRP up? Any Errors in Windows event log? When does it happen, could it be related to any Power saving setting?
Add new comment