I've connected to this family using their native SICS protocol and long-lived java sockets. It's not simple, unfortunately.
The unfortunate thing is that years ago when employees were still allowed to have modules in the module store... I had both generic MT-SICS and IND-specific drivers... but that ended, they never got ported beyond 7.7 or maybe 7.9, and never absorbed by IA.
I should try to find the source code 
I think they'd need a rewrite though, I was a bit obsessed with Scala back then.
Oy!
Scala was an oasis when all we had was Java 6/7/8 and Kotlin didn't exist yet.
1 Like
I used Groovy back then, contributing to an open source project. 
Gathered some more info,
Here is Technical manual for IND-780 Klyck Share Portal
The data comes back in this format
As long as 20 cycles per seconds (50ms scan rate), MT said the data should be good and give enough resolution on the progress bar. I would not be using both connections simultaneously. Either to PLC or Ignition but not both. I embarked on this with the goal to eliminate the PLC all together and do everything through ignition.
I have used the shared data server before with TCP module in ignition. All works fine until the connection drops, then there’s no indication the socket dropped anywhere and you just don’t get data.
"Continuous Output Format"
That rings a bell. IIRC, I was able to issue a command via SICS to cause the socket to start sending that. If the packets stopped coming in for any reason, my code would simply kill the socket and start another.