Stephane, OK, no problem! I think it's great that you are double-checking the driver. If you find anything else I missed I will gladly fix it! :-) -Ray

Hi Ray, Oh sorry ! I have read too fast. Please, forget this message. Stephane

Hi Stephane, CanSetPierSide is properly set to false because you cannot set the side of pier with the driver. SideOfPier is read/write but will throw a "not implemented" exception if you try to set

Hello Ray, I have posted in "files/ New ASCOM driver/Stephane's LOG" : CanSetPierSide.zip In fact, the property SideOfPier exists but when I look at the standard Telescope 2.0, I think the read-only

Alex, If you know the COMM port exists and you get that error message then the problem may be that your bluetooth device is using a buggy version of the .Net Framework that does not properly expose

Ray, Sorry, if I was not clear. I did not try both programs at once. One at a a time PEMPro worked and PulseGuide did not (where "worked" means "established communication with the mount"). I even

Hi Stephane, Thanks for reporting that solved the problems! Let me know if you find anything else. :-) -Ray

Alex. Not sure if this will make a difference but the baud rate must be set to 9600 to communicate with the mount. -Ray

Roy, Actually, AP talks about folks using the 6v out as a source for bluetooth serial. I had an old "FireFly" bluetooth serial adapter that I unsuccessfully attempted to use with a Sirius mount. So

Ray, Yes, this new driver fix the issues ... Thank you Stephane

That's what I thought. I have never tried it but don't see any problem running it on either side. Where the picture of the mount/scope set up was taken, was that a campground? Nice to have power so

Thank you Ray, I will try it as soon as I have time (this evening) and tell you if it works fine. Stephane Ray Gralak (Yahoo Groups) a écrit :

Hi Don, Thx. I figured I'd run it on that side so I can run most of the other cables (serial, hand controller, power) on the west side. It gives me a side where no cables will be moving so less

Hi Stephane, I just uploaded v4.99.46 to the files section. It should fix the two issues you reported (no tracking rate changes after park complete, and AtPark status after unparking) -Ray

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the ap-gto group. File : /_New AP ASCOM Driver/AstroPhysics V2 Setup

Great shot Danny! Very nice for first time out. Nice compact set up. I noticed you have the Dec drive motor cable on the East side of the mount as opposed to the west side as is standard. Any reason

Ray I was able to get the icon back. I had unchecked the 'switch to night vision mode on link'. When I do that, the icon isn't there. When I put it back, the icon shows up. go figure. Mike

Mike, You have to use the icon once minimized. You may wish to go to the setup dialog and set the option to show the handbox when connected (instead of the icon in the system tray). BTW, windows

In the task manager, the APV2 Driver is also in the list (of course). If I try to bring it to the front, though, nothing happens... Mike

It's there: astroPhysics V2Driver.exe is in the Process list