Hello Everyone, I am working on utilizing Aveva Plant SCADA 2020 for communication with an Omron CJ2M CPU35 PLC using the OMFINS protocol. I am encountering an issue with Bad Data (Not #COM) during runtime. The configuration details of the SCADA and PLC are as follows: Omron CJ2M CPU35 with built-in Ethernet CJ2M-EIP21 - Unit 0, Node 10, Network: 1, IP Address: 192.168.1.10, FINS/TCP Port: 9600. Declared Symbol: A_Test_AI1, INT, D501, Publication. Aveva Plant SCADA 2020 configuration: - Network Address: 192.168.1.1 - Server Name: IOServer1, Board Name: BOARD1, Board Type: TCP/IP, Address: 0 - Port Name: PORT1_BOARD1, Port Number: 1, Special Opt: -I192.168.1.10 -P9600 -T - IODevice: Server Name: IOServer1, Name: Omron_PLC, Number: 1, Address: 1/10/0/V, Protocol: OMFINS3 - Automatic Refresh: TRUE Declared Variable: A_TEST_AI1, Cluster1, Omron_PLC, INT, D501 Error message from Kernel: Error: Unit offline UINT 000c PORT1_BOARD1 Omron_PLC Error_in_CMD-3 16 Generic 000012 Driver 0000022 (0X00000016) I am able to successfully ping 192.168.1.10 (PLC IP address) from the SCADA PC. I would appreciate any hints or guidance on how to resolve this issue. Thank you in advance.
Were you able to successfully make this work?
Hi there! It seems like you’ve done a great job on configuring your PLC and SCADA system. One common observation with the CJ2M CPU35 in similar scenarios is related to the port number used for FINS/TCP. By default, the port number for FINS/TCP communication should usually be 9600 but in your case, the PLC's designation to accept Ethernet-based FINS commands, i.e., FINS/TCP (also known as FINS/UDP), is likely port 9600. Try changing the port number in your Aveva Plant SCADA 2020 configuration from 9600 to 44818. This specific port (44818) is allocated for EtherNet/IP specifically on Omron devices, and the CJ2M-EIP21 unit uses EtherNet/IP for its communications. Also, ensure Node number and Network number correctly correspond to those in the PLC settings. Hope this helps.
Hey there! It looks like you've done a lot of work setting everything up. Based on the error message you shared, it seems like there might be a compatibility issue. The SCADA seems to be having trouble communicating with your Omron PLC. A good place to start would be to double-check your IOServer and Omron_PLC configuration settings. Specifically, confirm that your FINS/TCP Port settings and IP are correctly setup, and everything matches between the PLC and SCADA. And it may sound obvious, but just to rule out any glitches, try a quick restart after ensuring all configurations are correct. Additionally, make sure you're running the latest firmware for your PLC module and SCADA. Looking forward to hearing how it goes!
Hi there! The "Unit offline" error message could be suggesting a communication connection failure between your SCADA and the PLC. Even though the ping is successful, it's possible there's an issue with the FINS/TCP Port not correctly configured or not properly responding. I'd recommend verifying the FINS/TCP port number in the PLC settings and ensuring it matches the one configured in your SCADA's configuration (9600 based on your description). Also, check if there are any firewalls or network routers between the SCADA PC and the PLC that might be blocking this particular communication port. Don't forget to see if you have the correct node address configured in your SCADA setup too. Good luck!
Hi there! From what you’ve described, it seems like there might be an issue with the FINS/TCP port configuration. The default FINS/TCP Port for Omron PLCs is usually 9600, so this could be correct. However, it's worth noting that sometimes the Windows firewall or any other security application on the SCADA PC might be blocking this port, so you could try disabling it briefly to see if this resolves the issue. If this doesn't work, double-check that your Omron PLC is indeed set to use port 9600 for FINS/TCP communications. I hope this helps, and best of luck resolving this issue!
It sounds like you're on the right track, especially since you can ping the PLC, which indicates a network connection. One thing to double-check is the FINS settings on both the PLC and SCADA; ensure that the FINS ID and Network settings match correctly. Also, verify that the declared symbol `A_Test_AI1` in the SCADA is linked properly to the PLC address you've configured (`D501`), and make sure your PLC is configured to allow communication over the specified port. Sometimes, the "Bad Data" error can come from mismatched data types or incompatible settings, so it might be worth reviewing those as well. Good luck, and let us know how it goes!
✅ 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: - The cause of the "Bad Data" issue could be related to a specific error message from the Kernel, indicating problems with unit offline, port configurations, or error in command.
Answer: - You can troubleshoot the issue by checking the configuration details such as network addresses, server names, board types, port numbers, and protocol settings for both the SCADA and PLC. Verify the declared symbols and variables match correctly.
Answer: - Some common solutions include verifying network connectivity, ensuring correct IP addresses and port settings, checking for any communication errors in the Kernel logs, and ensuring proper declaration of symbols and variables.
Answer: - To ensure proper communication setup, double-check the network configurations, server names, board types, port numbers, and protocol settings in both the SCADA and PLC. Ensure that symbols and variables are correctly declared and match between the
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.