Recently Browsing 0 members
No registered users viewing this page.
The Stellarium team are delighted to announce the release of Stellarium 0.21.1.
The major changes of this version:
- Updated designations of stars and handling of list of designations and common names those stars
- Updated Almagest and al-Sufi skycultures
- Many changes in plugins
- Many fixes in core and plugins for support HiDPI devices
- Enhancements in visualization of markings and in scripting engine
There have also been a large number of bug fixes and closes feature requests and enhancements (see full list of changes).
A huge thanks to the people who helped us a lot by reporting bugs!
Hello fellow astronomers, I have come to the forums as I have depleted all other options.
I own an NEQ5 GoTo with a Skywatcher 72ED. I have connected the mount to my computer using an EQDIRECT cable.
I am trying to use stellarium with ascom and eqmod to slew the mount to a desired object. I have configured my scope using the “telescope control” plugin in stellarium. In the past I had successfully achieved slewing through stellarium.
The problem is that now, one month later, when opening stellarium and trying to slew the telescope to a selected object (using either the “slew telescope to” panel or the shortcut (control + 1)) the mount moves for a fraction of a second and then stops, stellarium freezes and then the scope indicator in stellarium slides quickly to the horizon, and EQMOD control panel displays “horizon limit horizon limit” error. (Let’s call this the “main failure mode”.)
Note that :
I can use EQMOD and slew the scope manually without problem. If using it in tandem with stellarium, when I do so the scope indicator in stellarium moves without issue.
I have used the “resync encoders” button on EQMOD to establish the home position, but this does not affect the behavior.
I can use ascom device hub to slew the scope manually without a problem as well.
The main failure mode described above happens most of the time. However, I sometimes get other erratic behavior in stellarium:
Sometimes, when trying to slew the scope in stellarium, the mount moves for a second then stops (as described above), yet the scope indicator in stellarium moves to the selected object not the horizon, then the mount starts to track (even though it has not yet slewed).
Or, rarely, when trying to slew the scope in stellarium, the mount physically moves (seemingly to the object) and starts tracking, the scope indicator moves to the selected object -- appearing to work normally. But then, when trying to slew the scope a second time to a different object, it fails again as described in the main failure mode above.
I have tried opening stellarium as administrator but I still get one of the three outcomes when trying to slew.
Does anyone have any insight on this ?
Not strictly astro-gear but I took a look at the rules and didn't see any restrictions.
If this is a problem please just let me know, or remove it.
2009 Mac Pro 4,1 upgraded to 5,1 firmware.
2x X5680 3.33ghz CPUs - 12 cores total. 24GB (3x8) 1333mhz DDR3. AMD Radeon RX570 4GB. Apple GT120 GPU included (for recovery/boot screens) 256GB Samsung SM951 AHCI SSD on 4X PCI-e card (1) 256GB Samsung 970 EVO NVME on 4X PCI-e card (2) One CD/DVD R/RW/DL reader/writer. (room for two). Both SSDs do approximately 1400MB/s each way.
Plenty of room for additional internal storage, with 4 X empty 3.5" bays.
Latest officially supported OS is 10.14.6, which will be installed and up to date.
UK postage is an option - I have the retail packaging plus a layer of polystryene and additional outer box.
Buyer assumes all postage related risks. Can send plenty of packaging photos in advance.
Lovely condition - very clean - no dents or noticeable scrapes.
Less than two year old PSU and new replacement logic board.
UK + Bank transfer only - Looking for approx £800 but willing to talk.
Edit #1 : Pictures and further info.
Northbridge plastic retaining clips are a known point of failure on 4,1/5,1 Mac Pros.
This one had the clips replaced with metal nuts + bolts before there was any problem.
Custom fan curves always kept NB temps at 50 or below.
I've just been reading through the thread about scammers etc.
Perhaps I should have said while my post-count here is low, I've used the same name online for many years,
and am long-time admin of a pretty popular forum.
I'm not going to advertise that here but if anyone's interested in this machine I can send some links for character reference.
I also have 100% on ebay (800+) and would be happy exchange messages from my account, for confirmation.
I've recently started astrophotography, and after beginning with a DSLR and rotator haveprogressed to an EQM-35 GoTo mount and Zenithstar 73 telescope, with Ascom control and guiding with PHD2. While I've got some decent results, I've consistently had problems with guiding, even though I've tried adjusting the mount as described in online videos to remove backlash, and unbalancing the telescope. Initially there was obvious backlash that I could feel; I've now eliminated that, although I notice that the stiffness varies with declination (something I've seen reported by others), and it's almost impossible to avoid backlash at some declination angles without making the mount far too stiff at others.
While I'm aware that this type of mount is always prone to backlash issues, what I'm seeing is still different to what I'd expect. If I drive the mount, say, North (either manually or as part of calibration or guiding), stop so that everything comes completely to rest, and then drive the mount South, what I see is that it continues to move North for a while before beginning to move South as expected; the behaviour is exactly the same if I start moving South then switch to moving North. The attached image is part of a typical calibration from PHD2 Log Viewer to show what I mean. As you can imagine, this completely messes up guiding unless I offset the polar alignment and guide in one direction only, or align very accurately and switch off declination guiding altogether.
If this was simply backlash, I'd expect the mount not to move at all initially after switching direction rather than to move the wrong way, and I can't think of a mechanism to cause this behaviour. I'd be grateful if anyone can explain this, please, and give me some advice on how to cure it.