Sign in to follow this  
Followers 0
justwhy2003

GX Works 2 simulation, file set error 2400

5 posts in this topic

Hi I am working on an existing project on a Q12H CPU. The original project was created and commissioned using GX Developer and has been running successfully for a number of years. I am now looking to upgrade the project to GX Works 2 prior to adding features to the control system and am in the process of converting to a structured project to download and test to make sure that everything works as usual before adding any code. I have completed the upgrade and can compile the project with no errors (only double coil warnings). I would like to simulate on my laptop but am getting the following error: 2400 File set error (see attachment for screen shot of explanation). It seems like it is automatically writing to the ROM. Is there somewhere I can select which memory to use? As a test I installed GX simulator and tried simulate on the original GX Developer program but see the same error. My laptop is running windows 7 professional 64 bit. Thanks in advance JT

Share this post


Link to post
Share on other sites
File Set error tends to refer to the PLC parameters on the PLC File tab where you can establish file registers. Check the screen and make sure a proper file name was set to allocate file registers. Typically it points to the memory card, but if you do not have a memory card, you may want to turn off file registers.

Share this post


Link to post
Share on other sites
Crossbow Thanks. I checked in the PLC file section and the device initial value area was directed to the device initial value of the program memory. I switched this to not used and the error cleared. However I still get an operational error. Mitsubishi have said that it is probably because I have 8 PIDs in the program. Is there any way to simulate without deleting these? Thanks JT

Share this post


Link to post
Share on other sites
Don't know, never used PID in their controllers.

Share this post


Link to post
Share on other sites
I had the same error. When I downloaded the program to the PLC i did not check all program files. So when the program that was not checked was called the above error apeared.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0