Greetings! I am currently attempting to modify the IP address of an Omron PLC (NJ30-1200) and HMI (NB7W-TW01B) in order to connect them to our network. Sysmac Studio is the software utilized for the PLC, while NB Designer is employed for the HMI. However, after adjusting the IP addresses, communication between the PLC and HMI is lost. The PLC IP address is altered in Sysmac Studio, and both the PLC and HMI IP addresses are updated in NB Designer. Your assistance in troubleshooting this connectivity issue would be greatly appreciated.
Have you adjusted the NODE rotary dials on the NJ to align with the final octet of the PLC IP address?
IO_Rack inquired about aligning the NODE rotary dials on the NJ with the final octet in the PLC IP address. Thank you for your response. I haven't adjusted any rotary dials as there are no such dials on the CPU, only DIP switches. Should I also modify the DIP switches? Thank you.
When configuring the Node Address for the PLC/HMI in NB Designer, ensure it matches the last octet of the IP address. Also, verify the address updates in the communication settings. In Sysmac Studio, navigate to "Built-in Ethernet/IP Port Settings" and review the FINS Settings to confirm the node address. If automatic generation is enabled, it will reflect the last octet of your IP address. Additionally, check if both IP addresses being changed are on the same subnet. If not, consider adding entries to the IP address table for proper communication.
Chelton inquired: In NB Designer, have you assigned the PLC/HMI node address as the last octet of the IP address? Also, verify in the communication settings that the addresses have been updated. In Sysmac Studio, navigate to "Built-in Ethernet/IP Port Settings" and check the node address set in the FINS Settings. If automatic generation is enabled, it will use the last octet of the IP address. Are both IPs being changed within the same subnet? If not, additional entries may need to be added to the IP address table. Hello Chelton, I have not yet altered the node address. Please refer to the table below: Existing: - IP Address: 192.168.0.1 - Node: 1 Proposed: - IP Address: 192.168.40.7 - Node: 1 Should we update the node to 7 in the proposed configuration? I have also included the communication settings from NB Designer for your reference. Please let me know. Thank you.
Although it is not required for the node address to match the last octet of the IP address, aligning them can streamline FINS communication. It is recommended to set the node address to 7 for optimal functionality. Additionally, ensure that the HMI (NB) node address is configured correctly. If the node addresses do not align with the last octet address, refer to the address tables in both the NB and PLC for resolution. This can help facilitate seamless communication between devices.
Hello! In your situation, I think the issue could be related to the subnet settings. Make sure the subnet mask on both your PLC and HMI match the one used on your network. Also, you might want to verify if there's any firewall or other network restriction that could be blocking communication between your devices. Lastly, just to be sure, after changing the IP addresses in both systems, did you power cycle the devices? Sometimes, a good old restart is all it takes to apply the changes. Hope this helps!
Hey there! It sounds like an IP conflict might be at play here. Make sure your PLC and HMI IP addresses are in the same subnet, and that they don't conflict with any other IP addresses on your network. Also, check to ensure your HMI is set to communicate in the correct protocol that your PLC understands. Lastly, don't forget to check that the gateway and subnet mask settings on both devices are correctly set to match your network. If these settings are off, even a tiny bit, communication won't be possible. Hope this helps!
It sounds like you're taking the correct steps to set up communication between your PLC and HMI. One thing to check might be the subnet mask configuration as this could cause communication issues if not set up correctly across both devices. Additionally, ensure that both the PLC and HMI are set to the same communication protocol. Sometimes, a PLC reboot can help to establish the new IP address. If the issue persists, it could be helpful to record your steps or errors messages to narrow down the problem.
Hi there! It sounds like you're making the right moves with changing the IP addresses in both Sysmac Studio and NB Designer. However, it's essential to ensure that both the PLC and HMI are in the same subnet. If they aren't, that might be causing the loss of communication. Verify also if any firewalls are blocking the respective IPs which could disrupt the connection. Another suggestion is to check if the subnet mask matches in both Sysmac Studio and NB Designer, as an error here could also lead to communication issues. I hope this helps!
✅ 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: - When the IP addresses of the Omron PLC and HMI are changed, it is essential to ensure that the new addresses are within the same subnet and configured correctly to maintain communication between the devices.
Answer: - You can start by verifying the IP settings on both the PLC and HMI to confirm they are correctly configured. Additionally, check the network settings in both Sysmac Studio and NB Designer to ensure they match the new IP addresses.
Answer: - Sysmac Studio is typically used to configure the Omron PLC's IP address, while NB Designer is employed for the HMI. Ensure you are using the correct software for each device to avoid connectivity issues.
Answer: - Yes, it is crucial to update the IP addresses of both the Omron PLC and HMI in their respective software (Sysmac Studio for the PLC and NB Designer for the HMI) to ensure proper communication between the devices on the network.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.