v8.1.21
I've got an Ignition Edge Gateway installed on a client and Perspective Workstation (PW) installed with a client configured to the main Ignition (Standard) Gateway, with fallback to local Edge project. I tried unplugging the ethernet from the client and it successfully fell back to local.
This particular client is connected to the main network via a radio link. When I disconnect the radio link, PW has the banner up top saying "No Gateway Connection" but there's no timer to fallback, and it doesn't ever revert to local fallback gateway.
It sounds like the running session isn't notifying the bridge of the connection/lifecycle change. can you attach (or DM me) the workstation.log file from this client?
Just circling back to this. It looks like this was a problem between chair and keyboard 
"somebody" hadn't configured the fallback options in the Workstation application
2 Likes
Hello,
I have exactly the same issue. I have checked the settings several times and reviewed the documentation, but I still couldn’t find the reason.
I have uploaded a screenshot of the settings I configured.
Could you please guide me to solve this problem?
Thank you in advance.
I'm a little confused by the Perspective selection in Edge when your screenshot shows you are trying to use Vision client fallback? This topic is about Perspective Workstation, not Vision.
Hello, thank you for your reply.
I intend to enable fallback for Perspective, but I couldn’t find any specific option for Perspective fallback. I thought maybe there is a shared option for both Vision and Perspective.
Is my assumption incorrect?
Is it possible that fallback for Perspective is not supported at all?
You have to configure it in your local Workstation install:
Thank you very much for your guidance. However, this applies to fallback for the Workstation.
My users access the interface via the web browser, and the project goal is that when the connection to the main server is lost, users’ connection should switch to the Edge gateway until the main server connection is restored.
Is there any method or solution available for this scenario?
No, browser access doesn't support fallback. If you need a robust solution, you should be using redundancy on your main gateway, not Edge fallback. A live browser session does fail over to the backup server. (The only gotcha is that you need two URL bookmarks--main and backup--since browsers don't have mechanisms for opening an alternate URL when a first URL is non-responsive.)
Thank you for your guidance.
My goal is either to change the URL automatically or to display a button for the user to switch the URL manually.
Of course, the second option is better, as the operator decides when to switch.
For this, I have considered two approaches:
Using components that support JavaScript.
However, this method is not officially approved by Ignition, and there is a risk that this access may be blocked in future updates.
Developing a custom module compatible with Ignition APIs.
I personally prefer this second approach.
I would like your advice on whether the second method is practical.
I have many gateways, and many licenses will be installed on them. My goal is to help reduce costs and create a structure that meets my client’s requirements.
Please share your opinion, as it is very important to me.
If I achieve acceptable results with this method, I will definitely share them in this thread.
Thank you.
I recommend using Ignition Redundancy.
1 Like
