Jump to content

Problem with IO Linc 2450


salex319

Recommended Posts

Posted

My IO Linc doesn't cause this program to trigger. I can query the IO Linc and change the options. When I trigger the input sensor the LED goes on but the program doesn't start. I've also tried "switched Off." Can't see what I'm doing wrong.

 

If
       Control 'Alarm in-Sensor' is switched On

Then
       Set 'Alarm Lights' Fade Up

Else
  - No Actions - (To add one, press 'Action')

Posted

The status of the IOLinc probably changes before the THEN clause can fully execute.

 

Try changing the FADE UP command to ON. If it works with the ON command then you should have the IOLinc call a separate program that runs your FADE UP command

 

In your current program I believe The FADE UP will only execute as long as the IOLINC remains triggered

Posted

Does the status light on the IOLinc come on when it's triggered?

 

If you manually trigger the IO Linc does your program run?. If not you may have a communication issue. Check the status of the IOLinc in your ISY to see if it shows a change in status when triggered.

 

Is "Alarm in sensor" referencing the IO SENSOR or the IO RELAY?

 

If you manually run the THEN clause in your program does the light come on?

Posted

The Green LED on the I/O Linc at the wire connections should turn On/Off as the I/O Linc Sensor turns On/Off. If the Green LED does not turn On/Off look at what is controlling the I/O Linc Sensor input.

 

If the Green LED turns On/Off does the I/O Linc Sensor node "Current State" column cycle On/Off. The Sensor node may be On when the Green LED is Off depending on what is controlling the Sensor. If the Current State column does not cycle On/Off when the Green LED does there is a comm issue between the I/O Linc and the PLM.

Posted

Answers to reply 1

 

1)When triggered both the green LED next to the input connector and the white light on the side flash.

 

2) If I manually trigger the IO Linc the program runs.

 

3) Alarm In-Sensor is referencing the sensor.

 

Answers to Reply 2

 

1) The green LED goes on and the white one flashes on the IO Linc when I trigger it. Also I can change options from the ISY just fine.

 

I didn't know about triggering the IO Linc by pushing the Set button until it was suggested but since I tried that and the program runs that would seem to rule out comm problems.

 

When I hold my trigger input low the green LED comes on and stays on until I release the signal. The white light on the side and the relay also follow the green LED ( depending on how I set the options).

 

Oh and the ISY Admin Pgm doesn't respond to my trigger input but does respond to the manual trigger.

Posted

"Oh and the ISY Admin Pgm doesn't respond to my trigger input but does respond to the manual trigger."

 

What voltage is applied to the I/O Linc Sensor?

 

The Green LED turning On does not mean the Sensor is actually On enough to send a command. It sounds like what is controlling the I/O Linc Sensor is not applying I/O Linc GND to the Sensor Input.

Posted

Defiantly sounds like an issue with whatever is connected to your sensor input

 

Are you sure you're connected to the Ground and Senor inputs

 

What are you using to trigger the sensor input, a switch, or?

Posted

You are correct about the signal levels being the problem. It didn't occur to me that the logic that drives the white and green LEDs is separate from the logic that drives the Insteon transmissions but it must be. I have changed the wiring and it now works. Thank you.

Posted

When I bought the 2450 I hadn't realized it wasn't dual band and I've had some comm issues with the 2450 so for redundancy I added a 2843-222 Open/Close Sensor module in parallel. The 2843-222 worked fine (but it operates off of three volts - derived from a battery). Both were being driven from an open drain output of a PIC micro. I'll simply drive them from separate outputs now. I didn't actually look at the voltages but when I disconnected the 2843-222 the 2450 began to work properly. I might as well add a regulator to my board anyway and drive the 2843 from the 2450 power supply so I don't have to worry about replacing the battery. It would have been much simpler if there was a dual band 2450 but apparently there is not yet.

Posted

salex319

 

Before investing time working on the power for the wireless On/Off module, I don't think that module is doing anything to help the I/O Linc. The I/O Linc is powerline only. The wireless on/off module is RF only. Messages to/from the I/O Linc travel over the powerline. Messages from the wireless on/off module travel over RF to some Dual Band device. Messages sent to the I/O Linc will be transmitted over RF by some Dual Band device but have no way of getting from the RF only wireless on/off module to the powerline and the I/O Linc. The reverse, powerline messages from the I/O Linc will not be seen by the wireless on/off module so it will not be sending messages from the I/O Linc over RF.

Posted

I'm not trying to communicate between these devices. I'm only interested in making sure a message gets through from one of these two devices to the PLM. Since I've always had trouble with X-10 / powerline signaling (the reason I switched to Insteon) I don't trust the 2450 by itself. So I'm adding the 2843 to essentially make the combination of the two devices dual-band. I'm pretty confident that one of the two signals will get to the PLM.

Posted

Some added information.

I have done some tests on a 2450 I/OLinc and the Sensor Input has the Green LED on it.

You can pull the Sensor Level down enough to allow the LED to glow but not below around 1.0 volts to trigger the Insteon Signal to be sent. My tests showed approximately 800 Ohms from sensor Input to Ground would trigger it.

 

It also has its own voltage source on the Sensor Input to Ground so be careful that a voltage is not applied to it of if you do. Five volts or less maybe OK.

Posted

OK. Here's some more clarification. Turns out that even though the 2450 is a powerline only device and the 2843 is an RF only device if they are both triggered at the same time the 2450 signal is lost. When I wired separate drivers to each but triggered them about the same time the 2450 still failed. So the final solution was to delay the trigger signal by a few seconds to one of the devices.

Guest
This topic is now closed to further replies.

×
×
  • Create New...