10/26/2010 5:13 PM | |
Joined: 7/7/2010 Last visit: 3/10/2025 Posts: 15721 Rating:
|
I've recently worked on S7-1214C / RS-485. My first suggestion is to get the latest firmware in the PLC (1.00.02 or something like that). It corrected some issues we were having with RS485/ethernet communications. Second suggestion would be to investigate a RS485 isolator or full-duplex/half-duplex converter. The PLC RS485 module is half-duplex only and only have profibus wiring. There isn't any RTS/CTS, so you'll have to hardwire the RTS signal high (which you may be able to do with a RS485 full/half duplex converter. Can you communicate with a terminal emulator on your computer over RS485? I started out with a RS232 / RS-485 converter to verify communications parameters (baud/bits per word, etc.). Once the parameters were know, put them into the PLC program. Had the drive send out something and had the PLC watch table set to show the buffer. You will want to look at the FAQ on how to use strings with the buffer. https://support.automation.siemens.com/WW/llisapi.dll/42002283?func=ll&objId=42002284&objAction=csView&nodeid0=34612486&nodeid5=38718979&lang=en&siteid=cseus&aktprim=0&extranet=standard&viewreg=WW&load=treecontent It is also important to understand the start and end conditions for message receipt are "OR". If you know the last character appended to every message is <cr> (16#0D, Dec 13), you can put in 0D for the hex character and the software will do a much better job of pulling in message traffic one at a time. It takes some tweaking to find the right combination of start/end conditions, but it will help ignore the noise traffic (invalid packets of data). Hope this is helpful. |
science guy |
|
Follow us on