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

The BATT LED on my ProSoft MVI module is RED. How can I fix this problem?

Viewed 1 times since Wed, Nov 29, 2006

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

Viewed 1 times since Wed, Sep 24, 2014

When using an MVI69-xxx or PS69-xxx module, why does a L43/L45 CompactLogix processor fault immediately after a download or after a power cycle?

Viewed 1 times since Mon, Jan 18, 2010

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

Viewed 1 times since Thu, Jan 10, 2008

What are Optional AOIs and do I need them?

Viewed 1 times since Tue, Jun 7, 2016

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

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

Viewed 1 times since Fri, Oct 10, 2008

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

Viewed 1 times since Tue, Nov 28, 2006

IEC-60870-5-104 Server Tutorial

Viewed 1 times since Mon, Sep 3, 2012

Using CIP Connect with the Lite (free) Version of RSLinx Classic

Viewed 1 times since Mon, Jun 22, 2015