PMCR

Ricardo It sounds like you should be almost there! Trying the 2nd bar code reader on the 1st system was a very good idea! Did you also try the cable that you have for the second system? If you can trigger the reader, but are getting no data, it could be something as simple as the cable. Like Bob indicated, check the port settings. I do this in CX Programmer. Check each and every setting to make certain that the 2nd systems settings are the same as the first. If you are not seeing any response in the Trace function, then the data is not getting back to the card. Is the 'Protocol Macro Transmission Method' set for Half Duplex or Full Duplex? It should be Full Duplex, as this is RS232.

The other issue that I have seen is that the CP1W-CIF41 does not handle all of the other network traffic (Rapid Tree Spanning, Tree Spanning, etc) very well. Isolating the PLC removes all of the other 'IT' traffic from the PLC, and lets the CIF41 focus on what it was designed for: FINS communciations.

There is no software for an Omron F160. The setup / configuration is done through the F160-KP or the F150-KP (kepyads) and viewed on the monitor attached to the F160. The setup and configuration can be loaded and stored to a Compact Flash card mounted in the F160 controller.

Interesting thought. I have run the Web Server for long periods of time (I have one running all the time in my office), but not with logging. It will be interesting to see if rob5029 is using either one of those features in his application.

I agree with Mendon Systems idea, but I wonder why it needs resetting. I have used NS terminals for many years, and never run into a situation where this was required. Can you provide some details about the overall system?

See here. I assume you are using Modbus RTU. The documentation for this is for Omron inverters, but works well with Yaskawa, if you know the correct registers / coils to use. http://forums.mrplc.com/index.php?app=downloads&showfile=867

denise01 If the port on the SCU card is not configured correctly, nothing will work. Configure the SCU card through the IO Table tool. There are 2 places to create the IO table for the PLC: CX Programmer and CX Protocol. Create the IO table in CX Programmer. Here are the steps. 1. Go Online with CX Programmer. 2. Put the PLC in Program mode. 3. Double Click on the IO table (from the tree view). 4. Click Options / Create. 5. In the Dialog Box that asks 'Are you sure you want to create the IO table', click 'Yes' 6. In the Dialog Box that asks 'Initialize CPU Bus Settings', click 'Yes'. 7. In the Dialog Box that asks what to transfer, leave both boxes checked and click 'Transfer'. 8. Once the IO Table has been transferred, click OK. 9. Click the '+' sign next to Main Rack. 10. Double Click on the SCU31 card. 11. Make the settings as shown in the manual for the Modbus Master program. This is also shown below. 12. Click "Transfer PC to Unit'. 13. In the dialog box that asks 'Are you sure you want to continue', click 'Yes'. 14. When the transfer is finished click 'Close'. 15. In the dialog box that asks if you wish to restart the module click 'Yes'.

When you convert from a larger screen to a smaller screen, the objects are not automatically resized. So, most likely the objects that are 'missing' are simply off the screen. Change the Zoom to 100% (or smaller if needed) to see all the objects that are off the screen. You will need to open each screen and resize the objects. You can select all the objects, and then grab the corner of one and resize all the objects at once.

I just took a look at the port configuration for the SCU module. The first setting for Port 1 is Port Settings. If you leave this at 'Defaults', it ignores all the other settings that you make. It appears as though this is the case for your project. Set Port Settings to 'User Settings'. Also set "Maximum Number of bytes in Protocol' to 1000 to allow the maximum receive buffer size (this is not the problem). Look in the manual for the Modbus Solution (page 6) for the setup of the port. Set the port exactly as shown, and download the settings.

Lost Control appears to be on the correct path! The addresses in the ATV31 document appear to be in decimal, but Modbus need them in HEX. The other thing you may try doing is subtracting 1 from the Modbus address. Some manufacturers document the address, but the Modbus mapping is really 1 less. The other thing you could do would be to use CX Protocol and do a trace of the serial port. This would show us exactly what is being sent and returned from the drive (if there is a response). The .pdf below shows the steps. Save the Protocol Macro file, and then post when you are done. The data that you trace is saved as part of the file. CX Protocol Data Trace.pdf

The problem that you are having is that you are trying to mix protocols. EtherNet/IP is a CIP protocol. Controller Link is a FINS protocol. To connect across Ethernet to Controller Link requires using FINS Ethernet (either UDP or TCP). You can't connect to a PLC via EtherNet/IP, and then route across Controller Link with FINS. In any CX application, setup the CJ2, and then click the 'show all' checkbox under the Network Type dialog box. Then choose Ethernet as the comms method. This is why all CJ1 / CJ2 / CS1 / NJ EtherNet/IP modules also support FINS simultaneously. Make certain that the Ethernet card is in the FINS routing table.

Great discussion! I have seen a distributor come and go with B&R. The commends from the engineers centered aound the ease of use, or lack there of. I have not used the product, but from the users that I have seen who have used it, the sentiment is 'once you have it working, it works well', but 'good luck getting there'.

Given the correct Modbus RTU addressing, the E5CN is Modbus RTU capable. You do need to set the COMMS in the E5CN to Modbus. CompoWay/F (Omron protocol) is the default.

