While using the CX-Programmer V7.2 package from Omron, I wanted to have a play around with the SFC style of programming with a CJ1M PLC. Well, not so easy as it didn't work!
When adding a program section of the SFC type, CX-Programmer completely hung up.
After much digging, it appears that CX-Programmer (or the SFC editor alone, I'm not sure) is built upon the .NET framwork V1.1. Somehow, when the program was run, it was targetting version 2.0 of the framework, and consequently crashing.
The fix I came up with was to force the CX-P.exe program to target the correct framework version.
I should point out that the following was in no way suggested by Omron, or anyone else, and so should be taken at your own risk. OK, that's the disclaimer stuff out of the way...
Using info from this MSDN link...
...I created a file called 'CX-P.exe.config' and placed it into the CX-Programmer directory, ie. "C:\Program Files\Omron\CX-One\CX-Programmer".
Running CX-Programmer now, adding a SFC task to a CJ1M PLC for example, results in the SFC editor springing into life.
The file in question is nothing more than an XML file, the contents being:
1: <configuration>
2: <startup>
3: <supportedRuntime version="v1.1.4322"/>
4: <requiredRuntime version="v1.1.4322"/>
5: </startup>
6: </configuration>
This file forces CX-Programmer to use V1.1 of the .Net framework, and not the one it is (wrongly) using for reasons unknown. So far it appears to be working ok. Like I say, try at your own risk!
It may be that future update fixes this issue, so this is nothing more than a bit of interesting info.
I originally posted this a a thread on the MrPLC forum here.
0 comments:
Post a Comment