From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Does the Modbus driver accept 2 IP addresses for failover redundancy?
bosco
Member
07-31-2002 12:46 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I have two Motorola RTU's set up for redundancy with two different IP addresses. I am trying to figure out how to set up the redundancy on Lookout. Can two IP addresses be set up in the driver for this purpose. This works with the Tiway driver.
Khalid
Active Participant
07-31-2002 03:04 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
_______________________________________________
Hi Bosco,
The driver objects do not accept two IP addresses. The right approach in implementing redundancy is to create a second driver object with the standby RTU's IP address. This object would then take over the communication on failure of the first.
All your inputs and outputs (locally or remotely via clients) should be routed via a SymbolicLink so as to maintain the data flow transparently for them.
The Online Help of Lookout has a good section on Redundancy with all the details.
Hope this helps.
Regards,
Khalid 🙂
_______________________________________________
Hi Bosco,
The driver objects do not accept two IP addresses. The right approach in implementing redundancy is to create a second driver object with the standby RTU's IP address. This object would then take over the communication on failure of the first.
All your inputs and outputs (locally or remotely via clients) should be routed via a SymbolicLink so as to maintain the data flow transparently for them.
The Online Help of Lookout has a good section on Redundancy with all the details.
Hope this helps.
Regards,
Khalid 🙂
_______________________________________________
08-01-2002 09:09 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Thank you for the answer. I have only been able to find information on redundancy in a client server environment, which I have already implemented. I am still unsure as to how to implement hardware redundancy. I assume both driver objects would be identical except for name. Do I have to use a symbolic link each time I read to or write from an I/O? I have already built numerous graphic linking through the symbolic link to the server process using the single driver. Will all of these have to redone?
Khalid
Active Participant
08-01-2002 10:05 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I assume you have two RTUs on the Network and would like to switch from the "primary" to the "secondary" one.
In this case, yes, you will have two Objects with identical settings except for the Names and the IP addresses.
In Lookout, I assume your processes should not be affected (much) by this switchover of the RTUs. So, you will pass everything through a Symbolic Link and change the definition of this Symbolic Link based on the RTU you are currently communicating with.
Hope this helps,
Khalid 🙂
In this case, yes, you will have two Objects with identical settings except for the Names and the IP addresses.
In Lookout, I assume your processes should not be affected (much) by this switchover of the RTUs. So, you will pass everything through a Symbolic Link and change the definition of this Symbolic Link based on the RTU you are currently communicating with.
Hope this helps,
Khalid 🙂
08-01-2002 10:27 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I have created the two driver objects, identical except for name and IP, but the symbolic link object only allows a specific data member of the driver object to be used in the dynamic expression. This seems to indicate that each time I want to reference an analog input for example, I have to use a separate symbolic link.
Khalid
Active Participant
08-01-2002 12:16 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
The dynamic expression in the Symbolic Link can evaluate to any URL (not just to one Data member). So, you could have something like:
tif(heartbeat, "\\.\process1\RTU1", "\\.\process1\RTU2")
Where heartbeat is the signal you check for switching over to the standby. The above Symbolic link will switch between the two RTUs. So you will have access to all the data members of the RTU.
If you call your Symbolic Link as sylink you could then use the data members of the RTU as [sylink].40001 . And this expression would be valid regardless of which RTU is up and running.
Hope this helps,
Rgds,
Khalid
tif(heartbeat, "\\.\process1\RTU1", "\\.\process1\RTU2")
Where heartbeat is the signal you check for switching over to the standby. The above Symbolic link will switch between the two RTUs. So you will have access to all the data members of the RTU.
If you call your Symbolic Link as sylink you could then use the data members of the RTU as [sylink].40001 . And this expression would be valid regardless of which RTU is up and running.
Hope this helps,
Rgds,
Khalid
