|
Повідомлення створено: 12. 01. 2014 [11:21]
|
|
snowboy
saman ahmadi
Автор теми
Зареєстрован(а) с: 14.09.2013
Повідомлення: 13
|
Hi Roman :)
I would like to use DAQGate module.
I run two OpenSCADA in two separated virtual machines. I use these settings for them:
1- Work station1 with IP:192.168.4.40
remote stations list: Work station1
remote controllers: System.test
address: TCP:192.168.4.40:10005
2- Work station2 with IP:192.168.4.41
remote stations list: Work station1
remote controllers: System.test
address: TCP:192.168.4.40:10005
an output transport is made when DAQGate was configured. but when I want to change the status of transport of "Work station2" to running, it show me an error:
"connect to internet socket error: operation now in progress!" :(
and therefore it remains stopped and I have an error in DAQGate controller of "Work station2".
What's your idea about this problem?
could I use DAQGate for two separated OpenSCADA or it can just operate locally?
Thanks for your attention and help
B.R.
Вкладений файл
Screenshot.png (Тип файлу: image/png, Розмір: 133.03 кілобайтів) — 2785 завантажень
|
|
Повідомлення створено: 12. 01. 2014 [16:55]
|
|
roman
Roman Savochenko
Moderator Contributor Developer
Зареєстрован(а) с: 12.12.2007
Повідомлення: 3750
|
"snowboy" wrote:
an output transport is made when DAQGate was configured. but when I want to change the status of transport of "Work station2" to running, it show me an error:
"connect to internet socket error: operation now in progress!" :(
Remote host 192.168.4.40 unavailable into your network or port 10005 here closed or OpenSCADA here stopped or input transport on 10005 port no present into remote OpenSCADA.
"snowboy" wrote:
could I use DAQGate for two separated OpenSCADA or it can just operate locally?
DAQGate destined for remote DAQ sources from one OpenSCADA mirror to other.
Learn, learn and learn better than work, work and work.
|
|
Повідомлення створено: 13. 01. 2014 [06:05]
|
|
snowboy
saman ahmadi
Автор теми
Зареєстрован(а) с: 14.09.2013
Повідомлення: 13
|
Hi Roman
Thanks for your reply.
Remote host 192.168.4.40 unavailable into your network or port 10005 here closed or OpenSCADA here stopped or input transport on 10005 port no present into remote OpenSCADA.
I check these thing you mentioned. this is the result:
-I can ping "work station1" to "work station2" and vice versa.
-before trying to test DAQGate, firewall and security software are closed and disabled in order not to block the traffic.
-DAQGates of both stations are running. ("work station1" can read their own data and transport module shows the amount of transmitted data)
-in both stations, their default input transport is running without any error. its address is TCP::10005:1 .
unfortunately I don't know what to do to solve the problem. :(
Could I send you screenshots of the settings in OpenSCADA? (I think it will be more clear)
Any help you can give will be greatly appreciated.
B.R.
|
|
Повідомлення створено: 13. 01. 2014 [12:36]
|
|
roman
Roman Savochenko
Moderator Contributor Developer
Зареєстрован(а) с: 12.12.2007
Повідомлення: 3750
|
"snowboy" wrote:
-DAQGates of both stations are running. ("work station1" can read their own data and transport module shows the amount of transmitted data)
-in both stations, their default input transport is running without any error. its address is TCP::10005:1.
Module DAQGate you are need only on client part. On server part need only input transport with "TCP::10005:1" address and field "Transport protocol" sets to "SelfSystem".
"snowboy" wrote:
Could I send you screenshots of the settings in OpenSCADA? (I think it will be more clear)
Work example in live you can see into "Demo (AGLKS)" project!
Learn, learn and learn better than work, work and work.
|
|
Повідомлення створено: 14. 01. 2014 [14:15]
|
|
snowboy
saman ahmadi
Автор теми
Зареєстрован(а) с: 14.09.2013
Повідомлення: 13
|
Hi Roman
Thanks very much :) :)
I do everything you said. but I still had the same problem. Finally I find out that Centos is blocked 10005 port, so after adding this port to its firewall the problem is solved and every thing is OK now.
I think, it is as easy as possible to configure this module. Thank you for this friendly module. :)
By the way, I suggest you to add this issue to DAQGate document in order to other users also know about OS port blocking.
Thanks a lot for your help
B.R.
|
