KB Home \| Advanced Search \| News \| Ask Question
ProSoft Knowledge Base

I have an In-Chassis module, and am seeing a type mismatch shown in the module properties. What is the issue?

Article Number: 335 | Rating: 2/5 from 3 votes | Last Updated: Wed, Jul 9, 2014 at 9:38 PM

The type mismatch error is always shown since the ProSoft In-Chassis modules do not support the additional functionality required to respond to this inquiry from the processor. This field does not reflect the status of the ProSoft In-Chassis module, and does not have any impact upon the ability of the module to function.

Custom Fields

Attachments (0)

Attachments

There are no attachments for this article.

Comments

Comments

There are no comments for this article. Be the first to post a comment.

Related Articles

Can the MVI56-WA-EIP be used to acquire I/O data from a ControlLogix CPU from a remote rack?

Viewed 1 times since Wed, Feb 6, 2008

IEC-60870-5-104 Server Tutorial

Viewed 1 times since Mon, Sep 3, 2012

When saving a project including a ControlNet network in RSLogix5000 v18, a warning message appears - "Warning: Failed to create new device in ControlNet project file. Generic module cannot be created." What does this mean?

Viewed 1 times since Tue, Jul 27, 2010

Where do configuration files get stored on the MVI56E platform?

Viewed 1 times since Mon, Jul 7, 2014

Are the Ethernet port(s) Auto MDI-X ports?

Viewed 1 times since Wed, Sep 24, 2014

What RSLogix 5000 function will indicate whether a Prosoft module is present and functioning in the ControlLogix chassis?

Viewed 1 times since Tue, Nov 28, 2006

What is the heat dissapation for MVI56, MVI56E, MVI69, MVI46 and MVI71 modules?

Viewed 1 times since Thu, Jan 10, 2008

"Invalid Input Size" when adding an Prosoft module to RSLogix 5000

Viewed 1 times since Tue, Nov 28, 2006

RSLogix 500 sample for MVI69-xxx faults MicroLogix processor

Viewed 1 times since Tue, Nov 28, 2006

My MVI69 module is not working. What might be wrong?

Viewed 1 times since Fri, Oct 10, 2008