PMCR

Sergei is correct. The PLC does not process any instruction differently if you have a data type set for Channel, Word, UInt, etc. Channel is the 'generic' method that avoids errors, but it is less helpful when trying to remember if a symbol is being used as BCD, HEX, etc. In the olden days, I used to create symbols as B_Timer_Value (B = BCD), or H_Motor_Speed (H = Hex).

See the attached program. I have modified it to the point where I think it would work, but I did not actually try it on a CQM1. 1- in rung 6, the brake is set with an always-on bit. I've tried this with a negated contact of the motoroutput 000.00. Also a bit 030.00 parallel to 000.00 didn't work. Has this something to do with the inputsscan needing refreshment? Is there some memory that I can use for markers in the interrupt subroutine? A - I think the P_On should be just fine. The interrupt will only trigger 1 time on the rising edge of the mark sensor. 2- What about the use of timers in an (interrupt) subroutine Would it be possible to put rung 0 in the interruptsubroutine? A - No, you do not want to put the timer in the subroutine, because it only runs 1 time when the sensor triggers it. 3-where is the best place/moment to reset pending interrupts. I guess it would be better immediately after the motor has started? A - Why do you need to cancel the 'pending' interrupts? If you leave the interrupt unmasked, you will not have pending interrupts. Normally, you would unmask the interrupt, and leave it unmasked. 4- How to write a value in DM6628 in the program. The Move instruction can't do it? A - DM6628 is setup through the 'Settings' in CX Programmer. That did not exist when the manuals for CQM1 were written. motorinterrupttest2.cxp

BITS N BYTES 81 is the internal address where Omron stores the startup mode of the PLC. I will brew you up a Function Block to give you the mode. Done... RunMonitorModeDetection.cxp Basically, I am sending the CPU an 0601 FINS command. I seperate the Mode and Status parts of the response out for you. The FB will only run when the PLC is running, so use a W or CIO area for the Outputs from the FB. These will go to 0 when the PLC is not running. So, Mode = 0 when the PLC is stopped, Mode = 2 when the PLC is in Monitor, Mode = 4 when the PLC is in Run. I left it all unprotected so you can see / edit. I tested it in a CJ1H-H CPU, but you can save the FB and use it in a CP1L.

LostControl All the NS V2 products support the Web Server and FTP functions, with the exception of the Web Server on the NSJ. NSJ will not do the Web Server, but it will do FTP. NS V1 will support FTP server, but not Web Server. Not all FTP clients play well with the NS FTP server, but many do. I have a free FTP client that works very well with the NS if you need it. The OS used on the NS does not support all FTP functions, which is the reason that not all FTP clients will work. Automating the process should work just fine.

I chased my tail for a while trying to understand that all one day. The cross linking on the Microsoft web site is very confusing on this issue. Several individuals the I work with are running the XP Mode for Windows 7, with USB support for CP1H and other Omron products with no problems.

BobB Again, I could be wrong, but I think that Microsoft pulled a fast one on you. The last link switched you back to Virtual PC 2007. This does not support Hardware Virtulalization. It does support serial and Ethernet ports, and this is the environment that I use for my RS Logix 5000 on a WinXP machine.

BobB I may be wrong, but everything that I have read says that the new Windows Virtual PC is only for Windows 7. I don't have an Vista Business machine to try it out on. Let us know how it goes!

CX_Luigi Here is my take on this. I have copied out the code so others can read without opening the project. (* computes temperature difference used to determine partial water type dosings *); difference:=hotLineTemperature-coldLineTemperature; temp_hot:=batchTempDesires-coldLineTemperature; (* compute water quantity to dose *); volumeHot:=(temp_hot/difference)*volumeToDose; (* output control for dosing h/w and c/w parts *); dosingInProgress:=volumeToDose-volumeDosingInProgress; dosingHotInProgress:=volumeDosingInProgress-volumeHot; while dosingInProgress>0 do while dosingHotInProgress>0 do hotWaterValve:=true; end_while; hotWaterValve:=false; coldWaterValve:=true; end_while; The variables that you are using for the While / End_While are never going to get updated, as they only get updated when you call the FB from ladder. This is a FB that gets called 1 time per scan. Each time you enter the function block, you will stay in the While / End_While loop until it is satisfied. If you wrote this in VB.Net, which is a multithreading environment, you would stay in the While / Wend loop until it was satisfied, but the OS would allow threading to other processes. In the PLC, this is not the case. The only good use of While / End_While instuctions in a PLC (in my opinion) are for cases when you are updating the While variable in the While loop.

