I am currently involved in a project that initially began on a SparkFun RedBoard Artemis. After conducting some testing, I have decided to incorporate a PLC into the project for enhanced performance. The project entails the need for four RS232 communications for scale integration, PWM output for servo control (similar to an RC car), DC output for a small pump motor, and the ability to read from two encoders to track the number of revolutions. I encountered difficulties in establishing RS232 communication for the four scales, leading me to consider integrating a PLC. My main query is whether it is possible to establish communication between the RedBoard Artemis and the PLC. I am planning to employ a Productivity 2000 series PLC for this purpose. Given that all the necessary hardware has already been procured, I am keen on maximizing its utilization rather than investing in new equipment and redesigning the setup. Has anyone attempted a similar integration before? Essentially, I intend to leave the encoder inputs, servo, and DC motor on the RedBoard Artemis, while transferring the RS232 communications and data output (to an SD card) to the PLC. The PLC would be responsible for sending signals to the Artemis to control the servo and start the DC motor, as well as retrieving data on the encoder readings per cycle. I would appreciate any insights or suggestions on this matter!
1) While Modbus (RTU or TCP) is considered a relatively straightforward protocol, signal timing can sometimes pose a challenge. 2) Developing a custom protocol with a specific scope may not be overly complicated. What communication options does the Artemis support in terms of physical connections?
drbitboy mentioned that while modbus (rtu or tcp) is not overly complicated, signal timing issues may arise. Could you provide more details on what you mean by "signal timing"?srsicard3 shared that they are currently working on a project that was initially developed on a SparkFun Redboard Artemis. The Redboard Artemis is a popular board that I've been eyeing for some time. I have successfully connected to several PLCs and HMIs using MODBUS TCP with both the Arduino UNO and MEGA. Setting it up is straightforward, although understanding the MODBUS mapping can be a bit challenging at times. If you're interested, I can help you find some sample code.
Are you considering the expenses involved in acquiring these items? The 4 RS232 cards are a significant investment, and there are other non-standard components to consider when outfitting PLCs.
WhinnieThePooh asked for clarification on the concept of "signal timing." The Modbus specification outlines specific timing requirements for Modbus RTU (serial) communications, as detailed in the Modbus Serial Line Protocol and Implementation Guide V1.02, section 2.5.1.1. While many Modbus RTU-capable devices may have UARTs with buffers that exceed or disregard these specifications, it is essential to consider the devices OP is working with. Implementing the Modbus protocol itself is straightforward, but meticulous mapping is crucial, although some vendors may struggle with this. By providing an example of an Arduino Modbus application, users can find a solution for their task and enhance the Downloads section of this website. Additionally, the initial response to this thread was made from a mobile phone, possibly leading to the humorous autocorrect in the text.
The sample project files are attached for your review. The Arduino used in this project is a non-brand MEGA, paired with an ethernet shield from Sunfounder. The HMI display is a 10" LSIS model that was readily available. I conducted a successful test this afternoon and found that all components are functioning perfectly. The communication speed is impressive and the connection appears to be highly reliable. The software for the HMI can be downloaded for free to view the program file. Additionally, for more information on Arduino Modbus TCP, a quick search on Google can provide helpful insights. Enjoy experimenting with this project! Please find the HMI software here: https://www.ls-electric.com/products/view/Smart_Automation_Solution/HMI/XGT_Panel/XP-Builder. Please note that the video file had to be heavily compressed due to its large size, resulting in reduced quality, but it is still watchable.
Your project sounds really intriguing! I can understand why you'd want to stick with your current hardware. As for communication between the RedBoard Artemis and the Productivity 2000 series PLC, it’s definitely feasible through an RS485 or RS232 interface, given that both devices support them. You might need to write specific firmware for the Artemis to handle the communication protocol used by the PLC. This could be Modbus RTU, or perhaps you could set up a custom protocol if you find that easier. Something else you might consider is the PLC's ability to handle multiple RS232 communications simultaneously because this can potentially create a bottleneck in your system. Make sure the PLC you choose has enough processing power and the necessary number of RS232 ports. Lastly, transferring the data output to an SD card with the PLC may require additional programming knowledge as not all PLCs support SD cards natively. Good luck with your project!
Your project certainly seems complex but fascinating! I agree with your approach of maximizing existing equipment usage. I have limited experience with SparkFun's Artemis, but I've worked quite a lot with PLCs. The Productivity 2000 series from AutomationDirect supports Modbus TCP/IP and RS232 communication, among others; combinations of these could help you establish a connection with your RedBoard. For this, you might need a RS232 to TTL converter module if you don't have one yet. It's pretty straightforward to use UART for RS232 communication on Artemis, and there are plenty of libraries available to assist you. To ease your workload, perhaps consider dedicating the PLC to data-intensive tasks such as logging, and leave the real-time control to the microcontroller. This could prevent potential issues with latency, and would make the most of the processing capabilities of each platform. I hope this helps!
It sounds like an interesting project you have going on! Integrating the RedBoard Artemis with a Productivity 2000 PLC should be doable, especially since you're planning to use the PLC primarily for RS232 communication. You can typically establish serial communication between the two via something like a TTL-to-RS232 converter. Just ensure you manage the baud rates and communication protocols correctly. For the signals from the PLC to the Artemis, you might want to consider using digital input pins or even a simple I2C or SPI communication for more flexibility. It’d be great to keep the RedBoard for the real-time tasks while letting the PLC handle the more complex RS232 interactions. Keep us posted on your progress; it’ll be exciting to see how it all comes together!
It sounds like you've got a really interesting project on your hands! Using a PLC alongside the RedBoard Artemis can definitely streamline your RS232 communications, especially since it can handle multiple connections more robustly. To facilitate communication between the PLC and the RedBoard, you might consider setting up a serial connection between them, utilizing the UART interfaces. The Productivity 2000 series should allow for easy serial communication setup. Additionally, you can write a simple protocol for data exchange, which could simplify how the PLC sends commands to the Artemis for the servo and motor while keeping encoder readings organized. Just make sure to account for the timing and handle any potential data conflicts. Best of luck with your integration!
It sounds like a cool project! Integrating a PLC with the RedBoard Artemis can definitely streamline your RS232 communication challenges. If you're using the Productivity 2000 series, you might want to look into using Modbus RTU or TCP/IP for communication between the two devices, as both are quite reliable for industrial applications. You could connect them using serial or Ethernet, depending on what you find easier to implement. Just make sure to handle the data flow management properly; you want to ensure that both devices are talking to each other smoothly without overwriting any crucial data. I’ve seen similar setups work well, so with the right configuration, you should be able to optimize your project without too much hassle! 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: - Yes, it is possible to establish communication between the RedBoard Artemis and a Productivity 2000 series PLC.
Answer: - While specific experiences may vary, there have been successful integrations of Arduino boards with various PLCs for different projects.
Answer: - The encoder inputs, servo, and DC motor would stay on the RedBoard Artemis, while RS232 communications and data output to an SD card would be handled by the PLC.
Answer: - The PLC would handle sending signals to control the servo and start the DC motor, as well as retrieving data on the encoder readings per cycle.
Answer: - Difficulties in establishing RS232 communication for the scales have led to the consideration of integrating a PLC for enhanced performance and efficiency.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.