Service Request Error
You need to be logged in to get access to the forums. You can do so here
|
robert_builder
|
Sunday 05 February 2006 11:11:25 pm |
|
|
Service Request Error
Hi,
I'm having a problem with MVI56-GEC which is Module Fault.
(Code 16#000c)Service Request Error: Invalid mode or state for service request.
could you tell me what's wrong with it?
by the way, I have downloaded the example to ControlLogix and set the correct slot for this Module.
Thanks a lot...!!
Robert.
|
|
jsanders
|
Monday 15 May 2006 3:06:06 pm |
|
|
RE:Service Request Error
The Allen-Bradley support site had the following Tech Notes about that error code:
A70635394 - 1756-MVI CIP Message Error Code 16#000C
Last Modified: 01/20/2004
General Category: s Programmable Controllers
Programmable Controllers - I/O
Product(s): ControlLogix (1756)
Catalog #: 1756MVI
Series / Revision: N/A
Subject (Keyphrases):
Summary of Technote Information:
--------------------------------------------------------------------------------
1756-MVI CIP Message Error Code 16#000C Service request error. Invalid mode/state for service request.
This error code (16#000C) is being returned by the 1756-MVI due to the MVI not being able to process the request at this time; This is similar to receiving a NAK on DH+. The message instructions (CIP Generic) must be slowed down, to give the MVI time to process them. Usually a timer can be used, set for 1 second or greater, to trigger the message instructions to avoid this error code. The actual error code returned to the processor would read "Service request error. Invalid mode/state for service request.".
E111558167 - Message Error Code 16#000C: Service request error. Invalid mode/state for service request.
Last Modified: 03/08/2005
General Category: s Programmable Controllers
Product(s): CompactLogix (1769); ControlLogix (1756); FlexLogix (1794)
Catalog #:
Series / Revision: N/A
Symptoms (Keyphrases): MSG 000C object model conflict
Problem: Message to a module ends with a error and does not complete.
Cause: The message does get the module it is sent to, but the module responds by saying it is in the wrong state to process that message.
Verify:
Cure: Verify module is in the right rack and slot. Then try inhibiting the module and sending the message. Some modules do not allow certain registers to be written to when the module is running.
Prevention:
--------------------------------------------------------------------------------
PROBLEM:
Message error code 16#000C is described in manual as "Object model conflict" and is described in the message window as "Service request error. Invalid mode/state for service request." Neither of these descriptions give a good idea on how to troubleshoot this error.
SOLUTION:
First verify the slot/rack that the module is in. If the message is going to the wrong slot, the module that is in that slot may not be able process the message. If it is the right module and it is in the I/O configuration, try inhibiting the module. Some modules are set up so that you cannot write to certain registers in the module when it is running.
Both these notes point to a ladder logic or configuration error. If you continue to experience this problem, please contact ProSoft Technical Support at 1-661-716-5100 or e-mail a description of your problem and a copy of your ladder logic and module configuration files to Support@prosoft-technology.com
|
