Siemens Simatic NET about node-opcua HOT 13 CLOSED

Hi Victor,
I will need to know where this error come from with more details.
Can you provide the stack trace ?
Alternatively, can you provide a wireshark trace of the communication between the client and the server.

from node-opcua.

how to get stack trace?

from node-opcua.

https://www.dropbox.com/s/lb8rwnxflxsf3pj/wireshark-node-opcua.pcapng
https://www.dropbox.com/s/ng0d6jhtm5i0824/wireshark-opc-scout.pcapng

from node-opcua.

Unfortunately I cannot find any OPCUA traffic in the wireshark log. what is the port that you use to communicate with the OPCUA server ?

can you provide the full command that you have used ?

node simple_client.js --endpoint .... --node ....

You can also activate more debugging output by setting the DEBUG environment variable
export DEBUG=ALL for linux
or
SET DEBUG=ALL on windows
Let me know

from node-opcua.

http://youtu.be/yOVXPqM5OOQ

from node-opcua.

https://www.dropbox.com/s/pjinjzjs2tpbdsz/out.txt

from node-opcua.

here is a example of the command line arguments:
node simple_client.js --endpoint opc.tcp://localhost/UA/Sample --node "ns=1;s=some_text"

notes:

• the node id must be enclosed between quotes ( i.e "...") , because it will probably contain a semi-column that could be interpreted by the shell.
• the namespace following ns= shall be an integer.

from node-opcua.

https://www.dropbox.com/s/6zx7flhz4d7jx1l/out2.txt

from node-opcua.

it seems that you try to connect using the sign & encrypt protocol.

opc.tcp://<server>:4845?SignAndEncrypt?http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15

Unfortunately 'sign & encrypt' is not supported yet ,

from node-opcua.

https://www.dropbox.com/s/s0q6jtwnvih4107/out3.txt

from node-opcua.

I can help remotely deploy test environment Siemens Simatic NET

from node-opcua.

vm - https://yadi.sk/d/3swbTOJtYAD7A
screencast - https://yadi.sk/i/-hoEQ7fqYAD5v

from node-opcua.

closing due to lack of activity, problem is probably outdated

from node-opcua.