Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Unified Panel to LOGO! Connection

Created by: AutoGen_4505780 at: 3/6/2024 3:18 PM (9 Replies)

Rating (0)

Thanks 1

10 Entries

3/6/2024 3:18 PM	Rate (0)
AutoGen_4505780 Joined: 6/13/2023 Last visit: 4/26/2024 Posts: 13 Rating: (0)	Hello everyone, I'm trying to set up a Modbus connection between a LOGO! 8.3 and a Unified Basic Panel, however, I am unable to get the connection working. I'm wondering if I'm missing anything on either side. I include screen captures on both LOGO's and screen's end. P.S. - I have done VM mapping for LOGO! just not on the network connections, is that necessary? Thank you for your time Attachment Captures.zip (375 Downloads)

Suggestion To thank Quote Answer

3/6/2024 4:02 PM	Rate (0)
ixo65 Grandmaster Joined: 12/18/2014 Last visit: 11/13/2024 Posts: 34214 Rating: (4261)	I don't know WinCC Unified so I can't say too much about it. But shouldn't the IP address of the LOGO! be entered in the "PLC device" sector in the "Server:" input field in the connection settings? Unless, according to the screenshots, you have assigned the same IP address to the panel and the LOGO!. Since the HMI is the client, in my opinion there is no need to create a connection in the LOGO!. At least that's how it is with HMIs that are configured with WinCC TIA. Attachment Connection.png (346 Downloads)

Suggestion To thank Quote Answer

3/6/2024 4:59 PM	Rate (0)
AutoGen_4505780 Joined: 6/13/2023 Last visit: 4/26/2024 Posts: 13 Rating: (0)	ixo65 I don't know WinCC Unified so I can't say too much about it. But shouldn't the IP address of the LOGO! be entered in the "PLC device" sector in the "Server:" input field in the connection settings? Unless, according to the screenshots, you have assigned the same IP address to the panel and the LOGO!. Since the HMI is the client, in my opinion there is no need to create a connection in the LOGO!. At least that's how it is with HMIs that are configured with WinCC TIA. Thank you! I definitely made a mistake with the IP, that's corrected now, and while I would agree about the LOGO! Connection, for this particular project I need the HMI to both send and receive data, which would make it both client and server?? (not entirely sure tbh).

Suggestion To thank Quote Answer

3/6/2024 5:10 PM	Rate (0)
ixo65 Grandmaster Joined: 12/18/2014 Last visit: 11/13/2024 Posts: 34214 Rating: (4261)	I can only say by using WinCC TIA. It's not necessary there. The panel is the client, the LOGO is the server. The client makes the requests (read or write) and the server responds to them. And both via the one, same connection.

Suggestion To thank Quote Answer

3/6/2024 5:24 PM	Rate (0)
AutoGen_4505780 Joined: 6/13/2023 Last visit: 4/26/2024 Posts: 13 Rating: (0)	I'll try it and update the post with relevant information.

Suggestion To thank Quote Answer

3/12/2024 8:53 AM	Rate (0)
Murof Platinum Expert Joined: 8/3/2009 Last visit: 11/13/2024 Posts: 14165 Rating: (1772)	Hello I did only a few tests with LOGO and Unified comfort Panel: https://support.industry.siemens.com/forum/de/en/posts/unified-panel-to-logo-modbus-protocol/312817/?page=0&pageSize=10 I hope it helps Bye Murof
	If this Information really helps, you could use the Rate function
Suggestion To thank Quote Answer

3/12/2024 11:23 AM	Rate (0)
ixo65 Grandmaster Joined: 12/18/2014 Last visit: 11/13/2024 Posts: 34214 Rating: (4261)	Please then show us an example. The LOGO! 8.1 or newer can only Modus TCP/IP and in the other topic to that you have linked there is only a link to a PDF of Unified with Modbus RTU.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Murof

3/12/2024 11:23 AM	Rate (0)
ixo65 Grandmaster Joined: 12/18/2014 Last visit: 11/13/2024 Posts: 34214 Rating: (4261)	Please then show us an example. The LOGO! 8.1 or newer can only Modus TCP/IP and in the other topic to that you have linked there is only a link to a PDF of Unified with Modbus RTU.

Suggestion To thank Quote Answer

3/14/2024 9:20 AM	Rate (0)
Murof Platinum Expert Joined: 8/3/2009 Last visit: 11/13/2024 Posts: 14165 Rating: (1772)	Hello Yes I tested it a long time ago and there was only the RTU document available, now there is also a TCP one: https://support.industry.siemens.com/cs/ww/en/view/109925839/177165909131 I did the test again with a Unified Comfort 1000 and a Unified Basic Panel. I activated the Modbus TCP Server in the LOGO and just write some digital inputs to the VM area to do a quick test (I´m no LOGO Professional). In WinCC Unified V19 I used the Modbus TCP connection: I tested the Registers V und VM in the LOGO addressed with 0x1-0x16 and with 4×400001 (Word/ +-Int) in Unified. In Simulation and on real Panel Runtime I get a connection and I could also see the value change if I used the simulation board on the LOGO, so the connection works. I noticed a byteswap in VM addressing and the LOGO seems to be able to handle only one HMI connection. If a second one at the same time could not be connected. After activating the Modbus Server in the Logo It works only after a reboot of the device. I know this is only a rudimantary test scenario but I hope this helps if someone want to do this kind of communication. Bye Murof
	Last edited by: Murof at: 03/15/2024 08:49:21 If this Information really helps, you could use the Rate function
Suggestion To thank Quote Answer

6/14/2024 10:30 AM	Rate (0)
AutoGen_7903353 Joined: 8/31/2023 Last visit: 11/13/2024 Posts: 1 Rating: (0)	Hello Murof, I tested the connection with a Unified Basic Panel (TIA V19) and a new LOGO 12/24RCE (LOGO!Soft Comfort V8.4) I also activated the Modbus TCP Server in the LOGO and write two digital inputs to the VM area (see photo) In WinCC Unified V19 I used the Modbus TCP connection: In Unified I addressed the two digital Inputs with 0x1 and 0x2. But there is no Connection between LOGO and Unified. Do you know what I did wrong?
	Last edited by: AutoGen_7903353 at: 06/14/2024 10:32:31
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on