There is a 'work around' for Windows 7 64 bit and Omron USB drivers. Microsoft has a new virtual PC called Windows Virtual PC. This is for Windows 7 only. It is a free download, as is XP Mode, which is a virtual hard drive of Windows XP. This new Virtual PC features Hardware Virtualization, which must also be turned on in the BIOS of the PC. This allows direct support of USB in the XP OS, without loading the USB driver in the Windows 7 environment. This allows the USB drivers in CX One to work on a 64 bit Windows 7 machine. See more at the Microsoft site below. http://www.microsoft.com/windows/virtual-pc/default.aspx

gamerayers I verified this morning with a test on a CS1. You do not need to jumper 7 and 9. Some older Omron diagrams show this as the 'universal' cable. The reason for pin 7 to be included was to support the older H series PLC (C20H, C28H, C40H), as well as some older NT HMIs that had a built in 9 pin port, but SG was on pin 7. If 7 and 9 were jumpered on the programming cable, you could use the cable for C200HS, C200HX, CQM1, CQM1H, NT, C20H, etc, as a 'universal' cable.

tncanuck The module that you have is not capable of generating Email. Only a CJ1W-ETN21 attached to the side of the PLC is capable of generating Email. Due to patent held by another company, Omron cannot serve data by web page on the PLC. The NS series HMI is capable of serving data across the web from the built in web server, if you are using such a device. Don't worry, very few people are fluent in Klingon.

It may be as simple as not having the RTS / CTS lines on the port connected. Try placing a jumper between pins 4 and 5 (RTS and CTS).

The PT Notify area is information that is sent from the NT to the PLC, so you do not need to put anything in that area.The manual for the NT31C explains the format of the PT Notify area if you are interested in investigating.

f the NT is on a blank screen, this is screen 0. You cannot program screen 0.The way to move off of screen 0 is to move a #1 (for screen 1) to the first word of the PT Control area (setup in the NT software).So, in ladder, execute a MOV(21) #0001 D500, If D500 is the start of the PT Control area. I do this on the First Scan of the PLC by using the P_FirstCycle bit. (May be called the P_FirstScan, I am not at a PC with CX Programmer.)

You can change the from the constant '#15' to a variable 'DM50' (Data Memory 50) as an example. Then you can manipulate the data in DM50 however you need to. The timer will then time as a function of DM50. The image below will run at 1.3 seconds on, 1.3 seconds off when 0.00 is on, and 1.5 seconds on, 1.5 seconds off when 0.00 is off. You could use 2 different Data Memory locations to create independent on and off times.

I will answer this 2 ways. If your question is: Can I do this from within my facility, then the answer is yes, assuming the FINS routing is setup correctly. If your quesiont is : Can I do this across the Internet, then the answer get more compicated. It is possible, but the IP address of the router located at the PC location must be programmed into the NS. This is somewhat limiting. Either way, BobB is correct. It is somewhat slow. This can be mitigated somewhat by increasing the 'peripheral services' setting in the PLC to allow more time per PLC scan for servicing peripheral devices, but in the end it is still slow.

pszczepan This is very simple. In CX Designer, simply setup the SerialA setup in CX Designer, then go to the Find menu, and select Change Host. Search Host = Host3 Replace Host = SerialA (or Host2 if you are naming it that). Click Replace. You can leave the Ethernet service enabled for upload / download and Web Server functions without using it to connect to a PLC.

