← GQ3

Clients/GQ3/slack/2026/03/2026-03-24_google.md

slack
Source
4
Chunks
7
Entities
Doc
Type

Content

# #google — 2026-03-24 **08:14 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774365287730719):** automation direct says it was delivered 3/10 **08:16 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774365412224109):** ![[F0ANGLR0B1U_Screenshot_20260324_081631_Chrome.jpg]] **09:26 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774369578459469):** @Mason Radke do you have time now or later today to go over alarm animation logic? **09:26 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774369612687589):** Now would be great **09:28 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774369710203989):** starting a meeting shortly **09:34 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774370093733719):** im in there, ready whenever you are **09:36 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774370182335119):** weird **10:16 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774372563428269):** So some of the categories use the FX80 DisplayAlarm (ie AWN), and some use the N4 DisplayAlarm (ie AHUs). **10:16 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774372607662909):** The ones using the FX80 alarm are useful, the N4 ones cannot be used. **10:17 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774372624482529):** this may take a bit to wrap my head around, but im starting to see the picture **10:17 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774372667435229):** Yeah. The goal is to have you understand the existing system. I know it is a spiderweb. Every time I dig deeper I find more issues. **10:18 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774372710495989):** ok.. im learning. i'll drop questions here, no rush to respond if you're in other meetings, **10:26 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774373186664699):** We will get it figured out together. **10:41 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374090489549):** I did not get a new export before you logged into .100. You can make one using the method in the shared sheets document **10:42 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374137462369):** ok. im going to work on a proof of concept sort of thing **10:42 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374143010979):** ok **10:42 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374173605179):** is my understanding correct that if we can map that displayalarm value for each, it should give us the states? the logic is wired in from all the various sources already on the other system? **10:43 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374193084569):** For some boxes yes. **10:43 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374200874539):** ok **10:48 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374520435089):** You can check the wire sheets in the FX80 points folders to make sure that there is logic for the DisplayAlarms points (tags). **10:49 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374555529739):** ah, right.. so dsiplayalarm points that arent linked up we will need to find another way? **10:49 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374594375499):** Yes. **10:50 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374610110329):** I saw that AHU1 is not linked up. **10:50 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374643416829):** does that mean that the existing dashboard isnt working fully? or is it triggered another way **10:51 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374667774439):** It is triggered by the DisplayAlarm in N4. **10:51 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374682778889):** FX80 is a physical controller. N4 is the server. **10:51 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374697411649):** got it **10:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374786435669):** if you have time lets work through the first example. i'll share screnshots here. standby **10:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374807863819):** ![[F0ANL4VCJ4A_image.png]] **10:53 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374811992549):** line heaters.. this is the displayalarm point **10:53 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374826329719):** yes **10:54 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374861257989):** ![[F0APED211A4_image.png]] **10:54 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774374871230559):** should i be able to find that point here? **10:55 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374955762399):** I think so. **10:56 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774374971858679):** let me check the spreadsheet **10:58 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774375082285549):** Does not appear to exist yet. **10:59 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774375162033839):** so for this line heaters example, what would be the approach? do we need to add that object in the N4 system somewhere so its available in object list in ignition? **10:59 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774375165482039):** Also that is the wrong folder **10:59 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774375173132789):** oh **11:00 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774375219914019):** that is N4, not FX80 **11:01 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774375284091619):** how can i tell the difference? when i looked up the point source earlier it mentioned FX80 in its path. also is there a way to access the N4 objects from ignition? **11:03 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774375404249119):** No. It requires an OPC license. **11:04 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774375475660159):** I am deleting N4 and don't want to get more **11:05 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774375537451899):** ah ok.. ideas on getting this lineheaters displayalarm status in ignition? would we need to look at the individual alarm/warning statuses that make up the displayalarm point and doing the logic in ignition? **11:06 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774375569914099):** or is there a way to wire it up in N4 to write back to the fx80 controller somehow? im kinda guessing with that question **11:25 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774376752143339):** Just finished my last meeting. I am going to grab lunch at 1145 and be back on by 1230. I agree. Let's do the logic in the FX80 and pull DisplayAlarm points (tags) for each box. **11:26 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774376771444739):** Some do not exist and will need to be created. **11:26 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774376781035349):** once we get a method down we can run with it **11:26 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774376796535159):** Right. Can you meet at 1230? **11:26 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774376799928339):** yessir **11:27 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774376848237619):** I will schedule it and show you how to create points, and add them to the local machine (FX80 communication endpoint that Ignition pulls data from). **11:27 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774376859495729):** perfect **12:39 [Kevin](https://slack.com/archives/C0A56N14A5S/p1774381155852989):** @Reno Hiltermann ferrules or no? **13:10 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774383002461699):** Not necessary. **13:10 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774383016942609):** I assume you can get the strands in the terminals **13:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385319751769):** ok, i think i have the first panel working. **13:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385325806099):** i have two parameters on the UDT **13:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385332055319):** one for multistateinput instance **13:48 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385339442219):** and one for analoginput instance **13:49 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385355910989):** so you just pass the two instance numbers to the UDT **13:49 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385397805239):** and the status is customizable so if 0=normal it can easily be changed **13:50 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385402264399):** ![[F0APFMMDP8Q_image.png]] **13:50 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385437470459):** ![[F0ANR1M20UU_image.png]] **13:51 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385488846819):** ![[F0AN60N9Y31_image.png]] **13:52 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774385531955649):** @Reno Hiltermann this is on the N4 dashboard.. line heaters is showing grey for offline but says normal.. is that how it works when its offline? (showing the normal text?) **14:00 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774386052045899):** I broke that one. fix it in the wire sheet. **14:01 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774386064027029):** i thought maybe we did something there. **14:01 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774386079965919):** It was me. I can fix it in a while **14:02 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774386124866289):** im trying to figure out one more piece. im looking at AHU_1, the tmpdisplayalarm point is not in the localdevice/export table thing **14:02 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774386133179319):** trying to add it **14:05 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774386324149569):** Maybe try adding a new point that links to the output on the old point. **14:51 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774389094023649):** Back at my desk. Can I hop on .100? **15:23 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774391028404129):** I fixed the issue on the Line heater object to display offline, normal, or warning. **15:24 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774391046752619):** Shouldn't need an alarm for now. **15:50 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774392653093009):** ![[F0AP112P1AM_Screenshot_2026-03-24_154530.png]] **15:51 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774392690905659):** I created loopback tags in the FX80 that currently point to the display alarms in N4. **15:52 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774392754622149):** Now I will add to the export table by discovery **16:04 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774393472071069):** ![[F0AP12Z9117_Screenshot_2026-03-24_160411.png]] **16:27 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774394858091179):** Nice! **16:27 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774394870921959):** I think we're close to having this all figured out **16:31 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774395117396059):** Yes. Let's plan to use DisplayAlarms for each box. If they DNE I will create them. **16:32 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774395151517369):** Perfect **17:12 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774397559409759):** i stepped away, but im starting on this again now. **17:16 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774397793214139):** ok **17:16 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774397800325249):** did i just kick you off? **17:16 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774397818624769):** i see the new points added there **17:17 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774397823433089):** yeah all good. **17:17 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774397874878329):** Take AHU1 as an example **17:18 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774397890491739):** It was using the DisplayAlarm in N4. **17:18 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774397911353669):** I copied that point from N4 to FX80 AHU1 controller. **17:18 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774397918909689):** where is that done? **17:19 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774397972289469):** let me show you **17:20 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398004797079):** open a chrome browser and go to chrome rdp **17:20 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398041688929):** Use remote support and send me the code **17:20 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398050247949):** choose share this screen **17:21 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398108102939):** You can do it from the server. **17:21 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398114209559):** .100 **17:21 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774398117537039):** k **17:21 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774398119813109):** standby **17:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774398156271559):** a screenshot might be enough too if you can connect back to .100 really quick **17:22 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774398162735219):** but im working on the remote support connection **17:23 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774398199369319):** 748087810712 **17:25 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398315626039):** GO TO TOP OF TREE **17:25 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398315794949):** sorry caps **17:25 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774398329154739):** go to AHU1 folder under N4 server **17:25 [Slackbot](https://slack.com/archives/C0A56N14A5S/p1774398341448249):** **18:33 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774402422450079):** things are going well but have a question. **18:33 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774402433320189):** im on Purge N2, and i see it in the export table.. instance 189 **18:33 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774402437953469):** but its not resolving in ignition **18:36 [Reno Hiltermann](https://slack.com/archives/C0A56N14A5S/p1774402591983489):** on the road **18:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774402597041319):** ok, no problem **18:36 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774402603563299):** it can wait until tomorrow, i'll keep going **19:28 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774405733624649):** ![[F0ANSL24QKW_image.png]] **19:29 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774405766588439):** top group is done. all analog values are good.. just need alarm status for the grey items **19:30 [Mason Radke](https://slack.com/archives/C0A56N14A5S/p1774405844400749):** we should be able to wrap it up tomorrow

Extracted Entities

TypeKeyValueConfidenceEvidence
server N4 server IP .100 90% I did not get a new export before you logged into .100
system FX80 FX80 95% FX80 is a physical controller. N4 is the server.
system N4 N4 95% FX80 is a physical controller. N4 is the server.
system Ignition Ignition 95% FX80 communication endpoint that Ignition pulls data from
task Meeting at 12:30 2026-03-24 12:30 90% Right. Can you meet at 1230? ... I will schedule it and show you how to create points
task Create missing DisplayAlarm points Create DisplayAlarm points that do not exist yet 90% Some do not exist and will need to be created.
task Add points to export table Add created points to export table by discovery 85% Now I will add to the export table by discovery
File: Clients/GQ3/slack/2026/03/2026-03-24_google.md
Updated: 2026-03-25 02:45:14.167557