Hello everyone, I have been relying on this website for valuable advice for quite some time now. However, I have encountered a challenge that I need help with. I am working with a Red Lion DA30 controller using Crimson 3.2, attempting to establish communication with an Alicat MFC (Mass Flow Controller v7) that utilizes RS-232 Raw ASCII protocol. While I am familiar with Crimson, I have limited experience with Port commands and programming for communication purposes.
My current task involves sending a command to the Alicat MFC device. From the manufacturer's manual, the command structure is as follows: "Poll the device: [unit ID]
Welcome to the PLCTalk forum community! If you've come across tech note TNIA10 as your starting point, you're on the right track. To begin, consider starting with a basic task: creating a button that triggers the PortPrint instruction. Since it's a serial RS-232 connection, you'll use PortPrint instead of PortPrintEx. To determine which physical port to use on the DA30, refer to Crimson 3.2 and the default DA30 project. The "RS-232 Comms Port" is labeled as Port 2 in the lower left corner. Create a button with a simple line of code like PortPrint(2,"A\r") and test it by connecting to your PC's serial port using the appropriate settings. Next, configure the RS-232 port to execute a program when data is received. This involves entering the ProgramName() in the OnUpdate field in the Driver Settings for the RS-232 port. By following these steps, you'll be able to effectively utilize your RS-232 connection.
Are you looking for the part number of the Alicat MFC or a visual reference of the terminals? Do you need a diagram of the RS232 connection, including TX, RX, and GND? Are you unsure about the RS232 Port settings on the Alicat MFC, such as Baud and Stop Bits (commonly 8N1)? Have you encountered issues with software due to hardware errors, like incorrect wiring placements on RJ11 connectors used on Graphite HMIs? If so, a search on the Alicat website reveals the availability of their own Serial Tools software and drivers for seamless communication with Alicat mass flow and pressure instruments. These tools can be found on their website about halfway down the page. Don't waste hours troubleshooting like I did - make sure to verify all connections and settings before jumping to software-related issues. Make use of Alicat's resources to ensure smooth operation of your devices.
Ken Roach welcomes you to the PLCTalk forum community! If you've already checked out tech note TNIA10 as a starting point, that's great. To get started, focus on creating a simple button that performs a single action when clicked, such as using the PortPrint instruction for serial RS-232 communication on a DA30. Ensure you are using the correct physical port, which is typically Port 2 in Crimson 3.2 for the DA30. Try setting up a button with a basic line of code like PortPrint(2,"A\r") and test it by connecting to your PC's serial port. Then, configure the RS-232 port to execute a program when data is received by adding the ProgramName() in the OnUpdate field in the Driver Settings. Ken, it's great to hear that TNIA10 has been helpful for you. The subtle reminder of the RS-232 Comms Port in the lower left corner of Crimson is a handy feature. You can proceed with confidence and give it a shot! Thanks for sharing your insights!
In a discussion, BryanG asked for specific information regarding the Alicat MFC, such as the part number, a picture of the terminals, and details on the RS232 connection settings. He also mentioned spending time troubleshooting software issues only to realize there were hardware errors. He pointed out potential mistakes in RS232 connector types and wire placements on Graphite HMIs. A suggestion was made to use Alicat's Serial Tools for assistance. Additionally, Bryan shared insights on the Alicat's 6 pin Industrial Connector and its connection to an RJ11 cable. The pinout details for the DA30 RJ11 were also provided. Confirming the correct wiring, Bryan noted that the Baud Rates matched and were accessible through the MFC's touch screen.
The connection setup seems incorrect. RS232 utilizes TX and RX for transmit and receive signals, rather than the traditional (+) and (-) markings found in RS485. To ensure proper configuration, refer to the DA30 manual provided below. If using RS232, confirm that the Alicat is set to this protocol. Connect Alicat Pin 2 TX to DA30 Pin 2 RX, Alicat Pin 3 RX to DA30 Pin 5 TX, and Alicat Pin 5 GND to DA30 Pin 3 or 4 COM. If RS485 is being used instead, please contact me for revised pin assignments.
Hi there! You're definitely digging into some of the deeper layers of interfacing here! If you're struggling to get the DA30 to read data, I might suggest you confirm the basics first: Is the baud rate right? Have you set the parity and stop bits correctly? Once you validate those, here's a step you may not have considered: Make sure you're providing time for response between sending commands and attempting to read data. I've found the need to introduce a small 'pause' between write and read operations with certain devices. Also, ensure your communication wires are in their appropriate port. Remember, RS-232 can be a bit tricky with the transmit and receive wires as there are crossover cables. If crossing them over doesn't work, you might even consider scripting the process and use the WRITE followed by READ function in your script while working in Crimson. Keep going, and remember that sometimes it's the simplest things that trip us up!
Hey there, it sounds like you're on the right track but facing a bit of a pickle with the Port commands in communication. Here's a suggestion - you might want to ensure that both your DA30 and MFC are set to the correct baud rate, parity and stop bits, as communication issues often stem from these settings. Since Alicat uses 8-N-1 (8 data bits, no parity, 1 stop bit) configuration, make sure your DA30 is set to match it. Additionally, you could try using a terminal emulator application such as PuTTY or Tera Term to send commands manually and see the Alicat MFC's responses. That way you can see exactly what's being sent and received, which might help you diagnose exactly where things are going wrong. It also helps to start with simplest commands, confirm everything is working and gradually add complexity. Best of luck with your troubleshooting!
Hey there, it sounds like you're knee-deep in the nitty-gritty here. I've worked with Red Lion controllers before and even though you're familiar with Crimson, the communication aspect can get a bit tricky. Based on your situation, I would suggest verifying if your RS-232 settings match between your DA30 controller and the Alicat MFC. It's a common mistake that can often result in communication failure. Also, make sure your wiring is correct; RS-232 communication can be quite finicky about that. Lastly, remember to check your command string; typically, the RS-232 Raw ASCII protocol requires CR (carriage return) and LF (line feed) at the end of each command. Hope that helps and good luck!
Hey there! It sounds like you're on the right track, but I know how tricky serial communication can be. Have you double-checked the baud rate and other serial settings on both the DA30 and the MFC to ensure they're matching? Sometimes a simple mismatch can stop data flow. Also, make sure that the command you're sending includes both the unit ID and the
Hey there! It sounds like you're dealing with a tricky situation, but you’re definitely on the right track. Since you're working with RS-232, make sure that the baud rate, parity, data bits, and stop bits settings on the DA30 match what the Alicat MFC requires. The command structure looks good, but remember that special characters like
✅ 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: To establish communication, you can utilize RS-232 Raw ASCII protocol and send commands following the structure specified in the manufacturer's manual.
Answer: Answer: The command structure for polling the device is "[unit ID]
Answer: Answer: You can read data from the port using programming commands and protocols specified in the manufacturer's manual or relevant documentation.
Answer: Answer: You can review Tech Notes from Red Lion, reference sample code, and seek advice from forums or experts in the field to troubleshoot and overcome communication issues.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.