TR = Temporary Relay. PLC uses they 'behind the scenes' to remember the state of logic at a branching point. Drawn out for CJ1, CJ2, CS1, CP1H, CP1L would look like this. Drawn out for C200H, CQM1, CPM1, CPM1A, CPM2C, and other C Series PLCs would look like this. The only differences are that the timer contacts are TIM002 vs T002 and different internal addresses for P_On.

Charlie Great information. I think the IP router table is the issue. Lets get a look at the version of the ETN module. 1. Open the IO table in CX Programmer. 2. Upload the IO table if you do not see the Ethernet module listed. 3. Right click on the ETN21, and select Unit Manufacturing Information. 4. Look at the Unit Ver (the last item) as shown below. If this is 1.3, 1.4, or 1.5 then set the IP router table as shown. This will send all traffic not bound for the local network through the router. If the Unit Version is before 1.3, then setup as shown below. This will send all traffic bound for 10.160.6.* through the router.

Omron modules are typically not 'field upgrade' capable. Even if the firmware is older, there is no need to upgrade. You would simply enter the IP Router info differently. If you can put together the following information, I can probably nail down the issue: 1. Screen shots of the setup of the ETN21 from CX Programmer / IO Table utility 2. Screen shot of CX Programmer / Network / Setup / Driver tab for the 2 PCs talking to the PLC. (This is where the IP address of the PLC is set).

The idea of the IP router table is to build 1 or more 'gateways' to IP segments that are not local. The best way to do this on ETN21 modules of firmware 1.3 or higher (1.5 is current) is to set 0.0.0.0 10.160.5.254. This will force all traffic that is not being returned to the local network to go through the router. On firmware versions before 1.3 of the ETN21, 0.0.0.0 was not allowed, so you did 10.160.6.0 10.160.5.254. In either case, local IP addresses do not belong in the IP router table. Multiple PCs (SCADA, CX Programmer, etc) should not be a problem for an ETN21. On the setup of the ETN21, what 'Conversion' method are you using? Auto-Dynamic, Auto-Static, etc.

rquirch The issue that you are having is with the way that the NS resolves the IP address to send the response back to. We call this FINS to IP conversion. The PLCs and the NS do it slightly differently, with the PLC being more advanced. When the PLC Ethernet module is setup in AUTO:DYNAMIC FINS to IP conversion mode (the default), it maintains a dynamic list of the IP address of the originating FINS nodes that send a command to the PLC. Then it does a reverse lookup when it goes to respond to that node. The NS does not have the AUTO:DYNAMIC mode. It can only respond to nodes on its own segment, unless you create a table of nodes on other segments. In the NS, you will need to create entries in the Conversion Table to list all the IP addresses (and corresponding Node Numbers) of PCs and PLC on the other segments that you want the NS to communicate with. See the example below. The NS is 192.168.5.66. I added a node 44 at 192.168.1.44, which could be a PC or PLC. As you can see, the PC will need a static IP address to be in the list.

Sasha The USB ports on CP1E, CP1L, CP1H, CJ2 are only accessible through Omron software. For user applications, you can use CX Server Lite (ActiveX), CX Server OPC (OPC), or SYSMAC Gateway + CX Compolet (ActiveX through Sysmac Gateway). The protocols used are: CP1E, CP1L, CP1H: Toolbus CJ2 Toolbus or CIP.

To determine the actual time per device, I think you will need to do a data trace, so we can see what is going on. Trace A202.00, 1634.15, W10.00 (assuming node 1 is active). Tell me what your scan time is for the PLC. Do the data trace with a resolution of every scan, save the file, attach. Do the data trace with a resolution of 10 ms, save the file, attach. Trigger on the trailing edge of A202.00. Data Trace in structions are here if you have not used it. http://forums.mrplc.com/index.php?autocom=...mp;showfile=822 Also, do some Traces in CX Protocol to make sure there are no problems there. PMCR data trace instructions attached. PMCR_Data_Trace.pdf

I am using 8.3, and I get the same 'cannot find c:\...' message. There is no help associated with that specific function.