Re: Newbie Question - chooser seeing my driver
- Aha! I found the missing piece of information - how does focusmax (or
any other program) know to use my dll? For other Dummies / Newbies
like myself, here it is:
Apparently, when I create a dll file, I need to register in using the
Windows utility program
regsvr32 /s MyLittle.dll
The /s flag says to register is silently; there doesn't seem to be a
"noisy" flag which tells you it actually worked.
I can also unregister with a /u flag.
I assume this covers the issue of "your dll must be correctly
registered as a COM object", as mentioned by Mr. Long.
--- In ASCOM-Talk@yahoogroups.com, "robert_brewington"
> First - my code correctly sets the DeviceType for the profile;
> however, the vb script I was also using to register my focuser did
> not. So, the script was registering as a telescope. That is fixed now.
> Second - the focuser now works correctly on my development machine.
> Third - the focuser does not work when "installed" on the target
> observatory telescope.
> Installation involved copying the dll to the Ascom/Focuser directory
> and registering it with a vb script. My focuser shows up in the
> chooser, but clicking the Properties button in the chooser results in
> an error "ActiveX component cannot create object".
> Trying to create the focuser object in a vbscript generates a similar
> error "ActiveX component cannot create object 'MyFocuser.Focuser'".
> So, apparently something more is needed to install the dll on the
> observatory machine. Of course, it is 30 minutes away and has no
> internet, so I envision many drives back and forth to try different
> Next, I tried to read the article
> http://ascom-standards.org/developer.html as recommended by Bob. OK,
> I'm confused.
> It sounds like the Profile helper does not do the COM registration?
> How is this done? Surely COM registration does not involve the complex
> manipulations described in this article?
> I looked in the Automation Objects section of the OLEView output. On
> my development machine (where things seem to be working) I see no
> references to my focuser. The Telescope simulator shows up as
> described in the article. The article is talking about an exe-style
> driver; is my dll-style driver supposed to look the same? How can the
> development machine run correctly without having this information?
> Still lost in the wilderness:)
> --- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@> wrote:
> > Robert and Timothy --
> > Check out the Developer info on the ASCOM site at
> > http://ascom-standards.org/developer.html
> > as well as the sources of a few drivers (those that come with the
> > developer info).
> > Robert --
> > > set p = CreateObject ("DriverHelper.Profile")
> > > p.Unregister "Junk1Server.Focuser"
> > You need to tell Profile that your device is a Focuser:
> > set p = CreateObject ("DriverHelper.Profile")
> > p.DeviceType = "Focuser" <=== IMPORTANT
> > p.Unregister "Junk1Server.Focuser"
> > Without the DeviceType, it defaults to "Telescope" and registers
> your driver as
> > a Telescope driver, etc. The Overview doc for the Profile object is
> out of date
> > (it talks only about Telescope).
> > Have a look at sources for domes and focusers.
> > -- Bob
> I assume this covers the issue of "your dll must be correctlyRighto! Wow, you're living on the edge... developing a driver remotely!! I just
> registered as a COM object", as mentioned by Mr. Long.
did this for COMSOFT PC-TCS (combined Dome, Telescope and Focuser in one driver
exe). What fun. At least I had a working Telescope driver (ACL Telescope) to