PMCR

Carol I am a little confused as to which mode the PLC is changing to: 1. Monitor Mode -> Program Mode or 2. Monitor Mode -> Run Mode or both??? I have never seen a situation where the PLC is changing modes by itself. If the answer is 1 (Monitor to Program), then the there is not much you can do by programming in the PLC. If the answer is 2 (Monitor to Run), then the PLC can handle this. The PLC can monitor (via FINS commands) the operating mode. If the PLC changed to RUN mode, the PLC could send itself a FINS command to go back to Monitor Mode. This is a band aid fix, but does not explain the cause of the mode change. Poor power to the PLC???

Adrian I thought about the Serial PLC Link function, but it sounds like Simone want to be able to program across the serial link as well. I have not tried it, but I don't think that the 'serial gateway' function works in any port mode except for Protocol Macro or Serial Gateway. I think that Mike's idea of Protocol Macro is the best fit. You can transfer data on the PMCR and still program and monitor across the serial connection. PMCR

Simone There are 2 ways to do this, both of which should use RS422 not RS485. The Host Link Protocol is not supported by RS485. 1. Create a 'Host Link Master' protocol macro to send / receive data from the 'slaves'. 2. Use the Serial Gateway function (with the port set for Protocol Macro or Serial Gateway) to use Send / Recieve / CMND commands from the CJ1M to the slaves. Which one are you trying to do? Can you post or private message me the code that you are using?

Attached is some training material. Using_IR_and_DR_for_Indirect_Addressing.pdf

Scott When monitoring a binary protocol like Modbus, I find it more helpful to use the Binary view mode. This makes <02><03>% from the ASCII view mode appear as 02 03 25, which I find easier to read. The Logging mode may work better, as it seperates out the strings from one another, and time stamps them. I have not yet split apart the text files. Any idea where the errors occurred?

Scott Any RS485 converters should be OK. I simply had 2 NT-AL001s on hand.

This request for software should be directed towards an Omron distributor or Omron representative. They should be able to provide a demonstration version of CX Server OPC.

Scott &128 (&H80) is a timeout regardless of the function code. The fact that your Step 2 in your original post tested 2 inverters with Modbus, and they worked fine, seems to point to the Modbus to LON gateway devices. Did you use the same wiring for the VFD test that you are using on the LON gateways? When you are increasing your polling interval, are you timing between sending the first Modbus command and sending the second Modbus command, or are you timing from when you recieve a Modbus response to the first command until when you send the next command? In my code, I found that this second method (an intermessage delay) of ~ 20ms helped to increase stability. A packet snooper on the RS485 line would be the only way to tell for certain what is going on. If you happen to have a pair of Omron NT-AL001 adapters, the manual that I include with Supermon has a diagram of how to create an RS422 or RS485 snooper.

You are correct that altering the routing tables in the PLCs may be necessary if they are not setup up already to allow the routing that you need. CX Integrator or CX Net (found in Start / Programs / Omron / CX One / CX Programmer) will be required to change the routing tables.

I think I understand now. The PLC will not flush its memory (ie DM, CIO, HR, WR, etc). The host PC can overwrite the memory with a FINS command (0102, etc), but this action is caused by the host issuing FINS commands, not because the PLC is flushing data.

Section 6 http://forums.mrplc.com/index.php?autocom=...mp;showfile=870

File Name: W465-E1-03 CS and CJ EIP21 Operations Manual.pdf File Submitter: PMCR File Submitted: 30 Jun 2009 File Category: Manuals Ethernet/IP operations manual for CS1 / CJ1 / CJ2 Ethernet/IP modules Click here to download this file

Scott When the 'no response' occurs, does the port error bit turn on? That would be A392.12 for port 1, or A392.04 for port 2. (Yes, those bits appear backwards). Something to try would be to increase the peripheral servicing time. This helps out a whole lot with all kinds of comms. '50' as shown below, allows up to 5.0 ms per scan for servicing peripheral devices. By the way, did you see this posting? http://forums.mrplc.com/index.php?autocom=...mp;showfile=867

I am sorry, but I do not quite understand the question. The PLC that is 'flushing' the response, is it originally sending a FINS command, then flushing the response to the FINS command? There are no settings in the ETN module to 'hold' the last command or response. Anything like that would need to be done in ladder. The PLC has no way to capture the FINS commands from the PC to the PLC, or the responses back to the PC, if that is the question.

For CP1L / CP1H / CJ1 / CJ2 / CS1, you can change all timers and counters to work as binary. While offline, right click on your PLC (NewPLC1[CP1L]Offline an an example). Select Properties. Select Execute Timer/Counter as Binary. Then use TIMX, CNTX instructions. The 'X' indicates binary format.

Are you certain that the mapping is different? o2-09 is the Initilization Mode Selection. In the past, this usually has changed some of the settings that are made when you do an initilization of the inverter. I would strongly suspect that the Modbus register mapping does not change when the Initilization Mode Selection changes.

The response that you have recieved is showing a routing error. This is usually caused by PLC routing tables that do not match the Network numbers you are using in your FINS command. In this case, does the PLC have a routing table that identifies the ETN11 card as Network 1? The response code (0502) seems to indicate that there is not. c0 00 02 01 08 00 01 02 00 05 01 01 85 02 00 02 00 44 00 01 00 01 C0 = This is a response (Information Control Field) 00 = RSV Filed (not used) 02 = Gate Count 01 = Destination Net 1 08 = Destination Node 8 00 = Destination Unit 0 01 = Source Net 1 02 = Source Node 2 00 = Source Unit 0 05 = SID (Service Identifier) 0101 = Echo of the command you sent 8502 = Response code 0502, with bit 8 On. Bit 8 = routing error 00020044 - I don't recall what this is, but it is not the data you requested, as the response code is no 0000. 00010001 = Error Network and Error Node (Net 01 node 01)

All CS and CJ special IO cards (such as temperature control, high speed counter, motion control, analog IO, etc) have fixed addresses set by the 2 digit rotary 'machine number'. The setup of the modules is D20,000 + (100 x Machine number). The IO area is CIO 2000 + (10 x Machine number). To change the address, change the machine number, but you are always going to be in the 2000 + area for the CIO allocation of the module.

It is also in the Downloads section of MrPLC http://forums.mrplc.com/index.php?autocom=...mp;showfile=865

File Name: NSFirmware8.21.zip File Submitter: PMCR File Submitted: 11 Jun 2009 File Category: HMI Sample Code Firmware 8.21 (release version) for NS Series HMI Click here to download this file

If you look in the 'Memory View', does it agree with the complier? If you want to send the file to me (PM), I can take a look at it.

There are 2 different PT Notify / PT Control schemes, 1 older, 1 newer. In the old scheme (NT20M, NT20S, NT30, NT630), the first word of the Control area was where you write data to command a screen change from the PLC, and the first word of the Notify area showed the current screen, regardless of how you got to that screen. In the new scheme ( NT21, NT31, NT631), the first word of the PT Control area was where you write data to command a screen change, and also were the current screen is shown. I would need to double check the manual, but I think the NT11S follows the 'old' method. Shown below is the 'new' method.