Jump to content

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.

stash_old

Members
  • Content Count

    1,509
  • Joined

  • Last visited

Community Reputation

838 Excellent

About stash_old

  • Rank
    Sub Dwarf

Profile Information

  • Gender
    Not Telling
  • Interests
    Angling
  • Location
    Cranwell UK
  1. Used to but have "progressed" LOL From what you have written I would suggest that the Ascom driver for your version of the camera is either not loaded or the connection is faulty. You say using Atik s/w works with the camera so one can presume that the cable /camera is ok. Have you tried using Sharpcap or APT to verify the the correct Atik Ascom driver is loaded as it could be Astrotilla is at fault as it has not been updated for a fiar time and maybe is no longer compatible with the version of Ascom. If you use Sharpcap or APT (free mode) and they work with Ascom driver for your camera then it would look like Astrotortilla is at fault. If none of the above work with your camera then talk to Atik they may be of some help. Altermative is to use Sharpcap/APT or others which ,if they work in the above test, will give you Platesolving. Bear in mind Astrotilla uses the same platesolving backend as 80% of the platesolving out there - all based on Astrometry.net/Cygwin. ASTAP and Platesolve2 dont but do not have a direct Ascom interface - i.e. you would have to load the the image into the software and then platesolve. I forgot ASPS does have an ASCOM interface and as its uses Cygwin you can use the same index's - it would also test the Ascom interface for your driver - IF LISTED Hope that helps!
  2. Well that all depends - I have started experimenting with narrow FOV EAA (already did EAA before) with a slow F10 /fl2350 scope and small sized chip CMOS camera - I get images(not great quality) on bright DSO's very fast <15secs BUT there is no way I could stack the images in real time as the movement is too great due to the narrow FOV and movement. So in this case guiding would help but then I am not looking for high quality Astro Pic's. It depends what you are looking for - if its Astro high quality DSO images then unless you are prepaid to pay mega bucks for your kit then stick to normal Astrophotography IMHO. I am old school and still believe there is a major difference between EAA and "Normal" Astrophotograhpy . I still support the old views (which no longer seem to exist on SGL) that EAA means Electronic Viewing of DSO's with either no stacking or just real time stacking. But then thats my take on it and others will disagree. There is room for any method but for me, EAA on SGL seems to have become too much like "normal" astrophotograhpy and not near real time Electronic Viewing. Even if KIT is evolving to narrow the gap. Answer to your Questions IMO 1). guiding - not needed but doesn't cause problems either with EAA 2). Mount - alt or EQ will work BUT as with any mount it should be able to carry your kit with ease as you stated. 3. Camera - Mono is better as its more sensative. But I have(still do) done DSLR EAA with Astrotoaster live stacking no problem but confess to guiding(due to using DSLR) depending on the other factors invovled - DSO brightness,Wind strength,Sky quality,kit etc 4. Scope - as fast as possible but there are many variations/combinations is use with EAA. 5. Deep pockets - its can be very expensive as with all Astro stuff - if you let it 6. Portability - if you intend to work in the field or at remote dark sites. EAA with a small ALT Mount,Fast Wide Lens or small fast scope can give great views of the night sky. Continue doing your research as more time finding facts and deciding if EAA meets your wishes the better IMO. Clear Skies
  3. The Prolific chip set are known to be Crap - tech term - when used with Windows. You originally said you bought one of these Lynx Astro FTDI EQDIR USB which is NOT prolific chip. its a FTDI chip which ,if genuine, is know to have very very few problems with Windows 10 (or Linux or Mac). Put the Prolific chipped cable in the correct place - The Bin - harsh but just look at the hard facts - these chips cause problems (especially the older ones!). The Synscan software and Ascom are being used by lots of people happily on Windows 10. The odds are in favour of the software being OK. Thats why FLO/Lynx stopped selling Prolific based USB cables. Rebooting is useless when you have hardware problems - best always to power off ,count to 30 and switch back on without the new cable (non Prolific) being inserted until Windows has loaded and got its head togetner. Anyway Good luck. Clear Skies !
  4. And any help can only really be given with Screen prints as stated before of your step by step workflow etc. Ascom drivers are only used by clients - e.g. APT ,CDC etc so loading Synscan App PRO (and it has to be PRO version) does not depend on Ascom at all and wont cause issues no matter what state Ascom is in. You have installed ASCOM haven't you? - thats not the sysscan ascom driver but the base Ascom software - here on the web page right hand side. https://ascom-standards.org/Downloads/Index.htm If you have there is a Diagnostic program you can run from the Ascom menu which will check your installation and show any errors - maybe you should run that and see if it gives any errors . The only other thing to suggest ,besides checking event viewer , is to check Windows permissions ! The older version of Ascom installer did have some problems with not installing C++ Dist from Microsoft but I beleive this is not the case today.
  5. 1. You can either - an ASCOM driver is the only bit of software that APT will use for the NEQ6 - in which case you have to use/install EQMOD(ASCOM) then restart your Laptop. Then start APT press and hold SHIFT key + press CONNECT(only needed first time) - then choose EQMOD followed by properties when the EQMOD/ASCOM little Window appears. In the properties you have to input the correct COM port. Then you can load your Planetarium program and choose the same option (e.g. EQMOD) but dont select Properties just click OK. OR (and do not mix drivers and APP) start the Synscan App and connect to the mount via the Synscan App connect method THEN start APT as above but select the Synscan Mobile Ascom Driver - select the properties and select the IP address where the Synscan App is running (normally 127.0.0.1 if on the same PC). Then start your Planetarium software and select the Ascom Synscan Mobile driver BUT dont select the properties. If you use AUTO search you will be presented with any IP addresses the APP finds which you have to select the correct one - hence I used to use manual and input the correct IP address - As I say 127.0.0.1 works. The normal reasons for either of the above not working is software not installed correctly including C++ dists, you choose the wrong COM port or IP address. Sometimes Virus software and or Firewalls can block IP type work (normally ok if you use 127.0.0.1). As you dont provide any screen prints (e.g. Version numbers of software ,Device Manager,Ascom Driver Window with properties input etc) it is not really possible to help further in detail This is normal APT can only use ASCOM (last time I looked) - so no ASCOM driver (Synscan Mobile Ascom Driver) APT will not work with Synscan APP. You cannot for example try to use the EQMOD ascom driver with Synscan App loaded and connected to the mount. The reverse is also true! See attached - ok I am using Synscan App emulator as PC is in the house not in the Obsys. If the emulator route works then all you have to do is connect to the mount via Synscan App using the correct Com or Wifi port first the rest is the same process. Note I am not getting into the using the Handset as well as discussion - let someone else do that! BUT readme notes say :- Overview The SynScanMobile Telescope ASCOM driver is an alternative to the SkyWatcher Telescope ASCOM driver for controlling Sky-Watcher telescope mounts. SynScanMobile ASCOM driver requires the SynScan App, whereas SkyWatcher ASCOM driver requires the SynScan hand controller. During use, the SynScanMobile ASCOM driver controls the SynScan app. The SynScan app, in turn, controls the Sky-Watcher telescope mount. How to setup connection to mount Step 1. Connect SynScan App to mount Open the SynScan app on your smartphone. Use SynScan app to connect to the mount. See SynScan App's help for more details. You need to perform telesope alignment with the SynScan App before the mount can perform accurate go-to. If SynScan App is running on iOS, you should make sure the app is running in the foreground with the screen unlocked. Step 2. Connect ASCOM driver to SynScan App. Run program that uses ASCOM (such as Cartes du Ciel or TheSky) on the PC. The PC should be in the same network as the device running SynScan App. For example, if the phone running SynScan App has joined a SynScan Wi-Fi adapter's network, then the PC should also join that network. If there is problem with searching device, you can specify the IP of the device running SynScan App. ASCOM driver parameters Read timeout: How long to wait for response from SynScan App before reporting error Max retry count: How many times to wait for response from SynScan App before reporting error Shorter timeout and fewer retries lead to more communication errors, but longer timeout and more retries can make some program less responsive.
  6. use this https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/usbview perhaps might help
  7. https://support.simulationcurriculum.com/hc/en-us/community/topics :-)
  8. Yes but not simply (end user style not geek level) , Ascom Alpaca is a pain to set up IMO - hence the very very slow uptake. Indi works well on more than just PI - any Linux box and of course MAC. Why do I want a Web server and another protocol layer (REST) when Ascom and Indi are messagenging standards not comms std's. Sorry IMHO Alpaca will not take off (famous last words ) Alpaca is an Addon to solve a comms problem. Indi is far more versitile IMHO and supports many many more hardware products across more OS NOW - not just PI !. "Ascom isn't limited anymore" - The main part of Ascom still only runs on and only on Windows - end of story! Maybe someone will port Ascom to Linux etc I grant you Indi can be "flakey" in some area's but ask anyone on SGL about Ascom/Windows/USB(both native and serial convertion) problems - a good number of people have had many frustrating issues over long periods. An example - Prolific/CH340 (and others) chips that dont support unique serial numbers. I think we say have to agree we have an healthy difference of opinion But time will tell and good luck to whatever route people choose
  9. IMO as I have stated before the problem is not Ascom std but the comms layer as this relies on Serial or USB coommunications neither of which is a network protocol , run across neworks or run long distances - without some hardware/software converters - e.g. usb over ip ,Virtual Serial emulators etc Sky Watcher and Robert Brown WiFi Focuser are the only 2 OEM's (that I know of!) who support ASCOM via IP or UDP. E.G. you can run Synscan App Pro on a remote Winodws PC(mini and the like) but use the SW Synscan Mobile Ascom driver on another Windows PC allowing CDC,APT etc to control the mount which is not connected to the same PC. Doesn't requires Ascom on both PC's (Roberts doesn't require a 2nd PC at all as it use ESP32 Wifi and his own Ascom driver that has IP built in) and no Alpaca required - both therefore are very simple to set up and run very well.
  10. Zwo for one - thats what ZWO use in ASIAIR(Pro) - hence they support all the ZWO camera's as they use the ZWO supplied API/SDK for Linux !
  11. Extra software/comms layer that allow Ascom and hardware to run across many platforms and OS's as one unit - at the moment without Alpaca, Ascom can only run on one PC and all the hardware has to be connected to that PC to use ASCOM devices/drivers. There are a few exceptions! As yet ,as far as I am aware, very few Alpaca aware devices exist and I know of only 1 piece of software ,CCDCIEL,that allows connection using Alpaca. You can set up Alpaca to use existing Ascom devices across different PC's but they will tend to be on Windows OS only. - last time I looked.
  12. Then try and older version - see bottom of Pipp web page - it maybe you dont have the correct (being Win7) graphical interface software (or other C++ dist problem) OR the latest Pipp doesn't work with Win 7 and older Wins. There is an email on the Web site perhaps asking the author you will get an answer. Plus check your logs and see if there is an answer/pointer there. Plus some anti virus software are paranoid and will not allow some software to run - try scanning the program/directory folder with whatever anti virus your PC uses! Although the site does say " Current supported platforms: Windows XP with Service pack 3 or all later versions of Windows."
  13. Assuming you have downloaded the correct version 32 or 64 bit (later only works on 64bit) it could be set to "read" only in permissions (Windows 10 now comes up with a blue screen). I loaded the latest today and there was no problems - but that was on Win 7. I presume the extract worked ok - as it comes in a ZIP file.
  14. Used an old Canon 28mm FD lens attached to ZWO camera - unfortunate comet was over Lincoln/RAF Waddington lights . Sharpcap converted SER files via Pipp 00_05_22_pipp.avi 00_16_23_pipp.avi
  15. Stuart it just needed to have a nice Barn Owl caught as well !
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.