V 570 and kepserver

[active]

Hi All

 

Im working on a project that requires a v570 to communicate with kepserver using modbus ip has anybody achieved this and if so what settings were used for both the v570 and kepserver

 

Thanks

[Henny]

Hi All

 

Im working on a project that requires a v570 to communicate with kepserver using modbus ip has anybody achieved this and if so what settings were used for both the v570 and kepserver

 

Thanks

Hello Active

 

Just did a simple test with Kepserver and selected the ”Modbus tcp/ip driver”

Channel properties=>Ethernet settings selected port 502  and ip protocol tcp/ip.

Added a device and named it device1 and for the model selected “modbus”.

ID <135.0.2.78>20    The V570 has this ip address and 20 is the slave number in my test situation.

 

In the V570 socket init in my case socket 3 port number 502 and server(slave) followed by

A Modbus ipconfig,selected in this function block socket 3 and gave it network id 20,time out 100 and retries 3 and assigned a function in progress mb.

The indexes with slaves can be deleted using the clear link button.

 

The next network has to have a “Modbus ip scanex” block  and for the name in this block select the name of the Modbus ip config block.

TCP card init was already done somewhere else in the program but you could follow the example explained in the visilogic helpfile and it’s called “configuring a modbus slave device”.

In this example for the gateway you have to choose the ip address of the master unitronics plc but this is only needed I think if communication is between Unitronics plcs so leave the TCP settings in this block as they should be four your local network.

For addresses see the example in the visilogic helpfile called “slave addressing” under Modbus ip.

 

To test this  all I started kepware opc quick client and added here an item “channel1.device1.40032” and here I can see the actual value from MI31

So kepware acts as a Modbus client and the V570 as a Modbus slave device in this situation.

 

Did no projects with kepware and Unitronics but in our plant we have some Unitronics plc,s besides TI(CTI) PLC,s connected to Control Maestro(Wizcon) scada using Kepserver so this is why I could quickly made a simple test.

 

Hope it will help you

Regards

Henny

[SERTAN]

hi all.

I was reborn this topic.

Ihave same problem same equipment, but my kepwareEX version 6.0.2107.0

try to connect v570 via  kepwareEX like up side but i cant connect.

Can you helpme anybody please ?

give me a screen shot please.

[Isakovic]

It would be helpful to submit your ladder and screenshot of tags settings, that's probably where the problem is. If you did all as in Henny's post maybe you have a problem in network. Did you try to ping V570? Also try pinging with cable disconnected, maybe you have two devices with same IP address.

[SERTAN]

Solve the problem. just change TCP/IP Project Setting Port Number Change to 20257

Thanks All.

 

 

one more question.....

I already connect plc with KepserverEX, But I want to connect and see values on internet browser same time. 

when i cahge tcp/ip socket init ; socket 0, protokol: HTTP, Port: 80, server, i see on web browser but i cant see on KepserverEX

How can i make it ?

[Cam]

The 570 has 4 sockets you can use.  Init one for port 80 and one for KepserverEx.

[SERTAN]

Its working all fine.

Many Thanks to All of you...

Best regards.

[Rafe]

Got it going using the following settings

[Seversean]

I got Kepware pulling data using basically what's shown in the last photo.  However, we have dual IO servers requiring that there be two active modbus connections.  Only one will connect with this setup, any idea how to enable two servers to pull data via modbus?

[Flex727]

Use two different sockets and two different port numbers. You have 4 sockets available which gives you the capability for 4 simultaneous Ethernet connections.

[Seversean]

So this is how I currently have it.  Originally I had Socket 0 with TCP and port 502 (slave) and that by itself didn't seem to work.  I added the last instruction 'Modbus IP Config' and set the Network ID to 20 etc.  I'm just confused, do I need both of those instructions?  Do I only need the Modbus IP Config?  And if I want to open two sockets do I use two Modbus IP Config instructions?  Set them both to Network ID 20 or two different ID's?

[Flex727]

Yes you need to initialize and configure each socket you're going to use for MODBUS IP. Pick any two sockets, though I would leave Socket 1 initialized to Port 20256 to use for a VisiLogic connection. I would keep Socket 2 at the default of Port 502 and initialize Socket 3 to Port 503, but it doesn't really matter - just don't initialize two sockets to the same port number, keeping in mind the default assignments.

