# MovingAnalogIndicator - need more alarm levels **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [July 16, 2024, 4:42am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268 "2024-07-16T04:42:35Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![richardNZ15](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/richardnz15/32/33373_2.png) [@richardNZ15](https://forum.inductiveautomation.com/u/richardNZ15)\ **Post date:** [July 16, 2024, 4:42am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/1 "2024-07-16T04:42:35Z")
Seems strange to me that the MovingAnalogIndicator component in Perspective has ability to have 4 alarm zones: LoLoAlarm LoAlarm HiAlarm HiHiAlarm But we can only set **TWO** alarm colors..?? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/2/322707229cff307959cc09c92d88891cd86485e2.png) It kinda hamstrings us if we wanted to have the HiHiAlarm a different color to the LoLoAlarm. Which is totally valid depending on what priorities we'd set alarms at. Is this something that could get modified for future releases? ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [July 16, 2024, 11:35pm UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/2 "2024-07-16T23:35:54Z")
Hmm, I guess that makes sense setting the range colour to the priority colour - I never thought about that. (shameless plug) I have finally added my analogue indicator to the exchange, awaiting review. While I use the same philosophy (H/L and HH/LL use same colour), you could easily modify my component to use 4 colours. It also overcomes some of the issues with the MAI. I embedded this component into an Analogue Instrument View template to use with an AI UDT which has the PV, alarm ranges, etc. so that would make it easy to template the alarms and their priority colours into it. For mine I just used an ASM alarm symbol that has the priority colour/number/shape ![ASM Analogue Indicator v1.1 - img1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/5/1510e85ae9afac26da5a1570b4da68eab31eea40.png) Edit: Updated version: - fixed bug with negatives - added range labels [ASM Analogue Indicator Vertical v1.2 - Fixed bug in handling of negatives.zip](https://forum.inductiveautomation.com/uploads/short-url/leQywaIfrRjUls0OEn60jLsxPzY.zip) (11.6 KB) ---
**Author:** ![bwirth](https://avatars.discourse-cdn.com/v4/letter/b/41988e/32.png) [@bwirth](https://forum.inductiveautomation.com/u/bwirth)\ **Post date:** [July 17, 2024, 12:33am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/3 "2024-07-17T00:33:35Z")
I would think you could set those colors dynamically via binding. ---
**Author:** ![richardNZ15](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/richardnz15/32/33373_2.png) [@richardNZ15](https://forum.inductiveautomation.com/u/richardNZ15)\ **Post date:** [July 17, 2024, 1:10am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/4 "2024-07-17T01:10:19Z")
You could but that just seems unnecessarily complicated. You'd need to look at the PV to figure out if the color needs to represent the HighHigh or the LowLow value. Just seems like its a half implemented component. ---
**Author:** ![richardNZ15](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/richardnz15/32/33373_2.png) [@richardNZ15](https://forum.inductiveautomation.com/u/richardNZ15)\ **Post date:** [July 17, 2024, 1:10am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/5 "2024-07-17T01:10:47Z")
Nice one, much needed to combine the Indicator with the Linear scale.. what a pain that can be. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [July 17, 2024, 1:51am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/6 "2024-07-17T01:51:09Z")
Exactly... using two independent components is also fraught with issues when the page size chagnes too when trying to keep them aligned (it doesn't work) - note that in my component the bar and scale are part of the same SVG so there's no chance these will ever become misaligned. Also, this is the issue I see with using alarm priority colours: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/f/0f25889c54bf83a671da1a10f23e3501a801821a.png) HH = Critical, H = Medium The colours blend together, not enough contrast, maybe? ---
**Author:** ![richardNZ15](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/richardnz15/32/33373_2.png) [@richardNZ15](https://forum.inductiveautomation.com/u/richardNZ15)\ **Post date:** [July 17, 2024, 1:54am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/7 "2024-07-17T01:54:41Z")
Perhaps... Alarm priority colors can always be customized to suit though. Although the Ignition defaults are reasonably good. Maybe changing BG color of the PV indicator would be good enough. How did you say you utilized the ASM alarm symbol? On the device popup or on the device shown on the "mimic / screen" ? ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [July 17, 2024, 1:57am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/8 "2024-07-17T01:57:05Z")
> [@richardNZ15](#): > > Maybe changing BG color of the PV indicator would be good enough I did try this after a suggestion from a colleague, but it's not obvious enough (far left example): ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/d/dd110f7f481e97395bc283bf73f6ee1954107ecc.png) > [@richardNZ15](#): > > Alarm priority colors can always be customized to suit though I'm using the colours from HPHMI standards, so I can't really change them. > [@richardNZ15](#): > > How did you say you utilized the ASM alarm symbol? On the device popup or on the device shown on the "mimic / screen" ? I embedded my analogue indicator into another template view and added the alarm symbol into that ---
**Author:** ![JeremyMills](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jeremymills/32/70121_2.png) [@JeremyMills](https://forum.inductiveautomation.com/u/JeremyMills)\ **Post date:** [August 20, 2024, 11:21pm UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/9 "2024-08-20T23:21:15Z")
Nick, Thanks for developing this. I'm working on a solution today where I'm combining components and finding the indicator triangle of the built in MovingAnalogIndicator to be a hastle. Is your indicator triangle visibility able to be toggled on and off? ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [August 21, 2024, 6:18am UTC](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/10 "2024-08-21T06:18:45Z")
Not as-is, but it would be trivial to add a custom prop to control its visibility. ~~Just a note: I did find a bug in the above attached file where it doesn't handle negative minimum ranges. I haven't had any time to roll up the fix yet~~ I posted an update to fix this in my [OP](https://forum.inductiveautomation.com/t/movinganalogindicator-need-more-alarm-levels/93268/2)