In Vista, when I install Starry Night with ASCOM, or ASCOM drivers
separately, during the installation I get an error message that
says "can't open C:\Windows\system32\MSVBVM60.dll", and the
installation fails.

I have tried installing with administrative priviledges, in XP SP2
mode, and with User Account Control turned off, but with no success.

How can I get around this?

thanks! Kevin

Hi,
The recent questions about registering an ASCOM object remind me about
some things that I'm not sure about for the Version 5 installer.

There doesn't seem to be anything in the installer other than a [run]
command to register the exe:
[Run]
Filename: {app}\Celestron Driver.exe; Parameters: /regserver

Will this register the driver with the chooser? Or does it need a call
to CreateObject? This could be done with a [Code] section I think.

Will these commands do the things required to allow TheSky to use DCOM?
[Registry]
; set the access control for TheSky
Root: HKCR; Subkey: CLSID\{{2C56B40D-6C9C-42E5-8B2D-A37025C31FE9};
ValueType: string; ValueName: AppID; ValueData:
{{2C56B40D-6C9C-42E5-8B2D-A37025C31FE9}
Root: HKCR; Subkey: AppId\{{2C56B40D-6C9C-42E5-8B2D-A37025C31FE9};
ValueType: string; ValueData: {AppName}
Root: HKCR; Subkey: AppId\{{2C56B40D-6C9C-42E5-8B2D-A37025C31FE9};
ValueType: string; ValueName: AppID; ValueData:
{{2C56B40D-6C9C-42E5-8B2D-A37025C31FE9}
Root: HKCR; Subkey: AppId\{{2C56B40D-6C9C-42E5-8B2D-A37025C31FE9};
ValueType: dword; ValueName: AuthenticationLevel; ValueData: 1

The GUID has to be set to the application AppId of course.


Chris

Jay --

I am out of the office at the Bartlett Lake sheriff substation with a tiny
cell/data signal, and will be here for a few days, then off to ASP in Chicago.
I'll do my best to help...

What is an AS1/ASII driver? What requires a separate driver? These messages are
foreign to me.

The 4.0.14 driver is in use at lots of places. And the  original driver won't
support unparking, the Meade firmware changed a lot. But Jon Brewster has
updated it yet again, for later firmware:

Go to the ASCOM Talk (Yahoo! group) Files section, Jon Brewster folder, and get
the Meade LX200GPS 4-1-28 Setup.exe file. Don't get the 5.0 one, it's for the
Platform 5 which is still in beta.

As for the original pointing problems, note that ACP -should- be showing the
same thing (local topocentric/JNow system)! ALl ACP does is show what the
Autostar sends. This assumes that you have the ACP Pointing Corrector OFF! Don't
pay attention to the catalog coordinates for the time being. Catalogs are in
J2000 and typically differ a bit. The difference between local topo and J2000
will be arcminutes.

What's even stranger is that MaxIm  and ACP report different coordinates. They
both get their coordinates from the same source... the driver. Be sure MaxIm is
set to show "JNow" if you intend to compare it to ACP and the Autostar.

What bugs me is that the Autostar and ACP/MaxIm don't match. You're sure of
this? If ACP's pointing corrector is off, all that  should match.

   -- Bob

Check with FLI. Jim  Moronski is very familiar with ASCOM - their cameras have
ASCOM camera drivers available.

   -- Bob

Claude Boivin:
> Hi
>
> I'm looking for a ascom driver for the FLI filter wheel and dont seem
> to be able to find it?
>
> Can someone help me on this issue ?
>
> Does it exists ?
>
> Thank you for your help
>
> Claude
>
> Canada
>
>

Can you have your installer create an instance of the driver?

   -- Bob

dpanderson1960:
> Thanks Chris.  I am using the Helper functions to create my unique
> keys.  What I was referring to is the need to somehow get the driver
> registered the first time so that the Chooser can find it.  Currently I
> have the installer copy the DLL to the appropriate directory, then copy
> a short VB script,  then run the VB script, then delete the VB script.
> I have noticed on some installs, an error message occurs that says the
> object cannot be created.  Usually a second run of the VB script
> results in success.

Peter Eschman suggested I pass along the resolution of an issue I was
having with the connection of the Gemini ASCOM driver to my laptop
for future reference.

About a month ago, when trying to connect my scope using POTH, I got
a "scope driver not capable of providing equatorial or Alt/AZ
coordinates, disconnecting." When trying to open the driver
properties I would get "runtime error 429 Active X component cannot
create object."

The night earlier everything was working fine.  No software was
installed in the intervening period.  I also got a variety of other
errors from The Sky and other software when trying to connect to the
Gemini Controller. Interestingly, I could connect and retain a
connection with PemPro and record and upload PEC data but no position
information was displayed within PemPro.

After searching the web for runtime error 429, I ended up at the
Microsoft knowledge base.  Several causes were listed for the error
including registering active x components and several others.  After
going through the list without resolution, I got to a listing about
Windows Script 5.3.  I downloaded the software and reinstalled
Windows Script 5.3 and low and behold the connection worked.

Somehow this application within Windows XP got corrupted and the fix
ended up being somewhat simple after alot of detective work.

Jon Talbot

Jon Talbot wrote:

> Somehow this application within Windows XP got corrupted and the fix
> ended up being somewhat simple after alot of detective work.

No doubt you are installing the Microsoft "security fixes", which often include
non-security related bug fixes for XP, and occasionally include NEW BUGS for XP.
It's possible that one of those updates mucked up your system somehow.  I don't
suppose an update was downloaded between those two sessions...?

Doug

-----------------------------------

Doug George
dgeorge@...

Diffraction Limited
Makers of Cyanogen Imaging Products
http://www.cyanogen.com

25 Conover Street
Ottawa, Ontario,
Canada, K2G 4C3

Phone:    (613) 225-2732
Fax:      (613) 225-9688

-----------------------------------

Doug,
You may be absolutely right, I didnt check to see if any updates were
downloaded.  Next time something like this happens that will be the
first thing to check.  I have the updates set to automatic.

Jon Talbot

--- In ASCOM-Talk@yahoogroups.com, "Douglas B. George" <dgeorge@...>
wrote:
>
> Jon Talbot wrote:
>
> > Somehow this application within Windows XP got corrupted and the
fix
> > ended up being somewhat simple after alot of detective work.
>
> No doubt you are installing the Microsoft "security fixes", which
often include
> non-security related bug fixes for XP, and occasionally include NEW
BUGS for XP.
> It's possible that one of those updates mucked up your system
somehow.  I don't
> suppose an update was downloaded between those two sessions...?
>
> Doug
>
> -----------------------------------
>
> Doug George
> dgeorge@...
>
> Diffraction Limited
> Makers of Cyanogen Imaging Products
> http://www.cyanogen.com
>
> 25 Conover Street
> Ottawa, Ontario,
> Canada, K2G 4C3
>
> Phone:    (613) 225-2732
> Fax:      (613) 225-9688
>
> -----------------------------------
>

I normally use an installer custom action which calls the ASCOM
Profile.Register function. I build the custom action method right into
my driver and the installer calls it during the installation process.
I'm using Windows Installer (MSI). I can send you the source code for my
installer class if you like.

--Tim Long

-----Original Message-----
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
Behalf Of dpanderson1960
Sent: 31 August 2007 19:50
To: ASCOM-Talk@yahoogroups.com
Subject: Re: [ASCOM] Registering an ASCOM object

Thanks Chris.  I am using the Helper functions to create my unique
keys.  What I was referring to is the need to somehow get the driver
registered the first time so that the Chooser can find it.  Currently I
have the installer copy the DLL to the appropriate directory, then copy
a short VB script,  then run the VB script, then delete the VB script.
I have noticed on some installs, an error message occurs that says the
object cannot be created.  Usually a second run of the VB script
results in success.

Any comments on how others are taking care of this task would be
greatly appreciated.

Doug Anderson
Shoestring Astronomy

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...>
wrote:
>
> Hi Doug,
>
> Its best to avoid modifying the registry yourself in the installer -
or
> for saving and loading parameters in the driver - because there are
> plans to move this from the registry because of the changes made to
how
> the registry works with Vista.
>
> If you use the Helper functions then this will be sorted out for you
> with a new version of the helper.
>
> Chris
>




For more information see http://ASCOM-Standards.org/.

To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
TO SUBSCRIBE(!) to:
ASCOM-Talk-unsubscribe@yahoogroups.com


Yahoo! Groups Links

Jon --

I hope it was Windows Script 5.6, not 5.3 (which is at least 4 years old). If
not, then do get 5.6 and update to that! I suspect, though, that you already had
5.6, and the install just fixed some bad object registration stuff.

   -- Bob

Tim,

Yes, you could email that to me.  I use InnoSetup, but your source
code would probably show me what I need to try.

Thanks,

Doug Anderson


--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> I normally use an installer custom action which calls the ASCOM
> Profile.Register function. I build the custom action method right into
> my driver and the installer calls it during the installation process.
> I'm using Windows Installer (MSI). I can send you the source code for my
> installer class if you like.
>
> --Tim Long

Bob,

That is what my current installers do.  I had one customer that
couldn't get the installer to work, so I was looking for alternatives
where I would not need to run a script.  It turns out he had a bigger
problem, he had swapped out his hard drive and had forgot to
re-install the ASCOM platform.  Once he did this, his installer
problems went away!

Thanks for your comments,

Doug Anderson
Shoestring Astronomy.

--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> Can you have your installer create an instance of the driver?
>
>   -- Bob
>
> dpanderson1960:
> > Thanks Chris.  I am using the Helper functions to create my unique
> > keys.  What I was referring to is the need to somehow get the driver
> > registered the first time so that the Chooser can find it.
Currently I
> > have the installer copy the DLL to the appropriate directory, then
copy
> > a short VB script,  then run the VB script, then delete the VB
script.
> > I have noticed on some installs, an error message occurs that says
the
> > object cannot be created.  Usually a second run of the VB script
> > results in success.
>

Here are two ways of registering during setup. The first method is taken
from Bob Denny's driver template from the ASCOM 5.0 alpha, the second is
how I have been doing it pre-ASCOm-5. I think I prefer Bob's technique.
My solution writes diagnostic stuff to the windows event log but you
could easily strip that out or add it to Bob's code. My RegisterCOM
class is named that way for historical reasons, it would more
appropriately be called RegisterASCOM really.

In both techniques, the key is to mark the relevant class or methods
with an attribute - either [RunInstaller] or
[ComRegisterFunction]/[ComUnregisterFunction] which causes the code to
be invoked at the right moment.

OK so here's Bob's method:
========================================================================
==
		 #region ASCOM Registration // Borrowed from Bob
Denny's driver templates
		 //
		 // Register or unregister driver for ASCOM. This is
harmless if already
		 // registered or unregistered.
		 //
		 private static void RegUnregASCOM(bool bRegister)
		 {
			 ASCOM.Helper.Profile P = new
ASCOM.Helper.Profile();
			 P.DeviceTypeV = "Telescope";
//  Requires Helper 5.0.3 or later
			 if (bRegister)
				 P.Register(csDeviceID, csName);
			 else
				 P.Unregister(csDeviceID);
			 try
// In case Helper becomes native .NET
			 {
				 Marshal.ReleaseComObject(P);
			 }
			 catch (Exception) { }
			 P = null;
		 }
		 /// <summary>
		 /// Registers this driver with the ASCOM platform so it
appears in the Chooser.
		 /// This method is called whenver the assembly is COM
registered.
		 /// </summary>
		 /// <param name="t"></param>
		 [ComRegisterFunction]
		 public static void RegisterASCOM(Type t)
		 {
			 Diagnostics.TraceInfo("Registering with ASCOM
Chooser");
			 RegUnregASCOM(true);
		 }
		 /// <summary>
		 /// Unregisters this driver with the ASCOM platform so
that it no longer appears in the Chooser.
		 /// THis method is called whenver the assembly is COM
unregistered.
		 /// </summary>
		 /// <param name="t"></param>
		 [ComUnregisterFunction]
		 public static void UnregisterASCOM(Type t)
		 {
			 Diagnostics.TraceInfo("Unregistering from ASCOM
Chooser");
			 RegUnregASCOM(false);
		 }
		 #endregion

========================================================================
==

Now, here's my solution which relies on MSI custom actions. This is a
complete source file. Note that I use a library class called
LateBoundDriver which makes it easier for me to do late binding from C#
- rather than reproduce all that code here, if you are using C# then I
would recommend using the ASCOM 5.0 PIA and calling DriverHelper
directly. Otherwise you can just CreateObject(...) or write your own
LateBoundDriver helper class.

========================================================================
==

using System;
using System.Configuration.Install;
using System.ComponentModel;
using System.Runtime.InteropServices;
using System.Windows.Forms;
using System.Diagnostics;

using ASCOM.Standards;
//using DriverHelper;

namespace SyD.DDW.Install
{
	 /// <summary>
	 /// Custom install actions that must be carried out during
product installation.
	 /// </summary>
	 [RunInstaller(true)]
	 public class DDWInstaller : Installer
	 {
		 /// <summary>
		 /// ProgID of this component, used to create an ASCOM
device profile.
		 /// </summary>
		 const string cstrProgID = "DDW.Dome";
		 /// <summary>
		 /// String used to identify this module in debug traces
and the event log.
		 /// </summary>
		 const string csDbg = "DDW ASCOM Setup";
		 /// <summary>
		 /// Component description, used to create the ASCOM
'friendly name' that appears in the ASCOM Chooser.
		 /// </summary>
		 const string cstrDescription = "TI Digital DomeWorks";
		 /// <summary>
		 /// Event Log instance used for diagnostic logging
during install.
		 /// </summary>
		 /// <remarks>
		 /// The contents of this log are viewed using the Event
Viewer application, which
		 /// is found under Control Panel, Administrative Tools.
		 /// </remarks>
		 EventLog myLog;

		 /// <summary>
		 /// Open the SyD event log so that installation actions
can be logged.
		 /// </summary>
		 private void OpenEventLog()
		 {
			 // Create the event source, if it does not
already exist.
			 if(!EventLog.SourceExists(csDbg))
			 {
				 EventLog.CreateEventSource(csDbg,
"Software-y-Ddraig");
			 }

			 // Create an EventLog instance and assign its
source.
			 myLog = new EventLog();
			 myLog.Source = csDbg;

			 // Create a trace listener for the event log.

			 EventLogTraceListener myTraceListener = new
EventLogTraceListener(myLog);
			 // Add the TraceListener to the Trace and/or
Debug Listeners collection
			 if (!Trace.Listeners.Contains(myTraceListener))
			 {
				 Trace.Listeners.Add(myTraceListener);
			 }
		 }

		 /// <summary>
		 /// Custom Install Action that regsiters the driver with
the ASCOM platform as well as
		 /// registering for COM Interop, for backward
compatibility with legacy ASCOM.
		 /// </summary>
		 /// <param name="stateSaver"><see
cref="Installer"/></param>
		 public override void
Install(System.Collections.IDictionary stateSaver)
		 {
#if DEBUG
			 MessageBox.Show("Attach debugger to this process
now, if required", "Custom Action Debug", MessageBoxButtons.OK,
MessageBoxIcon.Asterisk);
#endif
			 OpenEventLog();
			 myLog.WriteEntry("Beginning Custom Install
Actions for DDW.Dome", System.Diagnostics.EventLogEntryType.Information,
2001);

			 //MessageBox.Show("Entering Install action");
			 base.Install(stateSaver);
			 myLog.WriteEntry("Begining registration of ASCOM
interface for COM Interop",
System.Diagnostics.EventLogEntryType.Information, 2001);
			 RegistrationServices regsrv = new
RegistrationServices();
			 if
(!regsrv.RegisterAssembly(this.GetType().Assembly,
AssemblyRegistrationFlags.SetCodeBase))
			 {
				 myLog.WriteEntry("COM Interop
registration failed", System.Diagnostics.EventLogEntryType.Error, 2002);
				 throw new InstallException("Failed To
Register ASCOM Layer for COM Interop");
			 }
			 myLog.WriteEntry("Begining registration of
Hardware Layer interface for COM Interop",
System.Diagnostics.EventLogEntryType.Information, 2001);
			 if
(!regsrv.RegisterAssembly(typeof(SyD.DDW.DigitalDomeWorks).Assembly,
AssemblyRegistrationFlags.SetCodeBase))
			 {
				 myLog.WriteEntry("COM Interop
registration failed", System.Diagnostics.EventLogEntryType.Error, 2002);
				 throw new InstallException("Failed To
Register Hardware Layer for COM Interop");
			 }
			 myLog.WriteEntry("Completed registration for COM
Interop", System.Diagnostics.EventLogEntryType.Information, 2001);


			 // Register with the ASCOM platform
			 myLog.WriteEntry("Begining registration with
ASCOM platform", System.Diagnostics.EventLogEntryType.Information,
2001);
			 //Trace.WriteLine("Registering ASCOM profile",
csDbg);
			 LateBoundDriver lbdProfile = new
LateBoundDriver("DriverHelper.Profile");
			 lbdProfile.SetProperty("DeviceType", "Dome");
			 object[] asParams = new string[2];
			 asParams[0] = cstrProgID;
			 asParams[1] = cstrDescription;
			 lbdProfile.InvokeMethod("Register", ref
asParams);
			 myLog.WriteEntry("ASCOM device profile
registered", System.Diagnostics.EventLogEntryType.Information, 2001);
			 asParams = new string[1];
			 asParams[0] = cstrProgID;
			 object oResult =
lbdProfile.InvokeMethod("IsRegistered", ref asParams);
			 if (oResult.GetType() != typeof(bool))
			 {
				 myLog.WriteEntry("Unexpected error
attempting to verify ASCOM profile status",
System.Diagnostics.EventLogEntryType.Error, 2004);
				 throw new InstallException("Failed to
verify correct device profile registration for DDW.Dome");
			 }
			 bool bSuccess = (bool) oResult;
			 if (!bSuccess)
			 {
				 myLog.WriteEntry("Unable to verify ASCOM
device profile status", System.Diagnostics.EventLogEntryType.Error,
2005);
				 throw new InstallException("Failed to
register ASCOM Device Profile for DDW.Dome");
			 }
			 myLog.WriteEntry("Custom Install Actions
completed successfully",
System.Diagnostics.EventLogEntryType.Information, 2003);
		 }

		 /// <summary>
		 /// Custom Install Action that removes the driver's
ASCOM Profile
		 /// and also removes the COM Interop component
registrations.
		 /// </summary>
		 /// <param name="savedState"><see
cref="Installer"/></param>
		 public override void
Uninstall(System.Collections.IDictionary savedState)
		 {
			 try
			 {
				 OpenEventLog();
				 myLog.WriteEntry("Beginning Custom
Uninstall Actions for DDW.Dome",
System.Diagnostics.EventLogEntryType.Information, 2001);
				 //MessageBox.Show("Entering uninstall
action");
				 base.Uninstall(savedState);

				 myLog.WriteEntry("Begining
deregistration for COM Interop",
System.Diagnostics.EventLogEntryType.Information, 2001);

				 RegistrationServices regsrv = new
RegistrationServices();
				 if
(!regsrv.UnregisterAssembly(this.GetType().Assembly))
				 {
					 myLog.WriteEntry("COM Interop
deregistration failed", System.Diagnostics.EventLogEntryType.Error,
2006);
					 throw new
InstallException("Failed To Unregister for COM");
				 }

				 // Unregister from ASCOM platform
				 myLog.WriteEntry("Removing ASCOM device
profile", System.Diagnostics.EventLogEntryType.Information, 2001);
				 try
				 {
					 LateBoundDriver lbdProfile = new
LateBoundDriver("DriverHelper.Profile");
					 object[] asParams = new
string[1];

lbdProfile.SetProperty("DeviceType", "Dome");
					 asParams[0] = cstrProgID;

lbdProfile.InvokeMethod("Unregister", ref asParams);
					 myLog.WriteEntry("Unregister
operation completed", System.Diagnostics.EventLogEntryType.Information,
2001);
					 object oResult =
lbdProfile.InvokeMethod("IsRegistered", ref asParams);
					 if (oResult.GetType() !=
typeof(bool))
					 {

myLog.WriteEntry("Unexpected error attempting to verify ASCOM profile
status", System.Diagnostics.EventLogEntryType.Error, 2004);
						 throw new
InstallException("Unable to verify correct removal of the ASCOM device
profile for DDW.Dome");
					 }
					 bool bStillThere = (bool)
oResult;
					 if (bStillThere)
					 {
						 myLog.WriteEntry("Unable
to verify ASCOM device profile status",
System.Diagnostics.EventLogEntryType.Error, 2005);
						 throw new
InstallException("Failed to unregister ASCOM device profile for
DDW.Dome");
					 }
				 }
				 catch (Exception ex)
				 {
					 // If we failed to unregister
the ASCOM device profile, then tell the user but otherwise
					 // allow the uninstall to
succeed, otherwise it can be difficult to get the driver uninstalled.
					 MessageBox.Show("Failed to
unregister ASCOM device profile for " + cstrProgID

+ "\nThe driver may still appear in the ASCOM Chooser but will no longer
work.",
						 "Digital DomeWorks ASCOM
Driver",
						 MessageBoxButtons.OK,
						 MessageBoxIcon.Error);
				 }
			 }
			 catch (Exception ex)
			 {
				 Debug.WriteLine(ex, cstrProgID);
#if !DEBUG // Fail silently for a debug build
				 throw ex;
#endif
			 }
			 myLog.WriteEntry("Custom uninstall actions
completed successfully",
System.Diagnostics.EventLogEntryType.Information, 2006);
		 }
	 }
}

Hi  Jose

Yes i'm pretty sure it is...

How can you help do you have this ascom driver ?

thanks

Claude



--- In ASCOM-Talk@yahoogroups.com, "jose canela" <jcanela@...> wrote:
>
>
>
> I have the FLI CFW1-8... if i's the same driver as yours maybe I
can
> help.
>
>
> ________________________________
>
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
Talk@yahoogroups.com] On
> Behalf Of Claude Boivin
> Sent: sexta-feira, 31 de Agosto de 2007 16:44
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] FLI filter wheel
>
>
>
> Hi
>
> I'm looking for a ascom driver for the FLI filter wheel and dont
seem
> to be able to find it?
>
> Can someone help me on this issue ?
>
> Does it exists ?
>
> Thank you for your help
>
> Claude
>
> Canada
>

Hi !

I am new to astronomy and also to this group...

... and I was just wondering... So far all I have seen is, that ASCOM
is tied to windows OS. Is there any ASCOM version that also works on
linux/unix/BSD. Or maybe "movement" to port it to linux...

Thanks in advance...

Andy

--- In ASCOM-Talk@yahoogroups.com, "Aleksander Rozman" <andy@...> wrote:
>
> Hi !
>
> I am new to astronomy and also to this group...
>
> ... and I was just wondering... So far all I have seen is, that
> ASCOM is tied to windows OS. Is there any ASCOM version that
> also works on linux/unix/BSD. Or maybe "movement" to port it
> to linux...

There is an ASCOM-like package called INDI:
http://indi.sourceforge.net/index.php/Main_Page

As a "movement", one could certainly take the ASCOM standards
definitions and write both client applications and modify the
existing drivers to allow them to be built under some other
  development environment than Microsoft's Visual environment.

have fun
--dick

My mistake Bob.  Yes it was Script 5.6.  Sorry for the confusion.

Jon Talbot


--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> Jon --
>
> I hope it was Windows Script 5.6, not 5.3 (which is at least 4 years
old). If
> not, then do get 5.6 and update to that! I suspect, though, that you
already had
> 5.6, and the install just fixed some bad object registration stuff.
>
>   -- Bob
>

"autostaretx" <rseymour@...> wrote:

> --- In ASCOM-Talk@yahoogroups.com, "Aleksander Rozman" <andy@...> wrote:
> >
> > Hi !
> >
> > I am new to astronomy and also to this group...
> >
> > ... and I was just wondering... So far all I have seen is, that
> > ASCOM is tied to windows OS. Is there any ASCOM version that
> > also works on linux/unix/BSD. Or maybe "movement" to port it
> > to linux...
>
> There is an ASCOM-like package called INDI:
> http://indi.sourceforge.net/index.php/Main_Page
>
INDI is not really ASCOM-like... Somone on their forum asked if it would be
possible to use ASCOM devices through INDI, and answer was that in that case
INDI would need a lot more configuration options, that it has now...


> As a "movement", one could certainly take the ASCOM standards
> definitions and write both client applications and modify the
> existing drivers to allow them to be built under some other
>  development environment than Microsoft's Visual environment.
>
Mhm. If it would be so easy someone would have already done it. It would be
probably easier to create java version of ASCOM, then porting it to linux...
(Not rewriting like they are now, but importing into .NET as C# and then
translating them into java)...

Problem with existing drivers is that some are written in C++ some in Vb...

Take care,
Andy

ASCOM uses Windows unique software.  Porting to Unix is not an option
(or a consideration) on this group.


Ralph Pass

Aleksander Rozman wrote:
>
> Hi !
>
> I am new to astronomy and also to this group...
>
> ... and I was just wondering... So far all I have seen is, that ASCOM
> is tied to windows OS. Is there any ASCOM version that also works on
> linux/unix/BSD. Or maybe "movement" to port it to linux...
>
> Thanks in advance...
>
> Andy
>
>

Jose

Even if it is true, I prefer not to do this, then I'm sure not to
have it...

Thanks anyway

Claude

--- In ASCOM-Talk@yahoogroups.com, "jose canela" <jcanela@...> wrote:
>
> Yes
>
> i you want it I can put itr online (FLI's support sucks)....
>
>
> ________________________________
>
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
Talk@yahoogroups.com] On
> Behalf Of Claude Boivin
> Sent: segunda-feira, 3 de Setembro de 2007 14:42
> To: ASCOM-Talk@yahoogroups.com
> Subject: Re: [ASCOM] FLI filter wheel
>
>
>
> Hi Jose
>
> Yes i'm pretty sure it is...
>
> How can you help do you have this ascom driver ?
>
> thanks
>
> Claude
>
> --- In ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk%
40yahoogroups.com>
> , "jose canela" <jcanela@> wrote:
> >
> >
> >
> > I have the FLI CFW1-8... if i's the same driver as yours maybe I
> can
> > help.
> >
> >
> > ________________________________
> >
> > From: ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk%
40yahoogroups.com>
> [mailto:ASCOM-
> Talk@yahoogroups.com <mailto:Talk%40yahoogroups.com> ] On
> > Behalf Of Claude Boivin
> > Sent: sexta-feira, 31 de Agosto de 2007 16:44
> > To: ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk%
40yahoogroups.com>
> > Subject: [ASCOM] FLI filter wheel
> >
> >
> >
> > Hi
> >
> > I'm looking for a ascom driver for the FLI filter wheel and dont
> seem
> > to be able to find it?
> >
> > Can someone help me on this issue ?
> >
> > Does it exists ?
> >
> > Thank you for your help
> >
> > Claude
> >
> > Canada
> >
>

Ralph Pass:
> ASCOM uses Windows unique software.  Porting to Unix is not an option
> (or a consideration) on this group.
>
> Ralph Pass

True. But the interface definitions are the result of wrestling with interface
agreements, and have proven themselves in large scale real-world use. There's no
reason those interfaces couldn't be implemented in (???) for Linux, and used by
(???) linux-based astronomy software. Leverage off the years of work and
experience that went into the interfaces themselves (which are not dependent on
any OS or language).

   -- Bob

G'day,

I love ASCOM and its extremely useful, but one simple thing seems
missing - basic scope nudges.  Let me clarify and mention the mounts
and software I use.

I've graduated from a Celestron CG5 mount to a Vixen Atlux, and from
Cartes du Ciel to the Sky6 Professional Edition.  I point my Atlux
using ASCOM from the Sky6 using the TeleApi driver.  TeleAPI points to
MaxPoint which points to the SkySensor2000-PC driver.  Almost
everything works beautifully!

The only function that doesn't is the motion controls to slew the
telescope North / South /East or West by a set speed in the selectable
range of 1x - 512x sidereal rate.

The Sky6 gives me two options for small pointing adjustments -
absolute nudges and relative positional adjustments it calls moves.  I
can nudge the scope in any directions by a set angular increment
defined by the Sky6 (arc seconds, minutes or degrees).  I can't
execute any of the relative directional move at a set slew rate.  When
I try nothing happens.

I tried pointing the TeleAPI to telescope simulator, told the
simulator it was a German equatorial will all features enabled.  I
issue an connect, did a few gotos fine.  Next I selected the motion
controls and tried to get the mount to move.  Nothing happens on
relative modes - it looks like TeleAPI isn't sending any commands to
driver.  If I say move East and 64x sidereal - even via the simulator
- nothing happens - it like this feature is simply forgetting to issue
     commands to the driver.

Is this just a simple bug / oversight that can be easily fixed -
because for remote controlled viewing relative movement nudges would
be hugely useful.

Thanks guys,

    Matthew

Could you please look at this and see if it was easy to fix - because
that is all I find missing for remote control in you marvelous software.

Best regards,

    Matthew

--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> Ralph Pass:
> > ASCOM uses Windows unique software.  Porting to Unix is not an option
> > (or a consideration) on this group.
> >
> > Ralph Pass
>
> True. But the interface definitions are the result of wrestling with
interface
> agreements, and have proven themselves in large scale real-world
use. There's no
> reason those interfaces couldn't be implemented in (???) for Linux,
and used by
> (???) linux-based astronomy software. Leverage off the years of work and
> experience that went into the interfaces themselves (which are not
dependent on
> any OS or language).

Could (???) be Java?

Chris

Isn't Script 5.6 itself pretty old?

MS has just released 5.7, see http://tinyurl.com/yu4xkf
(http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-d896-
482e-a0d6-524e7e844d81&DisplayLang=en )


Thank you very much,
    William Boyer
EDS - GM/Global Develop Product - Validation - ModComp support

William.Boyer@...
734-732-9866

-----Original Message-----
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
Behalf Of Bob Denny
Sent: Monday, September 03, 2007 2:52 AM
To: ASCOM-Talk@yahoogroups.com
Subject: Re: [ASCOM] ASCOM issue resolved

Jon --

I hope it was Windows Script 5.6, not 5.3 (which is at least 4 years
old). If not, then do get 5.6 and update to that! I suspect, though,
that you already had 5.6, and the install just fixed some bad object
registration stuff.

   -- Bob



For more information see http://ASCOM-Standards.org/.

To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
TO SUBSCRIBE(!) to:
ASCOM-Talk-unsubscribe@yahoogroups.com


Yahoo! Groups Links

Hi Everyone,

I have tried to connect my HEQ5 Skyscan to connect to starry night pro
6+ and had no luck.

Used the serial interface with a Rj11 lead and adapter (Both came with
my Meade DSI 2 C camera) and also selected Nextstar 5 as a driver for
the Ascom (Com1) but no luck I just get no celestron Telescope
connected (I did select RJ232 connection on the Skyscan controller also).

Any ideas please?

Thanks

James

Bob is right and I have always felt that the interface was valuable.
However, no one has stepped up with Linux (or Mac) software equivalent
to ASCOM.

I do not know if there are any interested Linux developers that would
start or work on such a project.

Ralph

Bob Denny wrote:
>
> Ralph Pass:
> > ASCOM uses Windows unique software. Porting to Unix is not an option
> > (or a consideration) on this group.
> >
> > Ralph Pass
>
> True. But the interface definitions are the result of wrestling with
> interface
> agreements, and have proven themselves in large scale real-world use.
> There's no
> reason those interfaces couldn't be implemented in (???) for Linux,
> and used by
> (???) linux-based astronomy software. Leverage off the years of work and
> experience that went into the interfaces themselves (which are not
> dependent on
> any OS or language).
>
> -- Bob
>
>

--- In ASCOM-Talk@yahoogroups.com, "James" <orionthehunter1971@...> wrote:
>
> Hi Everyone,
>
> I have tried to connect my HEQ5 Skyscan to connect to starry night pro
> 6+ and had no luck.
>
> Used the serial interface with a Rj11 lead and adapter (Both came with
> my Meade DSI 2 C camera) and also selected Nextstar 5 as a driver for
> the Ascom (Com1) but no luck I just get no celestron Telescope
> connected (I did select RJ232 connection on the Skyscan controller
also).
>
> Any ideas please?

Its the wrong cable. The Meade cable will plug in but the connections
are wrong for the Celestron and Synscan.

Chris

---

From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On Behalf Of Boyer, William
Sent: Wednesday, September 05, 2007 8:35 AM
To: ASCOM-Talk@yahoogroups.com
Subject: RE: [ASCOM] ASCOM issue resolved

Isn't Script 5.6 itself pretty old?

MS has just released 5.7, see http://tinyurl.com/yu4xkf
(http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-d896-
482e-a0d6-524e7e844d81&DisplayLang=en )

Thank you very much,
William Boyer
EDS - GM/Global Develop Product - Validation - ModComp support

William.Boyer@EDS.com
734-732-9866

-----Original Message-----
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
Behalf Of Bob Denny
Sent: Monday, September 03, 2007 2:52 AM
To: ASCOM-Talk@yahoogroups.com
Subject: Re: [ASCOM] ASCOM issue resolved
 

 

.