2 October 2020 at 4:30 pm #574747Nick AtkinsonParticipant
I have a Pulsar 2.7m Dome fitted with The Pulsar Dome Drive for the Azimuth and Shutter for the altitude the later linked by Bluetooth. My 6″ F7 refractor is using ring mounted on my faithful Astro Physics 900 mount. Recent upgrades incluse replacing the optical sensor with a magnetic activator and installing an AP GTO 4 box with Astro Physics Command Software (APCC). APCC has its specific ASCOM driver with SKY X linked by APCC virtual port.
Rather than using Pulsar on software, the idea of using SKY X Dome to slave the dome to the telescope appeared attractive. Using Pulsar Rigel Software for the Azimuth worked well until the telescope was close to the meridian when tracking moved too fast when set at sideral rate.
No issues arose when installing SYX dome control I did my best to work out the factors necessary to measure the radius plus the various offsets, shutter dimensions etc. Slaving the dome worked well until pointing to the meridian was reached on either side. Now the telescope is 50% obscurred. I tried various changes to the offsets withoout any improvement.
It maybe this issue I common to other domes on the market. The mathematics are quite complex.
Has anyone been more successful?4 October 2020 at 3:07 pm #583203William BristowParticipant
The SkyX dome setup is fairly well described in the manual (with one exception, see below) but here are a few tips from my experience using the smaller 2.2m Pulsar dome, the current Rigel dome controller and ACP/MaxIm with The SkyX and a Paramount.
Firstly, the dome driver (ASCOM or X2) does very little other than drive to a commanded AZ angle and open/close the shutter, the actual calculations for the position of the slot relative to the OTA are all handled by the observatory control program, in your case TheSkyX.
While the ASCOM driver for the Rigel dome controller works well in both ACP and MaxIm I found that it was unreliable and rather erratic when used with TheSkyX. I think this is a SkyX issue and nothing to do with the Rigel ASCOM driver and you will find TheSkyX X2 plugin for the Rigel dome controller works more reliably. I use the X2 driver when operating the dome via TheSkyX, for instance when building a T-Point or PEC model for the Paramount, but when running the dome normally under ACP/MaxIm I use the Rigel ASCOM driver where it performs well (in this configuration the dome is controlled by ACP and not TheSkyX).
You can download the X2 driver for the Rigel dome controller via the RTI-Zone website here.
Install the X2 driver as described in TheSkyX manual and select it in the dome setup tab, the geometry settings you already have remain intact.
Measuring accurately when configuring the dome geometry is vital for good OTA-slot alignment. You have to measure to within +/-5mm the mount and optical axis offsets and be sure to set the offset value signing correctly. Beside the mount and optical axis offsets the dome home-sensor offset setting must produce a real AZ value for the slot centre line that is within a degree of the displayed AZ value. To determine an accurate north reference I found using a compass bearing with lots of buried rebar in the dome concrete pad was useless with at least a 7 degree declination from true north at my location. For both pier and dome I used the local noon solar transit shadow method to determine true north, marked that on the dome wall and based my measurements for the dome home-sensor offset from that.
In TheSkyX dome setup there is one poorly explained setting that is critical for alignment between the OTA and the dome slot. In Dome Setup, Preferences, you will find the setting “Minimum angle from slit edge to telescope position” and it is not explained in the documentation how to determine the angle.
The starting point for calculating that setting is the formula: Arctan((L-D)/(2R)) where L = Width of slit in mm, D = Effective diameter of the OTA in mm (including guide scope if applicable) and R = radius of the dome in mm. Enter your calculated value in the box for “Minimum angle from slit edge to telescope position” and that should be a good starting value to ensure that the OTA optical axis always remains close to the centre on the slot. If you find any remaining overlap between OTA and slot then increase that value a degree at a time until the overlap is no longer present. For my current 100mm OTA = the calculated value was 8.58 deg and the actual value required was 12 deg to ensure that OTA and separate guide scope always remained aligned with the slot on both sides of the meridian. If that angle value is set too high or too low then the OTA will overlap either edge of the slot on both sides of the meridian.
Lastly, when driving the dome from TheSkyX the Rigel controller should be set to 0.00 sidereal rate on the control panel otherwise TheSkyX and the Rigel controller will argue over who is in control and the dome will oscillate continually. When driven from TheSkyX the dome does not continually track at sidereal speed but it moves in a series of incremental updates, the larger the diameter of the OTA relative to the size of the dome slot then the incremental updates occur more frequently. For my current 100mm OTA and 560mm width slot the dome increments about every three minutes, when I use a 350mm diameter OTA the dome increments every thirty seconds.
When setup correctly TheSkyX and the Rigel dome controller work well (using the X2 driver rather than the ASCOM driver) and I do not experience the overlap issues that you are reporting.
Hopefully there is something above that helps.
William.10 October 2020 at 5:03 pm #583233Tim HaymesParticipant
This is a very interesting conversation. In the example of the Pulsar Dome and Rigel controller, i would be interested to learn if anyone has used the LesveDome software and POTH, as described in Sky at Night Magazine 2018 Sept 5
It can searched in Google.
I am reluctant to use an advanced application such as SkyX or MaximDL, as this is not my approach to imaging or telescope control, but i would like to control the dome via goto from CdC or similar with appropriate software to control the dome through the Rigel setup. (I use SkyMapPro and EQMOD). As you may be wondering, im completely new to the idea of dome control, but i am learning and interested in anyone’s experiences. I don’t currently have a dome.
The Sky at Night article was written by Steve Richards.
Thanks – Tim (a future dome owner)11 October 2020 at 10:24 am #583234Paul LeylandParticipant
My dome is controlled by LesveDome and very successfully too.
The major problem, from my POV, is that LesveDome is Windoze only and I want to move to a Linux-based TCS. The only thing stopping me is the lack of an INDI driver for the Velleman K8055 controller board. If anyone knows of one, please let me know.11 October 2020 at 10:12 pm #583235Tim HaymesParticipant
I found an informative description of the Pulsar dome automation on the Rigel Dome Control website, with lots of helpful detail on software including POTH – so i think i have enough to chew on now.
- You must be logged in to reply to this topic.