Skip to main content
S
spatel-211-Visitor
1-Visitor
October 28, 2016
Question

Error in Kepware IOT gateway & Thingworx Integration

  • October 28, 2016
  • 2 replies
  • 5395 views

Dear community members,

 

We are working on integration of Kepware and Thingworx using IoT Gateway plugin.

 

On Kepware IoT Gateway side status shows connected to the Thing, but in Thingworx, in remote things tab, We are unable to see any active remote thing.

 

 

Thinworx and Kepware IOT.jpg

 

IMAGE$6F71588DF964D2B6.jpg

2 replies

T
ttielebein5-Regular Member
5-Regular Member
October 28, 2016

Can you find the remote thing within Composer? What value does the isConnected property have?

S
spatel-211-VisitorAuthor
1-Visitor
November 3, 2016

Hi Tori,

No, I'm unable to find remote thing in composer. The 2nd image is the screenshot of composer.

- Siddharth

T
ttielebein5-Regular Member
5-Regular Member
November 3, 2016

No, I mean, if you go to ThingWorx Composer's home screen (http://server:port/Thingworx/Compose/index.html) and type the name of the remote thing in the Spotlight search field, do you find an entity? Remote things need to be created on the Platform in order for you to see them, usually. I don't know that much about Kepware. Maybe it was supposed to import entities and it didn't? Maybe you don't need one to exist on the Platform for Kepware?

C
cc111-Visitor
1-Visitor
November 25, 2016

Hello,

I am experiencing the same problem. I guess you can even ommit the IoT Gateway, since the ThingWorx native client interface provides a direct connection to the ThingWorx Platform. I tried to connect to ThingWorx via KEPServerEX directly, but have the same effect: the remote thing does not show up in the unbound things list. I even used the KEPServerEX Remote-Thing-Template to model the thing. The connection log says:

ThingWorx Diagnostics         2016-11-25 20:32:14,953 twWs_Connect: Websocket connected!

ThingWorx Native Interface    Connected to ThingWorx. | Plattform: xxx.cloud.thingworx.com:443/Thingworx/WS, Thing-Name: 'KEPServerEX'.

Can someone help in analyzing this problem?

Thanks,

Christian

T
tlalime-21-Visitor
1-Visitor
November 28, 2016

Hi Christian,

Have you already created a RemoteThing with the name "KEPServerEX"? If so, KEPServer should bind automatically to that thing (that thing's 'isConnected' property will be true) and KEPServer won't show up in the unbound things list.

Only if there is no Thing on the platform matching KEPServer's configured thing name will you see it in the unbound thing list.

-Tyler

    C
    cc111-Visitor
    1-Visitor
    November 29, 2016

    Hi Tyler,

    Yes, I did model a Thing called KEPServerEX using the KEPServerEX Remote-Thing-Template. But no binding takes place. The 'isConnected' property stays false and the unbound thing list is empty, although the connection log says:

    ThingWorx Diagnostics         2016-11-25 20:32:14,953 twWs_Connect: Websocket connected!

    ThingWorx Native Interface    Connected to ThingWorx. | Plattform: xxx.cloud.thingworx.com:443/Thingworx/WS, Thing-Name: 'KEPServerEX'.

    Best reagrds,

    Christian

    Terms & ConditionsCookie settingsAccessibility statement