Chris Curran wrote: Yes, my mistake. I am sorry! I dod SO MUCH over the last couple of weeks to get the whole new ASCOM site and Platform going... I just missed this. I thought the file Ajai sent was

Daniel Verschatse: If you know how, look in the registry at HKEY_LOCAL_MACHINE\Software\ASCOM In the right hand pane of RegEdit, look for the PlatformVersion. Is it 5.0? Is should be after ins

Me: Done. The download from the ASCOM Download Center now consists of a proper installer for the driver, instead of the driver EXE itself. It will do everything needed (including the DCOM stuff needed

install the platform's Oh, geeze, I forgot that the package Ajai gave me was just the driver executable. I'll make up a proper installer for this driver now and post when I have updated it on the ASCO

I tried to invite you to ASCOM-Cross but your yahoo id chriscurran doesn't have a real email address, and chriscurran@... is deactivated (on purpose, and I don't blame you). So you can subscribe

Hi Chris -- Both ASCOM and INDI address the same problem: separating device-specific logic from applications. Abstractly, this is the "driver/client model" which has been de rigueur for all devices at

The ASCOM Initiative, now in its 10th year, is pleased to announce the ASCOM Platform 2008 and an all-new ASCOM web site. The new Platform includes extensive support for Microsoft's .NET family of lan

DC-3 Dreams is pleased to announce major releases of ACP Observatory Control Software and its free companion ACP Planner. Together, these two programs provide complete automated observing suitable for

astrokattner: The code in TheSky is not a driver, it is built into TheSky - small point, and it doesn't invalidate your (reasonable) question :-) Dunno about docs, but I an 99.9% certain that the driv

Rick K: Right you are, but one possible clarification: The ASCOM driver standard and the Meade protocol are unrelated. The Meade protocol isn't the basis for the ASCOM driver interface. Actually, ther

Rick Wiggins: Yes. And to make a slight correction to Jim's post, it only happens the first time AFTER ACP IS FIRST STARTED AND FIRST CONNECTED TO THE SCOPE, as opposed to the beginning of each observ

Jim McMillan: Yes - This dates waaaaay back (4+ years) to the Paramount GT-1100, which would cause TheSky (its telescope control system) to get sick and possibly die if you sync-ed across meridian pas

Joseph Dunning: Yes, I believe this is the case with CCD Commander also, and it definitely is with ACP. It's the best way to manage GEMs without the user getting involved (in bed or running via a brow

Ray Gralak: A driver implementing an extended API??? A driver by definition implements a standard. If AP or Celestron or Meade or ??? wants some goodie added to the standard, then they need to join th

OK, I'm outa here. There's already a way to add extensions to a driver: add a proprietary interface with your goodies, publish it, then go ut with your tin cup and try to get whoever to tie into it. I

Paul Gustafson: So, using a planetarium, you would care about more than the telescope pointing where you tell it to and tracking perfectly thereafter? **HOW** it does it is tangential. You've got bigg

Ray Gralak: Yeah, but I was trying to illustrate a point, and anyone can find fringe cases to refute something. The point I was trying to make still stands. Start with a standard interface and use a d

Roland C: OK, let me beg to differ. First, planetariums are not the only programs that control mounts. Programs like MaxIm DL, ACP, FocusMax, CCDCommander, CCDAutpilot, DeepSky 2xxx, etc. also do. Cam

Bob Holzer: To clarify: During a run, ACP never calls the driver's Park command. And ACP has no telescope-specific code in it at all. It does not talk to the serial port. That is all up to the driver

This has been discussed pretty thoroughly, and Larry, feel free to pop in at the DC-3 Dreams Comm Center http://forums.dc3.com/ and discuss ACP specifics. But, here are a couple possibly clarifying bi