Has anyone successfully established communication between a Micrologix 1400 and a Telesis TMC470 printer? If you have experience with this, which communication protocol did you implement? Any insights on the setup process would be greatly appreciated, as I've been facing challenges for the past few weeks. Additionally, is there a method to perform a loopback test on the RS-232 port of the TMC470 to verify its functionality? Thank you for your assistance!
You can easily test RS232 communication by utilizing your computer's serial port or a USB-to-serial adapter. I recommend using PuTTY (www.putty.org) since HyperTerminal is no longer commonly available. This terminal application allows you to send ASCII commands to the TMC470 by simply entering text, or you can connect to the 1400 model to monitor the data being transmitted by the PLC. Be sure to configure the serial communication settings correctly—typically, the default settings of 9600 baud rate, 8 data bits, and 1 stop bit work just fine. If necessary, use a NULL modem adapter to connect the receive pin to the transmit pin at the other end. Wondering whether your computer's serial ports are functioning properly? If you have two serial ports or USB-to-serial adapters, you can connect them using a null serial cable and run two instances of PuTTY. This setup allows the terminals to communicate with each other, ensuring that the serial ports are operational. Additionally, if the PLC is situated at a greater distance, the 1400 model offers the option of Ethernet TCP socket communication, providing greater flexibility for your setup.
Which protocol do you intend to implement: Programmable or Extended? Additionally, could you specify the data source for the output? Both Telesis protocols accommodate both printed and unprinted characters. The PLC effectively manages printed ASCII characters, but the unprinted characters may require additional processing and can sometimes appear distorted in Logix500. If the messages to be printed are generated on a PC or Human-Machine Interface (HMI), it is advisable to have that device assemble the complete message for the printer. You can then load it into a ST9 file and utilize the Automated Workstation Tool (AWT) in the PLC for efficient handling. – Shawn
To set up a programmable connection between your PLC and TMC470 printer, I’m specifically interested in implementing message type V (Variable Text). For instance, I would like to transmit a serial number formatted as 180327001, which represents the year, month, and day, followed by a three-digit serial number. The serial number would originate from a long integer in the PLC, which I will convert to a string as illustrated. I am looking for guidance on how to configure the TMC470 alongside the PLC for printed ASCII output. I must admit, I wasn't initially aware of the printed versus unprinted setup options, so I appreciate your understanding in this matter. Could you also clarify the serial cable connection between the PLC and the printer? Should I connect it as (2-2, 3-3, 5-5) or as (2-3, 3-2, 5-5)? Thank you for your assistance! It’s challenging to find individuals experienced with Telesis Printers, so I welcome any information you can provide. I will be on-site in a few days to finalize the logic and setup. One last thing to note: although you mentioned HMI/PC integration, all data will be generated from the PLC side. I assume I can simply transfer the long integer into my string (ST9) using the ASCII AWT function? Any insights would be greatly appreciated!
I must admit, I haven't personally used one of these printers; my insights are drawn from their manual and a bit of experience with ASCII and hex in MicroLogix. Below, I will walk you through the process using the Extended protocol, as I couldn't locate the message format for the Programming protocol. To communicate with the printer, input the following string: ``` Code:\1 \31 \2 01180327001 \3 \d ``` Next, send the subsequent command to the printer: ``` Code:\1 \47 \d ``` If all goes well, you should see the output "180327001" printed. It’s worth noting that the documentation lacks a clear example for this procedure. When discussing printed versus unprinted characters, we’re referring to the ASCII character set. It's essential to familiarize yourself with an ASCII table, which illustrates the correlation between Decimal, Hexadecimal, Octal values, and their corresponding characters. Certain characters play a role in signaling the printers but do not actually appear in the printed output; for instance, the carriage return is a common example. By understanding this information, you can effectively utilize your printer and troubleshoot more adeptly.
When sending strings via AWT or AWA, you can utilize the "^" symbol to mimic the functionality of the Ctrl key. According to the TMC470 documentation, it's crucial to implement the Programmable Protocol when establishing an RS232 connection. This protocol necessitates an initial character (Start of Text, or STX) and a terminating character (Carriage Return, or CR, represented by 13). While the manual outlines additional values for various configurations, the STX and CR are fundamental components. For RS500 programming, be sure to include these characters at the beginning and end of your string: ^B signifies STX, and ^M denotes CR. Additionally, AWA offers a convenient feature that automatically appends the required characters for you, streamlining the process.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.