Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
I am trying first time to connect RPi to TW, but it is giving the following error.
followd this course: https://developer.thingworx.com/en/resources/guides/thingworx-raspberry-pi-quickstart/launch-ems
[FORCE] 2019-11-07 07:58:52,435 ./wsems: Initializing EMS ....
[FORCE] 2019-11-07 07:58:52,435 main: Using config file /root/microserver/etc/config.json
[INFO ] 2019-11-07 07:58:52,435 ./wsems: Creating the WsEms proxy.
[INFO ] 2019-11-07 07:58:52,436 ./wsems: Starting HTTP Server.
[WARN ] 2019-11-07 07:58:52,436 Main: Encryption is disabled on HTTP Server.
[WARN ] 2019-11-07 07:58:52,437 Main: Authentication is disabled on the HTTP Server.
[INFO ] 2019-11-07 07:58:52,437 ./wsems: Initializing the ThingWorx REST interface.
[INFO ] 2019-11-07 07:58:52,438 wsEmsProxy::initialize: FIPS is disabled.
[INFO ] 2019-11-07 07:58:52,438 wsEmsProxy::initialize: Encryption is enabled on Web Socket connection.
[FORCE] 2019-11-07 07:58:52,450 httpServer: starting http server port=8080
[WARN ] 2019-11-07 07:58:52,465 SDK: SDK Version: 2.2.0
[WARN ] 2019-11-07 07:58:52,468 SDK: TLS Library: OpenSSL
[WARN ] 2019-11-07 07:58:52,471 SDK: TLS Library Version: 1.0.2l-fips
[WARN ] 2019-11-07 07:58:52,473 SDK: FIPS Capable
Illegal instruction
My config.json file is as follow:
{
"ws_servers" : [{
"host" : "172.20.20.50",
"port": 8001
}],
"appKey" : "727938a3-fa72-4dba-9287-99804d5ddad4",
"http_server" : {
"host": "localhost",
"port": 8080,
"use_default_certificate": true,
"ssl": false,
"authenticate": false
},
"logger" : {
"level" : "INFO"
},
"certificates": {
"validate": false,
"allow_self_signed" : true
},
"ws_connection": {
"encryption": "ssl",
"verbose": true,
"msg_timeout": 1000
}
}
Solved! Go to Solution.
Hi @posipova ,Thank you for your response.
The error was with the connection.
The problem is solved after changing the microserver from SP5 to SP6.
I don't see any actual error in the log you posted. Are you sure it's not connecting?
Hi @posipova ,Thank you for your response.
The error was with the connection.
The problem is solved after changing the microserver from SP5 to SP6.