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.



  • Content Count

  • Joined

  • Last visited

Everything posted by stash_old

  1. Canon 100d and SCT 9.25 works well enough - I do EAA with it so dont collect hrs of data. 100d is smaller and lighter than most and is well supported by the usually software BYEOS,APT and Linux Gphoto (Thats what Ekos/Indi uses in the background for Canon). The Sony mentioned above is far superior IMO but just isn't as well supported. The above was from a moddified 100d but short 30 or 60 secs exposure live real time stack in Astrotoaster .
  2. Wow cowboy - RS232 is not the same as TTL and you say you want to use your mount WITHOUT the synscan controller - do you mean without the handset ? Most mounts are TTL levels (3.3v or 5v) RS232 is +12v so be careful. If your want to connect PC directly to your mount (which is ? i) then you are using TTL levels (3.3v or 5v) and you can use the Lynx device from FLO £34 plus delivery. If you can use a soldering iron then one of these https://www.ebay.co.uk/itm/USB-to-TTL-Serial-Cable-FTDI-Genuine-chipset-3-3V-Black/292513285005?epid=1342449592&hash=item441b26838d:g:110AAOxy63FSrs93&shqty=1&isGTR=1#shpCntId prices shown is £12 + £3 del to Brazil - note if your mount uses 5v then same site have 5v version. Then just solder together 3 wires (need to check on EQDIR site for mount wiring details) - thats tx,rx,ground to your existing DB9 cable (which I assume is the mount end in your case). Just double/triple check you are using the correct wire. If it works (and it should) you can then use some heat shrink to cover the joins (which you cut and installed ready for the heat before soldering LOL). Note the above cable is a real FDTI cable not a "clone" hence the extra price but still cheaper than Lynx set up (you could buy a spare and still be cheaper). If you want a cheaper version then CH340G chip set are ok but you can have problems when using more than 1 at a time ! Lots of people on SGL and Cloudynights etc have done it with no problems!
  3. No other simple way works better or as quickly than using Platesolving - it tells you where you are and nearly (nothing is perfect) always will get to where you wanted to be AND if required dead centre an object in even the smallest FOV. Note it only gets you there what, happens next is outside the design of what Platesolve is for! BUT it does require a computer !
  4. +1 for you comments - i do the same - but dont tell the Indilib crew as they think we are just viewers "playing" (ok a bit hard maybe) at Astronomy and dont seem to understand EAA/EVAA at all IMO EAA to them seems to be limited to visitor exhibitions use! Plus a comment was made about why use Astrotaoster at all as "DSS live view is better" ! - would be interested in EAA / DSLR users views on DSS Live View vs Astrotoaster. Each to his/his own methods/views but "others" please dont put other methods down (not aimed @Howie_OZ) its all Astronomy Han's of ASTAP fame has created a "live view" version/ add on that might be interesting! Runs on Win and Linux I believe ! @Howie_Oz - tomorrow hope its a great game! On next camera I go with Howie's comments too but add how about "playing" and learning more with your existing kit!
  5. this shouldn't happen if its a true FDTI chip (as opposed to a clone) as the real chip and driver have a unique serial number which is recognised after you have installed the driver once. Moving USB sockets should not make any difference as it follows the serial number of he USB device. The same goes for Linux. Thats why you pay extra for a real thing. https://stackoverflow.com/questions/13741853/how-to-get-stable-com-ports-for-usb-serial-dongles-in-windows-xp still applies to Win 10
  6. if changing the com port in EQMOD as suggested above (DO NOT USE the search button) (after checking what the actual com port number is displayed in Device Manager - just in case its changed again) does work look at your cable ends and if using DB9 check for bent or missing pins. To test the adapter you can download Putty from the web - some virus checkers will complain but you should be able to scan the file - then loop rx/tx pins (harder to do if you mount end is RJ45 ). you then use Putty to talk to itself (hence the looping of TX/RX). Use connection type "Serial" on putty and this will then allow you to change the Com port to whatever your device number is shown in device manager. Whatever you type should be shown in Putty's window the adapter is working. If its working wiggle the cable in case you have a bad connection and see if the connection is dropped! If the later all works this would point to the Mount or the cable is wrongly wired!. If it fails have you another PC or a Astro friend to test out your cable and mount in case your PC OS software is corrupt! You have't displayed an image of the USB Adapter are you sure its a "real" FDTI and the voltage is the correct level (5v or 3.3v) depending on your mount . Plus I am assuming the Atlas Model(and firmware level) is supported by EQMOD - I think they are supposed to be the same as SW!
  7. Its the same on all serial connections - std is to quote std pins - e.g. TX means transmit only , RX means recv only - thats why you have to connect TX - RX and RX - TX. Well nearly all ways - some only have 1 wire which acts as both TX/RX but thats another story. Obvious if you know but well done for spotting it Its been like this for some +40yrs Glad you got sorted.
  8. How do you know it works on any machine - have you tried it. Try changing the cable. The is no reason why a working 450D is not recognised if everything is installed correctly. Very doubtful its anything to do with a correctly set up Win 10 O/S. Do as @kev m suggests.
  9. yep Julian is 100% correct suggest others carefully read the doc info first "If it aint boke dont fix it" - Vast options ,well tested software and created ,as I have stated already, created by M/S employee's AND I think he implies Windows's OS by saying RDP and BackyardEOS If we are talking multi OS then you are correct But as always the individual chooses what is correct for him/her
  10. The big problem with copying between computers is you dont want to kill all other network traffic - some copy applications do. This site provides the Front End GUI's for Robocopy which provided more than options to "hang your pc" - Again like Robocopy - Richcopy (Front end GUI to Robocopy) was also written by M/S employee https://www.howtogeek.com/130729/add-a-graphical-user-interface-gui-to-the-microsoft-robocopy-command-line-tool/
  11. If its Windows then +1 for Robocopy - as it was written by an M/S employee and good few years ago
  12. What R26 means is that your mount is NOT compatible with the £5 device as he thinks it uses RS232c voltage levels which are 12-25v and is something completely different to the TTL levels the £5 adapter uses (3.3v or 5v). However it would seem the DB9 on the mount is the same as EQ6 so that may be wrong. If so ,and you need to check , then the £5 adapter should work if connected ,has the correct voltage (3.3 or 5v) and you have wired it correctly - maybe this site will help you http://eq-mod.sourceforge.net/prerequisites.html
  13. No need to wait for clear skies - if you have some old images try them out during the day to test your settings - too late in the dark or when loosing valuable clear skies
  14. some more confusing details but might help - Not as i understand how eqmod works (which could be wrong LOL) . AT should ,if using Append mode (not dialogue) in EQMOD and using 3 point,you should see a point added - in Dialogue/nearest point I think it adds values (offsets) to DXSB/DXSA. I try and create smallish triangles of solved points around an object if I am having problems which in my view should make find a point within the area easier to goto - but it doesn't always work. Everyone ,except the authors, are still learning I guess - must have read the Help PDF "n" times and still not 100% clear in my mind. You can of course add lots of Sync points from either CDC or AT (or even manually !!!!) and see the result in the extended EQMOD window if you click the "Spanner" then click the "Points list" then click left or right mouse buttons. If it works for you use your own working workflow! But as you have found when it all works its great
  15. What are you doing with EQMOD - i.e. What Point alignment method are you using and are you clearing out the saved alignment points each time you start? For example creating bad alignment points or using "old data" when using a mobile set up can "screw up" the modelling. I even have to clear old EQMOD alignment data during session sometimes. You will probably see the Telescope pointer in CDC not move or "jump" mear to the target and AT will just give the same solved RA/DEC coordinates. Are you using CDC to Sync as well as AT ? Check CDC set up date / time - I have on occasions found its time out by a good few minutes even though it says its using System time - so I now use the "refresh option" and set the refresh to every 10 secs. Perhaps reading this may help http://forum.mainsequencesoftware.com/t/help-from-eqmod-users/2485/47 p.s If you dont know Chris Shillto is the EQMOD author (or one of them) Regarding PC O/S updates - Tip is start your PC well before you are going to use it to allow for any updates or disconnect your network or device from the Internet before starting. Also change the times Windows can do updates - doesn't stop updates totally unfortunately. There are loads of other methods to restrict Microsoft from doing its thing - google it
  16. Attached Prolific own spec - see Serial number mod is disabled but clearly explains why its needed Perhaps FLO can use its contacts for an official Sky Watcher response - to put peoples minds at ease
  17. Last time I looked even genuine Prolific devices don't put a unique serial number in so Windows and Linux have problems identifying the hardware if using more than one device with a Prolific Chip. Same problem with other Manufacturer's e.g. CH340G etc If someone can confirm that the serial number is now unique that would be handy - I cant find any info other than there EEprom writer disables this field for amendment - but maybe its now unique already This is for the PL-203HXD chip which Prolific recommends Obviously I dont know what version of Prolific chip Sky Watcher is using but "once bitten etc"
  18. IMHO a mistake by Sky Watcher - they seem to be using Prolific chips in the above new devices. People with Windows (Linux works ok with Prolific - just if you use them singly ) will remember the problems with Prolific driver chips. EQdir and Lynx ,I believe, all changed from Prolific due to same problem. Maybe Prolific have done major work on Windows driver compatibility so when Windows do an update they dont stop working! I will be steering clear of them and sticking with genuine FDTI chipped devices. Hope I am wrong so only time will tell.
  19. I dont know as I have always used it via an application - Ekos CCDCiel etc. I assumed that there was a Web interface ,as per Astrometry.net, only local IP - e.g. but I have never tried that route. But it does have a simple for configuration Besides ASPS ,Platesolve2 and Astrotortilla both have their own application front end. NOTE ASTROTORTILLA does seem to be able to use ANSVR version of Astrometry- never noticed before always assumed it was yet another version of Astrometry - So there's a front end! P.S. Had a quick look at Ansvr developer notes you could create a simple script as it seems putting an image in %LOCALAPPDATA%\cygwin_ansvr\temp\ folder and running Solve-field with parameters (see developes notes at adgsoftware.com) will provide a stars.wcs (fits) format file which includes RA/DEC I guess. Perhaps an email to the author will help you with a more "user friendly" application. Real example attached - well just the start up Sorry thats not too helpful. new 1.txt
  20. And using AZ not EQ Mode and unguided - very impressive Martin
  21. If you use that already then ANSVR is exactly the same engine only local (i.e. no internet) but remember to set up all the Index's required - safe bet download all and remove ones, to another directory, you think you dont need - less index's faster the solve time but you can copy them back if you change FOV. Else download ASPS (All sky platesolve software) which does "Blind solving" and has simple set up aids Solve times will depend on FOV and PC Hardware (SSD makes a big difference !) so dont take other peoples times as the std. Use any sim (even during he day) set up to test Platesolving whatever you use to get the feel BEFORE you go I presume Windows o/s as you didn't say
  22. Yes everyone has at sometime or other especially with any cheap Asian copies. As Julian said FDTI chipped (genuine) dont have a probem with Win once driver installed. Most other chipped USB/TTL/RS232 do not have a unique serial address so poor old Windows gets confused. Not Windows fault blame manufacturers for not putting the serial id - note same problem on Linux - Udev cant fix it only by position in hub. Note you cant use FDTI driver with a Prolific chipped USB adapter - software driver must match hardware. Without doing ANY changes just try plugging in USB devices one by one with a pause to let Windows reinstall the driver if it was there before. No need ,in most cases, to install new driver when it worked before! So with no other USB device plug in the USB to HC ports Adapter and try getting Scanscan App to open the serial port. Use Device manager to see the port number (i.e. COM1,com2 or com3 .... etc) Also note the connection from USB on PC to Handset is true RS232 (voltages 12v+) and this is NOT the same as directly connected from USB on PC to mount (i.e. NO handset) this uses TTL level (5v or 3.3v) depending on mount. Obviously Sky Watcher Wifi and the like type mount connections dont use USB adapters at all so dont suffer from the same kind of problems with drivers.
  23. I have used Astrotortila,ASPS,Platesolve2 (ASPS/PS2 only via APT) ,Local Astrometry via Ansvr,ASTAP(latter two via CCDciel and Kstars/Ekos Astrometry.net local. All have problems and are never 100%. I am currently moving to CCDciel for my DSLR which has access to 4/5 platesolvers(most of the above) and a very nice Sequencer. Main problem with CCDciel is it depends on the FITs file containing the RA/Dec info to do Platesolving - so my older CR2 files when converted to FITs do not have this info. Not a big problem for new images taken via CCDciel. With CCDciel i have decided to stick with ANSVR which is pretty good.
  24. He is using EQMOD so will not (cannot) be using Synscan App @Stickfarm8 I think if all your settings are correct and you are reasonably Polar aligned and you have NOT saved the previous alignment points in EQMOD you would be close - IMHO there is no point in saving the EQMOD alignment data between sessions if you have a mobile set up - as I say my opinion. However even with Polar alignment its not guaranteed to be "accurate" every time all over the sky hence why many use Platesolving to speed positioning and centring of objects. I can blind Platesolve in under 1 min and there after normally under 20 secs (my best about 6 secs). Platesolving cuts out most of the frustrations (not all ) of getting objects centred quickly - ok some would say lazily . BUT Platesolving involves a camera (DSLR,CCD etc) and so is not much use to visual only users.
  • Create New...

Important Information

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