Hi! In general, the configuration tends to be fairly application-specific. They have to be tailored to the specific devices being communicated with. So in the video, we knew what type of device we were communicating with and could look in that device's documentation for information on things like its Modbus Register Map or IP Address.
Hi there! Please reach out to your regional tech support team so they can help with your question: www.prosoft-technology.com/Services-Support/Customer-Support . Thank you!
Hi, With this module, I can write different devices each with its respective IP and a coil specific? How I can configure the MNet client table to do this?
Hi there! To assist with this, our technical support team will need more information from you. Please feel free to call 661-716-5100 or email support@prosoft-technology.com. Thank you!
Hello Guys! This is a very good video. I have a question regarding this module to be set up in a ControlLogix Firmware Version 13 using Sample Ladder. I've followed the steps and configured the Module using the Configuration Builder. User-defined data types and ladder code required for the application were added to the existing project as well. However, I'm not seeing any requests or responses in the Client Module Diagnostics, they both show zero. I've verified everything and don't see any problem. Module status is also fine as per the local LED indications. Could you please share your thoughts on this? Thank you very much!
Thank you for your question, we'd be happy to help you trouble shoot! Please either call our support team at +1-661-716-5100 or send us an email at support@prosoft-technology.com and we'll have a Tech Support Engineer follow up with you!
To get the data values, make sure you reference MNET.DATA and not Local:xx:I:Data in your PLC program! :)Good video. Thanks!
Very Good Session.
Hello. Great video, thanks! You said the connection parameters should be set as shown in the video. How are those values determined?
Hi! In general, the configuration tends to be fairly application-specific. They have to be tailored to the specific devices being communicated with. So in the video, we knew what type of device we were communicating with and could look in that device's documentation for information on things like its Modbus Register Map or IP Address.
@17:44 can a client (MVI) write data to the Server (ModSim32)?
From 19:06, why does the Modbus simulation software changes from MOdSim to ModScan?
No, these are two different softwares one to act as a server (i.e. ModSim) and the other is the client (i.e. ModScan)
when I click the Search Icon in PDS do not appear the device, why that happen?
Hi there! Please reach out to your regional tech support team so they can help with your question: www.prosoft-technology.com/Services-Support/Customer-Support . Thank you!
Hi, With this module, I can write different devices each with its respective IP and a coil specific? How I can configure the MNet client table to do this?
Hi there! To assist with this, our technical support team will need more information from you. Please feel free to call 661-716-5100 or email support@prosoft-technology.com. Thank you!
Hello Guys! This is a very good video. I have a question regarding this module to be set up in a ControlLogix Firmware Version 13 using Sample Ladder. I've followed the steps and configured the Module using the Configuration Builder. User-defined data types and ladder code required for the application were added to the existing project as well. However, I'm not seeing any requests or responses in the Client Module Diagnostics, they both show zero. I've verified everything and don't see any problem. Module status is also fine as per the local LED indications. Could you please share your thoughts on this? Thank you very much!
Thank you for your question, we'd be happy to help you trouble shoot! Please either call our support team at +1-661-716-5100 or send us an email at support@prosoft-technology.com and we'll have a Tech Support Engineer follow up with you!
Somebody give me one of those EDS file for ProSoft MVI56 module？
MVI56-MNET
There is no EDS file u have to add a generic module like what was shown in the video