Programming MODBUS for Automation Direct Sureservo Systems with AD 205 PLCs and 260 CPU

24-08-2024
w_harbuck
14 comments
4223
155

Question:

Hello everyone, I am in need of assistance with programming MODBUS for Automation Direct Sureservo systems using AD 205 PLCs with a 260 CPU. I have two systems that require programming, but I have no prior experience with MODBUS. My knowledge of PLC programming is limited to basic functions like inputs, outputs, timers, and counters with simple addressing. Math is not my strong suit either! I have reached out to AD tech support for help, but their technical explanations assume a higher level of programming expertise. I do have a basic understanding of Directsoft "V" addressing, which I believe is crucial for this task. If anyone can offer guidance, I would greatly appreciate it. Thank you, Will.

Top Replies

If you're looking for assistance with the Sureservo manual, be sure to check out Chapter 6 for a helpful starting point. If you've followed the instructions but still have questions, feel free to ask for help. While I have experience working with Modbus on the 260, I have not yet worked with Sureservo.

25-08-2024
bernie_carlton

Hello Bernie! I knew I could count on finding you here. Thanks to your help on the AD tech forums, I successfully calculated RPM's. It worked perfectly, so thank you! I followed the manual's instructions for multiple drives on the MWX and MRX, and it seems like the drives are now communicating effectively with no more comm errors. I think it would be beneficial to see a detailed program example and explanation of each segment to understand the functions of each register and box. On a side note, I have a great fondness for Washington - my mother lives just south of Tacoma. Thanks again, Bernie!

26-08-2024
w_harbuck

I may not be able to assist with the Sureservo, but hopefully someone with relevant experience will chime in. Although I reside on the drier and colder side of the Cascade Mountains from Tacoma, Washington holds a special place in my heart. (SEO-friendly words: Sureservo, Washington state, Cascade Mountains, Tacoma)

26-08-2024
bernie_carlton

I am optimistic about it. I have made significant advancements and can complete all tasks on this machine except for the servos. Thank you once again.

26-08-2024
w_harbuck

I am seeking assistance from someone who has some knowledge and experience with AD sureservo modbus.

26-08-2024
w_harbuck

Hey Will, I totally understand your predicament. MODBUS can seem a bit complex at first, but once you get the hang of it, you should be able to integrate it into your PLC projects seamlessly. Since you're familiar with Directsoft "V" addressing, you're already halfway there! A couple of things to keep in mind: the MODBUS addressing starts at 1, unlike the common "V" addressing which starts at 0. Also, Automation Direct PLCs are 16-bit, so this could be a tad tricky if you're coding for 32-bit MODBUS registers. I'd suggest starting by configuring your PLC as a MODBUS slave device, this'll make your learning curve a bit gentler. Be sure to follow the guidelines for the communication protocol - parity, stop bits, data bits, and baud rate. There are numerous online resources and practical guides available as well, such as the tutorials on the Automation Direct website. Don't hesitate to experiment and learn!

04-01-2025
Harper Carter

More Replies →

Have you explored theAutomationDirect community forum? Join the discussion and seek advice from knowledgeable members.

27-08-2024
bernie_carlton

Hello, what specific issues are you encountering? It is crucial to verify that you are effectively communicating with both servos. In the example provided, a single MRX and MWX with a slave address of 1 is demonstrated. It is important for each slave to have a unique address to avoid communication conflicts. To implement interlocking, I have previously utilized methods such as shift registers or stage programming to guarantee that only one MRX or MWX box is actively communicating at any given time. Feel free to reach out for further assistance. Tom

28-08-2024
wolverine1981

Have you encountered any issues with communicating with multiple servos? In the example provided, a single MRX and MWX with a slave address of 1 are shown. It is important for each slave to have a separate address to avoid any confusion. For interlocking, using a shift register or stage programming can help ensure that only one MRX and/or MWX box is communicating at a time. In a second example for multiple drives, everything appears to be communicating properly with the comm error transaction count staying at zero. A count interlock feature is also in place to prevent more than one drive cycle simultaneously. One question that arises is how the MWX and MRX boxes function. For instance, when loading a revolution count into a parameter, how should the boxes be configured? Additionally, is it necessary to load revolutions and pulse counts for every movement? For example, if a servo needs to move 100 revolutions forward at 1700 rpm, how would this be implemented in the MWX and MRX instructions? Thank you.

