Can you access the OPC gateway Vision via HTTP

[robert.canary]

We built an entire Vision HMI, and now at the end of the project, the customer says they need to access the SCADA via HTTP.

I told them this is the HMI, and while the HMI uses the SCADA tags to populate the display, their SCADA system would be the source for remote access.

NO, they want HTTP access to that display.

How can I do that?

[dkhayes117]

Remote access would be determined by the HMI Hardware/OS and not the vision project itself. I have remote access to all of my Raspberry Pi HMIs with VNC. The VNC software runs as a service in the background on the Pi, then I use a VNC viewer program on my laptop to connect to it.

If the hardware is windows based, you should be able to use Remote Desktop (RDP).

[robert.canary]

That is what I presented to them, as well as installing the Vision Client.

However, they want a simple URL/HTTPS solution.

I know this could be done in Perspective; however, can it be done in Vision?

[dkhayes117]

I'm not sure if that is possible.

[lrose]

@robert.canary

I know this could be done in Perspective; however, can it be done in Vision?

Once upon a time there was the Mobile module which would have allowed something like this, however, that module has been discontinued and is not available for 8.1+.

So the answer is, "Technically possible, but perhaps not feesible".

See here:

Run Vision on Mobile Device

I know the latest release of Ignition replaced mobile module with Perspective, does anyone know how to implement Vision on mobile device?

Specifically:

Run Vision on Mobile Device

I've heard of people using Apache Guacamole for this. https://guacamole.apache.org/ As Phil alluded to... The best answer is "you don't", because Java Swing, the technology that Vision relies on, was never [1] made available on mobile devices. with rare exceptions that never really worked ︎

As far as options for your client:

1. Do nothing and deal with RDP. (For what it's worth, I access VMWare from a browser and then RDP or VNC into the clients depending on the level of control I need on the client. Not sure if that counts).

2. Pay for the Perspective module and the large amount of work it would take port the project from Vision to Perspective.

3. Pay for the WebDev module if not already available, and develop and additional front-end to 'mimick' the current SCADA (Or provide access to whatever data they are truely wanting access to). Yet another large amount of work they would need to pay for, though depending on what exactly they're wanting perhaps less work than option 2, thogh Option 2 can also provide this too, so probably not worth it.

4. Pay for the time and effort it would take to port java with Swing to HTTP? An effort that has been largely unachieved in it's near 30 years of life.

Unfortunately, they failed to specify all of their needs at the begining of the project and therefore ended up with a product that doesn't have the mechanism to meet this one.