Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84589members
353854posts

Alarm Beacon Return to Normal Delay

EcoStruxure IT forum

A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.

Solved
DCIM_Support
Picard
Picard
0 Likes
4
341

Alarm Beacon Return to Normal Delay

This question was originally posted on DCIM Support by Mashwiz on 2016-01-29


Dear Team,

I have a beacon connected to NetBotz 570 and configured the Set Device Output State alert action to turn on the beacon when other sensers (temperature, humidity...) are violated, but then the beacon delays by almost a munite to turn off when the subject sensor returns to normal. am I missing out on a configuration.

I have disabled the beacon on the Edit threshold window, also is is possibe to extend the beacon cable as I have tried to extend the cable using the normal straight through cable and it didn't work.

Thank you.

Regards,

Felix

 

(CID:105461783)


Accepted Solutions
DCIM_Support
Picard
Picard
0 Likes
1
342

Re: Alarm Beacon Return to Normal Delay

This answer was originally posted on DCIM Support by Steven Marchetti on 2016-01-29


Hi Felix,

 

I did some testing as well and using a profile and sequence that only had the beacon alert in it, the beacon turned off within a second or 2. I would suggest that if you have multiple alerts that you try creating a separate sequence for the beacon and place that sequence first. I have not tested it myself but it would seem that your conclusions about other actions taking priority seems logical.

 

As for extending the beacon, I have tested this as well. I used a coupler  and a cat5 cable, I was able to extend and use the beacon. Perhaps your testing used a cat6 cable. I have seen where those would cause issues when extending sensors or a-link connections. I tested with a 10 foot cable but perhaps the one you're using is too long.

 

Steve

(CID:105461792)

See Answer In Context

4 Replies 4
DCIM_Support
Picard
Picard
0 Likes
0
342

Re: Alarm Beacon Return to Normal Delay

This comment was originally posted on DCIM Support by Mashwiz on 2016-01-29


When I use one alert action (Device Output State) in a profile the beacon turns off almost immediately with the violated sensor's return to normal, but when I include more than one alert action (email, sms and device output state) in the same profile I get a delay on the beacon turn off. Maybe be the NetBotz appliance is still executing process strings associated with the other alert actions thus causing this delay.

(CID:105461789)

DCIM_Support
Picard
Picard
0 Likes
1
343

Re: Alarm Beacon Return to Normal Delay

This answer was originally posted on DCIM Support by Steven Marchetti on 2016-01-29


Hi Felix,

 

I did some testing as well and using a profile and sequence that only had the beacon alert in it, the beacon turned off within a second or 2. I would suggest that if you have multiple alerts that you try creating a separate sequence for the beacon and place that sequence first. I have not tested it myself but it would seem that your conclusions about other actions taking priority seems logical.

 

As for extending the beacon, I have tested this as well. I used a coupler  and a cat5 cable, I was able to extend and use the beacon. Perhaps your testing used a cat6 cable. I have seen where those would cause issues when extending sensors or a-link connections. I tested with a 10 foot cable but perhaps the one you're using is too long.

 

Steve

(CID:105461792)

DCIM_Support
Picard
Picard
0 Likes
0
342

Re: Alarm Beacon Return to Normal Delay

This comment was originally posted on DCIM Support by Mashwiz on 2016-01-29


Thanks Steve, You are right, I used a Cat6 cable on extending the beacon cable. I shall test using cat5 and see how it goes. Regards, Felix

(CID:105461797)

DCIM_Support
Picard
Picard
0 Likes
0
342

🔒 Closed

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.