Open/Close Module to Control TV Lift

[SawStop]

I'm trying to use an 2444-222 Open/Close Micro Module to control a pair of relays to operate a TV Lift. This is very similar to using one to control blinds. I've seen the threads regarding the inability to use this device to position blinds at a mid-level, say 50%, via a dimmer setting, which fortunately I don't need to do. In my application, I don't mind (and would actually prefer) that the operator has to hold a button while the lift moves rather than having it just automatically go to one extreme or the other upon button push, which I think I could do by adjusting the timeout to match the travel time (with limit switches at the ends to automatically stop the motor). I've currently got the up/down or L1/L2 outputs wired to the coils of two relays, the contacts of which operate the motor in either forward or reverse depending on whether power comes from the L1 or L2 output. 

Currently, I've got it sort of operating off a single button on a 6 button switch. With the timeouts set to 0.1 seconds, pressing the button and releasing immediately 'bumps' the lift up or down and then pressing again bumps it the other way, rather like turning off or on a light by sequential pushes of the button. If I press and hold the button, the lift will continue to move as long as I hold the button, but then the switch goes into program mode because I've held the button so long. And, if I release the button midway, I have to press once to bump the opposite direction and then press and hold to complete the movement. Ideally, I'd like to have an up button and a down button on the switch, but I can't see any way to signal the Open/Close module that I want it to turn on just the "Up" output when I push a button, not toggle back and forth. And, then I'd like to be able to hold the button long enough to complete the lift cycle without entering the program mode. Is this possible with the Open/Close module - ideally via a scene? 

Thanks in advance for any suggestions.

[kclenden]

1 hour ago, SawStop said:

With the timeouts set to 0.1 seconds, pressing the button and releasing immediately 'bumps' the lift up or down and then pressing again bumps it the other way, rather like turning off or on a light by sequential pushes of the button.

Sounds like the button is in "Toggle" mode.  If you change it to "Always On", using the "Buttons Toggle Mode", perhaps it will work as desired.  Then set the button you want to use to make it go down to "Always Off".

1 hour ago, SawStop said:

And, then I'd like to be able to hold the button long enough to complete the lift cycle without entering the program mode.

The KeypadLinc manual references the ability to use software to lockout local programming, but I don't see anything in the Admin Console that allows you to do this.  Maybe another forum member knows if the ISY has a way to do this.

[SawStop]

You are spot on with both suggestions. The options button for the keypad on the bottom of the Admin Console page for the keypad has a program lock check box that worked to lock out the local program behavior. Now working exactly as I'd hoped. Thank you!

 

[kclenden]

5 hours ago, SawStop said:

The options button for the keypad on the bottom of the Admin Console page for the keypad has a program lock check box

Well that is interesting.  I don't see an "Options" button on the bottom of the page for any of my keypads.  I'm using version 5.0.15A of the Admin Console.  What version are you using?  Here are the buttons that I see:

[larryllix]

Rather odd. Without any options how would all the settings be available?
Here is mine with ISY v5.0.16C



...and with every button a further page containing options

[larryllix]

I don't think this non-alternate action can be done via a scene. IIRC scenes can only have one operator. It would be simple with a program or two using @kclendens button options, or I would just program all buttons to "always On' and detect both buttons in that style.

[kclenden]

11 hours ago, larryllix said:

Here is mine with ISY v5.0.16C

Thanks.  That is odd.  I was expecting to see an "Options" button because I faintly remember using it under V4.

11 hours ago, larryllix said:

...and with every button a further page containing options

I don't have an "Options" button on any of the button pages either.

I just checked and my Firmware and UI versions match.  I haven't upgraded to V5.0.16 because of some of the bug reports, but I guess I'll do it to see if it gives me the "Options" button.

[larryllix]

43 minutes ago, kclenden said:

Thanks.  That is odd.  I was expecting to see an "Options" button because I faintly remember using it under V4.

I don't have an "Options" button on any of the button pages either.

I just checked and my Firmware and UI versions match.  I haven't upgraded to V5.0.16 because of some of the bug reports, but I guess I'll do it to see if it gives me the "Options" button.

I felt lots of "negs" here about .16a and .16b here, but I think v5.0.16c should be pretty clean. OTOH, I have no Zwave and not much with Insteon has been happening since the ISY engine changed about v5.0.3-4.

[kclenden]

31 minutes ago, larryllix said:

I felt lots of "negs" here about .16a and .16b here, but I think v5.0.16c should be pretty clean. OTOH, I have no Zwave and not much with Insteon has been happening since the ISY engine changed about v5.0.3-4.

I don't have any Zwave either, but I thought some of the v16 reports were about Insteon open/close sensor of which I have a couple.

[larryllix]

23 minutes ago, kclenden said:

I don't have any Zwave either, but I thought some of the v16 reports were about Insteon open/close sensor of which I have a couple.

Yeah, I guess I did hear some of those but have none and I avoided 16b. Actually I downgraded to .15 after having problems with polyglot I couldn't resolve.