Ben_P

Citect SCADA v7.30 and Omron NX (Sysmac studio) communication

12 posts in this topic

Hi,

I need to make Citect v7.30 SP1 communicate with an Omron NX1P2 PLC via the PLC built-in Ethernet IP port and can't make it work.
First question is, can it work or is Citect v7.30 SP1 a too old version to be able to communicate with an Omron NX1P2 PLC?

To set it up I used the OMFINS3 protocol and set the following :

Board :
Type: TCPIP
Address: 0

Ports:
Special Opt: -I128.1.10.115 -P9600
          -I128.1.10.115 : PLC IP address
          -P9600 : PLC FINS port number

IO Devices:
Address: 1/115/250/V
          1 - PLC FINS network number
          115 - PLC node address
          250 - PLC Unit number - Not sure of this one. Written 250 in sysmac studio but meant to be between 00-15. Tried 0 as well didn't work. I am not sure how to figure this one out.
          V - Default parameter? - Tried without it as well or tried S but it didn't help.

My Citect IO server can ping the PLC but the communication doesn't work with the following error codes on the kernel:

With Unit number set at 250 : - Unit Status Offline
                                                     - Generic Error 000012
                                                     - Driver Error 0x000016

With Unit number set at 00 :   - Unit Status Offline
                                                     - Generic Error 000008
                                                     - Driver Error 0x001101

 

If anyone could help it would be great.

Thanks

 

 

 

 

 

 

 

 

 

 

 

Board.PNG

Ports.PNG

IO Devices.PNG

FINS Settings.PNG

FINS Settings_2.PNG

Kernel.PNG

Kernel_2.PNG

Edited by Ben_P
Hidding customer name

Share this post


Link to post
Share on other sites

Try IO Device

0/115/0/S

And add 

-U to special opt

Share this post


Link to post
Share on other sites

Still the same error codes : Generic Error 000008, Driver Error 0x001101

Share this post


Link to post
Share on other sites

Chelton, I saw you've made it work with an NJ serie PLC in the past.
Do you remember how you configured Citect and Sysmac studio?
Did you use protocol OMFINS3 as well?

Perhaps I have something not configured properly in sysmac studio?

Share this post


Link to post
Share on other sites

Did you download and install the OMFINS driver pack?

Share this post


Link to post
Share on other sites

Looking at your citect screenshot the unit that is not communicating is unit 2

Is unit 1 using the same driver?

 

Share this post


Link to post
Share on other sites

Hi Chelton, yes I have installed the last version of the OMFINS and the TCPIP drivers.

The error codes seems to say :

Generic 08 : General error - Vijeo Citect has established communications with the I/O device; however, the I/O device has detected an error in the protocol. This error could be caused by a fault in the communications link, or an error in the ladder logic (in the I/O device).
 

Driver error 001101 : A correct memory area code has not been used or Expansion Data Memory is not available. Check the command's memory area code and set the appropriate code.

I'm not sure what does that mean.
I've only created one tag to try at the address D1000.00 which is in the range normally usable with this driver.

Share this post


Link to post
Share on other sites

No unit 1 is communicating, it's an existing communication with another PLC (Schneider PLC).

Edited by Ben_P

Share this post


Link to post
Share on other sites

I remember having to add to the citect.ini something like [OMFINS] source address

Look in the parameters for omfins.

I have an NJ working with version 6

I still think your address should be 0/115/0/S 

I'm assuming you have created a tag in the plc with the AT %D1000

Edited by chelton

Share this post


Link to post
Share on other sites

Yes I have as well, I saw that in the forum.

I've added:
[OMFINS]
Block = 256
IgnoreNonFatalError = 1
Source = 1/1/0

But it still doesn't work.
I've tried 0/115/0/S and it didn't work as well.
In Sysmac studio the Local Network number can't be 0 anyway.

 

Share this post


Link to post
Share on other sites

I have comms working with an NX1P2-9024DT1

I/O Devices:

Address 0/115/0/S

Protocol: OMFINS3

Ports:

Special Opt: -I192.168.1.115 -P9600 

Citect.ini

[OMFINS]

Source = 0/14/0

PollTime = 0

Timeout=1000

Delay=20

IgnoreNonFatalError=0

Watchtime=30

Also in the NX memory setup i had to enable the CIO area even though i was only reading a single register in the DM area.

memory.png.28ac13f2dbad30ebd4e966c675b11

Edited by chelton

Share this post


Link to post
Share on other sites

Hi Chelton,

 

Thanks for your help, I ended up making it work with the Schneider support.
I have the following :

Boards:
Type: TCPIP
Address : 0

Ports:
Special Opt: -I128.1.10.115 -P9600 -T

IO Devices:
Address: 1/115/0/S
Protocol: OMFINS3

Citect ini:
Block=256
IgnoreNonFatalError=1
Source=1/1/0

But the funny thing is after setting this as recommended by the Citect support it still didn't work.
I've checked the data exchange with wireshark between the PLC and Citect and they were talking to each other but the reading request from Citect was trying to access the CIO memory area only regardless if my tag would be as a D or W, H ect...
The PLC would answer back memory area code invalid so i ended up trying the CIO area which worked
After that all the other memory areas worked...weird but it's what happened.

So I don't think the -T or /S really mater now.

I was modifying an existing COM with an old PLC being replaced, maybe it was a bad idea and I should have just create a new one and delete the old one. I guess it was making the COM block or whatever.

 

Wireshark_3.PNG

Wireshark_1.PNG

Wireshark_2.PNG

Edited by Ben_P

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now