jreimerddauto
Member
Hi All,
The factory I am at has a certain line using 2 separate Dynics HMIs running W7 Pro x64 FTView ME 6.10.00.9 CPR 9 SR 4.
We resumed from shutdown and one of the HMI's was unable to load it's application, the other was doing fine.
We did the following:
rebooted the HMI
POR'd the whole line
changed the problem-HMI out for a "new" Dynics HMI (Same type)
put a previous backup of the same HMI application on the HMI
and still had the same problem, and then one of the maintenance guys fixed it by changing some settings (wasn't informed on the specifics) and stuck a re-built runtime file on the HMI and in the HMI's "Startup" folder.
All was well and good for about an hour.
Then the 2nd HMI screen had the same problem, and the same method hasn't fixed it.
It is weird because it's the same problem on 2 different HMI's occurring at 2 different times, and the same steps we used to fix #1 won't fix #2.
Anyone run into this problem before, or have an idea?
Fortunately, the broken HMI is low-priority.
EDIT: We have tested the runtime file on multiple laptops in FactoryTalk Studio and it runs fine. The HMI system has more than enough storage and RAM.
The factory I am at has a certain line using 2 separate Dynics HMIs running W7 Pro x64 FTView ME 6.10.00.9 CPR 9 SR 4.
We resumed from shutdown and one of the HMI's was unable to load it's application, the other was doing fine.
We did the following:
rebooted the HMI
POR'd the whole line
changed the problem-HMI out for a "new" Dynics HMI (Same type)
put a previous backup of the same HMI application on the HMI
and still had the same problem, and then one of the maintenance guys fixed it by changing some settings (wasn't informed on the specifics) and stuck a re-built runtime file on the HMI and in the HMI's "Startup" folder.
All was well and good for about an hour.
Then the 2nd HMI screen had the same problem, and the same method hasn't fixed it.
It is weird because it's the same problem on 2 different HMI's occurring at 2 different times, and the same steps we used to fix #1 won't fix #2.
Anyone run into this problem before, or have an idea?
Fortunately, the broken HMI is low-priority.
EDIT: We have tested the runtime file on multiple laptops in FactoryTalk Studio and it runs fine. The HMI system has more than enough storage and RAM.
Last edited:
