Thor Hammer

PLC: 1769-L32C Input Cards: 2 Each 1769IQ16 Output cards: 1 Each 1769-QB16 This system has been in operation for 10 years. The client decided to have our company change out the old Panel View HMI for an Omron NS5 communicating via serial. The problem I'm having is the tag names in the Omron touch screen. I cannot use the actual alphanumeric tag name as shown in the PLC in the Omron NS5. When I do it gives me an error message of "unused symbols in project" and I cant download. Turns out I have to use the numeric address. I don't know how to do this. I attached two screen shots. One is symbol input which evidently is incorrect. the other is input direct address which is correct. Problem is I don't know what to put in the "File No." field. In the example provided on the Omron website it is shown as a number. See attached screen shot. Where do I find the file no. for the input or output I am addressing to? I understand slot no. and bit no. of course. Additionally, I can certainly input my physical I/O I am using in the HMI once I know what to put in the File no. field. But how do I assign a numeric address to the internal relays and inputs that are not attached to physical I/O in my PLC program to use in the HMI? Like turning on and off my pump for example. Any help greatly appreciated. I miss the days of using C-More panels. Not as powerful but so easy to work with.  

Gents, I'm up against a wall and reaching out to find a system integrator that can assist us in writing some code for our PLC program. CJ2M-CPU11 communicating with an NS8. The ETN21 is supposed to receive and send info in ASCII to a computer. We have never setup this type of connection. The project is due in two days and I am out of time to figure it out on my own. I wanted to know if there is anyone that we can hire to write this code for us. I've read through all the manuals on TCP connections, sockets, and the like. I have more questions than answers at this point. The logic in the program is written. I just need the ASCII code and communications written. I understand that the ascii will come in and go out as HEX. What I don't understand is in the instruction manual W421 section 6-7 page 129 there is a programming example to open a socket in TCP. Do I just copy and paste this code? Where do I put the SEND RECV commands? Where do I put my multiple DM addresses (BSET) to write the ascii words (hex) to be sent? Its all very confusing for me. Desperately need help. I could figure it out over time through experimentation. However my boss has stated I am out of time and this unit ships in two days time. Any help or suggestions on whom can assist in writing the code that's adept at this type of thing is greatly appreciated.

I figured it out. Just wanted to update this thread.

I have a question. If the PC sends me a command in ASCII such as: #AB,ALIVE,LR When received into the buffer it will be in HEX correct? I can then parse the data to extract the word ALIVE and IF it equals ALIVE then I can trigger an output in my FB to send a response back that says ALIVE. Is that right? Or do I need to convert it then parse it?

Michael we are located in San Jose California. I've been on site doing startup and testing on the system for the past week. Our customer is fortunately in the same city.  They declined downloading Kepware to their PC in the wafer tool. Bummer. So I am now having to write the necessary strings in STL in CX Programmer. I've been reading the manuals and planned to use FB's for the opening and closing of the socket. This is all new to me and now I have to be done by this Sunday. Sure.

I'll have to ask the client. However, it is just a computer running windows with their custom software.  

This is the document with the communications protocol the client has provided to us. QORVO Chemical Mixer - Protocol - ASCII Command - v2.docx

I just spoke with Omron tech support. System memory allocation is not critical for my setup. I am not utilizing any of the status bits or words in my PLC program. The error I'm experiencing points to communications issue. The tech stated the node addresses should be the same but he didn't sound certain. I currently have them both set to 1. I will try making them different and the same. I've also been told its ideal to set them to 0. Well, the PLC was set at 1 when the software was initially developed by other parties. Beyond serial config settings it could be my cable I had made. I'll be checking it and may end up making a new one myself.  

Thought I had this all figured out. Went on site and connected the panel to the PLC. Downloaded the software and I get two errors on the touchscreen. Timeout error for system memory allocation. Timeout error for downloading HOST1 data. I'm at a loss. I don't completely understand what I am supposed to put in the fields for system memory allocation under setup. Can someone point me in the right direction? I'm under the gun to get this done like yesterday. Another question. If I am using full duplex DF1 serial comm does the node number in the panel need to match the station number in the PLC? 9621_SCR_V2.IPP

Ok, thanks!

Thank you for this! Very much appreciated. As I am not yet proficient in RSLogix 5000.... do I need to insert a JSR instruction in the Main Routine to execute my IO Mapping Routine? Or will it scan all routines? I didn't originally write this program. Just got stuck upgrading it and learning as I go. I am much better with RSLogix 500. Enjoying learning this software as well!

Quick question: I found under the Logic drop down menu an option to Map PLC/SLC Messages. I created an N7 array and placed it in the table. Is this necessary? I have created my N7 array in the edit tags table so not sure if I also need to have the above done as well. I am aliasing single bits of the integer word to my tags that are used in the HMI. Then inputting the N7 addresses in the HMI symbol table. Courtesy of Automation Direct https://www.automationdirect.com/microsites/c-more/software-help/Content/323.htm

