Author |
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: August 23 2022 at 15:19 | IP Logged
|
|
|
I have a set of Velux skylight shades which can be opened and closed with a remote. I have a spare remote which I soldered wires to the remote's open/close microswitches and used a PH timed event to trigger the microswitches through two of the ELK M1 outputs via a relay. It stopped working after many years and I think it happened after upgrading from 2.15 to 2.2. The timed event basically triggers the relay to close for 0.25 seconds and then returns to the normally open state. The PH command (ph_setotherdigitalout) executes and returns a syntax error. The relays are not activating and the outputs don't appear to be activating. Any idea what might be occurring?
|
Back to Top |
|
|
smarty Super User
Joined: May 21 2006 Location: United States
Online Status: Offline Posts: 728
|
Posted: August 24 2022 at 13:17 | IP Logged
|
|
|
trying to help....
I use the ph_setotherdigitalout command with my El kM1 to open and close my front driveway gate. It works fine for me. I am on PH
version 2.2 beta 3-5.
In looking over your command versus my formula, I notice that I DO NOT include any spaces after each comma. For example, I have:
ph_setotherdigitalout("ELK",1,0,16,0)
where as you would have:
ph_setotherdigitalout("ELK", 1, 0, 16, 0).
I have no idea if the spaces might matter or not; it's just something I noticed.
Also, you might want to make sure the digital outputs actually work by connecting your panel to the Elk RP2 programming software supplied
by Elk. That software will let you manually toggle/test your Elk outputs.
Also, just for another idea, you might want to try to lengthen your wait time from 0.25sto something longer...just to see if there is a
difference (or it works)...
Hope you find the issue....
Edited by smarty - August 24 2022 at 13:30
__________________ Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: August 28 2022 at 00:43 | IP Logged
|
|
|
Thanks and sorry for the slow response. I didn’t get any email
notification and figured my query got lost in the PH-Elk void. The spaces
don’t seem to make any difference…I get the syntax error either way. It
used to work and I didn’t change anything except the version of PH. I did
try to trigger the relays with the Elk RP software and had no trouble. In the
meantime I am triggering the relays with timed events in the Elk module and
have deactivated the PH timed event macros. I don’t think the short
duration between the on and off commands has anything to do with it since
it worked perfectly for several years and the logs record everything
successfully (I had such a short pause because I didn’t want to “hold” the
relays open since they were soldered to the micro switch pads on the
window remotes and I wasn’t sure what a longer press would signal from
the RF remote to the window, but I’ll try changing the delay in the morning
just to rule it out).
Edited by Handman - September 07 2022 at 20:36
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: September 15 2022 at 17:34 | IP Logged
|
|
|
Still not sure why your ph_setotherdigitalout still works with ELK and PH 2.2, but after reviewing Dave's comments in the help files for version 2.2, it seems like he has deprecated several functions in favor of refined versions of other functions like ph_setdigitalout.
So, I was able to command the outputs on the Elk to operate using ph_setdigitalout("OUTPUT NAME",0/1) where OUTPUT NAME is defined in the PH Explorer>Devices>Digital I/O.
In this case the OUTPUT NAME is defined as the ELK controller/unit 1/ point 16. That triggers the Elk to open or close output 16 triggering my intended relay.
|
Back to Top |
|
|