Member Login
member
passwd
remember me on
this computer.

- join now -
- forgot username or password? -

Search

Jump to a Date

Sponsored Communities
Cool stuff
Select a topic of interest:
...and press:
Neat Stuff
Control.com Stuff

Visit our shop for nerds in control lifestyle products.

Fortune
You can't carve your way to success without cutting remarks.
RSS Feed
RSS feed Use this link to get an RSS feed of the Control.com article flow, for private, non-commercial use only:
www.control.com/rss/
To get a personalized feed, become a member at no cost.
Select a Page Style
Select one of the following styles:
- BluFu
- Classic
(cookies required)
advertisement
from the Automation List department...
Cimplicity 4.01 on WindowsXP
Human-Machine Interface and SCADA. topic
Posted by MikeWest on 9 January, 2008 - 1:27 am
My question is about building MK-5 HMIs on WindowsXP using the original GE software supplied with the WindowsNT 4 operating system.

We have built several HMIs using WindowsXP and TCI 1.08.02 and Cimplicity 4.01. Everything works just fine for extended periods.

However, we have found that Cimplicity will lose its license anytime the PC configuration is altered. For example, if you go into the BIOS
and change the boot order, Cimplicity loses its license. If you put in a new card (change an arcnet card for example) Cimplicity loses its
license.

I'm curious how many people have done this (Upgraded HMIs to XP without GE involved) and if you experienced this problem?


Posted by CTTech on 10 January, 2008 - 1:23 am
Is the license file completely lost? Do you have to contact GE for an new authorization code or does the existing code allow the licence file to be regenerated?


Posted by Mike West on 13 January, 2008 - 1:30 pm
I have to completly uninstall/reinstall to be able generate a key to re-register from the FANUC web site.

Of course FANUC is unwilling to troubleshoot because they no longer support 4.01.


Posted by CTTech on 15 January, 2008 - 11:43 pm
I believe this problem is associated with the "router" service of Cimplicity during automatic startup.

Automatic startup consisted of loading a Cimplicity screen object before the service objects have time to load.

I am making assumptions on your startup sequence.
Please correct me if I am wrong.

If you are loading a Cimplicity screen during startup i.e. in the Windows startup folder instead of being loaded as a Windows service, the problem may be there.

Instead of loading a Cimplicity screen from the startup folder, try allowing the computer to boot up to Windows and then start the Cimplicity screen.

I realize that this causes problems with automatic screen startup, but it may help find your culprit.

Send more info on your testing.

From Control Engineering magazine...
Related articles from Control Engineering magazine
Above articles copyright 2008 Reed Business Information. Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2008 Control Technology Corporation. All rights reserved.

Users of this site are benefiting from open source technologies, including PHP, MySQL and Apache. Be happy.

Internet Explorer 6.0 Fix

Advertisement
Our Advertisers
Help keep our servers running...
Patronize our advertisers!