Can not call configuration from plug-in.

[Mountainman]

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?

[stevea]

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

[Mountainman]

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.

[Michael McSharry]

that is what I would try

[Mountainman]

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?

[Michael McSharry]

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.

[Mountainman]

I'm battling this same problem, but I'm on a Windows 7 64-bit system. There are 3 files that aren't in my Windows\System32 directory that are in the ADIOcelot_Controls.zip file posted in this thread. When I try to register them using "regsvr32 comdlg32.ocx", for example, I get the error box "The module "comdlg32.ocx" failed to load. blah blah blah The specified module could not be found." The file is definitely in the Windows\System32 directory and I'm running the command to register it from a command prompt where the path is set to Windows\System32.

What do I need to do to get this to work under Windows 7?

[twa8000]

That fixed the problem! Thanks!

-Tom-

[Michael McSharry]

I'm attaching all the controls that ADIOcelot references other than the VB6 libraries themselves. I'm pulling them off of my laptop that is running XP Pro. If you already have the file on your computer then do not replace it. If you do not then put it in the Windows\System32 folder and use regsvr32 to register it.

[Michael McSharry]

The select menu 40 error is a library/component type failure. I will check the adiocelot source to see if any component is used there and not in mcssprinklers.

[Mountainman]

I'm not sure if this is what you are seeing, but sometimes the configuration screen does not get drawn on top of other windows (gets hidden behind the HS window). Run task manager, select the ADIOcelot application, and then 'bring to front' to get it on top.

[Clever1]

I tried installing the mcsSprinklers beta file you provided but still no luck. I have LogmeIn installed on my box if you think looking through the system might help to determine what the problem is.

[Michael McSharry]

Some are able to access setup and some are not. I suspect there is some software, such as VB6 library or component that is needed and does not exist on some computers. Likely the oldtimers that have been adding new software will have the old stuff that is needed and those starting fresh have the problem.

The Select Menu 40 error is generated when the software tries to load the VB form that contains the setup settings. It happens as is loads rather than happening after it loads and starts to put data on the form. This means the error is generated in the VB6 support libraries or similiar.

I know that one user reported success with one of the VB6 plugins after they install the VB6 Visual Studio. When HS2 was first being introduced I worked with Rich Helmke to identify all the libraries that I was using and should be part of the basic install package. I suspect over time some of these are no longer being included.

While not a guarantee, an approach that you can try is to install the standalone version of mcsSprinklers http://mcsSprinklers.com/setup_beta.exe. You do not need to run it after install. It likely contains all the VB6 glue that ADIOcelot would be using. It has an uninstaller so uninstalling should clean out all that was added if you find it does not help.

[Clever1]

This post has me wondering if this is something that occurs only with the Pro-100. Or maybe even with the Restore Flash Drive?

[Clever1]

I posted the same issue in the main Sticky thread in hopes that Micheal will respond to that.