Content
# #google — 2026-03-25
**08:21 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774452104144279):** I assume PN2 is still an issues to be resolved?
**08:21 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774452112141749):** yes
**08:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774452128811529):** let me double check the data real quick
**08:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774452147712959):** yes.. something not right there
**08:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774452164819239):** multistateinput_189
**08:24 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774452265093489):** Ok. I will have a look when I arrive in Goleta. For your general knowledge, I am on site 10am to 6pm 3 days a week. Usually, Monday, Tuesday, Thursday. Days change depending on work loads.
**08:24 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774452294858339):** gotcha
**08:42 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774453336596399):**
![[F0ANMJCPBMH_image.png]]
**08:43 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774453382832529):** dual analog panels are done. once the multistateinputs get linked up, these should just start to work
**08:43 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774453408343269):** working on the bottom panels now
**09:28 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774456084991219):** let me know when you're in. the alarm state isnt coming through for the AHUs either
**10:13 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774458787697499):** getting setup
**10:29 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774459751492019):** ok, just finished setting up all the tags. we will also want to test the offline status... are those wired into the displayalarm point? or is it another status we need to derive somehow
**10:29 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774459771446909):** we will also need to map those where 0=normal vs 1=normal
**10:32 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774459949494959):** I don't think so. There is another Bacnet Object.
**10:32 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774459964932049):** I am chasing down an urgent comms issue
**10:32 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774459972618509):** no problem
**10:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774460163046179):**
![[F0ANV1MUQJW_image.png]]
**10:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774460167226399):** ignition page
**10:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774460192972919):** all the error messages will clear once we have the multistateinput tags mapped
**10:37 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774460239397659):** Can you Add a Nav to the left side dock
**10:37 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774460256690269):** yeah
**10:38 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774460289969099):** Also, label it Legacy Dashboard on the title. Home Icon is fine for now
**10:40 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774460422791179):**
![[F0ANYKWFT1S_image.png]]
**10:40 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774460428326479):** the existing pop out nav is already there. did you want someting different?
**10:46 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774460779186259):** Add the next selection group to be Legacy Dashboard. The first sub item will be this page and called "Legacy Home"
**10:47 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774460853313429):** Pop Out is Under - views>docks>menu
**10:48 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774460907916379):** I believe it should be easy to duplicate a group and creat the new group. That is a standard Ignition Perspective Dock View that I utilized
**10:49 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774460994493329):** do you want legacy dashboard at the bottom top of the menu? under charts? at the bottom?
**10:52 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461169374909):** Bottom is good for now.
**10:59 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774461580779879):** got that working
**11:00 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461656726619):** Nice
**11:01 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461694387739):** So tracked down my current issue on SC1 power meter. You have time to fix it?
**11:02 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461739413999):** Could probably be a quick fix. The UDT's lost their parameters.
**11:02 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774461753014199):** yeah, whats going on?
**11:03 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461814351389):** Look at SC1 and SC1B folders. SC1B works, SC1 broke.
**11:04 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461894320039):** I think you can export SC1B, edit the JSON, and import back over SC1.
**11:05 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774461917085799):** should they be the same?
**11:05 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774461926597119):** which parameters is sc1 missing?
**11:05 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461932270629):** The FLOATS reference the MODBUS folders
**11:05 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461951319489):** All ~20 floats broke.
**11:06 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774461994092389):** Every setpoint gone. Every parameter back to baseline.
**11:06 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462008769489):** interesting. i wonder what caused that.
**11:06 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462017332529):** just for SC1?
**11:08 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462109973269):** Remember me discussing that 2 weeks ago? I missed whole device
**11:08 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462124608489):** i do.. this is a remnant of that event?
**11:08 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462128801769):** Yes
**11:08 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462131324549):** gotcha
**11:09 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462176436089):** I am not using the parameters actually
**11:09 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462180346519):** only tags.
**11:09 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462196897109):**
![[F0ANT7WDQBY_image.png]]
**11:10 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462200810669):** so here is active Power A on SC1B
**11:10 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462207780579):** which should i duplicate over to SC1?
**11:10 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462213245239):** (for each float)
**11:11 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462273892089):** I think it is simple. Export the whole SC1B FLOATS folder. Find and replace SC1B with SC1. Reimport over SC1 FLOATS folder.
**11:11 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462301060959):** so everything other than devicename?
**11:11 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462308069709):** should match?
**11:13 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462383182779):** I think. You can't make it worse.
**11:13 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462391410679):** haha
**11:13 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462391824199):** ok
**11:13 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462397015609):** i'll make backups too
**11:13 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462401913129):** Likely we will have to change some alarm setpoints.
**11:13 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462423037969):** I am having you do it to get more acclimated with my existing setups.
**11:13 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774462435902759):** sounds good
**11:15 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774462504637739):** Also, feel free to offload backups/exports and play with them in your Linux machine if you like. Nothing you have access to is IP.
**11:32 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774463562236009):** @Reno Hiltermann can you check to see if that helped?
**11:36 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774463801003259):** Appears to be good
**11:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774463807006569):** yeah??
**11:37 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774463846887409):** Turns out the setpoints match closer to LP13
**11:37 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774463875386889):** is the structure the same? i can try to copy the setpoints over from LP13
**11:38 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774463882326849):** Yes
**11:38 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774463888029969):** ok, let me try this
**11:40 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774464018077319):** Some alarms setpoints will need to be done manually. Unless you can automate setting HI/LO +/- 5% and HIHI/LOLO +/- 10%. I had theorized how Claude or gemini could do it, but did not try.
**11:41 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774464068745039):** can you get specific with the parameters?
**11:41 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774464074886939):** tell me exactly what you want and i'll see what i can do
**11:41 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774464112313099):** LP13 HI+5% -> SC1 HI
**11:41 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774464118779759):** LP13 LO-5% -> SC1 LO
**11:41 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774464119617319):** ?
**11:46 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774464411981509):** More like SC1 VN HIGHHIGH = snapshotted process value +10%.
**11:47 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774464469141969):** So like export the working SC1, then have the AI set the alarm setpoints +/- 10% based on the process value that comes out in the export (snapshot).
**11:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774464539190479):** Ok. I think I understand. Do you want it to round to the nearest whole number or 10th?
**11:49 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774464572006219):** Let's do whole.
**11:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774464798689229):** ok
**11:56 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465017767089):** hm.. tag exports dont include live OPC values
**11:57 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465022171589):** let me think
**11:58 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465087772739):** i have an idea
**11:58 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465131647609):**
![[F0ANP9Q1GRZ_image.png]]
**11:59 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465142095499):** ran a one time script in the script console to give me live values for all the floats
**12:03 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465380093519):**
```
his is very revealing. The picture is clear — almost every tag has completely wrong min/max and alarm setpoints. The values look like they were copied from SC1B which appears to be a 480V/277V system, but SC1 is clearly a 208V/120V system based on the live readings
```
**12:04 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774465477151629):** nice. It knows all
**12:04 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465489209149):** impressive
**12:08 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465695840589):** so voltage N-G shows zero..
**12:08 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465703966929):** we dont want to calculate setpoints off of zero i dont think.
**12:08 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465722436709):** should we use nominal voltage for this system and then add 10/5/-5/-10%?
**12:09 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774465759630349):** oh. nuetral to ground should be 0
**12:15 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774466119892909):** It should be.
**12:15 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466125362159):** right
**12:15 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774466136309919):** Idk what setpoints I used for the others.
**12:15 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466136527379):** i am putting together a table for you to review before we import
**12:15 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466139929459):** with before's and afters
**12:16 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774466208792279):** I need help with disabling the pipeline for Signl4 alarms. I figured out that the FX80 connection must be disabled, then reenabled in Ignition to refresh BACnet objects. Sent out ALL the alarms lol
**12:17 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774466233706029):** On a postive side, I got the handshake for AHU1 to work and can now fix all of them.
**12:17 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466249583729):** nice!
**12:17 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466262676099):** do we need to disable the pipeline now?
**12:17 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774466279239429):** No not yet.
**12:18 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774466294528099):** Having a disabled toggle tag would be great
**12:18 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774466309294899):** Idk if that is possible.
**12:19 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466391247409):** i think it is
**12:20 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466400452599):** i need to step away for a bit after i finish these tags
**12:20 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466402821229):** but will be back
**12:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466566854509):**
[[F0ANPF4LTDH_alarm_setpoints_1.html]]
**12:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466570535729):** can you open this in chrome
**12:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774466577303329):** and let me know how the numbers look
**12:54 [Kevin](https://slack.com/archives/C0A56N14A5S/p1774468454429669):**
@Reno Hiltermann Seth has a couple questions on the panel build
1. do the digital outputs wire to the terminal blocks next to the ziplink modules? they have labels of 3xxP which we are confused about
2. what are the fuses and term blocks next to the power supplies for?
**13:22 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774470143120289):** @Mason Radke LGTM
**13:22 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774470168301359):** Seth works for you?
**13:28 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774470503652079):** @Kevin I see my mistake on the power wiring. Yes that is the purpose of those terminals. Let's just delete wiring for the outputs, as ultimately, I may delete that card if it is unneeded. It is there for future use only.
**13:28 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774470539398149):** Does late this evening work for a revision? I have a few other things I want to focus on.
**15:18 [Kevin](https://slack.com/archives/C0A56N14A5S/p1774477086970139):** I subcontract my panel builds to Seth
**15:18 [Kevin](https://slack.com/archives/C0A56N14A5S/p1774477101288759):** I hope to employ him soon
**15:18 [Kevin](https://slack.com/archives/C0A56N14A5S/p1774477122248309):** ya get the revision over when you can
**15:18 [Kevin](https://slack.com/archives/C0A56N14A5S/p1774477135393119):** I'll just have him hold off on wiring the DOs