| Author |
|
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 21 2007 at 20:10 | IP Logged
|
|
|
I'm having problems with the X-10 Adim function. In the X-10 status screen, On and Off buttons are perfectly working but I'm not able to find what characters should I write in Adim. Could someone help me ?
Thanks
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: January 21 2007 at 20:48 | IP Logged
|
|
|
It should be a numerical value. Hit the button, not Enter.
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 21 2007 at 21:11 | IP Logged
|
|
|
I imagine there's something wrong elsewhere because I've tried 85 thinking that I should have the light set to 85 % but each time I've tried, the Adim button stays " pressed " and I'm no more able to do anything. I have to close Powerhome and even reset my 2814u.
I know my x10 modules do not have extended command and I picked the right modules from you list. Do I need to define something for dimming ?
That's a really good support, thank you very much !
Johnny
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 22 2007 at 15:37 | IP Logged
|
|
|
Johnny,
Welcome to PowerHome!
As long as the correct modules have been chosen for the X10 Type, then no other configuration should be necessary.
The ADIM function should send commands appropriate for your modules based upon the type. If the defined module supports extended commands, an extended dim is sent. If extended commands are not supported, then preset dim is checked for and sent if supported. Last case would be to look at the current level (as stored within PowerHome) and calculate the appropriate number of standard dims or brights to achieve the approximate level.
I wasnt familiar with a 2814U so had to look it up. It appears to the ICON version of the USB Insteon PLC (which should work fine though). The modules that you are trying to control are defined within the X10 Devices or the Insteon devices? Either way, the SDM log should show what is being sent. Could you copy and paste the snippet of SDM log that is showing what PowerHome is trying to send? It might help me pinpoint what needs to be done.
Thanks,
Dave.
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 23 2007 at 21:40 | IP Logged
|
|
|
Dave,
I sent you a PM but find here what you asked for.
- Using LM465 that we find in the X10 list.
- Using RSW17 equivalent to the WS467 in the list. This unit is used as master only. Both types of modules do not use extended x10 commands.
What I suspect is that for dimming Powerhome sends only the first part of the command ( as C8 ) and blocks ... I can see this very well in the Powerhome log where I can see only one blue line when I press Adim ( Insteon DM Powerlinc1 transmission of House code C, Unit code 8 ) and nothing else. Generally there are always 2 blue lines ( x10 commands ) : one for the house and unit code and the other for the command.
I did my best to identify what I was doing. Going backward is probably the best way for you to understand ... You should see
regular macros for house's lights
" Beginning of the test "
C8 On
C8 OFF
I entered 60, then Adim
Everything was blocked.
End of log
Here's the log :
ui:!sendx10raw=0,34
PLC:sendx10raw=True
uifinished:!sendx10raw=0,34
ui:!sendx10raw=1,35
PLC:sendx10raw=True
uifinished:!sendx10raw=1,35
ui:!sendx10raw=0,34
PLC:sendx10raw=True
uifinished:!sendx10raw=0,34
ui:!sendx10raw=1,35
PLC:sendx10raw=True
uifinished:!sendx10raw=1,35
ui:!sendx10raw=0,33
PLC:sendx10raw=True
uifinished:!sendx10raw=0,33
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,38
PLC:sendx10raw=True
uifinished:!sendx10raw=0,38
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,46
PLC:sendx10raw=True
uifinished:!sendx10raw=0,46
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,34
PLC:sendx10raw=True
uifinished:!sendx10raw=0,34
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,42
PLC:sendx10raw=True
uifinished:!sendx10raw=0,42
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,37
PLC:sendx10raw=True
uifinished:!sendx10raw=0,37
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,39
PLC:sendx10raw=True
uifinished:!sendx10raw=0,39
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,45
PLC:sendx10raw=True
uifinished:!sendx10raw=0,45
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,45
PLC:sendx10raw=True
uifinished:!sendx10raw=0,45
I had to reinitialize Powerhome to have any on and off commands working again.
In device status, I pressed :
C8 On
C8 Off and everything worked fine.
Here's the new log from SDM.
bad:03 len=561
bad:03 len=561
bad:03 len=561
bad:03 len=561
bad:03 len=561
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=USB4
connected=True
firmware=2.13
id=05.0A.A6
devicetype=InsteonPLC-USB
lastErrorMsg=#0:
endlist
uifinished:getplcstatus
ui:getlinks
uifinished:getlinks
ProgressStart
ProgressMax=1024
Progress=0%,0,1024
Progress=12%,128,1024
Progress=25%,256,1024
Progress=37%,384,1024
Progress=50%,512,1024
Progress=62%,640,1024
Progress=75%,768,1024
Progress=87%,896,1024
ProgressEnd=True
PLC:getlinks=beginlist
id=05.0A.A6,mode=sla,addr=FD60,laddr=0000,g=1,cmds=00 00,d=00
endlist
downloadTimer started
timerActivate enabled
bad:03 len=561
UI:ConnectedAndReady
SDM:DM=active,1.01.122.278,2007-01-23 20:05:55,responded,02.2D.06,0.5
starttime=00:21
ui:!sendx10raw=0,45
PLC:sendx10raw=True
uifinished:!sendx10raw=0,45
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,45
PLC:sendx10raw=True
uifinished:!sendx10raw=0,45
ui:!sendx10raw=1,35
PLC:sendx10raw=True
uifinished:!sendx10raw=1,35
Hope this can help you
Jean-Guy
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 23 2007 at 23:50 | IP Logged
|
|
|
Jean-Guy,
I got the PM, but have not had a chance to analyze in depth yet. I'll be looking over in detail the PM post as well as the post above tomorrow (Wednesday) and try to determine what is going on and get back with you then.
Thanks,
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 24 2007 at 21:07 | IP Logged
|
|
|
Jean-Guy,
Ok, Ive been through all of the information that you've sent and created test scenarios here. Unfortunately, everything has worked so far for me. I am able to get it to "appear" hung by changing the X10 device to support extended commands. In this case, the ADIM button stays depressed and nothing happens (the Insteon DM is incapable of sending extended commands), but a simple press of ON or OFF and everything is working fine so I know this is not your problem.
At this point, the best thing to do would be to send me a copy of your actual PowerHome database (pwrhome.db default located in c:\program files\powerhome\database). This way I can setup your exact system and see if I can reproduce the problem.
Thanks,
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 24 2007 at 22:56 | IP Logged
|
|
|
Ok,
Received your database and loaded it up. First thing I noticed is that the X10 Type for WS-467 is checked as supporting preset dim commands. This would cause the ADIM command to send preset dim commands rather than looping and sending multiple dim commands. However, I don't think this is the problem.
Anyway, I continued to load and reviewed the logs and the details you posted in your PM. I could clearly see where the X10 commands stopped being sent. PowerHome was not hung, but the Insteon DM controller definately was. In my testing with your database however, I had no problems and was able to ADIM all of your listed devices. This is now pointing to something peculiar in your hardware setup. From the code tracing Ive done, it would appear to be in either your PLC or your particular hardware/OS and internal PowerHome delay commands. I'd like to run a couple more tests to try and pinpoint this.
First, open the PowerHome multi-editor and make sure that you are in PH Formula mode (Shift-F6). Type the following command and run it:
ph_x10("POWERLINC1","C",3,0) + ph_x10("POWERLINC1","C",104,3)
We should see the following activity in the SDM log and PowerHome should not hang:
ui:!sendx10raw=0,34
PLC:sendx10raw=True
uifinished:!sendx10raw=0,34
ui:!sendx10raw=1,36
PLC:sendx10raw=True
uifinished:!sendx10raw=1,36
Next, type the following command and run it:
ph_x10("POWERLINC1","C",3,0) + ph_x10("POWERLINC1","C",104,50)
We should see the same SDM log activity except that the sendx10raw=1,36 should be repeated about 6 times. If the first command works and the second command hangs, then there is some problem in the way that your system is implementing the internal PowerHome delay command.
Let me know your results so I can continue troubleshooting.
Thanks,
Dave.
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 25 2007 at 21:02 | IP Logged
|
|
|
Dave,
No idea if I have good or bad news ... First thing the preset dim for the WS-467 was a test just in case ... and I forgot to remove it. That changed nothing.
I ran the first command you indicated in your mail. I had only the first 3 lines and PLC hung. I have read that some people had problems with the SDM 278 and decided to follow your post and changed to SDM 308. I think we made progress because now if I do an Adim command, it doesn't work but the plc doesn't hang anymore.
I tried your command again and same result, only the first 3 lines appeared in the log and PLC hung. With the insteon explorer I cleared the PLC ( PLC cleared ) and downloaded the core application. I got an interesting message
ui=dl=timecoreapp12
uifinished:dl=timecoreapp12
PLC:dl=e005:PARM1-File missing
and PLC hung ...
I reinitialized ph and without doing anything else I can do On and Off commands ...
I imagine something may be missing somewhere. By the way, as you were talking of hardware/os, this pc is not an new one. It a PIII 666 MHZ running Windows 2000 server with every updates done. Only Powerhome is running on the pc.
I hope this can help you.
Jean-Guy
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 26 2007 at 17:29 | IP Logged
|
|
|
Jean-Guy,
Well, based upon your testing, it doesnt appear to be a problem with the Delay command which would point to something peculiar in the OS/Hardware. Right now, it appears to be more specific to your particular PLC.
The fact that we cant download the CoreApp is going to cause us problems. Not sure if you copied and pasted or typed the info from the log but it should be timercoreapp12 (with the 'r' in timer). I noticed that what you've got in your message is timecoreapp12 which definately will not work.
I would open the SDM and give focus to the log window. Type D M and a command prompt box should appear within the DM. In this command prompt, type dl=timercoreapp12 and press enter. See if you can get success on downloading the Core app. You can do this by manually launching the SDM without even having PowerHome running.
Once the timercoreapp download is successful, launch PowerHome and go to the Setup tab in the Insteon Explorer. Select the "Clear PLC" button again and then select the "ADD ID's to PLC" button. You won't get any reliable communications unless you're able to get these steps done.
Once this is done, again take PowerHome out of the equation by launching the SDM by itself. In the command prompt window, type: !sendx10raw=0,34 and press enter. After that command is finished, try typing: !sendx10raw=1,36 and press enter again. This is a Dim command. See if the PLC hangs or if it completes successfully.
Dave.
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 26 2007 at 20:27 | IP Logged
|
|
|
Dave,
The good news is that we are making progress ..
Yes, I typed the log and I did a typo ( missing r )
I did the steps you mentionned. I did the command dl=timercoreapp12 amd got the same error than yesterday. Here is the log :
downloadTimer started
timerActivate enabled
SDM:DM=active,1.01.138.308,2007-01-26 19:55:02,responded,03.02.2D,4.8,xdevices=True
starttime=00:11
ui:dl=timercoreapp12
PLC:dl=E005:PARM1-FILE MISSING
first comment : my My PLC's address is 05.0A.A6. I remember that in Powerhome I see 2 PLCs: one is powerlinc1 with the correct address and a second line with Powlerlinc2 and a different address. Is it correct ? The log above doesn't include the Powerlinc1 address, is it correct ? All my x-10 devices are set with powerlinc1.
Now let me continue the story. Even if I was not able to download Timercoreapp I tried with some sendx10 commands :
I did sendx10=c10 : sendx10=con ( light went on ) ; sendx10=coff ( light went off ) ; sendx10=con ( light went on ) ; sendx10=cdim a few times and light dimmed ! sendx10=cbright few times light an it also worked. In fact I now know that from 100 % to 0 % it takes 12 dim commands.
Can we now say the PLC is good ? At least I now know that with sendx10 commands, I will be able to dim the lights, which is a very good news. Now, can we have it working as it should be ? Yesterday, I've seen that Windows 2000 server was not supporting HID, which is supposely required for the PLC. I validated on the Microsoft site and .. it is said that HID is not supported by Windows 2000 server ( windows 2003 server does support HID ). Could the problem come from there ?
I'm really sorry to give you so much trouble ! Thanks again for your patience !
Jean-Guy
03.02.2d
Edited by Johnny - January 26 2007 at 20:29
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 26 2007 at 20:46 | IP Logged
|
|
|
Dave,
I opened Powerhome and did a few more tests. I validated in insteon explorer and I saw 2 PLCs. One with the correct address and one with 02.2D.06. The one written on the PLC is 05.0A.A6. Here's the SDM log. Not the good PLC's id and not the good firmware. Isn't strange ???
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=USB4
connected=True
firmware=0.2
id=02.2D.06
devicetype=InsteonPLC-USB
lastErrorMsg=#0:
endlist
uifinished:getplcstatus
ui:getlinks
uifinished:getlinks
ProgressStart
ProgressMax=1024
Progress=0%,0,1024
Progress=12%,128,1024
Progress=25%,256,1024
Progress=37%,384,1024
Progress=50%,512,1024
Progress=62%,640,1024
Progress=75%,768,1024
Progress=87%,896,1024
ProgressEnd=True
PLC:getlinks=beginlist
endlist
downloadTimer started
timerActivate enabled
UI:ConnectedAndReady
SDM:DM=active,1.01.138.308,2007-01-26 20:31:52,responded,05.0A.A6,2.13,xdevices=True
starttime=00:09
ui:!sendx10raw=0,47
PLC:sendx10raw=True
uifinished:!sendx10raw=0,47
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,47
PLC:sendx10raw=True
uifinished:!sendx10raw=0,47
ui:!sendx10raw=1,35
PLC:sendx10raw=True
uifinished:!sendx10raw=1,35
You can imagine I'm not a specialist with ph to execute these x10 manual commands ( sendx10=c10,cdim ) to dim my lights. How can I send these sendx10 commands ? Formulas ??? I've seen that ph_functions can be used in timed events, do you have a ph_ function to send basic x10 command ? A few hints would be appreciated ...
Thanks again Jean-Guy
Edited by Johnny - January 26 2007 at 23:04
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 26 2007 at 23:30 | IP Logged
|
|
|
Jean-Guy,
Great testing. Unfortunately, it's all pointing to a problem either with the PLC itself or your machine. According to this line:
SDM:DM=active,1.01.138.308,2007-01-26 19:55:02,responded,03.02.2D,4.8,xdevices=True
Your PLC ID is 03.02.2D and your fimrware is 4.8...neither of which is correct. At this point, we cant say that your PLC is ok and good to go. Your further SDM log finally shows the proper address and firmware, but only after incorrectly reporting it during the GETPLCSTATUS command. Also, since you cant download the TimerCoreApp, PowerHome will not work correctly.
All of this is pointing to either the PLC itself having a problem or possibly as you suspect a problem with the USB and HID drivers.
Even though the sendx10 command appeared to work from within the DM, PowerHome only uses the sendx10raw command (a greater degree of control is available). The basic X10 function that PowerHome has available is the ph_x10 function that I had you test with previously. This is ultimately translated into sendx10raw commands to the DM.
At this point, I would probably contact SmartHome and see what they suggest about getting the SDM to work with your PLC. If you've got another PC to test with (hopefully with a different OS), then I would try just installing the SDM and see if the problem moves with the PLC. If it does, I would probably have SmartHome swap it out. If the problem is only on the 2000 Server machine, it may be necessary to upgrade the OS in order for the PLC and SDM to work properly.
Dave.
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 27 2007 at 16:53 | IP Logged
|
|
|
Dave,
I continued my testing work. I moved my controller to a PC operating with Windows 2000 pro. I had the same problems, Powerlinc appeared 3 times. log was saying wrong PLC's ID, wrong firmware, etc... Only bad news. I decided to uninstall SDM and start with a fresh install ( v 308 ), to the suggested directory ( program files\common files\smarthome ). I ran SDM from there and had the right PLC'S ID and the right firmware. I forgot to move the fresh SDM to the powerhome directory and even didn't close this running SDM and launched powerhome. I had a message ( I don't remember exactly the message ) but I understood SDM was already running. I closed the pop up window and a second SDM's instance opened ( I imagine Powerhome was launching it's own because I didn't rename the dir in powerhome directory ). I decided to close the last one opened by ph and validated with Insteon explorer. It was working perfectly, but I had 3 Powerlincs, with 3 addresses ( always the same 3 ones ). I validated if I was able to run the tests you gave me ... it ran ! I modified my macros to add the dim command and tested the lights and it dimmed ... So the wife is now happy !
I will for sure continue the tests, revalidate with the original PC ( redoing on purpose the same mistake ) but I think that when I move the fresh installed SDM in the powerhome directory, something wrong happens and that could explain the missing file reported when trying to load the timercoreapp.
I will keep you informed, because, if my PC stops with a power failure, ph will never correctly start by itself. I have to find a way to have it correctly working. I have the newest ph version ( 1.03.4.9). If you have something in mind I could do wrongly, some tests I could do, don't hesitate ...
Thanks Jean-Guy
Updated : now that all my commands to light and dim the lgihts worked, I checked the adim command in the device status. It's perfectly working but I can't have the light dimmed below around 50 % even if I indicate 1 %. Any idea ? I validated and with dim commands in Macros I can dim the light to 0 %. So I'm OK.
Here's the log I have with 1 % adim. If I go in ph explorer in - setup - controllers - settings - x-10 dim percent set to 10 so, as I get 4 dim commands in the log, 4*10, I should have - 40 % . Light is looking like it's at 60 %, but it should be almost closed with 1 % ( my test light is now C10 ). Adim may not use this 10 % level set in Setup.
ui:!sendx10raw=0,47
PLC:sendx10raw=True
uifinished:!sendx10raw=0,47
ui:!sendx10raw=1,34
PLC:sendx10raw=True
uifinished:!sendx10raw=1,34
ui:!sendx10raw=0,47
PLC:sendx10raw=True
uifinished:!sendx10raw=0,47
ui:!sendx10raw=1,36
PLC:sendx10raw=True
uifinished:!sendx10raw=1,36
ui:!sendx10raw=1,36
PLC:sendx10raw=True
uifinished:!sendx10raw=1,36
ui:!sendx10raw=1,36
PLC:sendx10raw=True
uifinished:!sendx10raw=1,36
ui:!sendx10raw=1,36
PLC:sendx10raw=True
uifinished:!sendx10raw=1,36
Edited by Johnny - January 27 2007 at 20:48
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: January 28 2007 at 13:12 | IP Logged
|
|
|
Dave,
I moved back my PLC to the previous Windows 2000 Server. I installed a fresh SDM ( v308) in the suggested directory. I ran SDM from this directory. Everything was fine with good PLC's address and with good firmware. I started Powerhome and I even didn't get the message " Could not activate HTTP port 9020 is the S.. D.. M .. already running ? Powerhome didn't start another SDM instance ( like the other PC was doing ). The SDM3.lok file is in the c:\program files\common files\smarthome\device manager. My powerhome is in c:\program files\powerhome and I still have a device manager in this directory. Only one instance of SDM is running and ... Powerhome looks perfect. I can use Adim from device status and the lights dim but ( like with the other PC ) never to the right value if it's below 60%. In using the dim command in macros I can bring the light from 100% to 0% with 13 dim commands. I changed the setting in powerhome explorer ; setup ; controllers ; settings ; x-10 dim set to 20 ( with the previous test it was set at 10). I did 4 Adim test : 80 % -- light looked good ; 60 % light looked good ; 40 % light didn't change ; 20 % light didn't change ; 0 % light didn't change. Light looks like it stops dimming at 50-60 %. Status in device status is indicating 0.
I imagine you may understand few things ...
Jean-Guy
Edited by Johnny - January 28 2007 at 13:19
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 29 2007 at 19:13 | IP Logged
|
|
|
Jean-Guy,
Glad to hear that progress is being made. PowerHome should still work even if you didnt put the SDM under the PowerHome directory structure. You should be able to put it there if you like (you would have to rename or remove the existing one), the key is that before launching PowerHome, you MUST manually launch the SDM from it's new moved location (this updates the registry properly). After than, PowerHome should launch it from the correct location (even if you leave it in the default location, because you've already manually launched it from the location, PowerHome should still work). The problem though, is that since you've installed a fresh SDM, you must copy the timercoreapp12.slb file fromt the PowerHome SDM directory to whatever SDM directory that you're using. This should fix the timercoreapp12 cant be found problem. You also must get the download to the PLC to happen or PowerHome will not operate 100% correctly.
Concerning the dim settings, if full bright to full dim takes about 13 dim steps, then 100 / 13 = 7.69 and this is the value that should be used for the X10 Dim percent in the Settings screen. If you use an abnormally high value such as 20, then the ADIM command will only Dim about 5 times before PowerHome thinks the dim setting is 0 and then won't dim anymore.
Let me know,
Dave.
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: February 03 2007 at 17:50 | IP Logged
|
|
|
Thanks again Dave,
I didn't have the timercoreapp12.slb at the right place ... I did everything as you explained. I cleared the PLC and downloaded the core app and I got no error. I tested again the Adim function with 2 parameters. First, I set x-10 Dim percent to 8. Here's what I got :
Adim Status info How light looked like
92 84 &n bsp; &n bsp; like 90 maybe 92 % ??
82 68 &n bsp; &n bsp; like 80 % maybe 82 % ??
60 52 &n bsp; &n bsp; like 70 %
40 36 &n bsp; &n bsp; like 60 %
24 20 &n bsp; &n bsp; like 50 %
16 4 &nb sp; &nb sp; like 50 %
I did the test again with x-10 parameter set to 4.
Adim Status info How light looked like
92 &nbs p;84 &n bsp; maybe 92 % as it should be
82 &nbs p;68 &n bsp; like 80%
60 &nbs p;52 &n bsp; like 70 %
40 &nbs p;36 &n bsp; like 60 %
24 &nbs p;20 &n bsp; like 50 %
16 4 like 40 %
1 ; ; 0 like 40 %
0 ; ; 0 like 50 % (light became brighter)
The light's intensity went lower with x-10 dim set to 4 but never close to 0, I would say maybe 40 %. So the x-10 parameter changes something but didn't solve the problem.
When I start with light at 100 % and do 0 % adim command, the SDM log shows only 6 dim commands. That explains why I see the light around 50 % dimmed.
Jean-Guy
P.S. When my macros run, the dimmed value in Device Status indicates the right value. For each dim command sent, the status goes down 8 % as indicated in x-10 Percent dim.
Edited by Johnny - February 04 2007 at 20:23
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: February 07 2007 at 19:53 | IP Logged
|
|
|
Dave,
I'm still trying to have my system properly working and tonight I did a test and found the problem ... I have a Leviton repeater/amplifier. When I disconnect it, your adim properly work. I decided to do this test because I saw the error light flashing when I was sending X10 commands.
Are you aware that Leviton repeater/amplifier may cause problems ?
Thanks Jean-Guy
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: February 07 2007 at 22:18 | IP Logged
|
|
|
Jean-Guy,
Yep...I had a very similar problem with my Leviton repeater/amp. It was causing all kinds of problems with my CM11A in my old setup. So much so, that I finally had to abandon using the CM11A and instead went with a TW-523 connected to my Ocelot (go figure why a different controller would make a difference).
Ive heard of numerous people having a problem with bright/dim type commands and the Leviton repeater/amp. It's surprising too since the Leviton is very highly respected.
From what I remember, it seems to be a problem with the repeater portion of the unit. Bright/Dim commands are transmitted differently from other X10 commands (something about no delays between commands) and this seems to be what causes the problem.
The only thing that I can suggest would be to try removing the Leviton and using instead a passive phase coupler (at least that is what I was mainly using my Leviton for).
HTH,
Dave.
|
| Back to Top |
|
| |
Johnny
Newbie
Joined: January 21 2007
Online Status: Offline
Posts: 27
|
| Posted: February 09 2007 at 21:12 | IP Logged
|
|
|
Dave,
I need to keep the repeater because without it some X10 modules, which are too far away form the PLC controller do not work correctly ( X10 problem !). So, I tried understanding what were X10 modules waiting to receive and I imagine that's what repeater is also expecting.
For C1-On command, I understood that a basic X10 controller is sending C1, C1, COn, COn (every string is sent twice). Repeater's output is C1, COn. Repeater doesn't send strings twice. At this stage I can imagine why was Powerhome Adim command never dimming the light below 50 %, repeater was cutting half of the dimming commands. Adim could not work below 50 % and Dim commands were even not reliable.
For 3 dim commands, a basic X10 controller is sending C1, C1, Cdim, Cdim, Cdim, Cdim, Cdim, Cdim. For Dim commands, repeater really cares about timing (AC cycles between each dim string). Repeater should output C1, Cdim, Cdim, Cdim. Without the right timing, repeater sees errors not dimming commands and that was my problem with Dim commands.
As PLC is working with X10 raw commands to operate X10 modules, I imagine that PLC's output may not always have the correct timing for the repeater. Sometimes, it accepts dim commands, sometimes it doesn't ... To avoid this timing problem, I added delays between my dim commands and ... it works.
So, here's my typical macro : C1 ON ; 150 msec delay : C1 Dim ; 150 msec delay : C1 dim ; 150 Msec delay : C1 dim. May not be elegant, but at least, it's working.
Jean-Guy
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: X-10 status screen
