prak7121

I feel silly asking this question after so many years of programming but I did a search and could not find a good answer for the following question: When I program, how does the If Path, Then Path, Else Path work? That is, how do I choose one of the 3 options and where do I put them. For example does Then Path only get put in the Then section or can it be both in the Then or the Else? Here is a sample program that I believe I fixed this morning. I had the (Then Path) as (If Path). If On Sun From 10:00:00PM To 11:55:00PM (same day) Then Set 'Plant Heat- Main' 44° (Heat Setpoint) Else Run Program 'VeriForm Plant afterhours' (Then Path) In the above example I want the Else commands to only run if the statements in If area are not true.

Thank you

I have two separate IO Lincs that have limit switches connected to Sensor inputs. If either of the limit switches are closed (on), the IO Linc sends a signal to the to the ISY which in turn sends a signal to one of the outputs on an EZIO2x4 and closes the contacts to start a fan. If both limit switches return to an open state (off), the ISY is programmed to open the contacts on the EZIO after a 3 minute delay. In other words, the fan runs for an additional 3 minutes after the limit switches are opened. The question I have, if either limit switch is re-closed within the 3 minute time delay, does the ISY still send a signal to the output on the EZIO to open its contacts and result in the fan turning off? Do I need to create a subroutine that aborts the 3 minute delay to ensure the fan continues running if either of the limit switches are closed during the 3 minute delay? Here is the current routine that we have: If Status 'P23-Sensor' is Off And Status 'P22-Sensor' is Off Then Wait 3 minutes Set 'VeriCONTROL' Off Set 'VeriCONTROL - 2' On Send Notification to 'fansetback' content 'fanmotoroff' Else Set 'VeriCONTROL' On Set 'VeriCONTROL - 2' Off

Any ideas that on a few things we can do to check and bolster our communications? We are pulling out our hair and my customer is extremely frustrated with me. I would be indebted for any help to eliminate the lag times and inconsistent activation of the EZIO2x4. No really, I am at my wit's end. The place is all 3 phase and we have done a great job of phase syncing the devices and we see the devices in the ISY GUI but the lag time is killing us. With the lag time we are thus getting the system being controlled by the IOLinc's via the EZIO2x4 not running or running at inappropriate times.

Those are great questions and I am not sure I can answer them for lack of insight and experience. But I can say this.....if I change the STATUS to CONTROL, is there anything I can do to monitor the results other than waiting for the customer to report to me that the system is not turning on or off when it should be? One example of my confusion is that I have seen the system not update (as it would update the status of each device after a Query) immediately. So I am concerned that the 2 IOLincs are experiencing changes through the limit switches they monitor but that the ISY is not seeing the changes in status and therefore there is a lag between the limit switches and IOLinc and the ISY. We have even raised all the devices in the large open space to make sure there is no loss of communication and that we have optimal lines of site for the RF. But when the limit switches are engaging the dust collector should be coming on quickly in just 2-3 seconds but instead we see anywhere from 5-25 seconds. We have even replaced the PLM and the ISY and put in 4 more access points to make sure the signal is consistent and not broken. Plus I would say 1-2 times per hour we lose connection with either IOLinc or the EZIO2x4. To the point that we created another program to run Query every 20 seconds. I hate having to do the query but it gives me some confidence that we are refreshing the devices to see their status. Hopefully I have given you enough details to answer the question of what our errors are.

Since installing an ISY994i at a customer site and installing the 3 series of firmware we keep getting the following Security Message popping up at login. Any idea how to get rid of the message permanently? We have tried a few things without success. The message keeps coming up at every login

Hi Vyrolan, are you 100% sure about the Control versus Status? I ask because we are doing this already at my company for 2 years using Status without issue. Mind you at my plant we only monitor 1 IOLinc whereas at this customer site we are monitoring 2 IOLincs.

Currently here is our program for making a dust collector run when 2 cutting torches are OFF or ON. (Program below at the end of the post) • Dust Collector running either VFD Default Speed or Speed 3 (EZIO2x4) o …..this is a variable frequency drive that turns the dust collector off when the variable frequency drive is enabled (ON) • Torch 1 is shown as P22 Sensor (IOLinc) • Torch 2 is shown as P23 Sensor (IOLinc) The program looks good to us and runs already here at my plant with zero issues. But we keep getting an error where the variable frequency drive should be running the VFD-Default Speed when either one of P22 or P23 Sensors are ON. We have a 3 minute delay whereby if either P22 or P23 or both are OFF, then the Speed 3 goes to ON. The problem we have is that when the P22 or P23 sensors return to ON, the Default Speed should come back in a split second. Instead we are seeing and measuring anywhere from 3, 5, 8, 15, 25 seconds randomly. On average 5 seconds is the main lag time but 3 to 25 seconds is not acceptable. My customer’s site fills up with smoke in 3-5 seconds. After 15-25 seconds I start to get nasty emails from my client. Please can you help us and give us your opinion on whether we have done anything wrong? Here is the program If Status 'P23-Sensor' is Off And Status 'P22-Sensor' is Off Then Wait 3 minutes Set 'VFD - Speed 3' On Set 'VFD - Default Speed' Off Send Notification to 'fansetback' content 'fanmotoroff' Else Set 'VFD - Default Speed' On Set 'VFD - Speed 3' Off One thing I want to add….we just discovered this. Both here and at my customer plant we are running both systems using the 3.3.5 firmware. But at my plant we have the ISY99iIRPro but at the customer plant we are running the ISY994i Here is a snapshot of their About:

On the about box, there is no mention of Radio Frequency, but we have the PLM. Is it possible the ISY994I is the wrong version, we should bought ISY994IR. We are using the PLM but the About box does not show the ISY as being RF capable. We are having communication errors at our customer site, that's why we are asking this question.

If the version on the item is not clearly shown as being other than v.00, is that an issue? Right now the EZIO 2 X 4 shows as being v.oo, will this cause communication errors or operational errors? What type of errors will this cause? I attached the picture, please have a look. We are having communication errors at our customer site, that's why we are asking this question.

Hello UD team......2.8.13 for 994i will not download, the link fails....is it not available yet? Paul in Canada