Posted: June 11 2004 at 13:27 | IP Logged

I am trying to get a light to go to 85% on a palm pad triger on G4on and then go to match the level of another light with a trigger on G4OFF.

I' using SendKeys in Triggers:

G4ON      ph_x10btn("G",4,100,85)

G4OFF     ph_x10btn("G",4,100,[X10LEVELG6])

When [X10LEVELG6] = 0, or if I substitute 0 in the function, X10status reports dimmed to 3 but the light looks more like it is at 20 - 30 %.

I pulled the plug on my "DIM eating TVs" and got the same result.

BTW, I am running this discussion forum from within power home and 0 from function results are showing up in the text.

Like this 0000 - that was due to G4ON, G4OFF, G4ON, G4OFF - How cool is that.

Posted: June 11 2004 at 13:58 | IP Logged

Deano,

The first thing is you probably want to change from using "Sendkeys" to "Formula" in your trigger.  That is why you are getting the 0's showing up in your post.  A "Sendkeys" is a formula that is evaluated and the result is then sent as keystrokes to the application with focus.  Sometimes, this is a desired result, but in this case, I don't think thats what you want.

Reading your post and seeing what you are doing...I might have mislead you in my earlier post concerning the dimpercent.  While this value in no way affects how the controller actually sends dim values, it will play a part in the number of "dim" commands sent from PowerHome to the controller.  When you specify a level to PowerHome, it checks the dimpercent value and calculates how many dim commands need to be sent for that particular controller to achieve the desired level.  I guess what Im trying to clear up is that each individual controller will dim a certain percentage when a single "dim" command is issued to it (not able to be controlled by PowerHome).  This value varies per controller which is why we have the dimpercent parameter.  PowerHome does use this value however to determine how many "dim" commands need to be sent to the controller to achieve a certain level.

In any event, it sounds as if the dimpercent needs to be adjusted in your case.  What controller are you using?  If you are using a CM11A, then you have probably found that there is no dimpercent for this controller.  The CM11A dim command allows you to specifiy a value from 1 to 21 meaning that there are only 21 increments available.  This equates out to a dimpercent of roughly 4.76%.  Since the CM11A is unique in its handling of dim commands, this value is hardcoded.  Most other controllers have a single dim command that dims a certain percentage and to achieve a desired level you just have to repeat the single dim command X number of times.

Another question...using the same controller, do all your lights seem to respond the same amount?  Or do some lights seem to get dimmer than others?

Dave.

Posted: June 12 2004 at 09:05 | IP Logged

Dave,

I am using a CM11A and although it is difficult to analyze due to different ambient conditions and fixture design, I think that they all dim about the same.

Some more testing with a different lamp/lamp module.

ph_x10btn("F",14,100,18/21*100)  results in 86

ph_x10btn("F",14,100,0) results in 5

Could this be the classic off by one error?

G4 does appear to be slightly brighter at 5% than F14

Tried ph_x10btn("F",14,100,-5) but it won't execute so I can't do linear interpolation to fix problem.

Posted: June 12 2004 at 09:55 | IP Logged

Dean,

A couple more tests to perform to rule out problems with the ph_x10btn function:

ph_x10(1,"F",14,0) + ph_x10(1,"F",104,95)

The above test should be run after the light is first turned on before any other dims are sent.  This should dim the light down to 5% and PowerHome should reflect close to same for the status.

Also, run the ph_x10btn("F",14,100,5) function.  Again, try this immediately after the light is first turned on with no dims sent to it.  This should also dim the light to about 5% and the level should appear to be the same as the test above.

The absolute dimming feature of the ph_x10btn function is reliant upon the correct current status.  How it works is that the current status (as recorded by PowerHome) is checked.  The status that you wish to go to is then subtracted from this status.  If the result is positive, DIM commands will be sent.  PowerHome calculates the number of dims by dividing the difference by the dimpercent.  If the result is negative, BRIGHT commands will be sent.  The ABS of the difference is then divided by the dimpercent and that many bright commands are sent.

As you can see, with each calculation, there will be a rounding error.  Also, over time due to occasional "eaten" commands and the not completely accurate calculations, the actual status and the PowerHome status will drift apart resulting in error.  The only way to really bring it back into alignment is to occasionally turn the light off (Actual status and PowerHome status are 0%).  This was my attempt at achieving something similar to the absolute dimming the more expensive modules have.

Let me know how the above tests go and I'll run some down here as well.  I won't be able to use a CM11A but might be able to uncover a way to minimize errors while using my Powerlinc.  It may turn out that I have to provide some kind of "fudge" factor for the CM11A. 

Also, as you've found out, the ph_x10btn function only accepts values from 0 to 100 for absolute dimming.  You could followup a ph_x10btn("F",14,100,0) command (to dim a light to 0) with a ph_x10(1,"F",104,20) command to dim an extra 20%.  This will also have the effect of "synchronizing" PowerHome to actual since the light should be fully dimmed (you could change the 20 to 100 to make absolutely sure ) and PowerHome will reflect a status of 0.

Dave.

Posted: June 12 2004 at 10:11 | IP Logged

Don,

Since my last post and a little bit of initial testing, one of the things Im going to add for the next version is that when doing absolute dimming or brightening in the ph_x10btn function is to add some extra dim/bright commands when the level value is either 0 or 100.  This should have the effect of "synchronizing" if the light isn't vastly off.

Dave.