Content
# #ccsd-water-ignition — 2025-08-27
**09:33 [andy](https://slack.com/archives/C08TVA84PD4/p1756312394234749):** I adjusted the MovingAnalogIndicatorSparkline to fit the display names
**09:42 [andy](https://slack.com/archives/C08TVA84PD4/p1756312926686369):** The inner tab container doesn't take up the entire screen width and is the underlying cause of the width issue.
I changed the root container to fixed mode and it allowed me to resize the inner container and now everything fits. I'm not fully aware of the implications of that change but it appears to work how I expect it to.
![[F09BXSXCG6B_image.png]]
**09:46 [andy](https://slack.com/archives/C08TVA84PD4/p1756313180551539):** I see that you created new displays for the views within that second tab container rather than using all of the displays that I set up for you to use. This is how the WWTP project is set up, using embedded views that have breakpoints for large and small view types.
**09:48 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756313314531009):** i decided to leave the resolution issues until i could verify on an ipad.. no way for me to tell if i was going in the right direction. im having a hard time with all the embedded views getting things to scale automatically as not everything is in a flex container
**09:49 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756313349473109):** i still embedded all of your existing views. i dont think i had to create any new ones.
**09:49 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756313398434649):** all the well pages are your embedded views that have the large and small views
**09:52 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756313555911479):** im trying to do my best in figuring out how to work with all of these existing views / containers / embeds / resolutions, etc. there lot already going on here.. im trying to re-use all that you have already done as much as possible.
**09:57 [andy](https://slack.com/archives/C08TVA84PD4/p1756313820850089):** I'm learning how you do things as much as you are learning my ways lol
**09:57 [andy](https://slack.com/archives/C08TVA84PD4/p1756313870741529):** I want to encourage my open door as far as execution of tricky things, I'm less flexible on this project as we are trying to keep the WW and W projects similar if possible.
**09:59 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756313948084109):** that makes sense. i am struggling a little bit with the embeds and the resolutions. but i think being able to check in real time on the ipad will get me there
**09:59 [andy](https://slack.com/archives/C08TVA84PD4/p1756313955280519):** All of that being said, the displays ALL look great on my iPad, i think it would be safe to proceed, as the large screen resolution is 1920x1080, and I just change my monitor resolution to that to make sure everything looks good, not just resizing of the browser display
**09:59 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756313977021509):** ok yes.. 1920x1080.. that should be easy enough to work with
**09:59 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756313979896739):** standard
**10:02 [andy](https://slack.com/archives/C08TVA84PD4/p1756314178056559):** I have an Ignition team that I can use to develop everything youre doing now, they are the ones that did the WW project. I'm concerned about the PLC stuff that only you and I can do. Control strategies and comms. I think I'd like to switch focus for you to work on PLC heavy stuff as we are already starting to see the crunch happen.
I have the water booster project that needs to be completely ready for use in 2 months, the cambria wastewater control strategies in about a month, let alone this cambria water project.
I think your most valuable use is on the under the hood side primarily, until you have more bandwidth to be able to handle both.
**10:03 [andy](https://slack.com/archives/C08TVA84PD4/p1756314230431249):** What would be a good breaking point for you, in regards to how invested you are in the Ignition work you are already doing?
**10:07 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756314443349969):** for ccsd? work is not letting me go easy, and i am still very busy with them. im just about out of vacation time (which has allowed me to get some of this ignition work started for ccsd).. i have officially resigned, but with the agreement to wrap up existing projects and not taking on anything new.
**10:07 [Mason Radke](https://slack.com/archives/C08TVA84PD4/p1756314470082629):** if you have ignition resources i think it makes great sense to utilize them now.
**14:41 [andy](https://slack.com/archives/C08TVA84PD4/p1756330870370609):** I reached out to my Ignition team and they are booked out so I will do this work myself. I think the highest priority and most effective use of your expertise is focusing on communications on this project.
This excerpt is copied from the project document:
1. Communications - reference [CCSD Water Project Backups IO Configs](https://drive.google.com/drive/folders/1ZneEKlJl7Q8l2tPbfo1Lk8wKAYmemYZu?usp=drive_link)
a. Reference this spreadsheet for IO Point correlation with Modbus addresses
i. https://docs.google.com/spreadsheets/d/1v5gXvtNvfIo58OJE3jPbdhaI5_uVJG3G/edit?usp=drive_link&ouid=105974013212587964753&rtpof=true&sd=true
ii. Andy to get screenshots of IO config within Opto 22 PAC Control
b. Create Program that creates sequential messaging (message RTU 1100, and once it gets DN or ER, move on to RTU1200) to each RTU with the following features:
i. Polling time between cycles display
1. Alarm if greater than 60 seconds or count the errors, greater than x, lets pick one
ii. Escalating attempt intervals (user editable, global intervals: internal 1- 10 seconds, interval 2 60 seconds, interval 3 300 seconds)
iii. Ability to disable polling a particular RTU by user
iv. WRF is an Allen Bradley Compactlogix Controller that can be messaged explicitly, this is what the Opto 22 controller is doing now, we can replace that functionality with the new SCADA controller, all other RTUs are Opto 22 SNAP PAC R1 or EB1 controllers.
c. Alarms:
i. ROC
ii. Watchdog, create AOI
iii. tank flatline use existing AOI
iv. Tie in Comm fails into each device IO Fault on the PAX object that it is affected by
[[F09BZ2BQJHM_ccsd_water_ignition_phase_3_io_points_for_modbus_reference.xlsx]]
**14:44 [andy](https://slack.com/archives/C08TVA84PD4/p1756331065386379):** Please use Page/Embedded/Comms page to develop your UI on