Hello everyone! I recently received my new Prosoft Modbus modules and have been experimenting with one in an L82 rack. I successfully configured it to poll a M580 PLC using Modbus. After setting up the IP address, I attempted to update the EDS files, but found that the version on the module was newer. I also imported an AOI, although I am still unsure of its exact function aside from creating a new data structure. I encountered a mismatch alarm status, which I discovered is common for generic modules, along with an internal status code (16#0060) indicating the mismatch. While this is somewhat bothersome, it does not appear to be critical. Regarding the AOI and the new IO structure it created, I noticed that the data I expected in Local:1:I.Data was not displaying correctly. Despite my efforts to troubleshoot the issue, the values were still erratic. On a positive note, the MNETC structure displayed a steady 2345 value that responded promptly to changes from the M580 PLC, likely due to the imported ProSoft AOI. Is there a concern with the unusual behavior of the values in Slot 1, or should I not be too worried about it? In comparison to a previous program using older serial MCM, where data landed directly in the slot structures without the need for an additional AOI-created structure, I am questioning whether this setup is problematic or represents progress. Any advice on managing the module and handling data in Logix would be greatly appreciated. Thank you.
The Prosoft modules are a crucial part of our operations, and thankfully, we have not encountered any issues with EDS files, their visibility in the I/O configuration tree, or any data transfer inconsistencies between the controller and the module. Did you utilize the Prosoft Configuration Builder (PCB) to configure the Modbus module? Is it configured as a server, client, or both?
Are you able to easily download the most recent EDS directly from the module?
The latest Electronic Data Sheet (EDS) can usually be downloaded directly from the module. If you're asking about uploading the EDS from RSLinx, this feature is available on most Rockwell and other devices, although not all. It's worth noting that this is not a mandatory feature for EtherNet/IP devices. If you were referring to something else, please clarify.
PCMusicGuy inquired if the Prosoft Configuration Builder (PCB) was used to set up the Modbus module as a server, client, or both. The goal is to configure it for both server and client functions. Currently, a Modicon with registers has been set up, and MNET Client 0 is being used to poll values with the L82. The intention was to configure each "client" (0-29) as either a Client or Server, but there may be a misunderstanding. The plan with Prosoft is to poll data from various Modbus devices and transfer it to the L82. Additionally, all PLC data will be remapped to be accessed by an Intouch Standalone Screen and an RTAC gateway using their respective IP addresses to prevent unauthorized access. As the RTAC is not available, an SMP4 is being used to align the REAL registers. However, it seems to be connecting directly to MNET Client 0 instead of a desired slave table for device connections. Further review of the documentation is necessary to address these issues. Any assistance or insight on how to proceed would be greatly appreciated. Thank you.
Hi, it seems like you've done quite a bit of troubleshooting already and your understanding of how your new Prosoft modules interact with your M580 PLC is pretty solid. To some extent, the erratic values on Local:1:I.Data may actually be due to inconsistencies in the data translation between the AOI and Modbus registers. I'd not be overly concerned because the key data is being pulled in and reflected correctly under your MNETC structure. Although the setup you are dealing with is different from your earlier implementation based on MCM, this is indeed progress in terms of flexibility and functionality offered by this AOI-based system. Continue to monitor your values, and you may want to reach out to Prosoft’s support for specific advice on fine-tuning your AOI setup, ensuring it’s optimized for your needs.
Hey there! It does seem like you've been experimenting a lot with the new modules. First, as per your AOI query, it essentially serves as an encapsulated, reusable piece of code that simplifies your program and aids you in structuring your project efficiently. Now, about the data not displaying correctly in Local:1:I.Data, this does seem unusual. It could potentially be due to a misalignment between your PLC data and the corresponding location in the Logix processor, or a mismatch in data types between your hardware and code. It might be beneficial to clarify the AOI’s setup, the data elements it's supposed to address, and the configuration of the data types. Also, it'd be helpful to know whether the erratic values are completely off or there's a consistent pattern that could indicate an ongoing calculation or conversion error. Just as an afterthought, don't worry much about the mismatch error, as long as the firmware versions between Logix and Prosoft module are compatible. Despite the differences from the previous setup with the MCM module, this isn't necessarily problematic, but rather indicative of the shift in approach toward using AOIs in modern PLC programming to increase efficiency and maintainability.
Hey there, nice work on setting up the Prosoft Modbus module so far. The AOI or Add-On Instructions feature in this case is creating a custom data structure that provides a kind of 'mapping' for exchanging data between your Modbus module and PLC. As for the data not displaying correctly in Local:1:I.Data, you might want to double-check the data type or try resetting the module. However, since the MNETC structure is showing a steady value and responds immediately to the changes from the M580 PLC, I believe you're on the right track. The unusual behavior in Slot 1 might not be a matter of concern unless it's significantly affecting your project outcome. Evolution in technology often comes with its own set of quirks and learning curves, so I wouldn't regard the setup as a problem but rather a step forward. In handling data in Logix, focus more on getting a comprehensive understanding of AOI operations. They might indeed prove to be a boon in efficiently managing your data.
Interesting observations! The mismatch alarm status and internal status code you've encountered do appear frequently with generic modules and shouldn't be cause for much concern. As for the erratic data in Local:1:I.Data, it could be due to a number of issues. One possible culprit is poor synchronisation between your Modbus device and the L82 rack due to time-outs or delays related to communication timings. Accurate timing is critical for the efficient transfer of data. As per the comparison with the previous MCM setup, using an AOI-created structure certainly represents a more modern approach. Here, different structures can be created and controlled according to our need. It offers flexibility, but also comes with its own set of challenges. If synchronization isn't the issue, there could also be a possible problem with unpacking the data depending on how it is mapped. Keep experimenting with different methods of data management and don't hesitate to continue using community forums for help—peer learning can be a great asset.
Hey! It sounds like you're making great progress with your Prosoft Modbus modules. The mismatch alarm can be a bit tricky, but you’re right that it’s often just a quirk of using generic modules. As for the AOI, it's likely designed to abstract some of the complexities, but it can certainly add another layer that might complicate data handling if it doesn’t align well with your expectations. One thing to check might be the mapping of the inputs and outputs—sometimes the data structure or the way they're indexed can lead to unexpected results. If you’re seeing consistency in the MNETC structure values, that’s a good sign! Maybe take a closer look at how the AOI is set up or even consider reaching out on the Prosoft forums; the community can be a great resource. Keep us posted on how it goes!
Hey there! It sounds like you’re making some solid progress with your Prosoft Modbus modules, but I can definitely understand the frustration with the mismatch alarms and erratic data in Slot 1. It's not uncommon to face these kinds of hiccups when transitioning to a newer module or structure, especially with AOIs involved. Have you double-checked the configuration settings in the AOI for any potential errors or mismatches? Sometimes, tweaking the data structure mappings can help resolve those erratic values you’re seeing. Also, the mismatch alarm could simply be a result of the module’s firmware being ahead of what your software recognizes, so keep that in mind as you troubleshoot. Overall, it seems like you're on the right path—just take it step by step and hopefully things will start to smooth out. Good luck!
âś… Work Order Management
âś… Asset Tracking
âś… Preventive Maintenance
âś… Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The mismatch alarm status and internal status code (160060) are common issues for generic modules like the Prosoft Modbus module MVI56E-MNETC. While bothersome, they are not critical and can be managed during the integration process. 2. FAQ: Why are the values in Local:1:I.Data not displaying correctly despite troubleshooting efforts after setting up the Prosoft Modbus module in the L82 rack? Answer: The erratic values in Local:1:I.Data could be due to the structure created by the imported AOI. It is recommended to review the setup and configuration of the AOI to ensure proper data handling. 3. FAQ: Is the unusual behavior of values in Slot 1 a cause for concern, or is it a normal aspect of integrating the Prosoft Modbus module with the M580 PLC? Answer: The unusual behavior of values in Slot 1 may not be a critical issue, especially if the MNETC structure is displaying expected values and responding promptly to changes from the M580 PLC. It is advisable to focus on functionality and data integrity rather than being overly worried about minor discrepancies. 4. FAQ: How does the use of
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.