Troubleshooting DeviceNet Network: Identifying Bits in RSNetWorx

Question:

Seeking assistance with troubleshooting a DeviceNet network. Need to replace an outdated Unidrive Classic with a Yaskawa GA 800. While I can view the transmitted and received bits in RSLogix 500 and Unisoft, I am unable to identify the corresponding bits in RSNetWorx. The software only shows 6 inputs and 6 outputs labeled as "". Any insights on this issue would be greatly appreciated.

Top Replies

Would you mind posting a screenshot for reference?

The PLC program indicates some information, but where is it mapped to?

Is the EDS file for the Yaskawa device properly included in the RSNetworx database?

I am currently reviewing the installation process for the Yaskawa product that was recently ordered.

Learn how to obtain a standard EDS file for DNET configuration in this comprehensive guide. Additionally, gain insight into the significance of bits in the process.

It seems like you might be experiencing an issue with the mapping of the DeviceNet I/O. Try double checking your Yaskawa GA 800 DeviceNet parameters to make sure they are set correctly. Similarly, ensure that the EDS file for the Yaskawa drive is installed in RSNetWorx. If these don't solve your issue, you may have to do a fresh scan of the network in RSNetWorx. Remember, always backup your network configuration before making adjustments. Hope this helps and keep us updated so we may assist you better.

It sounds like you're experiencing mapping issues in RSNetWorx. You should be able to define the inputs and outputs through RSNetWorx by going to the "Connection" tab in the DeviceNet Scanner. From there, select the device you wish to manage and go to the "Input" or "Output" tab. You can then map the drive parameters to the I/O. If the issue persists, you might want to consider updating your RSNetWorx software or reviewing the Yaskawa GA 800 manual for any specific setup directions.

It sounds like you might be facing a mapping issue between your Yaskawa GA 800 and RSNetWorx. To rectify this, you have to manually define the input and output points in RSNetWorx software to match with your GA 800. As this procedure can be device-specific, you can refer to the Yaskawa GA 800's product manual for the detailed mapping. Do ensure the drive firmware is up-to-date and that you are not having any communication discrepancies on the DeviceNet network. If the issue persists, reach out to Rockwell Automation Support or a Yaskawa representative.

It sounds like you're facing some classic DeviceNet mapping challenges! When you see those "" labels in RSNetWorx, it's usually a sign that the parameters for your GA 800 aren't set properly, or the device isn’t fully configured in the software. Double-check that the EDS file for your Yaskawa GA 800 is correctly imported and that you’ve set up the appropriate I/O objects in your network configuration. Also, ensure that the node is correctly addressed on the DeviceNet network, as address mismatches can lead to communication issues. If you haven't already, consider consulting the GA 800 manual for specific configuration settings. Good luck!

It sounds like you're dealing with a bit of a challenge there! Since you're seeing inputs and outputs labeled as "", it might be worth checking the DeviceNet configuration in RSNetWorx to ensure that the Yaskawa GA 800 is properly declared and that all the necessary parameters are set correctly. Sometimes, missing or incorrect EDS files can cause devices to not report their parameters correctly, so double-check that you have the latest EDS file for the GA 800 installed in RSNetWorx. Additionally, make sure the device's MAC ID and baud rate match the configuration settings, as mismatches are a common source of connectivity issues. If all else fails, consulting the Yaskawa manual for specific setups regarding DeviceNet might reveal more insights. Good luck!

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 identify the corresponding bits in RSNetWorx for my DeviceNet network?

Answer: Answer: This issue could be due to differences in software configurations or settings between RSLogix 500/Unisoft and RSNetWorx. It's important to ensure proper mapping and compatibility between the different software platforms.

FAQ: 2. How can I troubleshoot a DeviceNet network when replacing an outdated drive with a new one like the Yaskawa GA 800?

Answer: Answer: Troubleshooting a DeviceNet network during a drive replacement involves verifying the network configuration, device compatibility, and ensuring correct mapping of inputs and outputs. Consulting device manuals and technical support can also provide valuable insights.

FAQ: 3. Why does RSNetWorx show only 6 inputs and 6 outputs labeled as "" for my DeviceNet network?

Answer: Answer: The display of "" inputs and outputs in RSNetWorx could indicate a mapping or configuration issue within the software. Double-checking the network setup, device parameters, and software configurations may help resolve this discrepancy.

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  β†’