Announcement

Collapse
No announcement yet.

Help setting up Ninja control

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Help setting up Ninja control

    I've recently rebuilt my HS2 machine and dug the CM19a out of the cupboard after seeing support for the ninja unit in the Hauppauge Capture plug in.

    Could some one give me some pointers as to how to get the plugin to work with the ninja base as I have setup the devices (I believe) and the camera.asp page shows the cameras and indicates two of them are controlable but below the camera buttons it says "No camera movements are available".

    I must admit the CM19a plugin occasionally generates overflow errors in windows but most of the time the commands from the remote are received and shown within HS.

    Any pointers would be appreciated.

    Regards

    Dave

    #2
    I have the Ninja control working but not for the camera.asp. That takes a capture from the selected camera but doesn't give you a live feed to see the movement. The only way I have used the Ninja over the web is with the Streaming.ASP so you are able to watch the movement in semi real time. On my system it has about 10-15 seconds backlog for any movement to be seen on the client. It has a backlog of live image that must be sent before you see it at the display end. The same delay applies to changing cameras or stopping the streaming. Your time will probably vary depending on the connection speed and what speed you are sending out the video stream. I had mine set to 768KB and it was intermitent. Changed to 256KB and it worked much better although I ended up using 96KB so it would work for just about all callers every time.

    When you are setting up the configuration, be sure to press the SET button for each camera after you have the setting for each. They have to be set individually and those with Ninja support, meeds the Ninja box checked. When you see a display of the available cameras for streaming, you should have the ones with Ninja support display in BLUE.

    Make sure the cameras are within the range limit of the CM19a. The docs for the unit say 50'. That may be less if going through alot of building such as brick or other stuff. The transmitter is in the milliwatt range. A USB extention to get the CM19 in a better location would help.

    I have found that the remote actually has a better range than the CM19 but then my CM19 is currently in the basement and the remote is just inside a window that I can see the camera mount outside move.

    As a note, all my cameras, fixed and Ninja are outside with the closest one about 40' away from the house so I am really pushing the limits. I don't use any X10 cameras. All are bigger and heavier and use a home made enclosures. Because of the heavier load, I have to mount the Ninja base, upside down and reverse the remote and website actions.

    I am working on extending the range using an external antenna but still testing the modification to the unit.
    Last edited by Kyham; February 22, 2006, 07:04 PM.

    Comment


      #3
      Don,

      Thanks for the pointers as I had not thought of checking the streaming page. I have not set the streaming capability up yet as the corporate firewall I'm behind while at work is to restrictive so I can only use the web server on port 80.


      On a side note I did have a look at your set up last week and I'm very impressed. I'm tempted to go down the touchpad route as the general interface as it is less cluttered than the normal homeseer page. Alas I'm not a coder so my scripting skills are somewhat limited to modifying what already exists.

      Regards

      Dave

      Comment


        #4
        If you need any help with anything I have running on my system I will be glad to help.

        All of the plugins I use that were written by someone else, I have made the buttons and ASP pages available in my download section. Keep in mind that the changes were based on the Americana style. Don't know what would be needed to change for the other styles. I tried to make the changes with lots of comments but not always.

        As for scripting skills, that is what I did. Just play around making changes and seeing what the results were. Learned alot that way.

        Comment


          #5
          Before you can use the Ninja events to move the camera, you should verify that everything is working properly first. If you click on the dropdown (in the HomeSeer device panel) on a Ninja controlled camera, you should see all the predefined actions that are available with the cm19a plugin. Make sure that the ninja actually moves. Once that is owrking, you can now setup the Capture plugin to control those Ninja's. To get the camera movement events to show on the camera and stream pages, you must do two things (all described in the docs).

          First: create a group of HomeSeer events all with the same unique group name (I suguest Ninja). The Ninja events should be named that indicates what movment will occur. All the events can be created for one ninja device even if you have multiple ninja camera's.

          Second: on the General tab of the config form, enter the unique group name (Ninja). Presto - all the movement events will be available in the dropdown.

          Originally posted by Fatlab
          I've recently rebuilt my HS2 machine and dug the CM19a out of the cupboard after seeing support for the ninja unit in the Hauppauge Capture plug in.

          Could some one give me some pointers as to how to get the plugin to work with the ninja base as I have setup the devices (I believe) and the camera.asp page shows the cameras and indicates two of them are controlable but below the camera buttons it says "No camera movements are available".

          I must admit the CM19a plugin occasionally generates overflow errors in windows but most of the time the commands from the remote are received and shown within HS.

          Any pointers would be appreciated.

          Regards

          Dave
          Bryan
          (Config is in my profile)

          Comment


            #6
            Chaps,

            Thanks for the pointers, I now realise why I only had On/Off as actions for the cameras as I recreated the devices manually to remove the '&' from the device type to allow UltraView to work. I have now created the devices via the CM19 plugin and begun to create the events.

            One problem I have noticed is that the Hauppauge plugin is hanging then failing when switching the X10 camera power supplies. My CM12U (UK 230V) is working fine as I can switch appliance and lamp modules via the webpage and from remotes, so I have discounted a hardware problem.

            I have attached an extract from the log ald would appreciate if anyone has any suggestions.

            24/02/2006 10:47:04 - Hauppauge Captu - camera_switch - Found our camera that should be turned on C2 Kitchen Camera


            24/02/2006 10:47:36 - CM11A - Unable to send to CM11A/CM12U


            24/02/2006 10:47:36 - CaptureUtility - Switching to camera Kitchen Camera
            24/02/2006 10:47:36 - CaptureUtility - Entered ResetCameraConfig() for camera Kitchen Camera Not Streaming - Snap in progress False - Capture filter enabled True
            24/02/2006 10:47:36 - X10 Received - N11 (Sammys Den Motion Sensor) N On
            24/02/2006 10:47:36 - X10 Received - N11 (Sammys Den Motion Sensor) N On
            24/02/2006 10:47:37 - CaptureUtility - Brightness-0-10000-39-5000(5000) Contrast-0-10000-39-5000(5000) Hue-0-10000-39-5000(5000)
            24/02/2006 10:47:37 - CaptureUtility - Saturation-0-10000-39-5000(5000) Sharpness-0-10000-39-5000(5000) Gamma-0-10000-39-5000(5000)
            24/02/2006 10:47:37 - CaptureUtility - Video Source-1/Video Tuner Channel-27 V Size-320 x 240 Color Format-RGB24
            24/02/2006 10:47:37 - CaptureUtility - Autotuning channel 27
            24/02/2006 10:47:37 - CaptureUtility - TakePicture Hauppauge - Starting Initial Timer -100
            24/02/2006 10:47:37 - CaptureUtility - tmFormTimer - Timer fired for Form Timer - Interval was:100
            24/02/2006 10:47:37 - CaptureUtility - tmFormTimer - Connected to drivers
            24/02/2006 10:47:38 - CaptureUtility - Snapping Image set 7 for Kitchen Camera D:\homeseer\html\Capture\Kitchen Camera_2006-02-24_10-47-38.jpg
            24/02/2006 10:47:38 - Process info - hspi_Hauppauge_Capture.exe - 6044 | ImageUtility.exe - 6528 | CaptureUtility.exe - 26644 |
            24/02/2006 10:47:38 - CaptureUtility - Purging for D:\homeseer\html\Capture\Kitchen Camera_*.jpg for 50
            24/02/2006 10:47:38 - CaptureUtility - FinishUpWhenDone from (1) - Streaming(False) Capture (True) AVI Capturing(True) Still Capturing(False) Capture filter enabled(True) Preview(True)
            As you can see the system hangs for up to a minute before it times out with the error. I have reset the unit, shutdown the PC, changed the batteries, etc. As I said the CM12U is working fine as shown in this log extract.

            24/02/2006 10:37:00 - Startup - Initializing Plug-Ins
            24/02/2006 10:37:00 - Info - Initializing X10 Plug-in: X10 CM11A/CM12U On COM Port 9
            24/02/2006 10:37:00 - Info - Initializing Plug-in: X10 CM11A/CM12U
            24/02/2006 10:37:00 - Info - Initializing CM11A/12U on COM port 9
            24/02/2006 10:37:00 - Info - Done initializing X10 interface X10 CM11A/CM12U
            Anyone got any suggestions?

            Regards

            Dave

            Comment


              #7
              I have seen the "unable to send to cm11a" problem intermittently but that error comes from HomeSeer however the plugin doesn't hang on my system. Usually when that happens on my system an X10 command sent on the powerline via another interface fixes that problem right up (it is a hardware issue). When you say you switch lights off via a remote is the remote using an RR501 or TM751 (X10 transceiver module) or are all the X10 commands only sent on the powerline via the CM12U?

              The plugin does wait for the command to successfully get on the powerline but stops trying after 3 attempts and then will output an error to the HS log indicating that the camera swithc has failed. Sometimes the retries could last minutes because HomeSeer also keeps trying to send to it's interface. During that time it would appear that the plugin in hanging but if left long enough it will start responding again as expected. From the excerpt of the log you've shown, the camera did switch because the line "CaptureUtility - Switching to camera Kitchen Camera" appears meaning the X10 command did get onto the powerline.
              Bryan
              (Config is in my profile)

              Comment


                #8
                Bryan,

                The only route to the powerline is via the CM12U, I have a W800RF unit for my motion sensors and palm pads which I have tested and transmit fine onto the powerline. I can also send commands direct from HS2 via the web interface to the CM12U which also works fine. Some how the plugin is getting in a twist trying to send the on command to the camera.

                I have just tried it again and the initial log entry from the plugin is the camera_switch entry which then hangs everything for up to a minute. In the entry attached I clicked the button on the cameras.asp page and then fired several commands from a palm pad and motion detector. The commands appeared to be queued by the ACRF plugin until things started moving again 48 seconds later.

                25/02/2006 19:44:23 - Hauppauge Captu - camera_switch - Found our camera that should be turned on C1 Study Camera

                48 seconds delay during which HS2 was unresponsive

                25/02/2006 19:45:11 - X10 Received - M7 (Lounge Motion Sensor) M On
                25/02/2006 19:45:11 - X10 Received - C7 (?) C Off
                25/02/2006 19:45:11 - X10 Received - C7 (?) C On
                25/02/2006 19:45:11 - X10 Received - C5 (?) C On
                25/02/2006 19:45:11 - X10 Received - C5 (?) C Off
                25/02/2006 19:45:12 - CaptureUtility - Form_Load - form loaded - Init value is True
                25/02/2006 19:45:14 - CaptureUtility - Form_Load - CapPreview Form Loaded
                25/02/2006 19:45:14 - CaptureUtility - Switching to camera Study Camera
                25/02/2006 19:45:14 - CaptureUtility - Entered ResetCameraConfig() for camera Study Camera Not Streaming - Snap in progress False - Capture filter enabled False
                25/02/2006 19:45:14 - CaptureUtility - ResetCameraConfig - Adding brightness:5000
                25/02/2006 19:45:14 - CaptureUtility - Brightness-0-10000-39-5000(10000) Contrast-0-10000-39-5000(5000) Hue-0-10000-39-5000(5000)
                25/02/2006 19:45:14 - CaptureUtility - Saturation-0-10000-39-5000(5000) Sharpness-0-10000-39-5000(5000) Gamma-0-10000-39-5000(5000)
                25/02/2006 19:45:14 - CaptureUtility - Video Source-1/Video Tuner Channel-27 V Size-640 x 480 Color Format-RGB24
                25/02/2006 19:45:14 - CaptureUtility - Autotuning channel 27
                25/02/2006 19:45:14 - CaptureUtility - TakePicture Hauppauge - Starting Initial Timer -100
                25/02/2006 19:45:15 - CaptureUtility - tmFormTimer - Timer fired for Form Timer - Interval was:100
                25/02/2006 19:45:15 - CaptureUtility - tmFormTimer - Starting preview
                25/02/2006 19:45:16 - CaptureUtility - tmFormTimer - Connected to drivers
                25/02/2006 19:45:16 - CaptureUtility - Snapping Image set 1 for Study Camera D:\homeseer\html\Capture\Study Camera_2006-02-25_19-45-16.jpg
                25/02/2006 19:45:17 - CaptureUtility - tmCaptureImage - Starting AVI capture for 15 seconds - D:\HomeSeer\html\AVI\Study Camera_2006-02-25_19-45-16.avi
                25/02/2006 19:45:18 - Process info - hspi_Hauppauge_Capture.exe - 6064 | ImageUtility.exe - 6528 | CaptureUtility.exe - 16064 |
                25/02/2006 19:45:18 - CaptureUtility - Purging for D:\homeseer\html\Capture\Study Camera_*.jpg for 50
                25/02/2006 19:45:18 - CaptureUtility - FinishUpWhenDone from (1) - Streaming(False) Capture (True) AVI Capturing(True) Still Capturing(False) Capture filter enabled(True) Preview(True)
                25/02/2006 19:45:19 - Hauppauge Captu - NinjaEvents() # of events found 10
                25/02/2006 19:45:23 - X10 Received - M3 (Hall Motion Sensor) M Off
                25/02/2006 19:45:26 - X10 Received - M7 (Lounge Motion Sensor) M On
                25/02/2006 19:45:33 - CaptureUtility - AVI Capture complete
                25/02/2006 19:45:33 - CaptureUtility - FinishUpWhenDone from (3) - Streaming(False) Capture (False) AVI Capturing(False) Still Capturing(False) Capture filter enabled(True) Preview(True)
                25/02/2006 19:45:33 - CaptureUtility - Purging for D:\HomeSeer\html\AVI\Study Camera_*.avi for 50
                25/02/2006 19:45:34 - CaptureUtility - Entered ResetCameraConfig() for camera Study Camera Not Streaming - Snap in progress False - Capture filter enabled False
                25/02/2006 19:45:34 - CaptureUtility - ResetCameraConfig - Adding brightness:5000
                25/02/2006 19:45:34 - CaptureUtility - Brightness-0-10000-39-5000(10000) Contrast-0-10000-39-5000(5000) Hue-0-10000-39-5000(5000)
                25/02/2006 19:45:34 - CaptureUtility - Saturation-0-10000-39-5000(5000) Sharpness-0-10000-39-5000(5000) Gamma-0-10000-39-5000(5000)
                25/02/2006 19:45:34 - CaptureUtility - Video Source-1/Video Tuner Channel-27 V Size-640 x 480 Color Format-RGB24
                25/02/2006 19:45:41 - X10 Received - M7 (Lounge Motion Sensor) M On

                This time select different camera

                25/02/2006 19:46:00 - Hauppauge Captu - camera_switch - Found our camera that should be turned on C2 Kitchen Camera
                25/02/2006 19:46:32 - CM11A - Unable to send to CM11A/CM12U

                Acknowledgement of send failure which was confirmed by the captured image being from the previous camera

                25/02/2006 19:46:32 - CaptureUtility - Switching to camera Kitchen Camera
                25/02/2006 19:46:32 - CaptureUtility - Entered ResetCameraConfig() for camera Kitchen Camera Not Streaming - Snap in progress False - Capture filter enabled False
                25/02/2006 19:46:32 - X10 Received - M7 (Lounge Motion Sensor) M On
                25/02/2006 19:46:32 - CaptureUtility - ResetCameraConfig - Adding brightness:0
                25/02/2006 19:46:33 - CaptureUtility - Brightness-0-10000-39-5000(5000) Contrast-0-10000-39-5000(5000) Hue-0-10000-39-5000(5000)
                25/02/2006 19:46:33 - CaptureUtility - Saturation-0-10000-39-5000(5000) Sharpness-0-10000-39-5000(5000) Gamma-0-10000-39-5000(5000)
                25/02/2006 19:46:33 - CaptureUtility - Video Source-1/Video Tuner Channel-27 V Size-640 x 480 Color Format-RGB24
                25/02/2006 19:46:33 - CaptureUtility - Autotuning channel 27
                25/02/2006 19:46:33 - CaptureUtility - TakePicture Hauppauge - Starting Initial Timer -100
                25/02/2006 19:46:33 - CaptureUtility - tmFormTimer - Timer fired for Form Timer - Interval was:100
                25/02/2006 19:46:33 - CaptureUtility - tmFormTimer - Starting preview
                25/02/2006 19:46:34 - CaptureUtility - tmFormTimer - Connected to drivers
                25/02/2006 19:46:34 - CaptureUtility - Snapping Image set 2 for Kitchen Camera D:\homeseer\html\Capture\Kitchen Camera_2006-02-25_19-46-34.jpg
                25/02/2006 19:46:34 - CaptureUtility - tmCaptureImage - Starting AVI capture for 15 seconds - D:\HomeSeer\html\AVI\Kitchen Camera_2006-02-25_19-46-34.avi
                25/02/2006 19:46:36 - Process info - hspi_Hauppauge_Capture.exe - 6068 | ImageUtility.exe - 6544 | CaptureUtility.exe - 16280 |
                25/02/2006 19:46:36 - CaptureUtility - Purging for D:\homeseer\html\Capture\Kitchen Camera_*.jpg for 50
                25/02/2006 19:46:36 - CaptureUtility - FinishUpWhenDone from (1) - Streaming(False) Capture (True) AVI Capturing(True) Still Capturing(False) Capture filter enabled(True) Preview(True)
                25/02/2006 19:46:36 - Hauppauge Captu - NinjaEvents() # of events found 10
                Do you have any suggestions as to how best to debug the error or at least track down the cause of the problem?

                Regards

                Dave

                Comment


                  #9
                  Only going to use 1 camera base?

                  One question. How many cameras are you planning on using Ninja for?

                  If only 1, I can suggest a way around not needing to use a powerline interface.

                  Plugin the ninja power and turn the unit on with some type of a controller OR supply the Ninja base with a wallwart that stays powered on.

                  In the Hauppauge configure page, not sure which one but I think it is the second tab from the left. Click the NS box for a non standard power source.

                  In the last tab on the right, select that camera and check the box that says NO DELAY.

                  This way, for a single camera base install you don't need to use the X10 addressable wallwart.

                  Comment


                    #10
                    Don,

                    Unfortunately I have two X10 cameras with pan tilt units and one wired camera setup with a non-standard power supply in the Hauppauge Capture plug in.

                    I have been doing some debugging by plugging the 2 X10 Ninja supplies and an appliance module set to the same house code so I have C1 & C2 for the cameras and C3 for the module and I have been seeing inconsistencies in the switching. I have not confirmed it yet but I may have a dud Ninja power supply.

                    Can someone confirm how the camera supplies should function if they are C1 & C2 respectively and I send an X10 command of C3 ON over the power line?


                    I'm assuming that the camera PSU's should shut down as they have received a Housecode ON which was not explicitly for their Unit no.

                    EDIT:
                    I've just noticed in the HS2 Interfaces page that there is an option to Enable an X-10 interface on the Hauppage Capture Plugin line. When I did this it gave an error message in HS2 log and disabled my existing CM11/CM12U interface even though it correctly identified the Comm port.

                    I tried running with the X-10 interface enabled in the plugin but nothing was being passed onto the power line even though it removed the CM11 error message and didnt freeze. This item isn't documented in the help file which still relates to HS V1.x so could some one give me a clue as to how the interface section needs to be configured?

                    Regards

                    Dave
                    Last edited by Fatlab; February 25, 2006, 09:13 PM.

                    Comment


                      #11
                      Bryan,

                      Any chance you can give me an update on how the X10 element of the capture plugin should be configured in the context of the earlier posts?

                      Dave

                      Comment


                        #12
                        Well they way the normal X10 camera's work is in groups of 4 and I believe that the Ninja's work the same. Unit codes are grouped by 1-4, 5-8, 9-12 and 13-16. For example if the cameras are on house code C and an X10 command to turn on C1 is sent, X10 camera's C2, 3 and 4 would automatically turn off if they were on.

                        Now in your case you have C1 and C2 as Ninja controllers, and C3 is set as a non-standard camera in the plugin. What happens when the plugin needs to turn on C1 it checks to see if any other camera is on. If C2 is on it is ignored because it should turn off automatically when it 'sees' the on command for C1. If C3 was on however, the plugin firsts send an off command for C3 then sends the on command for C1.
                        If an on command is sent for C3 then C1 and C2 will automatically be turned off when they 'see' the C3 on command.

                        I only have one Ninja so I can't test this. Maybe Don knows since he has three Ninja's set up now. If you find one of the Ninja camera's isn't automatically turning off, then just tell the plugin it is a non-standard camera and it will sent the required off command if it is on.

                        The X10 interface must not be turned on for this plugin as it only listens to X10 commands. The plugin uses HomeSeer to do the sending of X10 commands. This option was not available for 1.7 but it is available for 2.0.

                        Does this answer you questions Dave?
                        Bryan
                        (Config is in my profile)

                        Comment


                          #13
                          Bryan,

                          I have it configured as you suggested with the X-10 option disabled for the plug-in within the interfaces screen. I have also set all the PSU types to non standard and the same problem is happening.

                          03/03/2006 09:07:48 - Hauppauge Captu - camera_switch - Found our camera that should be turned on C1 Study Camera

                          03/03/2006 09:07:51 - CM11A - Unable to send to CM11A/CM12U

                          03/03/2006 09:07:51 - CaptureUtility - Switching to camera Study Camera
                          03/03/2006 09:07:51 - CaptureUtility - Entered ResetCameraConfig() for camera Study Camera Not Streaming - Snap in progress False - Capture filter enabled False
                          For some reason the plug in is failing to call the X-10 switching routine. As shown in the other posts I can send X-10 commands via the ACRF plugin onto the power line via the CM12U, directly from Homeseer webpage or by events/scripts without problems.

                          It's only the switching routine that is failing. I don't profess to understand how the coding/scripting of plug-ins work but it appears to hang Homeseer for up to a minute then any other queued commands are processed.

                          I'd really like to get this sorted as it is a show stopper for the plug-in so any help would be appreciated.

                          Dave

                          Comment


                            #14
                            I'm not sure what to tell you Dave. When a camera is required to be turned on, the plugin makes the request to HomeSeer to turn on the camera, so HomeSeer is sending out the X10 commands, not the plugin. That error you are seeing "Unable to send to CM11A/CM12U' is coming from HomeSeer, not the plugin. By the elapsed time period in your example, three seconds had passed. It is difficult to tell if that error is even as a result of the camera switching because any request to turn any device on or off can result in that error being displayed.

                            Lets see if we can figure out what is causing your issues ... some experimenting ... One thing the plugin does do is that when it requests HomeSeer to send out an X10 command the request is made to wait until a good signal is sent on the power line. The plugin uses the ExecX10 function like this "hs.ExecX10 "B2","ON", 0, 0, True". Try using this function in a script to turn some sevices on and off and see what happens.

                            The other question I have for you is how long of a delay is there from the time you request a device to turn on and when it actually turns on? Try this from the HomeSeer device panel, one of your hand held remotes and from a script using the ExecX10 function using the wait parameter (True as the last parameter).

                            I frequently see those errors in my log even if there is no camera activity. Often in my installation, they don't clear themselves up and I have to intervene by having an X10 command sent on the power line from some other device. This is usually caused by my flakey X10 cm11a (as a lot of them are).
                            Bryan
                            (Config is in my profile)

                            Comment


                              #15
                              Bryan,

                              You are right, after putting a test script together it generated the following log entries.

                              05/03/2006 17:59:07 - Info - Event Trigger "CM12 Test Script"
                              05/03/2006 17:59:07 - Info - Running script in background: CM12Test.txt
                              05/03/2006 17:59:07 - Debug - Sending ON Command to C4
                              05/03/2006 17:59:08 - Debug - Control returned, sending OFF
                              05/03/2006 17:59:09 - Debug - Control returned, sending ON
                              05/03/2006 17:59:11 - CM11A - Unable to send to CM11A/CM12U
                              05/03/2006 17:59:11 - Debug - Control returned, sending OFF
                              05/03/2006 17:59:59 - CM11A - Unable to send to CM11A/CM12U
                              05/03/2006 17:59:59 - Debug - Control Returned, end of script
                              05/03/2006 18:00:00 - Info - Event Trigger "HSTVSetDevices"
                              05/03/2006 18:00:00 - Info - Running script in background: HSTvSetDevices.txt
                              05/03/2006 18:00:26 - Info - Event Trigger "CM12 Test Script"
                              05/03/2006 18:00:26 - Info - Running script in background: CM12Test.txt
                              05/03/2006 18:00:26 - Debug - Sending ON Command to C4
                              05/03/2006 18:01:07 - Debug - Control returned, sending OFF
                              05/03/2006 18:01:25 - CM11A - Unable to send to CM11A/CM12U
                              05/03/2006 18:01:25 - Debug - Control returned, sending ON
                              05/03/2006 18:02:11 - Debug - Control returned, sending OFF
                              05/03/2006 18:02:13 - Debug - Control Returned, end of script
                              I reckon as your plugin is the only one I use which actually waits for confirmation of transmission, it's why I have never seen the message before. I guess I will have to look at debugging my X10/powerline interface now.

                              Regards

                              Dave
                              Last edited by Fatlab; March 5, 2006, 12:46 PM.

                              Comment

                              Working...
                              X