cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Remote Access in Asset Advisor

SOLVED
Highlighted
Regular Member

Remote Access in Asset Advisor

Hi,

 

i am trying to use the remote access functionality in manufacturing app.

Web socket server and lua script run on a Raspberry Pi. RealVNC server is installed and running fine.

 

I am able to do file transfer and the tunneling seem to be working.

However nothing appeared when i clicked on Connect.

 

vnc2.png

 

My wsems log just say that TUNNEL ENDED without any specific error:

[FORCE] 2018-09-12 12:16:05,970 ./wsems: Initializing EMS ....
[FORCE] 2018-09-12 12:16:05,970 main: Using config file /home/pi/Desktop/microserver/etc/config.json
[INFO ] 2018-09-12 12:16:05,970 ./wsems: Creating the WsEms proxy.
[INFO ] 2018-09-12 12:16:05,970 ./wsems: Starting HTTP Server.
[INFO ] 2018-09-12 12:16:05,971 Main: Using built-in certificate for HTTP Server
[WARN ] 2018-09-12 12:16:05,971 Main: Encryption is disabled on HTTP Server.
[WARN ] 2018-09-12 12:16:05,972 Main: Authentication is disabled on the HTTP Server.
[FORCE] 2018-09-12 12:16:05,972 httpServer: 
[INFO ] 2018-09-12 12:16:05,972 ./wsems: Initializing the ThingWorx REST interface.
[INFO ] 2018-09-12 12:16:05,973 wsEmsProxy::initialize: FIPS is disabled.
[INFO ] 2018-09-12 12:16:05,973 wsEmsProxy::initialize: Encryption is enabled on Web Socket connection.
[WARN ] 2018-09-12 14:16:05,975 SDK: SDK Version: 2.1.2
[WARN ] 2018-09-12 14:16:05,975 SDK: TLS Library: OpenSSL
[WARN ] 2018-09-12 14:16:05,975 SDK: TLS Library Version: 1.0.2l-fips
[WARN ] 2018-09-12 14:16:05,976 SDK: FIPS Capable
[INFO ] 2018-09-12 12:16:06,3 WsProxy::initialize: EMS Version 5.4.2.334
[INFO ] 2018-09-12 12:16:06,3 WsProxy::initialize: twApi singleton initialized
[WARN ] 2018-09-12 12:16:06,4 WsProxy::initialize: Certificate validation is disabled.
[WARN ] 2018-09-12 12:16:06,4 WsProxy::initialize: Self signed certificates are enabled.
[ERROR] 2018-09-12 14:16:06,6 SDK: twMap_Add: parse function returned null.
[INFO ] 2018-09-12 12:16:06,9 WsEmsProxy::registerVirtualDirs: Adding virtual dir repo: /home/pi/Desktop/microserver/repository
[INFO ] 2018-09-12 12:16:06,9 WsEmsProxy::registerVirtualDirs: Adding virtual dir staging: /home/pi/Desktop/microserver/repository/staging
[INFO ] 2018-09-12 12:16:06,9 wsEmsProxy::initialize: Initialization complete!
[INFO ] 2018-09-12 12:16:06,11 ./wsems: Starting the connection.

xxxxxxxxxxxxxxxxxxxxxx:443-->[ERROR] 2018-09-12 14:16:06,14 SDK: twStream_Delete: NULL Pointer passed in
[INFO ] 2018-09-12 14:16:06,121 SDK: Server supports websocket extensions: permessage-deflate
[INFO ] 2018-09-12 14:16:06,121 SDK: twWs_Connect: Websocket connected!
[WARN ] 2018-09-12 14:16:06,292 SDK: twBindBody_Delete: NULL body or stream pointer
[INFO ] 2018-09-12 12:16:06,313 Main: Succesfully connected.  Saving .booted config file
[WARN ] 2018-09-12 14:16:07,477 SDK: InfoTable precheck: Name "reason" not found in datashape "(null)"
[FORCE] 2018-09-12 14:16:15,383 SDK: TUNNEL CREATED. Entity: Asset_PiThing, tid: 81d592c3-03b4-4570-a9a8-994cfe935016, target: 127.0.0.1:5900
[ERROR] 2018-09-12 14:16:15,386 SDK: twStream_Delete: NULL Pointer passed in
[INFO ] 2018-09-12 14:16:15,506 SDK: twWs_Connect: Websocket connected!
[FORCE] 2018-09-12 14:16:15,506 SDK: TUNNEL STARTED. Entity: Asset_PiThing, tid: 81d592c3-03b4-4570-a9a8-994cfe935016, target: 127.0.0.1:5900
[FORCE] 2018-09-12 14:16:18,314 SDK: TUNNEL ENDED. Entity: Asset_PiThing, Peer: Administrator, tid: 81d592c3-03b4-4570-a9a8-994cfe935016, target: 127.0.0.1:5900

VNC's log say that wsem disconnect by itself.

 

The tunnel appear in the subsystem

vnc4.png

 

Here is my config.json:

{  
    "ws_servers":   [{
        "host": "xxxxxxxxxxxxxxxxxxxxxx",
        "port": 443
    }],
    "http_server":  {
        "host": "localhost",
        "port": 8000,
        "ssl": false,
        "authenticate": false,
	"use_default_certificate" : true
    },
    "appKey":   "xxxxxxxxxxxxxxxxxxxxxxx",
    "logger":   {
        "level":    "INFO"
    },
    "auto_bind":    [{
            "name": "Asset_PiThing",
            "gateway":  false
    }],
    "certificates": {
        "validate": false,
        "allow_self_signed":true
    },
    "ws_connection":    {
        "encryption":   "ssl",
        "verbose":  true,
        "msg_timeout":  1000
    },
    "file": {
	"buffer_size": 8192,
	"max_file_size": 8000000000,
	"virtual_dirs": [
		{"repo": "/home/pi/Desktop/microserver/repository"},
		{"staging": "/home/pi/Desktop/microserver/repository/staging"}
	],
	"idle_timeout": 12000,
	"staging_dir": "staging"
    },
    "tunnel": {
	"tick_resolution": 5,
	"buffer_size": 10000,
	"read_timeout": 100,
	"idle_timeout": 300000,
	"max_concurrent": 3,
	"verbose": false,
	"duty_cycle": 100
    }
}

Best,

Bach

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Remote Access in Asset Advisor

I fixed the problem by installing tightvncserver and set tunnel address to 127.0.0.1:5901

View solution in original post

5 REPLIES 5

Re: Remote Access in Asset Advisor

Can you try the same by running EMS version 5.3.4 ?

Re: Remote Access in Asset Advisor

Yes, still the same.

Re: Remote Access in Asset Advisor

Hi Bach,

 

Are you able to see the Asset_PiThing as connected  in composer ? If yes , then are you able to browse the remote properties of this remote thing ?

 

If both is working fine , then there is no issue with lua and ems . Then we need to check the vnc configuration .

Re: Remote Access in Asset Advisor

Hi,

 

everything is working, except for the VNC.

The VNC should be running. I am able to do remote using other VNC viewers.

 

 

 

 

Re: Remote Access in Asset Advisor

I fixed the problem by installing tightvncserver and set tunnel address to 127.0.0.1:5901

View solution in original post