| Unstable attenuated DANS01 output level |
1.The DANS01 sensor(s) may be detecting audio from its own output and / or adjacent outputs and interpreting this as noise.
2.The nature of the background noise may cause instability.
3.Possibly the output level (maximum broadcast level) has been increased on one or more
outputs after DANS commissioning.
4.If it is still not possible to commission DANS01 to a satisfactory behaviour.
|
Potential Resolution Steps for First Reason:
- Mute the DANS01 controlled output and all adjacent outputs.
- Trigger an ANS enabled announcement to the DANS01 output.
- Trigger an ANS disabled announcement to all adjacent zones.
- Unmute the DANS01 output.
- Confirm the audio has minimal or no effect on the DANS01 output “Gain” meter.
- If it is greatly affected, increase the “Output” setting in 1 dB steps until it stops.
- Mute the DANS01 output.
- Unmute the first adjacent output.
- Confirm the audio has minimal or no effect on the DANS01 output “Gain” meter.
- If it is greatly affected, increase the “Adjacent 1” setting in 1 dB steps until it stops.
- Mute this adjacent output.
- Repeat from step 8 above for all remaining adjacent outputs.
- If it is not possible to get one or more outputs to have minimal or no effect on the “Gain” meter, repeat from step i. but try to get the DANS01 behaviour as stable as possible.
Potential Resolution Steps for Second Reason:
- Increase both “Attack” and “Release” in 25 ms steps until it is stable.
- Note that this may slow down the DANS01 reaction speed when there is a large change in background noise. If it is still not possible to get one or more outputs stable, reduce the attack and release back to satisfactory reaction speeds.
Potential Resolution Steps for Third Reason:
- DANS01 will require commissioning again.
Fourth Potential Resolution Step:
- Set the “DANS Type” to “Gap”. This will stop output level adjustments whilst audio is present on the DANS01 output.
- The “Attack” and “Release” settings determine the output level adjustment speed. Short “Attack” and “Release” will result in the output level changing between words in an announcement. Longer “Attack” and “Release” requires a longer pause in audio before the output level is adjusted.
|
| Not possible to get full range attenuation even at the lowest background noise level. i.e. the “Gain” meter never matches the “Range” setting. |
1.This may occur when the background ambient noise level is greater than <Max Noise Threshold> - <Range>.
2.Possibly the output level (maximum broadcast level) has been lowered on one or more outputs after DANS commissioning.
|
Potential Resolution Steps for First Reason:
- Reduce the DANS01 sensor(s) input level by 10 dB.
- Reduce the Max Noise Threshold by 10 dB.
- Recommission the “Output” and “Adjacent” faders.
- This will give an extra 10 dB headroom for the DANS01 attenuation.
Potential Resolution Steps for Second Reason:
- DANS01 will require commissioning again. Specifically: DANS01 Output Commissioning and Adjacent Output Commissioning.
|
| IPxx AUDIO INPUT reported on DANS01 connected inputs |
Input Surveillance Not Commissioned Correctly
Please note:
- This will cause all outputs controlled by this sensor to output at full volume regardless of the current route’s “ANS” setting.
- If an output is controlled by multiple DANS01 sensors, a fault on one (or more) sensor will cause the output to go to full volume.
|
Potential Resolution Steps for First Reason:
- Check the connection between DANS01 and the audio router.
- Recommission the audio input.
|