Thank you Joe. This is very helpful and yes, it all makes sense.  I didn't understand what the file number was or where to find it. Sorry for the late reply. Was on a job in New York all weekend. I would happily use C-More or Red Lion. I didn't realize it would take mapping all my HMI tags in the PLC. We use Omron almost exclusively in all of our systems we build. Anthony

Attached is the Omron document on how to setup the serial port for AB. Is that what you're looking for? Edit: Jay beat me to it. Duplicate file. Omron NS Series Connection to AB PLC.pdf

Thank you Jay!

According to the instruction help file for a CP1E; data for TXD and RXD must be in UINT. However the device I am communicating with over RS485 in no protocol mode requires I send it a command string in Hex and Read back in Hex. I am a bit confused and could use some clarification on this. Can I send my data as UINT BCD or will the RS485 option port not recognize that data type? This project is a nightmare. The device I am communicating with is a Thermofisher chiller that has its own proprietary protocol. It states in the manual all data must be sent and received in HEX. Not ASCII. Would appreciate any insight.

Not confusing at all. Thank you for the reply. I now completely understand the different data types and how they translate. The attached code is what I last tried in an attempt to communicate with the Chiller. No luck. My boss said I needed to clear the buffer before transmitting my TXD so that's what I did. When I send the TXD the reception complete flag never turns on. And the port ready flag A392.13 flashes repeatedly. Would anyone care to look at my logic and see if anything jumps out at you as being blatantly wrong? I only included the sections in question from my complete program. I emailed Thermofisher and their lead tech said I do indeed need to send the zero's in the hex command string. His email to me: Hi Anthony,   Zero bytes (00) are required by the NC protocol. In the example used below, a total of 8 bytes must be transmitted by the master for this command. Master Sends: CC 00 01 F0 02 00 FA 12   All of the examples use bytes represented in hex as indicated by the letters (A,B,C,D,E and F).  No conversion is necessary.   The checksum is the last byte.  No additional end byte is required.  The chiller knows how long the command is based on the “n-bytes” that is transmitted with each command.   Best regards,   Scott   You can see that in my MOV instructions I have included the zero's where necessary. And in the above command after the F0 you see 02 This is the "n-bytes" field as there are 2 each. FA (00 which has no value but supposedly necessary in the command string) and the checksum value of 12. I assume that is correct.   In order for the checksum to calculate correctly I had to use the MOVD instruction and add up the bytes separately or it would not work. When I test my CS code using the example in the manual the result is correct. At least one thing works!   8262_PLC_V9 SVCS.cxp

As of right now my data in consecutive D-Memory locations to send to the chiller over the RS485 line is UINT. So what you are saying is I should change the data type to Channel? Will that make a difference and if so, why? Just curious. Thank you for clarifying and the table. I have that same table printed out on my desk.    

So I have never setup serial communications before. I have learned a lot in my research the past few days but I am new to this so...go easy on me. I have an Omron CP1EN40S1DR-A with built in RS485 port. And an Omron NS series 5" color touch screen. I need to send and receive commands with a Thermoscientific Recirculation/Chiller bath. The communications protocol in the Chiller manual is listed as NC Serial Communications. All data is sent and received in Hex according to the manual. No ASCII conversion allowed or utilized. I believe I would set my PLC to communicate in No Protocol mode but this option is not available in the pull down list on the Serial Options Port tab. I don't know what settings to use. I have been through the CP1E manuals and all it shows is RS232 and Modbus Easy Master. Any help greatly appreciated.   I have started to populate my MOV instructions with the command string in Hex. I am stuck on how to handle the Checksum. The chiller will not send a response without the checksum attached. According to the manual it is a bitwise inversion of the sum of the bytes in the checksum region. I take that value and XOR it with FF hex to get the bitwise inversion value.   Can this be done with simple add instructions in ladder logic? Then perform an XOR? what instruction for that? Even if I can generate my checksum value how do I then add it to my command string? And what do I compare it to? Wish I could just leave it off!   Manual pages attached and  my code so far (Serial_Comm) file. I have a long ways to go. All I want to do in this instance is read alarms, send a value for temp setpoint in 5 recipes and read the current setpoint. Pretty simple, but challenging to implement! NC Serial Thermofisher 2500.pdf 8262_PLC_V5.cxp

Thank you for the reply! I spent a lot of time on this yesterday. I have done exactly as you suggested. I created a subroutine for calculating the checksum and then moving that to a DM location at the end of my hex command string. All in consecutive order. I understand the difference in CX-Programmer #. & hex/decimal.  Do I need a start and end code? I think that is optional. Or is it required? Thanks again!

Anyone have any input?

Oh and if I am not mistaken CX-Protocol does not support CP1E series. Only CP!H. Is that correct?