| Home » Categories » Rockwell In-chassis » ControlLogix » MVI56 Series |
"Invalid Input Size" when adding an Prosoft module to RSLogix 5000 |
| Article Number: 225 | Rating: Unrated | Last Updated: Tue, Jul 1, 2014 at 6:26 PM |
|
Confirm that the Comm Format parameter in the modules I/O configuration is set to Data - INT. The default setting for this parameter in RSLogix5000 is Data - DINT. This setting will generate the error message mentioned above. If the incorrect comm format is set, the only way to correct this is to delete the module from the I/O configuration and add the module using the correct Comm Format.
|
Attachments (0)
There are no attachments for this article.
|
Comments
There are no comments for this article. Be the first to post a comment.
|
The BATT LED on my ProSoft MVI module is RED. How can I fix this problem?
Viewed 1 times since Wed, Nov 29, 2006
My ControlNet network shows a maximum usage value of 99.61% when an MVI56-XXX or MVI56E-XXX is in the rack, why is this?
Viewed 1 times since Fri, Oct 15, 2010
What is the backplane current draw for MVI56, MVI56E, MVI69, MVI46 and MVI71 modules?
Viewed 1 times since Thu, Jan 10, 2008
Debug port connection parameters for Prosoft modules and gateways
Viewed 1 times since Tue, Nov 28, 2006
I upgraded my RSLogix5000 software from an older version to Version 16 and now the clock in my MVI56 module does not seem to show the correct time. Why not?
Viewed 1 times since Tue, Oct 14, 2008
What is the heat dissapation for MVI56, MVI56E, MVI69, MVI46 and MVI71 modules?
Viewed 1 times since Thu, Jan 10, 2008
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
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
Why do I have a yellow question mark in the RSWho window or in RSNetworx for my MVI56 Series module?
Viewed 1 times since Tue, Nov 28, 2006
I have an In-Chassis module, and am seeing a type mismatch shown in the module properties. What is the issue?
Viewed 1 times since Fri, Apr 27, 2007
|

Add Comment