We use cookies to personalise site content, social media features and to analyse our traffic. We also share information about your use of this site with our advertising and social media partners.
hello sir.
so the big question is what driver should i use to connect to logo 8 ?
i have tried s7 communication protocol suite -> tcp/ip and enter the ip of the logo ( the connection between logo and PC is direct through lan cable) but the status always disconnected.
is there special communication that i have miss ? or there is a download driver for logo8 ?
Best regard
You are correct to have seen posts stating LOGO! cannot directly write to Modbus Input Registers. LOGO! Modbus TCP/RTU communication is primarily designed for reading from Input/Holding Registers and writing to Holding Registers only.
Why Input Registers are Read-Only for LOGO! writes: The LOGO! Modbus Master function blocks are configured to write to Holding Registers (function code 6). Input Registers (function code 4) are typically read-only for security and data integrity reasons.
Solution: If the Modbus device allows it, you'll need to map the data you want to write to a Holding Register instead. Consult the Modbus device’s documentation to see if register 406000 can be configured to function as a Holding Register, or if there's an alternative Holding Register you can use for the same purpose.
Resources:
If you confirm the target device supports writing to a Holding Register, please provide details about the data type and range, and I can help you configure the LOGO! program accordingly.
Hi there!
You're on the right track with the LOGO! Soft Comfort Starter Kit. To create a PC-based HMI (Human Machine Interface) for your LOGO! and run it remotely (e.g., via VNC), you'll need LOGO! Soft Comfort – specifically, a version that includes HMI functionality.
The Starter Kit (6ED1057-3BA00-0AA7) typically includes a limited version of LOGO! Soft Comfort which might not support the full HMI editing features. You'll likely need to upgrade to the full version of LOGO! Soft Comfort 8 or newer.
Here's a breakdown & resources:
Important Note: Ensure the version of LOGO! Soft Comfort you purchase is compatible with your LOGO! hardware.
As a home enthusiast, purchasing the full version of LOGO! Soft Comfort gives you the flexibility to develop complex HMIs and explore the full potential of your LOGO! system.
For detailed information and to purchase software, please visit the Siemens LOGO! website or contact your local Siemens distributor.
Hello Murillo,
Siemens CMR requires the CA certificate to be in .CER format for proper upload and functionality when configuring email services with Gmail.
While Gmail provides certificates in PEM and DER formats, you'll need to convert them to CER. You can use online conversion tools or OpenSSL for this conversion. Here's a basic OpenSSL command example:
openssl x509 -in your_gmail_certificate.pem -out your_gmail_certificate.cer -outform DERImportant Resources:
Please ensure the converted CER file is valid before uploading it to CMR.
If you continue to experience issues, please open a support request via SiePortal, including details of the conversion process and the error message.
Best regards,
Siemens Self Support
Hello! Siemens Self Support here, integrated with SiePortal.
The "Can't access IP" message, despite a successful ping, usually indicates a firewall or port blocking issue. Here's a breakdown:
Troubleshooting Steps:
For detailed troubleshooting and FAQs, please refer to these resources on SiePortal:
If the issue persists, please provide your LOGO!Soft Comfort version and operating system for further assistance.
Hello! Siemens Self Support here, integrated with SiePortal. You're right to identify the client/server roles. The LOGO! 8.FS4, when using Modbus TCP, typically operates as a Modbus Server, not a client.
However, controlling coils via Modbus TCP requires writing to specific registers. The LOGO! 8's Modbus interface provides access to its memory, including coils (outputs). You need a Modbus TCP Client (like your Arduino or QModMaster) to send write requests to these coil registers.
Key Considerations:
Resources:
If you continue to face issues, please provide details on your LOGO! 8 configuration and the specific Modbus commands you're using, and I’ll assist further. You can also find more detailed information and support through the SiePortal.
Dear User,
It appears you're experiencing an issue with placeholder resolution in your CMR 2040's firmware, specifically with text messages containing multiple signal placeholders. The first placeholder resolves correctly, but subsequent ones display as "!xxx!".
Here are potential causes and troubleshooting steps:
Recommended Actions:
Sincerely,
Siemens Self Support
Hello Wilson,
The "Cannot connect to AWS IoT" error, despite valid credentials, often points to network connectivity or security group configurations. Here's a breakdown of potential solutions:
For detailed guidance, please refer to the following SiePortal resources:
If the problem persists, please provide your region and the exact error message for further assistance.
Best regards,
Siemens Self Support
Congratulations on successfully registering with AWS IoT! You've completed a significant step. Creating the webpage in AWS to visualize your LOGO! PLC data requires using AWS services like IoT Core, Lambda, and potentially API Gateway with a frontend hosted on S3 or a similar service.
Here's a breakdown and helpful resources:
Tutorials & Examples:
SiePortal Search: For more specific examples related to LOGO! and AWS, try searching SiePortal using keywords like "LOGO! AWS webpage" or "LOGO! AWS data visualization".
You're looking to trigger a specific I/O status report from your Logo! 8 using a custom SMS alias sent via the CMR 2040. This is achievable, but requires some configuration and understanding of the Logo! 8's network capabilities.
Directly accessing the "backend" to modify Logo! 8 behavior isn't generally supported or recommended. Instead, leverage the Logo!'s network functions.
Important Considerations:
Resources:
This method avoids sending the entire Logo! 8 configuration and provides a user-friendly, targeted status report.
Hello, as Siemens Self Support integrated with SiePortal, I understand you're facing connection issues with your LOGO!8 despite successful ping and visibility in Soft Comfort's Network View, similar to the case referenced here.
Since ping is successful and the LOGO! is visible in Soft Comfort, the issue is likely with the communication protocol or firewall settings, even though you have basic connectivity.
If these steps don’t resolve the problem, please provide the following information for further assistance:
You can find further resources and FAQs on the Siemens Industry Online Support.
Based on your query and the provided documentation, direct communication between LOGO! PLCs and your Aveva Wonderware System Platform via the SIDirect DAServer is not directly supported.
The SIDirect DAServer specifically supports S7-200/300/400/1200 controllers using TCP/IP communication. While LOGO! PLCs can communicate over TCP/IP, they don't natively utilize the S7 protocol expected by the SIDirect DAServer.
Options to consider:
We recommend verifying Modbus TCP compatibility with Wonderware or contacting Wonderware support for clarification before implementing that solution.
We understand your frustration regarding the web access limitations with the LOGO! 8 6ED1052-1MD00-0BA8. You are correct; not all 0BA8 variants support web server functionality. We apologize for any misleading information you may have encountered.
Unfortunately, the 6ED1052-1MD00-0BA8 does not support direct web access for visualization or parameter changes. It lacks the necessary firmware for the integrated web server.
However, you still have options for remote monitoring and control:
While a direct "teleservice" style web interface isn't available, the LOGO! 8 App provides a viable solution for monitoring and basic control of your heat pump. We will forward your feedback regarding clearer product labeling to the relevant teams.
For detailed information, please refer to the LOGO! 8 FAQ and Compatibility of LOGO! 8 with Web Access in SiePortal.
You're right to identify the 32 Network Analog Input limit in LOGO!. While using Modbus to VW transfer and then Network Analog Inputs is a common approach, it quickly becomes restrictive. Here are alternative ways to access your Modbus data within the LOGO! program:
Recommendation: Upgrade to LOGO! 8.3 or higher to leverage the more flexible Modbus integration features. If an upgrade isn't feasible, focus on directly utilizing the VW memory where the Modbus data is stored within your program logic.
Based on your description, the issue likely stems from a communication mismatch despite successful pinging. Here's a breakdown of potential causes and solutions:
If the above steps don't resolve the issue, Wireshark can be helpful. Look for:
If you continue to experience problems, please open a support request via SiePortal, including details of your LOGO!Soft Comfort version, network configuration, and any Wireshark captures.
Hello, thanks for reaching out to Siemens Self Support!
It's common to encounter issues when first implementing Modbus with LOGO! 8.3. Here's a breakdown of potential causes and troubleshooting steps, given your successful ping test but lack of coil control:
The video you referenced can be a good starting point, but ensure all settings align with your specific device's Modbus implementation. If you continue to have issues, providing details of your target device and the exact settings you’re using in LOGO!Soft Comfort will help me assist further.
Hello Kevin, welcome to the LOGO 8 world! It's great you're starting with a test program. The issue you're facing – inability to access the LOGO 8 when connected through a router – is common. Here's a breakdown of potential causes and solutions:
For detailed guidance, please refer to the following resources on SiePortal:
Regarding your Swimming Pool Controller project, the LOGO Soft Web Editor will eventually simplify this process, but getting basic network connectivity working first is crucial.
Good luck, and feel free to post updates or further questions!
You are encountering a known limitation in the 0BA8 PLC when configured in Master/Slave mode. The Master/Slave communication protocol restricts data transfer to 32 data points (inputs/outputs) per connection.
As you've observed, using Master/Master mode with multiple connections bypasses this limitation, allowing access to all I/O.
Unfortunately, there is no direct way to bypass the 32 data transfer limit within the standard Master/Slave configuration. The limitation is inherent to the protocol implementation.
Workarounds/Alternatives:
For detailed information on Master/Slave vs. Master/Master configuration, please refer to the following SiePortal documentation:
SIMATIC PCS 7 - Master/Master and Master/Slave Communication Hello, we understand you're experiencing issues with Modbus TCP communication between your LOGO 8.3 and Arduino after upgrading from V8.FS4.
Here are some potential solutions/ideas:
For more detailed troubleshooting and specific configuration guidance, please refer to the following resources in SiePortal:
If the problem persists, please provide your LOGO 8.3 program (relevant parts) and Arduino code (Modbus section) for further assistance.
It appears you're encountering issues with a password prompt and subsequent operational problems after program modifications and downloads to your LOGO 8FS4 using LOGO!Soft Comfort V8.3.
Here's a breakdown of potential causes and troubleshooting steps:
Recommended Actions:
For more detailed troubleshooting and FAQs, please refer to the Siemens Support articles and documentation on SiePortal:
If the problem persists, please gather details about the specific error messages, program size, and any changes made before the issue arose, and create a support request on SiePortal for further assistance.
You're looking for a local, wireless display of your LOGO! 0BA2 TDE data on a smartphone within a 20-meter range, without internet access. Your router/WiFi approach is viable, but here's a breakdown and alternatives:
This is a good starting point. You’ll need a router capable of creating a local WiFi network and a method to get the LOGO! data onto that network. Unfortunately, the LOGO! 0BA2 doesn't natively support WiFi. You would need an intermediary device.
SiePortal Resources: Explore the LOGO! 8 FAQ and search for "remote access" or "mobile visualization" for more ideas.
Close Player
Minimize Player Maximize Player
Our flexible community website is a platform that allows users to connect, share information, and collaborate on various topics of interest. The website offers a range of features such as discussion forums, messaging, user profiles, event calendars, and more. Users can customize their experience by creating and joining different groups or communities based on their interests or location. The website is designed to be user-friendly and adaptable to the needs and preferences of our diverse user base. Whether you are looking to network professionally, share hobbies and interests, or simply connect with like-minded individuals, our flexible community website has something for everyone. Join us today and become a part of our thriving online community!
Share this page with your family and friends.