Vijaya Welcome to the world of Omron! What Omron PLC are you using? This will help us to provide more specific answer. In CP1L, CP1H, CJ1, CS1 PLCs, there are 2 different ways you can use timers and counters: BCD and Binary (HEX) ranges. BCD Timers / Counters have a range of #0000 to #9999, and Binary Timers/ Counters have a range of #0000 - #FFFF (&0 - &65535). If you are using a CJ2M or CJ2H PLC, you do not need to select between using BCD or Binary Timers/ Counters. You can use both types of timers / counters in a program. For CP1L, CP1H, CJ1, and CS1, you make a choice of using BCD (default) Timers / Counters or Binary Timers / Counter by right clicking on the PLC in the tree view in CX Programmer, and selecting Properties. You can put a check mark in Execute Timer/ Counter as Binary to select the Binary timers / counters (TIMX, TIMHX, and TMHHX, instuctions). There is also a 'long' version of the 100 ms resolution timer (TIML (BCD) or TIMLX(Binary)) Unfortunately, the Totalizing Timer that you are using is not available in a long version, so the range is limited to &0 - &65535 (0 - 6553.5 seconds) The other way that I tackle this type of timing is simply use some of the P_xxx system bits such as P_0_1s to increment a UDINT value, as shown below.

The attached .pdf should have all the settings that you need for the NS, CJ1, and CP1Ls. NS Comms.pdf

ICase Yes, this can be done! It takes a little doing, and some understanding of FINS Routing in an Omron PLC. If you can provide the exact configuration, I can walk you through the setup. What I need is: 1. Model(2) of CP1L (specifically 1 or 2 plug in slots on the front). 2. Which socket the CIF41 is plugged into on the CP1Ls. 3. IP Addresses (or at least the last octets of the CJ1M and CP1Ls). 4. FINS Network number (if any) that was assigned to the CJ1M and / or CP1L for Ethernet. 5. Which serial port (Port A or Port B) on the NS is connected to the CJ1M.

That's great! I agree FBs are very useful. It begs the question: can you share your function block? I have created one that takes the output of PID and time proportions it for a digital output. You can pass the output of the PID function, the output resolution of the PID instruction, and the time base (control period) of the digital output into the FB, and you get a digital signal and a MV for monitoring.

You can also look here for a more complete solution. http://forums.mrplc.com/index.php?app=downloads&showfile=867

The 'Socket Services' function of the ETN21 is just the Omron way of saying 'user defined protocol', as opposed to FINS. I have used it for bar code readers, torque wrenches, and numerous other non Omron protocol devices. It works with UDP and TCP, and you can have up to 8 sockets open at a time.

ptrksr First of all, great diagnostic information! Screen shots are the best way to get help quickly! In your CIF41 setup, you show 10.50.2.32 as the IP address, with 32 as the node number. Proper standard FINS node address based on the last octet of the IP address. In the Color Coded FINS Messaging Tool, you have 54 as the Node Number (which I hard coded as the default). Do you still get the same response if you change the node number to 32? I have tried to replicate this with a CIF41, and as long as I have the destination node number set correctly, I cannot cause the error.

Yes, the PID instruction is for exactly this. There are 2 different instructions: PID and PIDAT. PID is the older version. PIDAT is the newer version, and does everything that PID does, and adds Auto Tuning (that's the 'AT' part of PIDAT). I would strongly suggest PIDAT. When you go to implement PIDAT, give us some information about your control loop, and we can help you with the handful of parameters needed to set it up. It can be a little confusing at first, but once you have it setup, it works great! The information that we would need is: What is the numeric range of the input data. ie 0 - 2000, 0- 4000, 0 - 12000, etc. This would be the data coming from the input device. What do you want the range of the output to be? 0 - 2000, 0 - 4000, etc. This would be the data going to the output (if it is an analog output). Is this a Forward Loop (meaning that you want the output to go UP as the input goes UP), or Reverse (meaning that you want the output to go DOWN as the input goes UP).

I would agree with Geir The PIDAT instruction should be a very good fit for a pressure control application, if the control loop is not exceptionally complicated. The LCU for the CJ is a good fit for more complex process loops such as feed forward, cascade control, etc. PMCR

Attached is a photocopy / scan of the Hostlink settings that I use for both a 3G2A6-LK201 and a 3G2C7-LK201. C Series Host Link Settings.pdf

For a simple diagnostic, you can use either Supermon or Multiway for a simple Hostlink test. The most basic test command for Hostlink is @00TS123443*<CR> , where <CR> is Carridge Return. @ = Hostlink Header 00 = Hostlink Unit number TS = 'Test' command 1234 = data 43 = FCS *<CR> = terminator Supermon http://forums.mrplc.com/index.php?app=downloads&showfile=575 Multiway http://forums.mrplc.com/index.php?app=downloads&showfile=836

Yes, my router has the information from my ISP as to where the DNS server is located, and it passes DNS requests to the DNS server. Yes, mail.comcast.net is the POP server.