Skip to main content
16-Pearl
January 29, 2024
Solved

not able to see kepware values in thingworx 9.5

  • January 29, 2024
  • 1 reply
  • 1587 views

i have upgraded the thingworx from 9.3 to 9.5. i have created industrial connector thing for kepware connection its showing connected status. but when I create Edge thing with industrial connector as

Suraj_Patil_1-1706529469907.png

as industrial thing ,status of that Edge is showing disconnected. Am i missing something here in binding or settings?

Suraj_Patil_2-1706529611987.png

 

 

 

Best answer by Suraj_Patil

nop...it got resolved automatically ...which is surprise to us well ... may be some permission issues from clients IT team ..not sure

 

Thanks,

Suraj Patil

1 reply

16-Pearl
January 29, 2024

Hi @Suraj_Patil 

The isConnected flag on the platform would mean that the websocket is connected and the thing is bound. If the websocket connection is broken, then the whole bind process needs to be done again. Create the websocket, send an auth request, and send a bind request for all things. In the context of the Java SDK, a ConnectedThingClientChangeListener needs to process the closeConnection event and set isBound to false. When you check the bind status using if (!this.isBound), you are simply checking the local flag. You will need to locally flip the isBound flag or you will never reissue the request. Instead of checking if!bound, just bind again. let us know if you have any doubts.

16-Pearl
January 30, 2024

Can please elaborate it more.

i can see kepware thing(industrial connector) is connected in my instance.

but the Edge thing which i created using industrial thingshape is showing disconnected status.

i followed this procedure to do connection

https://community.ptc.com/t5/IoT-Tips/Connect-Kepware-Server-to-ThingWorx-Foundation-Part-1/ta-p/809423

16-Pearl
January 30, 2024

Hi @Suraj_Patil 

 

I see you have created a salesforce case for this, thanks for this because we need to check it at the call, let us know if your issue will not be resolved at tomorrow's meeting.