Issue with mitsubushi melsec PLC modbus QJ71MT91 connection with FActory IO

[raheelredben 0]

I want to communicate my Q series PLC with Factory IO using GX works 2 software, I want to use modbus tcp/ip as server in factory IO and the ips are as follows
plc CPU: 192.168.1.30
modbus:192.168.1.245
pc:192.168.1.240 (I have set the ipv4 settings with ip address that i wrote subnet mask:255.255.255.0 and default gateway: 192.168.1.1)
local network: 192.168.1.1

I want a start stop switch as an example and a warning light so that i get to know how the communication works as it is not working currently I have done the communication through modbus tcp/ip as client but unable to do for modbus tcp/ip as server.
the ladder logic code is as follows.

the addresses for y80, y81 and y82 are , QY128, QY129 and QY130

I have done some settings for automatic communication parameters
that are as follows

 

The auto refresh settings are as follows
 

or the factory IO i have created the following environment

the settings for driver configuration is as follows

Can you let me know whats the issue here as i am unable to communicate via the factory IO with the PLC . Can you guide me in any way?

 

 

Edited 7 May by raheelredben

[Gambit 332]

Wouldnt it be scada which is the client (asking the questions) instead of server ?

Also you are using D100 and D300 for reading and writing the modbus devices.

When you write a value of 1 to D300 does the light come on 

 

Edited 7 May by Gambit

[raheelredben 0]

Actually my supervisor wants to do both master slave and slave to master communication. Right now we are not using the scada and want to build a connection by having modbus as server. As factory IO supports both and I couldn't communicate. In addition the light of Factory IO doesn't turn on as it simply doesn't pick up the ladder code . which is the main issue? Can you let me know what I am doing wrong?

 

[raheelredben 0]

1 hour ago, Gambit said:

Wouldnt it be scada which is the client (asking the questions) instead of server ?

Also you are using D100 and D300 for reading and writing the modbus devices.

When you write a value of 1 to D300 does the light come on 

 

i have also tried the modsim32 it communicates with the device buffer memory in the gXworks 2 but it also doesn't pick up the code, it just turns on and of the the outputs and inputs that i turn on on modsim32 and device buffer .

[Gambit 332]

1 hour ago, raheelredben said:

i have also tried the modsim32 it communicates with the device buffer memory in the gXworks 2 but it also doesn't pick up the code, it just turns on and of the the outputs and inputs that i turn on on modsim32 and device buffer .

But the code has nothing to to with the modbus devices when used as client  !! Why would it turn on 

Also the basic paramter startup setting should be on user

If you use the QJ71MT91 as a server than Y81 = Coil 128

If you use the QJ71MT91 as a Client than D200.0 = Coil 128 but you have to set user param

Edited 7 May by Gambit

[raheelredben 0]

Just now, Gambit said:

But the code has nothing to to with the modbus devices !! Why would it turn on 

I agree but that factory IO setup should turn on the light right when i press the start button?

 

[Gambit 332]

28 minutes ago, raheelredben said:

I agree but that factory IO setup should turn on the light right when i press the start button?

 

I am not familiar with factory IO

[raheelredben 0]

17 hours ago, Gambit said:

I am not familiar with factory IO

But lets suppose if i use modsim 32 and as y80 represent coil 129 in modsim 32 and y81 represent coil 130 and y80 131 . so if i turn on 128coil 131 should be turned on right but it doesn't can you tell me why? and how can this ladder code be worked did i set the communication parameters right? 

[Gambit 332]

Ok First lets choose the first comm style with Factory IO being the client asking the questions.

In this case all you have to to set the basic params and don't need the autom comm settings or Refresh.
In this case Y80,Y81,Y82 reperesent Coil 128,129,130. 

So If you set Coil 128 on Factory IO coil 130 should set as well.

 

[Gambit 332]

Now lets change and let the System Q be the client.

Then you need to change the basic parameter setting to user setting parameters

Set the automat comms and refresh as you have set now.

Now you are reading Coil 130 => D100.0

and writing coil 128 and 129 with the status from D200.0 and D200.1

So you code in the PLC schouls also be with hose devices where 

Y80 - D100.0

Y81 - D200.0

Y82 - D200.1