You also need to configure each socket you're going to use for MODBUS IP with a MODBUS IP Configuration block. Don't duplicate addresses. The network ID isn't important with TCP, as I understand it, but you can assign them any way you want.

Then you will need two separate MODBUS IP SCAN_EX function blocks. Be sure the SCAN_EX block assignments match to the relevant MODBUS configuration names.

Set up one of the masters to communicate with port 502 and the other to port 503.

That's all there is to it.

[Seversean]

Curious how mine is working then if you need to initialize and configure each socket.  I initialize socket 0 (502) and then configure Socket 2 (502).  Seems like maybe socket 2 is working without any initialization?

[Flex727]

Socket 2 defaults to Port 502. You have both Socket 0 and Socket 2 set to Port 502. Sometimes that works, but it is very bad practice to do that. Unitronics generally recommends that you Initialize all 4 sockets, even if don't plan to use them all so that you can be sure there are no conflicts.

[Seversean]

OK, these are the new rungs.  So the default for socket 3 is TCP(20257) but I've initialized it to TCP 503.  It still shows up in the config as TCP(20257) though.  Guess that's just documentation saying thats the default?  See any issues with this?  Forgive any mistakes, I have no experience with Unitronics. 

[Flex727]

Yes that all looks correct assuming you have the SCAN_EX blocks addressed correctly. And yes, you are correct that the MODBUS Configuration block is just showing you the defaults.

There is no need to pack your ladder rungs so much. I like to tell people that Unitronics does not charge you by the rung. Break those logic pieces into separate rungs. What you have should work, but new users often get in trouble with overly complicated ladder rungs that don't compile the way you think they would. I would place each Socket Initialization, with its accompanying MODBUS Config into a separate rung (with SB 2 in front), and each SCAN_EX block into a separate rung.

[Seversean]

OK, I can redo all that.  Simplify it.  Again, I have zero experience with Unitronics so using the software, moving stuff around and creating new rungs is all foreign to me, coming from Allen Bradley background. 

BTW the config in the Kepware does ask for the network ID number...

 

 

 

 

[Seversean]

Not sure why but this doesn't appear to have worked.  SB149 and SB150 are not set to 1. 

[Flex727]

A couple of things:

1) Please do NOT place multiple logic threads in a single ladder rung. You did not break them up into separate rungs. The whole point of ladder rungs is to separate out the logic so there are no conflicts or confusion within a logic statement.

2) You don't really need anything in front of the SCAN_EX blocks. Just hang them directly on the left ladder rail. If you feel like something should be there, use SB 145 & SB 146 instead.

[Flex727]

2 hours ago, Seversean said:

moving stuff around and creating new rungs is all foreign to me, coming from Allen Bradley background. 

You didn't use Ladder Logic with Allen Bradley?

[Seversean]

11 minutes ago, Flex727 said:

A couple of things:

1) Please do NOT place multiple logic threads in a single ladder rung. You did not break them up into separate rungs. The whole point of ladder rungs is to separate out the logic so there are no conflicts or confusion within a logic statement.

2) You don't really need anything in front of the SCAN_EX blocks. Just hang them directly on the left ladder rail. If you feel like something should be there, use SB 145 & SB 146 instead.

Yes, used ladder logic in AB of course but I think things are defined differently.  Looks like what you're calling a rung is the whole blank space between the lines with the number 1,2,3 etc.  And what I'd call a rung you're referring to as a logic thread.  AB constructs the rung lines automatically as you drop in instructions.  I believe this format is similar to Modicon and others I've used on occasion.  Calling the whole space or rung a 'Net'.  Just different and I have to orient myself and figure it out. 

So I need to create a new  'Net' and put each individual rung or logic thread per Net.  I think I can see why it didn't work now...

Exactly what I meant by new at Unitronics. 

[Seversean]

I believe this is what you meant to do...

[Simon]

Yes, that's it 🙂

[Seversean]

After all that neither IO server can poll the PLC now.  Before all this I was able to at least get one of them to poll the PLC successfully.  It shows I have sockets 2 and 3 initialized but no connections. 

[Joe Tauser]

Make sure your sockets are set up as TCP slaves

 

You don't have to pull the output instructions all the way to the right.  Unitronics is much more free-form than AB.  Back in the day, Modicon 984s also programmed in "nets".  

I still program AB when the customer calls for it and, yes, Unitronics takes some getting used to if that's your background.  If you're still getting hung up post your program so we can "zoom in" to the blocks.

 

Joe T.