Access to variables from another PLC
-
Hi,
I test lots of configurations and doesn't work yet.
This is what I have in mervis:
!
And netstat command:
So, plz, can U tell me what's wrong ? -
As seen in https://kb.mervis.info/lib/exe/fetch.php/cs:mervis-ide:sharkprotocolspecification_user_2017_05_30.pdf,
In port monitor:
On receiving:- 01 SSCP address
- C5 00 Read variables directly error
- 00 04 Data length
- 00 00 01 14 NotLogged
So I have a resonse, credentials seems too be wrong, but I have admin - rw on PLC configuration and SSCP Device.
Do you have an explanation ? -
Up @tomas_hora
-
I read the same information in my port monitor
only option I see is to check the ports at the router. In Cisco forums they mention to open TCP port 2000, so will try this later on.
system status says for both sscp channels:
I cannot find the problem
-
Hi, this is the SSCP Server log. Can U tell me how is managed the login on the RT (maybe cookie with wrong acl) and if the sscp connection have to be permanant keep-alive because it seems to reconnect on each request.
[10.05 09:16:44.863] TSvr12346: New connection on port 12346 (remote 192.168.1.55:48494) [10.05 09:16:44.883] <-> TSvr12346: Assigned client context no. 0 [10.05 09:16:46.909] <-> TSvr12346: Unassigned client context no. 0 [10.05 09:16:46.914] TSvr12346: New connection on port 12346 (remote 192.168.1.55:48496) [10.05 09:16:46.919] <-> TSvr12346: Assigned client context no. 0 [10.05 09:16:48.959] <-> TSvr12346: Unassigned client context no. 0 [10.05 09:16:48.965] TSvr12346: New connection on port 12346 (remote 192.168.1.55:48498) [10.05 09:16:48.970] <-> TSvr12346: Assigned client context no. 0 [10.05 09:16:51.010] <-> TSvr12346: Unassigned client context no. 0 [10.05 09:16:51.015] TSvr12346: New connection on port 12346 (remote 192.168.1.55:48500) [10.05 09:16:51.020] <-> TSvr12346: Assigned client context no. 0 [10.05 09:16:53.060] <-> TSvr12346: Unassigned client context no. 0 [10.05 09:16:53.066] TSvr12346: New connection on port 12346 (remote 192.168.1.55:48502) [10.05 09:16:53.085] <-> TSvr12346: Assigned client context no. 0 [10.05 09:16:55.111] <-> TSvr12346: Unassigned client context no. 0 [10.05 09:16:55.116] TSvr12346: New connection on port 12346 (remote 192.168.1.55:48504) [10.05 09:16:55.121] <-> TSvr12346: Assigned client context no. 0
-
@CKB this is caused by a bug in the Mervis RunTime, which should have been fixed in the IDE I sent you, but unfortunately not :( We expect to make an official release within a few weeks where this issue is fixed for sure - tested today with @Giamba (THX!) If anyone has the same issue, I can send a pre-release of the new IDE, but I cannot guarantee 100% functionality since not all features have been tested - but the SSCP is fixed.
-
Hi Tomas, can you share the pre-released IDE with the fixed SSCP please?
-
Hi, did it work for Giamba? It still doesn't work for me even with the new IDE.. :/
-
Hi CKB.
Yes it's ok for me now. Tested with example and with my project. -
Hi Tomas, just FYI - Giamba was so nice to help me in a short teamviewer session. It works now fir his example project. Will transfer it to my solution later on :)
-
Am I to understand from this thread that SSCP communications between UniPi devices is broken in the released software? How long until a fix is released? I am having the same problem described above and need to get my devices talking to each other.
-
@mdturnerphys Hopefully the next release will be published within a few weeks in the meantime, you can create Modbus TCP connection between those two units
-
@tomas_hora Is there documentation or an example project available? I need to communicate an int between the two devices.
-
@mdturnerphys Unfortunately no. But for example, you will need to create a Server channel on one side (A) select port different than 502 and map your variables to holding/input registers/coils so you can read and write to them from the other (B) side. You can map the variables to Units for example 0-10 (if you need more, just map it as you wish). On the other side just create a custom device on Modbus TCP channel (B), set the IP address and port of the (A). Then on (B) create a read group with starting register 0 and 10 number of registers and map the variables from (A) to data points (create datapoint by right click, assign read group...). Check F1 help of Mervis for 'Modbus' there is a nice explanation. You can also check eg. the Inepro example project from our downloads section.
-
@tomas_hora Any updates on when the SSCP fix will be released?
-
@mdturnerphys Sure! We expect to release the new Mervis IDE and required tutorials on our new knowledge base this Friday.