Announcement

Collapse
No announcement yet.

Can not call configuration from plug-in.

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

  • #16
    I'm guessing that one of the C libraries that was used to build the control is not on your computer. There was a program called Depends that I have run in the past that shows the dependency tree of object code modules.

    Comment


    • #17
      I ran the latest version of Dependency Walker on the hspi_adiocelot.exe file. It lists 1 file that is missing: msvbvm60.dll

      I have this file on another system running Windows 7 64-bit that has Visual Studio 2012 installed. Should I simply copy the file to the Windows\System32 directory and run regsvr32?

      Comment


      • #18
        that is what I would try

        Comment


        • #19
          I discovered that this file, msvbvm60.dll, is already on the HomeSeer computer in the Windows\SysWOW64 directory. I copied it from this directory into the Windows\System32 directory and registered it successfully with regsrv32. However, the config button in ADIOcolet still does not work. I get this in the HomeSeer log:

          8/31/2013 8:40:37 PM ConfigIO Calling ConfigIO for ADIOcelot
          8/31/2013 8:40:37 PM ADIOcelot ConfigIO 20

          When the plug-in initializes, it looks like it first tries COM1 instead of COM4 as configured - but it then tries COM4 and works since that is where the hardware is attached:

          8/31/2013 8:27:13 PM COM Plugin Calling InitIO
          8/31/2013 8:27:13 PM ADIOcelot Open Comm Port 1 80
          8/31/2013 8:27:16 PM ADIOcelot Ocelot Plug-in Error, Timeout looking for CPU-XA/Ocelot 0
          8/31/2013 8:27:19 PM ADIOcelot Ocelot Plug-in Error, Timeout looking for CPU-XA/Ocelot 0
          8/31/2013 8:27:35 PM Plug-In Finished initializing plug-in ADIOcelot
          8/31/2013 8:27:35 PM Plug-In Initializing X10 Plug-in: ADIOcelot On COM Port 4
          8/31/2013 8:27:35 PM Plug-In Initializing Plug-in: ADIOcelot
          8/31/2013 8:27:35 PM ADIOcelot Initializing X10 Interface on port 4 0
          8/31/2013 8:27:37 PM ADIOcelot Using Comm Port 4 0
          8/31/2013 8:27:38 PM ADIOcelot Found CPU-XA/Ocelot 0
          8/31/2013 8:27:38 PM ADIOcelot Ocelot IR size: 1024 0
          8/31/2013 8:27:40 PM ADIOcelot Unit found: SECU16I Addr: 1 0
          8/31/2013 8:27:40 PM ADIOcelot Unit found: SECU16 Addr: 2 0
          8/31/2013 8:27:42 PM Plug-In Finished initializing X10 interface ADIOcelot
          8/31/2013 8:27:42 PM Plug-In Initializing Infrared interface ADIOcelot on COM 4
          8/31/2013 8:27:42 PM Plug-In Finished initializing infrared interface ADIOcelot

          Dependency Walker shows other files that are missing, but I see these same missing files on other programs that appear to be working. See the attached screenshot.

          Any ideas on how to proceed? This plug-in worked incredibly well on my old Windows XP machine and I would like to use it again.

          Thanks.
          Attached Files
          Last edited by Mountainman; August 31st, 2013, 09:47 PM. Reason: added attachment

          Comment


          • #20
            When I moved to Win7 the ADIOcelot plugin would not work. I can't remember the details, but I think Michael has made it clear he is not doing any more updates to it, so I switched to the Homeseer one. It wasn't a drop-in replacement, but it was not that hard to make the move. There are a couple of annoying items with the Homeseer one (and I'm certain they will never fix them), but there are work-arounds. I don't think spending tons of time trying to get the old one (RIP) to work is worth it.

            Steve

            Comment


            • #21
              Steve, thanks for the insight. I assumed someone had this working under Windows 7.

              I am using A/D inputs and digital inputs. Do both of these work with the HomeSeer plug-in?

              Comment

              Working...
              X