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

Apparent data corruption in 33 words of MVI56-MCM or MVI56E-MCM ReadData or WriteData arrays.

Article Number: 182 | Rating: 5/5 from 1 votes | Last Updated: Thu, Jul 17, 2014 at 4:22 PM

In your controller tags, if MCM.Config.ModDef.ErrStatPtr is 0, then status data is likely overwriting the first 33 words of the MCM's ReadData or WriteData arrays which would typically be used for Modbus data.

Enter a value of -1 for this variable if status information isn't being used. If it is being used, then enter a value that corresponds to an unused Read Data address. Toggle the MCM's warmboot tag for this change to take effect.

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

What is the difference between your MVI56E-MCM and MVI56E-MCMR modules?

Viewed 1 times since Tue, Jan 23, 2007

Which of your products support RS-485 serial protocols?

Viewed 1 times since Wed, Feb 6, 2008

Where is the configuration for the MVI56(E)-MCM?

Viewed 1 times since Wed, Jul 9, 2014

How to configure more than 100 commands per port when using an MVI46-MCM, MVI69-MCM, or the MVI56-MCM as a Modbus master?

Viewed 1 times since Tue, Nov 28, 2006

When I increase the ReadData or WriteData array sizes in my program, all of the configuration parameter values go to 0.

Viewed 1 times since Tue, Nov 28, 2006

What is the purpose of the UseGuardBand/GuardBandTime or InterCharacterDelay parameters in an MCM module?

Viewed 1 times since Tue, Nov 28, 2006

Which ProSoft products can communicate with a Honeywell DCS System?

Viewed 1 times since Tue, Jan 22, 2008

What is the difference between the MVI56-MCM and the MVI56-MCMR?

Viewed 1 times since Tue, Nov 28, 2006

How to avoid slow data updates on a Modbus network with an MVI56(E)-MCM or MVI69-MCM when some Slaves are either not on-line or not functioning correctly?

Viewed 1 times since Wed, Mar 19, 2008

I was not using both Modbus ports on my MVI56-MCM module, so I set all the port parameters for the unused port to zeros to disable the port and now my module is faulted and will not restart. Why?

Viewed 1 times since Tue, Nov 28, 2006