Clients/Rancho-Ynecita/slack/2026/01/2026-01-10_rancho-ynecita.md

# #rancho-ynecita — 2026-01-10 **15:51 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768089085247789):** ![[F0A7XQ3K66A_image.png]] **15:51 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768089098770759):** water level visualization in tank **17:55 [Kevin](https://slack.com/archives/C09D358F91R/p1768096505021469):** Beautiful! **17:55 [Kevin](https://slack.com/archives/C09D358F91R/p1768096515969719):** ![[F0A83L0R6HJ_screenshot_20260110-174803.png]] **17:55 [Kevin](https://slack.com/archives/C09D358F91R/p1768096527125739):** Look at that beautiful trend **17:55 [Kevin](https://slack.com/archives/C09D358F91R/p1768096547521179):** Great work @Mason Radke **18:01 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768096885225539):** Yes, sir! **18:01 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768096896565609):** I put the comm buffering on the flow rate as well **18:01 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768096914497159):** If you see any potential issues, let me know and we’ll work them out **22:08 [Kevin](https://slack.com/archives/C09D358F91R/p1768111690371229):** Both wells came on and just overshot the off setpoint a bit, causing the high alarm. I think we can raise high alarm to 11.5