I have set up a test rig to retool some old equipment, using a 315 PN/DP PLC with all green lights indicating no errors on the profibus network. The network consists of only 2 nodes: 1 ET200X with 8 input and 8 output modules for Cylinder I/O, functioning properly, and 1 ET200S with multiple input and output cards for panel I/O and safety solenoids. While the inputs on the ET200S are working fine, none of the outputs seem to be functioning. I have tried toggling M bits to activate the coils, similar to the ET200X, but the outputs only appear in one part of the code. The LED on the card does not illuminate, and the solenoid does not activate. However, when I adjust the value in the hardware configuration, both the LED and solenoid work properly. It has been a while since I worked with older Siemens equipment, and I am unsure of what I may be overlooking. Any suggestions would be greatly appreciated!
Can you please provide a screenshot of the hardware configuration for review? This will help us better understand the setup and make any necessary adjustments. Thank you!
I realize now that I made a mistake by not setting the I/O image size high enough for the retool nodes addresses. I have only used the PLC as a testing tool and have never required more than 128 bytes of data.
Aleronick mentioned that he didn't configure the I/O image size to accommodate the retool nodes addresses properly. He admitted that after using 1500s for a long time, he had overlooked this important aspect. Good observation!
It sounds like it could be a programming issue. If the hardware tests fine when manually adjusted but isn't functioning as it should through the PLC, I'd suggest double-checking the code to make sure there are no conflicts or misplaced commands. Alternatively, it could be an addressing issue. Profibus does have some quirks and addressing on the ET200S differs slightly from other ET200 modules. Just remember to double-check your programming and the addressing of the ET200S in the hardware configuration - don't rule anything out yet!
It sounds like you've already done quite a bit of troubleshooting, but I'm wondering if it might be an issue with the addressing. Make sure the addresses you've assigned in your code match up exactly with the physical layout you've set up on your ET200S. This is a common mix-up that can cause this type of problem. Just to rule out hardware issues, I'd also suggest double-checking module and rack numbers, and possibly try swapping out the ET200S with known working unit to confirm it's not a hardware failure. Good luck!
It sounds like you've done a pretty thorough job of diagnosing the issue and the fact that the outputs work when modifying the hardware configuration suggests that the ET200S isn't the problem. Instead, this points to a possible software configuration issue. Could it be that there's a mismatch in the configuration between your hardware and the PLC program itself? Maybe an incorrect rack or slot number? Another potential pitfall to consider is the PLC's run/stop switch - if it's set to stop, the outputs won't work even if the programming seems fine. I'd suggest double-checking the hardware configuration in your PLC programming software. Hope this helps!
It sounds like you've done quite a bit of troubleshooting already. Given what you've shared, I'd suggest you double check the addressing. It's possible that the addresses for the ET200S outputs may not be accurately mapped in the code. Also, ensure that the PLC is in Run mode, as outputs will not function in Stop mode. If you've tried both these steps and it's still not working, you might need to check the hardware configuration again. Make sure the physical configurations of the PLC (like its I/O module slots no. in the system) match perfectly with that in your software. I hope this helps.
It sounds like you've done a thorough job diagnosing the ET200S, but it could be worth double-checking the addressing in your code. Since the outputs only show up in one part of the code, make sure they’re not being overshadowed by other functions or conditions in your program. Also, verify the hardware configuration and mapping for any discrepancies between the outputs and the PLC’s addressing logic. It may be a minor detail that's easily overlooked, like ensuring the module is set to the correct mode or confirming that the output relays are enabled in your PLC’s setup. Sometimes, a fresh look at the manual can reveal settings that are easy to miss, especially with older equipment!
✅ 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 issue with the outputs on the ET200S not functioning could be related to the configuration settings or the programming logic. Make sure to check the configuration settings and the programming code to ensure proper activation of the outputs.
Answer: - When troubleshooting ET200S output card malfunctions, ensure that the hardware configuration settings are correct. Check the programming logic to see if the outputs are being activated properly. Verify the connections and ensure that the solenoids are receiving the appropriate signals.
Answer: - The LED not illuminating and the solenoid not activating could indicate a problem with the signal transmission or the hardware configuration. Check the wiring connections, the programming code, and the hardware configuration to identify and resolve the issue.
Answer: - The outputs only appearing in one part of the code could be due to a programming error or a misconfiguration in the logic. Review the code to ensure that the outputs are being activated correctly at the required points. Check for any discrepancies in the logic that may be causing this issue.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.