Kkula
Browse Questions » LOGO! - Communication: Transmit Binary Signal Parameter (M1) Originating From Logic module Towards Jumo

About User

Siemens Self Support

Questions Asked: 37.9K

Answers Given: 32

Statistics

Tags

0
  • Open
Siemens Self Support
Asked:18 Oct 2025

LOGO! - Communication: Transmit Binary Signal Parameter (M1) Originating From Logic module Towards Jumo

Hello to everyone.
Aslo I got new verison of Jumo LOGOSCREEN700 and like to set communication over Modbus with LOGO!
Have LOGO!: 6ED1 052-1MD08-0BA1, LogoSoft V8.3.
I was able to get temperature value of AI1 from Jumo via Modbus on LOGO!, ... but can't send digital value (M1) from LOGO! to Jumo and record that value state.
On online test read bit M1=V1104.0, M2= V1104.1, but not see on Jumo700. Also try mapping with V100.0 an V100.1
Try different datatype, addresses ...
not sure that i missing...  if anyone have some solution i appriciatet 
------------------------------------------------------------------------------------------
Split from
Connect LOGO to Jumo700
.

#sosflex #LOGO! - Communication #siemens
1Answers 9Views 0Votes
0 Likes 0 Favourites 0 Followers 0 Comments
Answers(1)
Siemens Test Added an Answer on18 Oct 2025

Modbus Communication Issue: LOGO! to JUMO LOGOSCREEN 700

Hello!

You've successfully read analog values from JUMO to LOGO!, but are facing difficulties writing digital values (M1/M2) from LOGO! to JUMO. This is a common issue with Modbus implementations.

Here are some troubleshooting steps, based on similar cases:

  • JUMO Address Mapping: Double-check the JUMO LOGOSCREEN 700's Modbus register map. Ensure the address you are writing to (V1104.0/1 or V100.0/1) is actually configured as a writable register for digital input/output. JUMO devices often have separate read/write areas.
  • Data Type: Confirm that the data type in LOGO! (e.g., bit, byte) matches what the JUMO device expects for that register.
  • Modbus Function Code: Verify you are using the correct Modbus function code for writing (typically Function Code 06 for writing a single register). LOGO! should handle this automatically with the correct configuration.
  • Network Configuration: Re-verify the Modbus communication settings (baud rate, parity, stop bits) are identical on both devices.
  • LOGO! Configuration: Ensure the network connections within LOGO! are properly configured for Modbus TCP/RTU and that there are no firewall or communication blocks.

SiePortal Resources: Please refer to these resources on SiePortal for more detailed information:

If the issue persists, providing the JUMO LOGOSCREEN 700’s Modbus register map will help diagnose the problem more accurately.

Best Regards,
Siemens Self Support

0