BW4030 Ethernet to DeviceNet Gateway Support
Documents and Downloads
BW4030 User Manual, BWConfig Tool and EDS File
Commonly Asked Questions
What are the installation requirements?
- 24VDC, see the user manual for the operating voltage range and other specifications
DeviceNet Network Power
- Ensure the BW4030 is installed on a properly-wired and terminated DeviceNet network
- Ensure the DeviceNet network length is correct for the desired DeviceNet Baud Rate
- Ensure that the BW4030 DeviceNet node address is unique on the network and is set correctly for Master or Slave operation
- Ensure the BW4030 is installed on a properly-wired and segmented Ethernet network
- Ensure that the BW4030 IP address is unique on the network
- Basic Node Commissioning and Settings: You will need BWConfig 2.0 to set the node address and other module-specific settings. The BWConfig 2.0 tool is a Microsoft Windows application that communicates with the BridgeWay device over a USB connection. BWConfig 2.0 is compatible with Microsoft Windows XP, Windows 7, 8.x and 10.
How do I operate the BW4030 as a DeviceNet Master?
You can use RSNetwork for DeviceNet from Rockwell Automation, NetTool-DN-D or ACM from HMS to configure the DeviceNet Master Scanlist in the BW4030.
How do I operate the BW4030 as a DeviceNet Slave?
How do I operate the BW4030 as a bridge?
The BW4030 can be used as a CIP or Modbus TCP Bridge out of the box. See the BW4030 user manual for further instructions.
How do I diagnose an issue when using the BW4030?
- Visual indicators on the module LEDs regarding status, warnings and errors
- See the BW4030 user manual for an explanation of the LED states
- The BW4030 provides status information on the input data, status registers (status assembly) and web pages provided by the module
- See the BW4030 user manual for detail on the status information and diagnostic web pages
Why is my device showing a “?” in the network view when using RSNetworx for DeviceNet or ACM tools?
You must register the EDS file and module icon before using the BW4030 in RSNetworx or ACM. See Rockwell Automation’s RSNetworx for DeviceNet or HMS’ ACM documentation on registering new devices.
I set up the device but don’t see DeviceNet Slave nodes when using RSNetworx or ACM.
To troubleshoot this issue:
- Ensure that there are no warnings or errors displayed by the LEDs or indicated in the status information provided by the BW4030.
- When using the BW4030 as a DeviceNet Master, ensure that you do not set the module to Autobaud and that the slaves are set to Autobaud to ensure they are all at the same baud rate.
- Ensure that DeviceNet Network power is connected.
- Ensure that the DeviceNet (CAN H and CAN L) wiring is connected properly and that termination has been properly applied.
My BW4030 is running and sharing data but indicates one or more slaves are not available.
To troubleshoot this:
- Ensure that the DeviceNet Slave node addresses are correct based on your BW4030 Scanlist configuration.
- Ensure that the I/O data size for the DeviceNet Slave devices matches what was configured in your BW4030 Scanlist.
- Ensure that the DeviceNet Slave devices are online with no faults. They should indicate that the BW4030 is connected to them and they are being polled.
- Ensure that the DeviceNet Slave devices are set to autobaud to the BW4030 or that they are set to the same baud rate as the BW4030.