Announcement

Collapse
No announcement yet.

IR through Ocelot.

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

  • IR through Ocelot.

    I am using the ADIOcelot plugin and often when I restart HS software the IR does not work.

    I am not sure when it started because I was just kind of hoping it would go away...

    HS 2.2.0.11
    ADIOcelot plugin 1.14.4

    When the problem occurs, the ADIOcelot plugin works fine with the other modules. 2 SECU16 and 1 Secu16i.
    And on HS start it does list all of my modules everytime, 2 Secu16, 1 secu16i and 1 secu16ir.

    I have logged the communication to the ocelot, and it appears that the IR commands are not even being sent from HS.

    Any idea what might be causing this ?

    StevenE
    Why oh why didn't I just leave things alone, they had been working.

  • #2
    The attached has a HS Log output during init when HS asks for IR capabilties, when it configs and inits IR, and each direct and zone IR command sent. This should tell where the problem starts. Do confirm that the setting in HS still have ADIOcelot as the IR device.
    Last edited by Michael McSharry; July 29th, 2007, 03:14 PM.

    Comment


    • #3
      Micheal,

      This is from the log.

      7/29/2007 3:35:08 PM ~!~Info~!~HomeSeer version is: 2.2.0.11
      7/29/2007 3:35:08 PM ~!~Info~!~Initializing phone interface...
      7/29/2007 3:35:08 PM ~!~HSPhone~!~HomeSeer Phone Web Interface initializing.
      7/29/2007 3:35:09 PM ~!~Startup~!~Checking for available plug-ins
      7/29/2007 3:37:09 PM ~!~Info~!~HS Compatibility, cannot access plug-in HSPI_ADIOCELOT.HSPI ActiveX component can't create object
      7/29/2007 3:37:09 PM ~!~Info~!~Registering hspi_ADIOcelot.exe with Windows
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: ADIOcelot, version: 1.14.0.6
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: CheaperRFID Plugin, version: 2.0.3.0
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: Labjack U12 Plugin, version: 1.1.0.250
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: MLHSPlugin, version: 2.0.0.17
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: Temp05, version: 0.0.0.9
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: ACT TI103, version: 2.0.0.0
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: W800 RF (32Bit) Controller, version: 2.1.0.0
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: WAF AB8SS, version: 1.2.0.0
      7/29/2007 3:37:11 PM ~!~Info~!~Found plug-in: WAF AB8SS2, version: 1.2.0.0
      7/29/2007 3:37:11 PM ~!~Startup~!~Restoring device status
      7/29/2007 3:37:11 PM ~!~Startup~!~Initializing Z-Wave Interface on COM port: 13 at 115K baud.
      7/29/2007 3:37:53 PM ~!~Error~!~(Init/Sync) Initializing Z-Wave Interface: Could not communicate with the interface to get the version.
      7/29/2007 3:37:53 PM ~!~Startup~!~Initializing Plug-Ins
      7/29/2007 3:37:53 PM ~!~Info~!~Initializing X10 Plug-in: ACT TI103 On COM Port 6
      7/29/2007 3:37:53 PM ~!~Info~!~Initializing Plug-in: ACT TI103
      7/29/2007 3:37:53 PM ~!~Info~!~TI103 Plug-in, Version 2.0.0
      7/29/2007 3:37:55 PM ~!~Info~!~TI103, Communications established at 9600 baud
      7/29/2007 3:37:55 PM ~!~TI103~!~Warning: Plugin is set to ignore the following housecodes: A, B, C, D, E, G, H, I, J, K, L, N, O, P
      7/29/2007 3:37:55 PM ~!~Info~!~Finished initializing X10 interface ACT TI103
      7/29/2007 3:37:55 PM ~!~Error~!~Initializing Infrared interface ADIOcelot: Object variable or With block variable not set.
      7/29/2007 3:37:55 PM ~!~Info~!~Finished initializing infrared interface ADIOcelot
      7/29/2007 3:37:55 PM ~!~Info~!~Initializing Plug-in: ADIOcelot
      7/29/2007 3:37:55 PM ~!~Error~!~Initializing interface: ADIOcelot->Object variable or With block variable not set.
      7/29/2007 3:37:55 PM ~!~Info~!~Finished initializing plug-in ADIOcelot
      Why oh why didn't I just leave things alone, they had been working.

      Comment


      • #4
        There are a couple errors generated because the hs object has not been defined at the time initir and initx10 are called by HS. It does show that HS is calling the InitIR. There is nothing in the log when an IR command was issued from user/HS. I updated the debug file to not write to the log too early and left the log outputs when HS calls for IR output. The lack of any IR requests from HS to the plugin looks to be the problem.
        Attached Files

        Comment


        • #5
          Michael,

          Here is the HS.log and the ocelot log during a period where IR was not working.

          I restarted on 2007-7-30 and did not get a chance to test IR until tonight 2007-7-31.
          But the wife informed me it wasn't working all day...

          StevenE
          Attached Files
          Why oh why didn't I just leave things alone, they had been working.

          Comment


          • #6
            The HS Log shows the commands being delivered by Homeseer and the Ocelot log shows normal traffic in both directions to/from the ocelot. There is no acknowledge available from the Ocelot that it sends out IR.

            The logs show the software is asking it to send IR locations in the 100-300 range and across zones 1 to 3. What looks fishy is that the request is to send it via the Ocelot which ignores zones, yet HS is setting different zones. Zoned IR is requested by HS via the PlayRemoteIR while unzoned is via PlayIR and only PlayIR is in the log.

            Comment


            • #7
              When I was testing, I was just using the HS send ir button from the 'IR signals' page, no script or events.

              I had assumed that the ocelot comm log would show the ir being sent like the other functions, is that incorrect ?

              How can you tell IR has been sent in the ocelot comms log ?

              Is there any hope of preventing this problem ?

              Thanks
              StevenE
              Why oh why didn't I just leave things alone, they had been working.

              Comment


              • #8
                Commands to the Ocelot are placed in a queue and delivered one at a time until the queue is empty. The message to the HS log shows where it is placed in the queue. There is no feedback from the Ocelot that it receives any commands over the serial connection. If you are able to control other items in the ocelot then you know the queue is being delivered. The data put in the ocelot log is data that is sent by the ocelot to the PC. Since there is no command acknowledge in the protocol and the IR does not change the value or state of anything there is no feedback related to any IR commands that will show up in the Ocelot log.

                I would check the ocelot IR hardware by using CMAX to send IR.

                Comment


                • #9
                  That is exactly my problem, Cmax always works fine and HS does not.

                  Currently HS cannot send IR signals through the ocelot, So I just exited HS, started up CMAax and CMaxcould send IR signals with no problems to each of the 4 zones.

                  I then exited CMax and loaded HS, the IR initialized at startup, yet I cannot send any IR commands.

                  I am at a loss, and this is becoming very frustating every time I restart HS I have to remember to test the IR.

                  StevenE
                  Last edited by stevene; August 2nd, 2007, 06:42 PM.
                  Why oh why didn't I just leave things alone, they had been working.

                  Comment


                  • #10
                    Going over things again, I noticed that when the IR is not working, There are no configured Zones listed on the bottom of the IR Screen in HS.

                    After a few restarts, and the IR is working, the Zones are listed on the bottom of the IR screen in HS.

                    What would cause HS not to load the zone configurations ?

                    After comparing the startup logs from working and non working I noticed....


                    **********************************************
                    NON-Working ADIOcelot startup

                    7/30/2007 7:54:06 PM ~!~Info~!~Initializing Infrared interface ADIOcelot on COM 7
                    7/30/2007 7:54:08 PM ~!~ADIOcelot~!~Using Comm Port 7 0
                    7/30/2007 7:54:08 PM ~!~ADIOcelot~!~Found CPU-XA/Ocelot 0
                    7/30/2007 7:54:09 PM ~!~ADIOcelot~!~Ocelot IR size: 1024 0
                    7/30/2007 7:54:11 PM ~!~ADIOcelot~!~HandleIOPointChange 60
                    7/30/2007 7:54:15 PM ~!~Info~!~Finished initializing infrared interface ADIOcelot
                    7/30/2007 7:54:15 PM ~!~Info~!~Initializing Plug-in: ADIOcelot
                    7/30/2007 7:54:15 PM ~!~COM Plugin~!~Calling InitIO
                    7/30/2007 7:54:18 PM ~!~Info~!~Finished initializing plug-in ADIOcelot

                    ***********************************************
                    Working ADIOcelot startup

                    8/2/2007 7:27:03 PM ~!~Info~!~Initializing Infrared interface ADIOcelot on COM 7
                    8/2/2007 7:27:05 PM ~!~ADIOcelot~!~Using Comm Port 7 0
                    8/2/2007 7:27:05 PM ~!~ADIOcelot~!~Found CPU-XA/Ocelot 0
                    8/2/2007 7:27:05 PM ~!~ADIOcelot~!~Ocelot IR size: 1024 0
                    8/2/2007 7:27:07 PM ~!~ADIOcelot~!~Unit found: SECU16 Addr: 1 0
                    8/2/2007 7:27:07 PM ~!~ADIOcelot~!~Unit found: SECU16I Addr: 2 0
                    8/2/2007 7:27:07 PM ~!~ADIOcelot~!~Unit found: SECU16 Addr: 3 0
                    8/2/2007 7:27:07 PM ~!~ADIOcelot~!~Unit found: SECU16IR Addr: 4 0
                    8/2/2007 7:27:13 PM ~!~Info~!~Finished initializing infrared interface ADIOcelot
                    8/2/2007 7:27:13 PM ~!~Info~!~Initializing Plug-in: ADIOcelot
                    8/2/2007 7:27:13 PM ~!~COM Plugin~!~Calling InitIO
                    8/2/2007 7:27:15 PM ~!~Info~!~Finished initializing plug-in ADIOcelot
                    Thanks

                    *********************************************************

                    The modules are not specifically listed in the non-working startup.

                    Is this an issue ?

                    Thanks
                    StevenE
                    Why oh why didn't I just leave things alone, they had been working.

                    Comment


                    • #11
                      Could there be some parameters in the ocelot that effectively tells it to ignore IR from the serial? One of the reasons I did ADIOcelot was I use IR recognition within CMAX and the settings used by HST was to have the IR recognition forwarded to the serial connection. I only know enough about the ocelot to do what I needed to do and that was a few years ago. There will be more help on the ADI forum for configuration questions of this nature.

                      I could log each outgoing byte to the ocelot log, but very unlikely this will uncover anything if other outputs to the ocelot are working.

                      Comment


                      • #12
                        Michael,

                        The IR does work, but sometimes after a restart it doesn not.

                        Do you know why when the plugin initializes when it lists the 4 modules and why sometimes it does not list the modules ?

                        If there is no solution, I am just going to switch to different hardware for IR.

                        StevenE
                        Why oh why didn't I just leave things alone, they had been working.

                        Comment


                        • #13
                          During startup the Serial port is opened and requests are sent down to the ocelot to return its parameters and enumerate the attached via RS485. The HS log should reflect what it finds or reflect if there is a timeout after waiting 3 seconds for the ocelot to respond with the expected 268 characters.

                          With a restart-only problem then it looks as if your serial hardware is not yet ready when HS starts, control is taken by something going through initialization so the serial port cannot be managed, or similiar timing-related issue. When the plugin is waiting it returns control back to the OS and then every 200 milliseconds it looks on the serial port to see if the input buffer has received anything. The serial port is configured in binary mode and settings of 9600,n,8,1.

                          Comment

                          Working...
                          X