adccommunitymod (AutomationDirect) asked a question.
Created Date: February 13,2020
Created By: Dommbro
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
I have a "D0-06AR " PLC. When I hook up via Comm Port 1 of the described PLC, is there a way to identify the IP address? Background: When my laptop is connected to the internet via ethernet I can easily establish what the IP address is. Along with all of the other PLCs that are connected to the network. Currently trying to map where all of the PLC's are physically located. So I have to disconnect my laptop via ethernet. I'm trying to verify the PLC IP address by communicating through Comm Port 1.
Created Date: February 13,2020
Created by: Dommbro
I have a "D0-06AR " PLC. When I hook up via Comm Port 1 of the described PLC, is there a way to identify the IP address?
Background: When my laptop is connected to the internet via ethernet I can easily establish what the IP address is. Along with all of the other PLCs that are connected to the network. Currently trying to map where all of the PLC's are physically located. So I have to disconnect my laptop via ethernet. I'm trying to verify the PLC IP address by communicating through Comm Port 1.
Created Date: February 13,2020
Created by: franji1
If you can't use NetEdit, then you can write ladder logic to read the IP Address. See the IBox ECRDIP - ECOM100 Read IP Address.
The 06 manual is available here:
https://cdn.automationdirect.com/sta...d006userm.html
EDIT: sorry, the main IBox chapter is chapter 5. The end of that chapter has the IBoxes you are looking for. The appendix at the end only contains the NEW IBoxes for DirectSOFT 6.
Created Date: February 13,2020
Created by: Dommbro
I'll have to look into NetEdit some more to see if will let me determine the PLC's IP address.
If not, I will attempt to input the ladder logic.
After I am to input that portion of ladder logic, will I be able to read the IP address when monitoring the PLC on my laptop?
Created Date: February 14,2020
Created by: bcarlton
Netedit is executed over Ethernet. You appeared to want to limit communication to the serial port.
Created Date: February 14,2020
Created by: franji1
After I am to input that portion of ladder logic, will I be able to read the IP address when monitoring the PLC on my laptop?
Yes. ECRDIP instruction will stick it into 4 V registers, one for each "octet " of the 32 bit IP Address. I can't remember the order. In the example from the manual, it puts the 4 bytes into 4 V registers V3000 thru V3003. So, if the IP Address is 192.168.1.42, I can't remember if it will be stored with V3000 being 192 (MSByte of address) or V3000 being 42 (LSByte of address). They are definitely binary format, not BCD.
Hence, DirectSOFT or an HMI like C-more could easily monitor those 4 V registers over a serial connection.
Created Date: February 14,2020
Created by: Dommbro
Netedit is executed over Ethernet. You appeared to want to limit communication to the serial port.
I noticed there is an option to scan my laptop's Comm Ports. Specifically the one I'm using for communication to the PLC. It will scan for about 15 seconds and then show nothing. Is it possible to Netedit to find the IP address when communicating through the PLC comm port?
Maybe I need to look into the process of setting up a PLC's IP address and work backwards.
Created Date: February 16,2020
Created by: RoloTomassi
This may already be understood, just not being mentioned...
I’m seeing references in the posts to port 1 and IP Address. The CPU itself does not have an IP Address. Port 1 is an RJ12 serial port. In order for the DL06 to support an Ethernet connection, an H0-ECOM100 would be required in one of the option slots. The H0-ECOM100 would be the device that has the IP Address and would communicate to the CPU across the back plane. NetEdit is used to discover the H0-ECOM100.
Again, I apologize if this is already understood. It just seemed like there may have been some confusion going on.
Created Date: February 19,2020
Created by: NevergoldMel
You can wireshark it.
https://www.wireshark.org/lists/wire.../msg00140.html
Created Date: February 19,2020
Created by: Dommbro
This may already be understood, just not being mentioned...
I’m seeing references in the posts to port 1 and IP Address. The CPU itself does not have an IP Address. Port 1 is an RJ12 serial port. In order for the DL06 to support an Ethernet connection, an H0-ECOM100 would be required in one of the option slots. The H0-ECOM100 would be the device that has the IP Address and would communicate to the CPU across the back plane. NetEdit is used to discover the H0-ECOM100.
Again, I apologize if this is already understood. It just seemed like there may have been some confusion going on.
This was not understood. Thank you for the information.
When I use NetEdit, I select the "Network " drop down, Protocol> Serial> COM4 (My usb port).
It runs for a little bit but then displays nothing. This is while I'm connected from the laptop directly to the PLC using the PLC's Comm Port 1.
Is it possible to see the H0-ECOM100's IP address using a method like this?
Created Date: February 19,2020
Created by: franji1
Is it possible to see the H0-ECOM100's IP address using a method like this?
No. That is not for PLC CPUs, but direct connecting with WinPLC and EBCs serial port - not ECOMs, nor through an 06 serial port.
Use ECRDIP in your program, then just use any Modbus or DirectSOFT or HMI to read those 4 V locations. Serial, Ethernet, Modem.