Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

PowerLogic T300 - Preventing PM6 LBS to operate with SF6 loss interlock

Protection & Control

Schneider Electric support forum about Protection Relays, Substation Controllers & RTUs, Arc Flash Devices & Systems in Medium Voltage and Low Voltage. A place to get support on product selection, installation, commissioning and troubleshooting.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • EcoStruxure Power & Grid
  • Protection & Control
  • PowerLogic T300 - Preventing PM6 LBS to operate with SF6 loss interlock
Options
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
Araceli_Monje
Lt. Commander Araceli_Monje Lt. Commander
22
HenriGRASSET
Captain HenriGRASSET Captain
14
Rudolf_Simon
Commander Rudolf_Simon Commander
13
View All
Related Products
product field
Schneider Electric
PowerLogic T300

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to Protection & Control
Solved
Mikel_Beltrán
Ensign Mikel_Beltrán Ensign
Ensign

Posted: ‎2021-06-24 12:31 AM . Last Modified: ‎2025-05-26 12:44 AM

0 Likes
3
1233
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-24 12:31 AM

PowerLogic T300 - Preventing PM6 LBS to operate with SF6 loss interlock

Hello,

 

in a MV application where we use the T300 to control a pole-mounted LBS (load break switch), we want to use formulas in Easergy Builder to implement additional blocking conditions for switch control.

 

These are the DIs in SC150:

 

 

SC150 digital inputs.JPG

 

 

 

By default, DI5 is used to activate/deactivate the switch interlock, and we already use that DI for manual blocking.

 

But we also want to block the switch if the SF6 level is low, so we need to use another DI for that purpose. DI7, for example, as it is configurable.

 

We have followed the steps described in the attached Application Note and it seems to work just fine. Now the LBS can be blocked from both DI5 and DI7.

 

However, our concern is the following. At the first step of the procedure, in Easergy Builder, we completely replace the source of these commands:

 

 

1.JPG

 

 

On that 1st step, it requires us to remove the original “Cilo” source of those commands, that look like this:

 

 

2.JPG

 

 

And replace them by these formulae:

 

 

3.JPG

 

 

After doing that step and the others in the Application Note, our tests confirm that it just works fine as I said.

 

But we just wonder if we have caused a non-desired side effect in our LBS application by removing the original Cilo source of those commands in the 1st step of the procedure.

 

I would appreciate if someone with experience with this particular case share their thoughts.

 

Many thanks in advance.

  • Thumbnail of PowerLogic T300
    Schneider Electric
    PowerLogic T300
View products (1)
Attachments
Labels
  • Labels:
  • Application cases
  • PowerLogic T300
Tags (4)
  • Tags:
  • english
  • PM6 LBS
  • PowerLogic T300
  • SF6 interlock
Reply
  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
TomBerry
Lieutenant JG TomBerry Lieutenant JG
Lieutenant JG

Posted: ‎2021-06-24 05:56 AM

2 Likes
1
1224
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-24 05:56 AM

The App Note describes another step that you don't mention in the email

 

The original CILO sources should still be used - they should have been moved to some new variables that are used in the OR() formulas

Add new Command variables with source Cilo

Name

Description

Source

Source Coordinate

HU01_CILO1_BlkOp1_stVal

Block operation from Head Unit to SC01

Cilo

CSWI_BLKOP:SC01

HU01_CILO1_EnaOp1_stVal

Enable operation from Head Unit to SC01

Cilo

CSWI_ENAOP:SC01

 

I think you must have done this, otherwise the system would have reported an error when loading the configuration; and the commands would not work

 

 

See Answer In Context

Tags (1)
  • Tags:
  • english
Reply
Replies 3
TomBerry
Lieutenant JG TomBerry Lieutenant JG
Lieutenant JG

Posted: ‎2021-06-24 05:56 AM

2 Likes
1
1225
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-24 05:56 AM

The App Note describes another step that you don't mention in the email

 

The original CILO sources should still be used - they should have been moved to some new variables that are used in the OR() formulas

Add new Command variables with source Cilo

Name

Description

Source

Source Coordinate

HU01_CILO1_BlkOp1_stVal

Block operation from Head Unit to SC01

Cilo

CSWI_BLKOP:SC01

HU01_CILO1_EnaOp1_stVal

Enable operation from Head Unit to SC01

Cilo

CSWI_ENAOP:SC01

 

I think you must have done this, otherwise the system would have reported an error when loading the configuration; and the commands would not work

 

 

Tags (1)
  • Tags:
  • english
Reply
AndreMelo
Commander AndreMelo Commander
Commander

Posted: ‎2021-06-24 07:30 AM . Last Modified: ‎2021-06-24 07:31 AM

1 Like
0
1221
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-24 07:30 AM

Hi @Mikel_Beltrán 

 

As @TomBerry well said,  you must relocate the old TAG.

 

However, I would suggest a simpler way to avoid all these changes, you can just use Source 2 as following:

 

 

 

comand t300.PNG

 

 

it works like an OR logic.

 

Configure the DI you want in the Blocking command source 2 and it is done.

 

Best Regards

 

Tags (1)
  • Tags:
  • english
Reply
Mikel_Beltrán
Ensign Mikel_Beltrán Ensign
Ensign

Posted: ‎2021-06-28 12:05 AM

2 Likes
0
1215
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2021-06-28 12:05 AM

Hello @TomBerry ,

 

thanks a lot for your reply!

 

Just to clarify: we followed all the steps described in the Application note, from the first to the last (I'm afraid I wasn't clear enough on that point in my previous message, sorry).

 

So yes, we did that step that you mention too, indeed.

 

I guess we can be sure that everything will work safely, then. Thank you.

 

 

@AndreMelo thank you for sharing an alternative. Since we are starting to learn how to use these configurations, it helps to understand how they work.

Tags (1)
  • Tags:
  • english
Reply
Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

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.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

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