Stargazers Lounge Uses Cookies
Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.
Search the Community
Showing results for tags 'ascom'.
Found 13 results
-
Sooo...I'm getting quote frustrated here. This spring I tested my HEQ5 with guiding. The synscan controller was connected to the computer trough the USB plug on the hand controller. This worked like a charm in my living room. On the new controllers you dont need the rs cable. But when I tried the whole thing with guide cameara for some live shooting, it just did not work. I get something wrong with the com port in decice manager, driver not working. I have tried 3 different drivers. The whole thing responded, connected and was guiding when i did a dummy test before the summer. So setup is pc-synscan via usb for pulse guiding. Can it be a problem with windows 10? What t h.... just happened? Where can I find a driver that works? And believe me it worked 5 months ago, argh. Thanks for any respons and support
-
Hello, Last year I developed an 'all sky' imaging application to run my Starlight Xpress Oculus camera (for Oculus owners you can find out more here: https://groups.yahoo.com/neo/groups/allskeye/info). I have recently added 'experimental' ASCOM support for it but don't have any other cameras to really test in on. If anyone is looking for this kind of software and would be happy to carry out some beta testing please let me know. Please bear in mind: The software is really designed for traditional astronomical cameras using longer exposure lengths i.e. not video astronomy and am not sure how well it will work with faster CMOS cameras The software is mono only, no colour images can be processed (although it might be possible to use a colour camera to produce mono images - something I would like to test) It has been running for a while so is reasonably stable but please bear in mind that this will be a beta test so do expect problems! :-) Oh and sorry but it will only work on Windows computers from Vista onwards (no XP) Thanks, Mike
-
Good afternoon, I'm still new to astronomy in general, my setup is explained in my previous post. I am trying to get plate solving working. I can get results from Astrometry.net, and I can get All Sky Plate Solver to solve when given an image file, but I am trying to get it to work with my ZWO ASI224MC direct. When I try "Click, Solve & Sync" I get an error "Camera array data unsupported." I have my camera connected with ASCOM as ASI Camera (1). The Image Type options are Raw8, Raw16 and Y8. Raw16 is selected and seems to be the default. I have tried the others and they all produce the same error. I've tried it with and without MonoBin. Binning is set to 1 and Subframe to 100% (50% tried). Filter is blank. I can connect to the camera in SharpCap via ASCOM (although it warns that it prefers native drivers). I've also tried the SharpCap native Plate solver with the astrometrics install from ASPS, it tries to solve takes a while, but can't find a solution. I also tried AstroTortilla, that reads from the camera but just returns "No solution in 0.0s". I've tried a Google search for the ASPS error but it doesn't find anything. I have checked only one application has the ASCOM camera at once. Any suggestions would be appreciated. -
Ok, after a stalled attempted a few months back, I am now determined to learn how to use SGPro for helping out with my imagining sessions. Going to be lots of questions over the next couple of weeks, and the first one is pretty basic . I am using an Atik One 6 CCD camera which has a built in filter wheel. Does anyone know what driver (ASCOM?) I need to use so that SGPro connects and controls the filter wheel properly? I am proberly doing something stupid, but none the the dropdown ones seem to work .
-
Setting up all the software on my win10 laptop and getting things to talk to one another is a nightmare. I'm starting a new thread, so I can post all the problems I am having, one at a time, so issues don't get confused. This will also hopefully help anyone coming to similar situations later, as the problems and answers will not be interlaced. First issue: APT does not detect ZWO camera. I have got the camera (ZWO) drivers installed and sharpcap can see it and will connect to it properly. However, when I try to connect the camera in APT, the only CCD options it gives me are SBIG (which it isn't), QSI (which it isn't) and ASCOM. Now it shouldn't need to use an ascom driver, because the proper driver is installed, but I give it a go anyway, and this just offers me 2 simulators and 3 QHY cameras (I have one qhy driver installed for the guidecam .... I'll get to that later!). I have disconnected both the filterwheel and guide camera from the camera hub, so they cannot be interefering with the process. I am at a total loss ... any suggestions? Thanks.
-
For those that may have missed this an update to ASCOM platform version 6.3 was released on 17 Jan 2017. Several components updated, new Windows 10 installer (post Anniversary edition) that fixes many Windows 10 installation issues, enhanced .NET support and updated MS Visual Studio templates. Added support for safety monitors and observing conditions interfaces, extended support for new astronomy applications and drivers that have appeared since ASCOM version 6.2 was released. http://ascom-standards.org/Downloads/Index.htm
-
Read more and download: http://www.lightvortexastronomy.com/tweet-remote-control.html Tweet Remote Control is a Windows program written in Visual C# 2015, embedding the Tweetinvi and ASCOM references. It is meant to act as an inconspicuous safety backup, particularly useful to those with remote hosting for their astrophotography equipment. The original motivation behind Tweet Remote Control is for when you lose remote control of the remote computer. This can happen due to various reasons, including TeamViewer failing or their server encountering connectivity problems. It is sometimes necessary to restart the computer, or TeamViewer alone, for example, in order to recover remote control. When all else fails, parking your mount and closing your roof may become necessary measures to protect the equipment against possible collisions and from the elements. It is here that Tweet Remote Control can assist, provided the remote computer has an active Internet connection, of course. This stops you needing to have someone to immediately attend to the equipment physically. Put simply, Tweet Remote Control starts with Windows and runs in the background. It connects to a Twitter account of choice and therefore responds to specific commands, effectively sent by tweeting them via the connected Twitter account. The program monitors this connected Twitter account and reads new tweets made. If a tweet made matches a command written into the program, it deletes the tweet, executes the command received and tweets on your behalf (to update you on what is happening). Since all the program requires to function is a connection to a Twitter account, it need only be running on the remote computer with an active Internet connection - the rest is up to your tweet commands! Many features are supported, including control of ASCOM roofs, mounts and power relay switches (as well as Lunatico Astronomia's Seletek Dragonfly). Tweet Remote Control ensures it always starts automatically with Windows (once you connect a Twitter account, that is), and re-authenticates with Twitter automatically every two minutes. This ensures the program is always active with minimum delay, even if the remote computer's Internet connection drops for a period of time. When Tweet Remote Control starts, if it is connected to a Twitter account, it does so minimised to your Windows system tray as a small, black and white icon labelled TRC. Here, the program will remain with no user input required and with no pop-ups whatsoever. The key is being always-on and always-ready without user input and without hassling the user with pop-ups or messages. Finally, Tweet Remote Control is 100% free. Please feel free to contact me for bug reports or to request new features be added! Current list of capabilities in version 1.4: 1. Restart your computer 2. Shut down your computer 3. Restart TeamViewer on your computer 4. Close an ASCOM roof 5. Open an ASCOM roof 6. Check the current status on an ASCOM roof 7. Park an ASCOM mount 8. Check the current status on an ASCOM mount 9. Open power relays (turn off) on a Dragonfly 10. Close power relays (turn on) on a Dragonfly 11. Check power relays on a Dragonfly 12. Open power relays (turn off) on an ASCOM power relay switch 13. Close power relays (turn on) on an ASCOM power relay switch 14. Check power relays on an ASCOM power relay switch -
I have got a problem with my QHY5L-ii. (1) It works with Sharpcap - so it cannot be the hardware or connections per se. (2) When I try to run PERecorder I get a black screen and the 'configure' button tries to configure my main ZWO camera (which is not connected). Previously it was automatically connecting to the camera in the laptop, which I have now disabled in Device Manager. (3) When I tried to run it in APT, it was not recognized. I discovered I needed an ASCOM driver so downloaded and installed both (capture and guide) from this page (V0141). Now the camera is recognized and appears to work, except that no image is captured [nothing covering front of camera!]. I have followed through the instructions on this page, and (except for the camera selection not being IC8300 - it is "QHY5LII-C-6117d81029b92212") everything goes fine until I click 'start', when it starts going through the motions (on the log screen), but nothing is produced. The preview screen is on(fit) and I have also checked the saved files (which are blank). As both APT & PERecorder are ASCOM-related, my guess is that, if I can cure either (2) or (3) above, the other will be cured as well. And I would also guess that more people are using this camera on a regular basis with APT than PERecorder. Therefore, if there is anyone who uses this camera on APT, who can offer any pointers as to where I may be going wrong, I would be most grateful. Thanks.
-
My first dip into guiding. I've got a DMK2104AU camera on my guidescope, and am trying to connect my EQ6 to my laptop via an RS232-USB adaptor to use PHD2 for guiding. PHD successfully connects to the camera but when I try to connect the mount (I've downloaded the ASCOM drivers for Skywatcher ASCOM), I get an issue in that it says the Port field cannot be left blank. When I go into Device Manager on Windows I can see the Serial-USB adaptor successfully assigned to COM Port 3. However in PHD this just isn't appearing in the dropdown and I can't just type it in. Any thoughts on how I can get PHD2 to recognise the COM Port required for Serial-USB adaptor? Thanks in anticipation.
-
I have a venerable old Meade LX200 Classic which I drive using the Meade LX200 Classic and Autostar #494, #495, and #497 (combined telescope/focuser, 5.0.4) driver on an ASCOM6.1 platform on my Windows 7 Pro 64 bit computer. Last night all was running well with Cartes du Ciel,(CdC) PHD guiding and APT camera control all connected simultaneously with no problems. CdC is used for GOTOs, PHD for guiding and ASCOM talks to the mount for plate solving and for dithering. Half way through the night I shut down APT and relaunched it, only to find that it wouldn't connect to the scope. On testing, I found that in fact this problem was not restricted to APT. What had happened is that I could connect to the scope via ASCOM with any of these pieces of software one at a time, but regardless of the order I launched the software, not two programs simulateously. (I checked that PHD was set to server mode). I have tried uninstalling the Meade drivers and ASCOM itself and installing the latest version of each but I still get the same problem. Ideas? Thanks
-
I have recently bought a Stepper Bee board and stepper motor to build a computer controlled autofocuser. The stepper bee software works like a trean on a PC and the clumsy assembly that I made to connect the stepper motor to the focuser also works fine. Then I started thinking it would be nice if I could find an ASCOM driver that could control the Stepper Bee. that way I could perform automatic focusing. Before I start to develop the code myself I did some search on the internet but could not find anyone who has successfully developed such code. I found a thread about dome control with stepper bee & ASCOM however, and I am thinking perhaps the codes could be similar. Does anyone knows of any code / plug-in that has already been develped? Is anyone using Stepper Bee for autofocusing? I can really use some advise. Thanks, Naeim
- 5 replies
-
- 1
-
-
- stepper bee
- ascom
- (and 1 more)
-
Hi I'm looking for an ASCOM compliant Electric Focuser which I can attach to my low profile Moonlite Focuser which is attached to my Skywatcher 250 Pointers appreciated Regards John B
-
Hi So I use Windows 7 EQMOM ASCOM 6SP2 Cartes du Ciel and for Guiding im using PHD So I set up and align with EQMOD with no issues and then slew to target and image away, PHD does the guiding independently of EQMOD and all is well. If I then try to move to a new target I get the message that EQMOD is not responding so I have to kill Cartes du Ciel and restart. This behaviour is consistent, I have no way of knowing when EQMOD stops responding but it does. So is there any logging within EQMOD that may help track down the issue ? Regards John Berman
