Content
# #tough-smr — 2025-08-21
**15:06 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755813970392109):** SMR gateway and project loaded no problem
**15:10 [andy](https://slack.com/archives/C08NFJSU753/p1755814257666719):** and I apologize, I think you've sent it to me before, but I need to program the sensaphone to match the alarm outputs you programmed, do you have a list I can reference?
**15:11 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755814301461929):** no need to apologize! yeah let me see what i can find
**15:17 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755814643559929):** • *DO/0 – Tank Alarm:* HIHI, HI, LO, LOLO, I/O fault, Fail (any alarm on the faceplate)
• *DO/1 – Chlorine (Cl₂) Alarm:* HIHI, HI, LO, LOLO, I/O fault, Fail (any alarm on the faceplate)
• *DO/2 – Turbidity Alarm:* HIHI, HI, LO, LOLO, I/O fault, Fail (any alarm on the faceplate)
• *DO/3 – Well Alarm:* Any pump alarm or flow alarm (as configured on the well faceplates)
• *DO/4 – Transfer Alarm:* Any pump alarm, upstream pressure alarm, downstream pressure alarm, transfer flow rate alarm, CLA-VAL alarm (as configured on the faceplates)
• *DO/5 – Booster Pump Alarm:* Any booster pump in alarm
• *DO/6 – System Pressure Alarm:* Any system pressure alarm (as configured on the system faceplate)
**15:17 [andy](https://slack.com/archives/C08NFJSU753/p1755814671876789):** awesome thanks
**15:20 [andy](https://slack.com/archives/C08NFJSU753/p1755814857472099):** I have an alarm on DO/0, is that correct since you're in there
**15:21 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755814872154899):** let me look
**15:23 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755814984698559):** what do you mean? we have the xt100 alarms going to DO/0
![[F09B4PJSC7R_image.png]]
**15:23 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815002033089):** let me xref do/0
**15:23 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815010779169):** see if anything else is tied to it
**15:23 [andy](https://slack.com/archives/C08NFJSU753/p1755815013450629):**
![[F09B4PM15KR_image.png]]
**15:23 [andy](https://slack.com/archives/C08NFJSU753/p1755815029184609):** I saw the output on the other day as well
**15:24 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815068374939):** oooooh.. like is it currently active
**15:24 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815072214169):** standby let me go online
**15:24 [andy](https://slack.com/archives/C08NFJSU753/p1755815083802879):**
![[F09CAL73PDE_img_4904.jpg]]
**15:27 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815270366719):** uh.. so i see several alarm outputs on.. but not DO/0
**15:28 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815280643729):** unless it alarms when the signal is false
**15:28 [andy](https://slack.com/archives/C08NFJSU753/p1755815282756679):** lol in my pics I saw the same thing
**15:28 [andy](https://slack.com/archives/C08NFJSU753/p1755815305520689):** the common might not be tying through the relay outputs, but theres something fishy.
**15:28 [andy](https://slack.com/archives/C08NFJSU753/p1755815322729739):**
![[F09BWMT6B7T_img_4944.jpg]]
**15:28 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815324222809):**
![[F09BFV9PNJH_image.png]]
**15:29 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815352189409):** do/4 is also energized... but 5 and 6 or off
**15:29 [andy](https://slack.com/archives/C08NFJSU753/p1755815375790219):** So that tracks between PLC to interposing relays, but not translating to the sensaphone
**15:30 [andy](https://slack.com/archives/C08NFJSU753/p1755815414755169):** Sounds like something @Kevin could figure out in a millisecond when he has time
**15:30 [andy](https://slack.com/archives/C08NFJSU753/p1755815450164399):** Typically sensaphones you can use the common wire tied through all the relay contact commons to switch the relay circuit, which is what i did there.
**15:31 [andy](https://slack.com/archives/C08NFJSU753/p1755815476493639):** Are all of those alarms accurate?
**15:31 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815489615949):** let me load a client and see how that tracks
**15:31 [andy](https://slack.com/archives/C08NFJSU753/p1755815518275449):** Depending on how you tied it in, the PAX object latches failure mode and needs to be cleared before it clears your condition
**15:32 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815574812769):**
![[F09B4QJB971_image.png]]
**15:33 [andy](https://slack.com/archives/C08NFJSU753/p1755815592498159):** right cuz it's not connected
**15:33 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815610529049):** so thats likely why that one is energized?
**15:33 [andy](https://slack.com/archives/C08NFJSU753/p1755815611655549):** right the SC hach devices are still offline I believe
**15:33 [andy](https://slack.com/archives/C08NFJSU753/p1755815619193909):** turb should be the same then
**15:33 [andy](https://slack.com/archives/C08NFJSU753/p1755815639280419):** wells and transfer alarms?
**15:34 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815644249409):**
![[F09CAM727L0_image.png]]
**15:34 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815653205689):** turb doesnt have anything enabled
**15:34 [andy](https://slack.com/archives/C08NFJSU753/p1755815675583829):** right, then that's incorrect outputting right?
**15:35 [andy](https://slack.com/archives/C08NFJSU753/p1755815704883139):** config error?
**15:35 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815724926969):**
![[F09CAMBEZLY_image.png]]
**15:35 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815734123749):** the pax object for turb is still in fail mode.. value=32
**15:35 [andy](https://slack.com/archives/C08NFJSU753/p1755815744543899):** hit the ack button and see if it goes away
**15:36 [Kevin](https://slack.com/archives/C08NFJSU753/p1755815779319559):** or troubleshoot to see why they dont show on faceplate first
**15:36 [andy](https://slack.com/archives/C08NFJSU753/p1755815803770649):** we should know if val=32
**15:37 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815847515289):**
![[F09BH86LCAE_image.png]]
**15:37 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815854748169):** without digging into the AOI.. i see the sts_fail energized here
**15:37 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755815859041939):** likely because we're under range
**15:38 [andy](https://slack.com/archives/C08NFJSU753/p1755815897767649):** hm they aren't enabled so it doesn't show. I guess that makes sense I never leave them that way
**15:40 [Kevin](https://slack.com/archives/C08NFJSU753/p1755816037498549):** sounds like an issue with whereever the enable check boxes are tied to?
**15:41 [andy](https://slack.com/archives/C08NFJSU753/p1755816073013199):** If the relays are energized they should be passing the sensaphone alarm circuit through the relay contact though, even if they are not energized appropriately
**15:43 [Kevin](https://slack.com/archives/C08NFJSU753/p1755816201688979):** Sorry, thought you were talking about the one sensaphone input that is energized
**15:45 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816308385159):**
![[F09BWPD6YHF_image.png]]
**15:45 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816310616229):** so the UDT for P_VSD
**15:45 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816313857609):** on the sts_fault alarm
**15:45 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816318680119):** is missing a binding for the label
**15:45 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816325485429):** will update now to match the others
**15:47 [Kevin](https://slack.com/archives/C08NFJSU753/p1755816449506619):** did ya'll notice the new "to-do" lists in Slack? Not sure if it's something we want to use.
**15:47 [andy](https://slack.com/archives/C08NFJSU753/p1755816462436809):** {pathtotag} is a passed in parameter, have you been changing those to hard coded bindings?
**15:47 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816462507149):** i just added one here
**15:47 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816476182549):** im looking for a way track requests
**15:48 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816498016819):** no.. i have not been hard coding those.
**15:48 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816513832649):** the label is missing its binding so thats why the description was missing on the alarm list.
**15:48 [andy](https://slack.com/archives/C08NFJSU753/p1755816528047869):** Ah gotcha
**15:49 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816555292869):**
![[F09BG1VL3N1_image.png]]
**15:49 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816556635599):** regarding that screenshot
**15:49 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816562263969):** it should be fixed now.. let me test
**15:49 [andy](https://slack.com/archives/C08NFJSU753/p1755816572179189):** yep makes sense now
**15:51 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816664478349):**
![[F09B4S1B68P_image.png]]
**15:51 [andy](https://slack.com/archives/C08NFJSU753/p1755816680985569):** nice looks good!
**15:51 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816684458389):** looks better
**15:51 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755816701648689):** ok cool.. moving onto trends
**15:59 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755817168331109):** @andy there is a chart shortcut on the left side menu and then i added a trend tab to the main horizontal menu.. do you want trends accessible from both locations?
**15:59 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755817186719239):** the left side menu is nice because we can use the sub tabs easily.
**16:00 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755817225003819):**
![[F09BMAP6MS8_screenshot_2025-08-21_at_4.00.04___pm.png]]
![[F09BWQRLR25_screenshot_2025-08-21_at_3.59.59___pm.png]]
**16:01 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755817284478699):** if we use the trend tab at the top we'll have to build some sort of sub menu to access multiple trend pages
![[F09BMASKL3W_image.png]]
**16:01 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755817308218849):** OR wait.. i should be able to make that link to the trend page with the 3 tabs
**16:04 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755817469326919):**
![[F09BMB5KHB6_image.png]]
**16:04 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755817482964379):** boom i like this.. the trend tab at the top embeds the chart page with its own set of tabs
**16:30 [andy](https://slack.com/archives/C08NFJSU753/p1755819001013479):** I like as well
**16:30 [andy](https://slack.com/archives/C08NFJSU753/p1755819028477989):** I don't need trends accessible from both, delete the menu tab if you want to keep it simple
**16:33 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755819200010599):** had to update the UDT so the pump speeds were being logged to the edge historian
**16:33 [andy](https://slack.com/archives/C08NFJSU753/p1755819208099269):** awesome
**16:33 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755819209840049):** (do you like to trend pump speeds?)
**16:37 [andy](https://slack.com/archives/C08NFJSU753/p1755819429800799):** yes please
**16:37 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755819433426109):** copy
**16:54 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755820490565439):** Trends are almost done. Need to group onto axis to improve readability. And add some pump speeds.
**16:55 [Mason Radke](https://slack.com/archives/C08NFJSU753/p1755820515962989):** Will wrap it up tomorrow