29-08-2024
w_harbuck

How do MRX and MWX boxes function and how can they be used to load a revolution count into the appropriate parameter? In the provided example, Rung #8 demonstrates loading a value of K3 revolutions and a Position Pulse word of K500. However, you have the option to load a variable memory location, such as V2011 and V2012, to the LD instructions for data input from a touch screen or data view. It is essential to load revolutions and pulse counts for each unique movement, such as in the case of moving servo 1 at 100 revolutions in the forward direction at 1700 rpm. You can adjust values in the MRX / MWX boxes or use V-memory locations as shown in Rung 14. In Rung 14, the desired velocity is displayed using V-memory; simply input V2013 (Motor Velocity Reference in RPMs) in the Data View under the Element column and type 1750 under Edits. Click on the "Write Current Edit" button to apply the changes. I hope this information is helpful for your programming needs. Thank you.

29-08-2024
wolverine1981

Hey Wolverine, one challenge I'm encountering is that the standard V addresses provided only support one drive. I'm considering loading the data into a separate v memory location for the second drive, but I was under the impression that this process should be simpler.

29-08-2024
w_harbuck

After finally connecting with an experienced individual, I learned a valuable tip that has been holding me back. It turns out that V memory addresses are customizable, unlike the fixed v-memory locations I initially thought. Armed with this new insight, I am confident that I can make significant strides forward. I will continue to update everyone on my advancements. Thank you for your support.

29-08-2024
w_harbuck

In the Sureservo manual, Chapter 6 provides a starting point for setting up your servos. Have you followed the instructions in the manual and encountered any issues? I have experience with Modbus on the 260 but not on the Sureservo. I need help expanding the control to handle 6 servos - 2 on each station. I am struggling with creating additional stations without their feedback interfering with each other. The sample program uses notation like N2 for each address of the second servo. I assumed the IP address would differentiate the drivers, but that is not the case. The Modbus TCP card's IP address does not prevent the stations from reading each other's feedback.

29-08-2024
FrankT

FrankT asked Bernie for help with controlling 6 servos, with 2 servos assigned to each station. Despite using the provided sample program for two servos, FrankT is having trouble creating additional stations without interference. The program includes notation for each servo, with the second servo labeled as N2 for each address. FrankT assumed that using different IP addresses would separate the drivers from each other, but this is not the case. The IP address for the modbus TCP card still does not prevent interference between stations.

29-08-2024
FrankT

Hey FrankT, since this thread is over 12 years old, it would be best to create a new post in order to attract more attention and engagement. This will help increase exposure and reach a wider audience.

29-08-2024
jstolaruk

Streamline Your Asset Management
See How Oxmaint Works!!

✅ Work Order Management

✅ Asset Tracking

✅ Preventive Maintenance

✅ Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..

Frequently Asked Questions (FAQ)

FAQ: 1. What is MODBUS and why is it important for Automation Direct Sureservo systems?

Answer: - MODBUS is a communication protocol commonly used in industrial automation to establish communication between different devices. It is crucial for Automation Direct Sureservo systems as it allows for seamless data exchange between the PLCs and other devices.

FAQ: 2. How can I start programming MODBUS for Automation Direct Sureservo systems if I have limited PLC programming experience?

Answer: - To start programming MODBUS for Automation Direct Sureservo systems, it would be beneficial to first understand the basics of MODBUS communication protocol. Additionally, familiarize yourself with the Directsoft "V" addressing system and consider seeking resources or tutorials tailored for beginners in MODBUS programming.

FAQ: 3. What resources or guidance are available for learning MODBUS programming with AD 205 PLCs and 260 CPU for Automation Direct Sureservo systems?

Answer: - Apart from reaching out to AD tech support, you can explore online forums, user manuals, and tutorials specific to programming MODBUS for Automation Direct Sureservo systems with AD 205 PLCs and 260 CPU. Additionally, consider enrolling in training courses or workshops focused on industrial communication protocols.

FAQ: 4. Is math proficiency necessary for programming MODBUS for Automation Direct Sureservo systems?

Answer: - While basic math skills can be helpful in understanding certain aspects of programming, you can still learn and work with MODBUS communication without advanced math knowledge. Focus on

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo →