Troubleshooting Communication Issue with MVI56-MNET Module

Question:

Greetings! I am currently encountering an issue with my MVI56-MNET module, which has been installed alongside an EN2TR module within a subnet of approximately 10. All the necessary instructions have been incorporated into the project, and the MNET module has been assigned a subnet of around 20, connected via a Stratix switch. However, despite the presence of the module's IP address on the network, I am unable to establish communication with it through the Prosoft Builder program. The diagnostic overview does not display the device. My module features one ethernet port and one Cfg port. I am curious to know if this module can only be configured through the Cfg port or if remote configuration via ethernet is possible. Your insights on this matter would be greatly appreciated. Thank you.

Top Replies

ProSoft Technology offers top-notch user manuals on their website, providing valuable guidance for users looking to optimize their experience. Check out their website for more information.

According to FluxCap, ProSoft Technology offers top-notch user manuals that are easy to follow. For more information, visit their website at https://www.prosoft-technology.com. I will give the manual another read to better understand the product.

The MVI56-MNET module, which was replaced by the "Enhanced" MVI56E-MNET over a decade ago, is equipped with four RJ45 jacks. Among these, the top left jack serves as the Ethernet port for Modbus/TCP communications. The topmost jack is labeled "CFG" and functions as a serial port rather than an Ethernet port. To facilitate communication through this port, Prosoft modules have been bundled with an RJ45/DB9 Female adapter for many years. It is my understanding that the CFG serial port is the sole means of transferring a Prosoft Configuration Builder configuration file to the module. The enhanced modules, boasting a single Ethernet port, can be accessed via RSLinx paths, such as through a ControlLogix backplane, thanks to the "CIP Connect" feature, which was particularly relevant during the prevalence of ControlNet.

Ken Roach mentioned that the MVI56-MNET module, which is now considered obsolete, was superseded over a decade ago by the upgraded MVI56E-MNET module. The enhanced version features a single Ethernet port and can be programmed via RSLinx paths through a ControlLogix backplane using the "CIP Connect" feature. The older MVI56-MNET module, on the other hand, is equipped with four RJ45 jacks, with the top one serving as the Ethernet port for Modbus/TCP communications. The "CFG" labeled jack is actually a serial port and requires an RJ45/DB9 Female adapter to connect for programming using Prosoft Configuration Builder software. The CFG serial port is essential for downloading configuration files to the module. While the communication settings are not explicitly specified, it is recommended to utilize RS-232 protocol with the appropriate speed settings. To facilitate the connection, a combination of RJ/DB-9 adapter, RS-232 cable, and MOXA Uport 1150 can be used.

Hi there! Have you made sure the correct IP address has been assigned and also that there isn't an IP address conflict within your network? Sometimes, even though the IP appears on the network, it may not communicate if there's a conflict. Also, while the MVI56-MNET module does indeed feature an Ethernet port, this can be used for communication within the network but not for configuration. For configuring the module, you'll have to make use of its Cfg (configuration) port. This is primarily due to the fact that the Cfg port has direct access to the hardware of the module, whereas the Ethernet port is designed for network communications. However, remember to maintain the safety practices while physically handling the module for configuration. Hope this helps!

Hello! It seems like you're experiencing a typical issue with the MVI56-MNET module. To address your question, yes, the MVI56-MNET module can be configured remotely via ethernet. However, you'll need to make sure your cable connections and IP configurations are correct. It might be an issue of conflicting IP addresses in your network range, or an improperly set gateway. As your Prosoft Builder program can't detect the device, my first suggestion is to double-check your module and ethernet addresses. Remember, physical connections are just as significant in these cases as the logical ones. Also, make sure that your firmware versions for both modules are up-to-date. It might be a good idea to try a factory reset if other options don't work. If all else fails, consider contacting technical support. They're usually helpful in problem-solving these specific issues. Hope this helps!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. Why am I unable to establish communication with my MVI56-MNET module through Prosoft Builder despite the module's IP address being present on the network?

Answer: There could be several reasons for this issue, such as incorrect configuration settings, network connectivity problems, or software compatibility issues. It is advisable to double-check the configuration settings in Prosoft Builder, ensure proper network connectivity, and verify software compatibility.

FAQ: 2. Can the MVI56-MNET module be configured remotely via ethernet, or is configuration only possible through the Cfg port?

Answer: The MVI56-MNET module can be configured both through the Cfg port and remotely via ethernet. It is essential to ensure that the network settings are correctly configured to enable remote configuration.

FAQ: 3. How can I troubleshoot communication issues with the MVI56-MNET module in a subnet environment with multiple devices?

Answer: To troubleshoot communication issues in a subnet environment with multiple devices, you can start by checking the network settings, ensuring proper IP address assignment, verifying network connectivity, reviewing firewall settings, and checking for any conflicting configurations with other devices on the network. Additionally, inspecting the diagnostic overview and logs for any error messages can provide valuable insights into the communication problem.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’