Industry Automation and Control Forum
This forum is addressing industrial automation design & engineering, operations, asset performance, cyber security and digital transformation for Plants & Machines.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-21 02:22 AM
Hello, I have a system with two M580 redundant with this configuration:
Rack: BMEXBP0400 / CPU: BMEH582040 / eNOC: BMENOC0301
and this is my network:
Now I have a SCADA and two HMIs that needs to connect to the PLCs and so far I am connecting to them using the Primary eNOC @IP "192.168.3.95" but it seems that the Secondary doesn't swap to the mains @IP automatically when the main is off, is there something I am missing in my configuration or what ? because nor the SCADA nor the HMIs are getting any data when the primary is off.
Because I am used to working with Siemens 17-1500RH and the PLCs create a 3rd shared @IP that the main PLCs use.
SCADA is connected through Kepware server Modbus Suite and the HMI is the HMIST6600.
another question: Is the M580 secondary PLC picks up control on the spot or does it needs operator intervention and only preserves the Data; if so, where can I configure it.
Best regards.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-25 03:50 AM
Hello @the18 ,
This typically occurs because the PAC M580 doesn't have time to synchronize task data.
The MAST_SYNCHRONIZED, FAST_SYNCHRONIZED, and SAFE_SYNCHRONIZED variables indicate whether the database exchange between the Primary and Standby PACs was successful.
If not, the task cycle time must be increased:
MAST MAST task period %SW0 > Last cycle execution time (in ms) %SW30
FAST FAST task period %SW1 > Last cycle execution time (in ms) %SW33
SAFE SAFE task period %SW4 > Last cycle execution time (in ms) %SW42
Configuring MAST/FAST Tasks
The duration of the Data Pack/Unpack process depends primarily on the number of DFB instances to be exchanged.
Data Pack/Unpack
Copies the values of all variables into memory blocks, preparing for the data transfer.
All allocated variables in one memory block.
All unallocated variables in one memory block.
One DFB instance in one memory block.
What happens when the Scan time is too short?
Situations that may affect this:
A large number of DFBs to perform Pack/Unpack takes longer (1 ms per 100 DFBs).
A MAST task period that is too short.
Solutions:
I recommend that you review the following document, the Exchanging M580 Hot Standby Data section
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-23 12:09 AM
hello my friend @the18
Yes, the secondary takes control, you can share the pictures again, they aren't displayed correctly.
Also share an image of the CPU and NOC network configuration, as well as the Control Expert connected to the CPU.
BR
Ricard
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-24 03:19 AM
Hello @Ricard ,
Please find attached the requested images:
601.jpg : M580 Network configuration
602.jpg: NOC Network configuration
603.jpg: Ethernet network for all devices
604.jpg: Control expert version informations
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-24 03:46 AM
It appears you're connecting correctly.
Have you performed swap tests? Can you display the PLC status in runtime?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-24 09:13 AM
They should swap automatically and bumplessly. Make sure that your controllers are matched and the secondary is in RUN_STBY/EQUAL state. Also add operator screen to your project from Control Expert ISO from folder "\Extras\Operator Screens \m580 hsby operator screen v11.xcr" and provide screenshot of this screen.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-25 02:16 AM
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-03-25 03:50 AM
Hello @the18 ,
This typically occurs because the PAC M580 doesn't have time to synchronize task data.
The MAST_SYNCHRONIZED, FAST_SYNCHRONIZED, and SAFE_SYNCHRONIZED variables indicate whether the database exchange between the Primary and Standby PACs was successful.
If not, the task cycle time must be increased:
MAST MAST task period %SW0 > Last cycle execution time (in ms) %SW30
FAST FAST task period %SW1 > Last cycle execution time (in ms) %SW33
SAFE SAFE task period %SW4 > Last cycle execution time (in ms) %SW42
Configuring MAST/FAST Tasks
The duration of the Data Pack/Unpack process depends primarily on the number of DFB instances to be exchanged.
Data Pack/Unpack
Copies the values of all variables into memory blocks, preparing for the data transfer.
All allocated variables in one memory block.
All unallocated variables in one memory block.
One DFB instance in one memory block.
What happens when the Scan time is too short?
Situations that may affect this:
A large number of DFBs to perform Pack/Unpack takes longer (1 ms per 100 DFBs).
A MAST task period that is too short.
Solutions:
I recommend that you review the following document, the Exchanging M580 Hot Standby Data section
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.
With achievable small steps, users progress and continually feel satisfaction in task accomplishment.
Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.
of