Error Problem on RSLogix RSEmulate 5000

alpine · Mar 3, 2012

I use RSLogix RSEmulate 5000 V19 and I have problem as follows,

1. When I try to download program to AB_VBP-1 , Virtual Chassis, I can not download
because There is an error message

"Error : Controller not in correct mode."

2. Later, I try to fix this problem by removing Emulator Controller ( Slot 1 )
On Chassis Monitor, But I can not remove it because
Chassis Monitor appears dialog box

"ERROR ! The Emulator module currently has faults or is in PowerUp mode.
The module can not be romoved in this state."

I check Properties of Emulator Controller ( Slot 1), I see that the Emulator Controller is in PowerUp mode

Everyone can suggest me to fix this problem

Thank,

alpine

md.abdullah · Mar 4, 2012

in rslogix 5000 emalutor see there is any red or yellow light is blinking.if red light is there means your module is faulted .right click and clear fault on rs emalutor....if any battery problem is there in your rs emalutor then double click on the particular module and remove all traces then its fine it will works.....have a nice time ....

alpine · Mar 4, 2012

It is battery problem.

To Mr. md.abdullah

It is battery problem because there is yellow light blinking on RSEmulator, I will try to fix this problem as you suggest.

Thank
alpine

alpine · Mar 4, 2012

To Mr. md.abdullah

I try to fix this battery error problem. by click "Remove all traces" Button
but, It does not work. Yellow light sitll blink.

alpine

MichaelG · Mar 4, 2012

post a screen shot of what you are seeing

Use Print screen and Paint and save the image as file type .png

http://www.hoax-slayer.com/creating-screenshots.html

Operaghost · Mar 4, 2012

In the past I have seen this battery issue also. Of course, there is no battery in the Emulator. I read a Tech Note on Rockwell's site that told me to delete and then recreate the RSLinx AB_VPB-1 Virtual Backplane driver. I did that and the problem went away.

OG

alpine · Mar 7, 2012

I will try to fix this problem as your suggest

To everyone

I will try to fix this problem as your suggest. If these methods you suggested can fix this problem, I will tell to everyone immediately.

Thank everyone

alpine

iDeeW · Dec 13, 2012

Hi everybody,
this is my first ever post & new to the PLC world.
I was having the same problem. Did anyone managed to figure this one out.

I follwed this tutorial.
http://www.plcdev.com/a_quick_tutorial_on_rslogix_emulator_5000

Please help

Thank you

pichej · Mar 13, 2013

Been a lurker for a long time, but I accidently found this workaround this morning (after my rsemulate 5k CPU was stuck.. again)

I get this fairly regularly, and found a quick and easy way to fix the program.

The processor gets stuck in startup, and cannot be removed. There's a method involving deleting your VBP in linx, restarting stuff in a certain order, etc etc. Sometimes it clears out the slot, some times it doesn't.

When you get a hung processor.

CTRL-ALT-DELETE. (Bring up the task manager, if it does not come up with C-A-D).
Got to the processes tab, and then "Show processes from all users".

Kill the task Emulogix5868. The hung processor should switch to a red X.

Then you should be able to remove the stuck processor from your VBP rack in the chassis monitor. And add a fresh one.

Hope this saves some heartache.

Cheers, Joe.

fabrizio · May 9, 2013

thanks Joe! It worked for me

Takisawa · Jun 12, 2013

thanks Pichej.... You just saved my day!!.

zacslade · Jan 9, 2015

Sorry to revive an old thread. I was using RSEmulate 5000 and I ran into a battery fault. I tried removing and replacing the processor as instructed here, and it didn't clear my fault. What finally cleared it for me was pressing "clear fault" in the minor fault tab of the controller properties in RSLogix 5000.

Also, for anyone out there who wants to know the details of this error, here's an excerpt from an old tech note:

It will help to start with a little background. Under the hood,
SoftLogix uses the same software that RSLogix 5000 does to
maintain changes made by another workstation. A heartbeat thread
in RSLogix 5000 periodically asks the controller if any changes
have been logged to the change log. If so, it reads those
changes and applies them to the current image.

Likewise, in SoftLogix, there is a separate process, the
SL5KServer, which has the same thread. The engine communications
with its server via IPC and the server communicates to the engine
using normal communication protocols via RSLinx.

Following download, the SL5KServer opens the image sent to the
engine during download and attempts to go online. Similarly,
following a power cycle (or pull/redrop), the server opens an
ACD, downloads it to the engine, and automatically goes online as
part of a normal download. Either way, once the controller has
an image to run, the SL5KServer should be online.

Every 10 seconds, a thread in the engine asks the server if it is
still online. If it is not, then the engine turns the battery
LED ON (RED) and sends a command to the server to ask it to try
to go online. If the battery LED was not already ON, it also
logs a battery fault. If communications are just busy, the LED
may go RED and then when the comm thread has more time, it may
eventually turn green again. This thread checks every 10 seconds
even if persistent storage save is disabled, since a save will
still occur at powerdown.

Every time interval, the thread referenced above in the engine
will also ask the SL5KServer to perform a save.

Following this, it should be clear that anything that would cause
RSLogix 5000 to go offline will also cause the SL5KServer to go
offline (and hence turn the battery LED RED). A few
possibilities:

Comm thread in engine not responding for 32 seconds.
Any RSLinx communication problem (including a crash).
Loss of communications with the engine.
Loss of correlation.

In addition to these possibilities, the following cases will also
cause a RED LED:

Fatal exception in SL5KServer (including RSLogix 5000
support DLLs).
Any serious error that occurs in the save of the archive:
hard disk errors, insufficient disk space, etc.

I hope this helps someone out there!

harryting · Jun 10, 2016

Thanks, solved my issue while I'm still online with RA tech support

AndreyIV · Jul 21, 2020

I faced such problem, additionally to troubles listed above, I could not upload the program downloaded before, from emulator to RSLogix 5000 (disconnected with same error - "persistent memory access")
I found solution for Win7 (in VM):
- Disable UAC (it fixes stuck in "PowerUp" mode)

- Add the emulator directory full path (e.g. C:\Program Files\Rockwell Software\RSLogix Emulate 5000) to the system environment variable “Path” – it rectifies "persistent memory access"

)
Now my emulator works well!
Good luck to all!

Error Problem on RSLogix RSEmulate 5000

alpine

Member

md.abdullah

Member

alpine

Member

alpine

Member

MichaelG

Member

Operaghost

Member

alpine

Member

iDeeW

Member

pichej

Member

fabrizio

Member

Takisawa

Member

zacslade

Member

harryting

Lifetime Supporting Member

AndreyIV

Member

Similar Topics