jared

Hi Siva,

I have been using your set of VIs for communicating PLC with LabVIEW via Ethernet IP. I am experiencing a problem with a particular PLC... while I am communicating seems like a loose signal for an instant and then I get an error... the only way to get the program working again is to reset the AB ENI converter (that converts serial to ethernet from the PLC). When I monitor the PLC by itself I have noticed that the ms for each scan is very slow... this PLC manages a lot of variables and I guess that amount of data makes the data transfer very slow... I wonder if there is an instant in which the VI does not get data and that is why it get an error. Any ideas??

Thanks,

Jared

QUOTE (jared @ Mar 12 2008, 06:21 PM)

Hi Siva,

thanks for your reply... I do not know how to implement what you are suggesting... I went to NI.com trying to find info regarding wrapper VIs and Drive VIs but I could not find anything. I will be reading a lot of data, but only sending one bit of information (to stop the system). Is there an example where I can see how to do this??

Thanks again for your help

Jared

Hi Siva,

thanks for your reply... I do not know how to implement what you are suggesting... I went to NI.com trying to find info regarding wrapper VIs and Drive VIs but I could not find anything. I will be reading a lot of data, but only sending one bit of information (to stop the system). Is there an example where I can see how to do this??

Thanks again for your help

Jared

QUOTE (siva @ Feb 29 2008, 03:51 AM)

These VIs cannot function properly if put in parallel. PLease do the following to over come the proble,

1) Build a Wrapper VI (Driver VI / a single Interface VI) using 3 VIs(Init, Update, Scan) as SubVIs

2) Use the Wrapper VI in your code instead of directly calling Init, Update or Scan..

This will overcome the race around condition..

Please write to sivamgr@gmail.com if you face any problem in implementing this..

Thanks for all the help you have giving me previously... I am using your EtherNET/IP VIs but I had problems when trying to use the Update VI. I have several instances of the SCAN VI to read different integers, but as soon as I try to use a Scan VI to write a value to the PLC I get an error (something that has to do with the network busy or something like that). Any ideas of why this error and what do to to fix it. The weird thing is that when I use the Test program you provide (one SCAN and one Update) it works fine... but as soon as I put it in MY program with multiple Scans, then I get the error. Any ideas will be greatly appreciated.

Jared

QUOTE(siva @ Jan 10 2008, 06:32 PM)

Hi Jared, By Changing the Constant(0x07),. any Integer file can be accessed. But, before changing the constant, create that particular file in the PLC and configure it as integer. also configure the number of registers in that file as required. Accessing Bool File directly is a bit tough. Instaed of accessing a Bool File., You can keep some registers in the N7 and access it. In plc side, keep a logic to read from the integer file register and update the bool file. Use one of the these values for this field. Do not use any othervalues; doing so may result in unpredictable results.

Admin Note: Content removed because it was messing up the RSS feed. Please don't use nonprintable characters in posts. Next time use an image of the content.

QUOTE(siva @ Sep 11 2007, 12:48 AM)

Implementation of Common industrial Protocol (CIP) via EtherNet [EtherNet/IP (CIP)]

EtherNet_IP_PCCC

Use these set of VIs to communicate with MicroLogix Series PLCs Via EtherNet.

These VIs use simple TCP/IP Communication.

Communication : Ethernet, TCP/IP

Protocol : EtherNet/IP

Service :CIP (For Connection Management), CIP Service for PCCC

Command : PCCC

Tested with : MicroLogix 1100, MicroLogix 1500,1200(with NET-ENI)

No OPC Server Required

No Automation Server Required

No NI-DSC Module Required.

Note: These VIs access N7 Integer File. To access other Files in the PLCs, just replace the "Fileno" Constant(0x07) with a Control and make it as a parameter to the SubVI.

EtherNet_IP_CIP

Use these set of VIs to communicate with CompactLogix, Control Logix Series PLCs, Any Device that supports CIP(EtherNet/IP)

These VIs uses simple TCP/IP Communication.

Communication : Ethernet, TCP/IP

Protocol : EtherNet/IP

Service :CIP (For Connection Management, Read, Write)

Command : CIP Commands

Tested with : Compact Logix Series PLCs

No OPC Server Required

No Automation Server Required

No NI-DSC Module Required.

Visit : http://www.odva.org/' target="_blank">ODVA Website for EtherNet/IP Protocol Specification

Hi, I tried the VIs using a control to replace the "Fileno" Constant(0x07), However I got errors for each N value I tried, except for N7... Any ideas where my problem is? Also, if I want to write o read a Bit, do I only need to change the FileType to 0x85?

Thanks