Hello, I am currently attempting to control a drive using Sysmac Studio. I am able to successfully ping the drive and observe the logic bits changing as commanded. However, despite all parameters appearing correct on both the drive and PLC connection sides, the drive is not performing its operations. The FWD/STOP indicators on the keypad are illuminated. Have you faced this issue before? If you have, please share how you resolved it. Thank you.
To ensure safety compliance, ensure proper wiring of both STO1 and STO2 to +24vdc if the safety torque option is not being utilized. Check and set the following parameters for communication cards: P00.21 and P00.31 to 5, P00.20 and P00.30 to 8. Additionally, set P09.74 to 1 for Ethernet IP functionality.
The STO fault appears when the circuit is disconnected, indicating a connection issue that needs to be tested. It is important to ensure that all components are correctly connected to prevent any disruptions in the system.
Make sure you have verified the following settings: P00.21 and P00.31 should be set to 5 on the communication card, while P00.20 and P00.30 should be set to 8 on the same communication card. Additionally, ensure that P09.74 is set to 1 for Ethernet IP connectivity.
Yes, all of them are set to be exactly like that.
Every setting in this image has been configured accordingly, except for the IP address.
Hey there! I experienced a similar situation a while back. In my case, it turned out to be an issue with the enable input not being activated. It seems like you've confirmed both FWD and STOP are illuminated but you should double-check the enable status. Make sure the PLC program is running and that the drive is enabled for operation, as the drive won't perform any task unless the enable input is active. Hope this helps you out!
Hello! I've encountered a similar issue before with Sysmac Studio and a drive. What worked for me was double-checking not just the PLC connection side, but also all hardware connections. There could be a possibility of loose or broken wiring. Besides, check the drive's motor connections and ensure that your drive is receiving the right power supply. If everything then seems fine and you're still having trouble, it might be time to consider a factory reset of the drive or reaching out to the manufacturer's support team. Just make sure to backup any important data before a reset. I hope this helps. Best of luck with your troubleshooting!
Hey, I've faced a similar issue before. I found that even if the parameters appear correct, you might want to double-check the parameters related to the operational mode of the drive itself; these would be in the user settings. Also, ensure that your input bits in Sysmac are correctly configured, as a misconfigured input bit might prevent triggering the drive. Lastly, check the status of the Fault Reset/Override functionality. Even though they sometimes seem inactive, they may influence the drive operation. Hope this helps!
Hey there! I’ve run into a similar situation a while back and it turned out to be a simple configuration issue. Even though the parameters look correct, make sure to check the drive's motor settings like the encoder type and feedback configuration; sometimes these can be overlooked. Also, double-check that the communication settings match, as sometimes the operating mode may prevent commands from executing even if everything seems correct. If you haven’t already, try power cycling the drive after making any changes; that helped in my case! Good luck!
It sounds like you’re pretty close to getting it resolved! I had a similar issue once where everything seemed set up correctly, but the drive wasn’t responding. I checked the command settings in Sysmac Studio and discovered that the drive was still in a "ready" state instead of "enabled." Make sure to look into any safety or enabling conditions that might be preventing operation. Also, verify if there's any fault condition indicated on the drive itself—sometimes it's a simple watchdog or reset situation. Good luck!
Hi there! I had a similar issue with a drive not responding despite everything looking correct on the setup. One thing that helped me was re-checking the drive's configuration parameters – sometimes, even a small mismatch can prevent it from executing commands. Make sure the drive is in the right mode for the operations you're trying to perform, like checking if it's set to "run" instead of "stop." Also, ensure that there’s nothing blocking the drive’s permissions or safety settings. Good luck!
✅ 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: Answer: The illuminated FWD/STOP indicators on the keypad could indicate a specific fault condition or error that is preventing the drive from operating as expected. Further troubleshooting may be required to identify and resolve the issue.
Answer: Answer: To troubleshoot the issue, you can start by checking the drive's fault codes, ensuring correct parameter settings, verifying the communication setup in Sysmac Studio, and confirming that the command signals are being sent correctly to the drive.
Answer: Answer: Some steps to resolve the issue could include checking the network configuration, ensuring proper data exchange between the PLC and drive, verifying the firmware compatibility, and reviewing the communication settings in both Sysmac Studio and the drive's configuration.
Answer: Answer: Monitoring the logic bits changing in Sysmac Studio can help confirm that the command signals are being transmitted as intended from the PLC to the drive. However, it is also crucial to investigate further if the drive is not responding as expected despite the logic bits changing.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.