Citect Scada and MicroLogix 1100

From there, the next thing to check is the ports.  Not the ports form, but the ethernet ports.  I haven't worked with that particular controller, but some AB controllers have a default port of 0, and some on port 2222.

Normally, this would be in the ports form under special options - replace -I10.78.232.60 -P0 -T with -I10.78.232.60 -P2222 -T

However, the special options on the ports form for this driver does not appear standard.

You could try pinging the ports with PSPing (SysInternals) or possibly read the difference in the Wireshark traces form the programming software to Citect.

Next step would be to check ports as Michael says but it is port 44818. On the Citect IO server machine try to start a telnet session to the Micrologix.

From windows command prompt Telnet 10.78.232.60 44818  (That is if you have telnet windows option installed) 

If you don't have Telnet installed or it's difficult then Putty is an excellent utility to use

Don't bother modifying the ports form in Citect, just have the Micrologix IP only and no other options.

Hello everybody!
First, thanks for your replies. Sorry for my delay.

I tried port 2222, 44818 and It is still not working.
I checked the connection differences between the Rslogix and Citect Scada via Wireshark. RSLogix uses 44818 and the strange thing is that when I run the project from Citect no package is captured by Wireshark (meaning that no package is sent by the Citect to establish the connection?); this is so strange. I tried to connect the Citect to another PLC (Delta with Modbus TCP) and I am able to see all packages going out from the ethernet port and It works flawlessly.

Does anyone have any idea of what can cause this? Maybe the driver? I have the latest version installed.

Thanks again,

Gustavo.

Two things I would try:

1. Run computer setup wizard again, make sure IO Server is running.
2. Create new project with just MicroLogix comms config and single tag.

Also enable full logging within citect.ini to see if anything abnormal is happening.

[ABMLXEIP]
DebugLevel=ALL
DebugCategory=ALL
LogFileSize = 10000

Launch PowerShell and execute the following command

test-netconnection -computername 10.78.232.60 -port 44818

The PLC does listen to this port if the result contains TcpTestSucceeded : True.

The driver always uses the default port - 44818. try to remove the port number if it is specified in the port special options where only PLC IP is required. Make sure the device is not accidentally configured as the memory mode.

Hello Olivier, Jacky.

I tried running setup wizard again and it did not work. Also, i made a new project with just MicroLogix comms config and it didn't work either.

The PowerShell command succeeded with "true" as the result. I removed the port number in the special options and just left the IP, but It is still not working.

As I said in my previous comment, the strange thing is that no package goes out from the computer when I start the Citect project.

Any other ideas? :(

Thanks for your help,

Gustavo.

It is indeed very strange that the Citect runtime doesn't send out any packets onto the network. When you use Wireshark, are you listening on all NICs on your machine? Perhaps the packet is being routed onto a different network/card?

Another option is to try 3rd Party OPC Server which has a MicroLogix driver (like Matrikon). Then do the same packet monitoring to see if Matrikon OPC Server can communicate with it.

Another thing to try is to setup a Modbus simulator and MODNET IODevice to see if the same problem occurs.

I'd also check in the Citect\Bin directory that the MicroLogix dlls are present (ABMLXEIP.dll, ABMLXEIP.ilk, ABMLXEIP.DBF).

Wishing you the best of luck getting to the bottom of this issue!