InTouch Unlimited Professional - Usage

Hi Community,

InTouch Unlimited Professional supports unlimited Web Clients and unlimited RDS clients.

So what does that exactly mean regarding RDS clients?

When using a Tag Server architecture you basically do have one view running as a tag server on the Terminal Server with the following part number:
InTouch Wrkst Unlim Tags 1 23.1 intouch-groupCUnlim

Normally all the clients use the part number:
InTouch HMI Server with Unlimited RDS Clients 1 23.1 intouchunlim-groupunlim

For these clients to get a license it's a must to NOT select "InTouchView application" in the WindowMaker

This is conterintuitive because it explicitly states "InTouch tag server". This also has other consequences, meaning all the RDS clients not only can connect the view running in the console session (the tag server application) but they can access whatever they want.

Of course customer can use this license that way and I don't see any hint why this should not be used that way?

Is that correct or is this bad design of the IT Unlimited license?

Thanks
Peter

Parents
  • Hi Peter, so the Intouch unlimited works as follows:

    You will need a Tag server that runs as console session, this can also be an independent machine/ VM

    The tag server connects to PLC I/O and does the IO processing, lets call this Intouch project 1.

    You will need to create another project , lets call it intouch project 2, this Intocuh project will have remote reference to tags in Intouch project 1 ( and no direct I/O tags )

    This Intouch project 2 needs to run on Windows server and have RDS Session licenses.

    Then the thin clients will need to point at this RDS server running project 2 and you can obtain unlimited ( practical max 40 sessions ) from this project 2.

    To make any changes in a project, you will need to make a change in project 1 and project 2 ( which is insane )

    I would like this whole process to be a lot more simpler than what it is and the unimited license ( Intouch professional ) forcing RDS where Intouch is amazing as standalone clients in another big pain point

Reply
  • Hi Peter, so the Intouch unlimited works as follows:

    You will need a Tag server that runs as console session, this can also be an independent machine/ VM

    The tag server connects to PLC I/O and does the IO processing, lets call this Intouch project 1.

    You will need to create another project , lets call it intouch project 2, this Intocuh project will have remote reference to tags in Intouch project 1 ( and no direct I/O tags )

    This Intouch project 2 needs to run on Windows server and have RDS Session licenses.

    Then the thin clients will need to point at this RDS server running project 2 and you can obtain unlimited ( practical max 40 sessions ) from this project 2.

    To make any changes in a project, you will need to make a change in project 1 and project 2 ( which is insane )

    I would like this whole process to be a lot more simpler than what it is and the unimited license ( Intouch professional ) forcing RDS where Intouch is amazing as standalone clients in another big pain point

Children
  • Hi Rainer,

    That's only the way the tag server works. But it's not the way InTouch Unlimited has to work.

    With InTouch Unlimited it's possible to have these "second" applications access whatever they want, not only the Tag Server and that's great for many customers. They do access the I/O source of the Terminal Server and do whatever they want.

    That's related to the setting "InTouchView application" which can't be used with IT Unlimited otherwise the licenses won't work.

    But yes, in a tag server application setup it's cumbersome to take care of two projects.

  • Hi Peter, you are right but there are several technical challenges if the second application has to acces whatever it wants. Intouch is a single threaded application for it's view.exe , so that means for it to access I/O , do scripting and present graphics it all happens in a single core CPU EVEN though your hardware maybe top of the line multi-core system. That's the main reason for two projects and it's a fundamental core problem that AVEVA is solving hopefully in new releases.

    We need a fast, multi-threaded Intocuh system with appropriate licensing.