Drivers Orion Cameras

  
  1. Drivers Orion Cameras App
  2. Drivers Orion Cameras Review

I believe NINA supports Altair cameras, which they recently came out with the Altair Hypercam 269C and I am 99% sure the Orion G21 is just a clone of it. The capture software is almost identical to the Altair software, pretty much just a different name at the top. Maybe it would be an easy addition since they are from what I can tell the same camera.

Orion StarShoot Download? - posted in Astronomy Software & Computers: I have the Orion Starshoot Solar System Imager IV. I have replaced my computer but cannot find my software disc. The computer it is on is kaput. Does anyone know if this software can be downloaded? I am using Windows 7 Pro. Hi guys, I’m using the EAF on a RASA 8 with the SCT 8-9.25 bracket. Like Jim I cannot use the full travel of the focus knob. I have determined that it’s safely 28 turns from 0 to full travel on the focus knob and one full turn is roughly 5720 steps so the maximum “Max step” value would need to go up to 160,160 (5720 steps x 28 turns = 160,160) on a RASA 8.

Also the camera will randomly disconnect if I use the ascom drivers for the camera, though it was fixed by using the X86 version but seems to sill be an issue!

Comments (8)

Orion

Drivers Orion Cameras App

Orion

Drivers Orion Cameras Review

1. Connection Options: As you make selections for the various devices, you will usually see a prompt asking if the device is already connected and ready to communicate with PHD2. If you say 'yes', PHD2 will try to connect and then fill in some of the data fields with information read from the device. Saying 'no' simply means you'll have to enter the data by hand. If PHD2 tries to connect with the device and fails, you'll still be able to proceed by just entering the data manually. Device-connection in the wizard is basically a convenience feature that makes it easier to fill in the fields with accurate values. You won't see the prompt if PHD2 already knows the device can't return useful information - for example, if the mount choice is 'on-camera.'
2. Camera connection pane: unbinned pixel size. If you said 'yes' to the connection prompt, this information will usually be filled in automatically and the control will be disabled. If you said 'no' or if the device doesn't report its pixel-size, you'll need to enter the value by hand. You should be able to get the unbinned pixel size from the camera spec sheet or the manufacturer's web site. If the pixels aren't square, just specify the larger dimension or the average value if you prefer. This won't have any effect on your actual guidng results, but it will allow PHD2 to know the image-scale for your set-up. This is used for setting baseline guiding parameters, doing sanity-checks on calibrations, reporting guiding performance, and getting support on our forum..
3. Camera connection pane: binning level. If your guide camera supports binning (many do not), you can specify what level of binning you want to use for this equipment profile. If you want to use the same equipment set-up with different binning levels, it's best to create separate profiles for each binning value. If your guide camera has very small pixels and you have also specified a long focal length, you may see a 'warning' icon next to the Pixel Scale field. That is telling you that the specified image scale is probably too small and you should bin the camera if possible.
4. Camera connection pane: guide scope focal length. This seems to be a common place for mistakes, so it's worth being careful and getting it right. The correct value is not the aperture of the guide scope, it is the focal length. So, for example, if you're guiding with a 50mm finder scope, the focal length willl not be 50mm - it will probably be something closer to 150-175mm. A 60-80mm refractor guide scope will probably have a focal length in the range of 240-500mm, not 60-80mm. Similarly, if you're guidng with an OAG on your main imaging scope, the focal length will be that of the main scope. In some cases, you may be using a small threaded focal reducer on the guide camera, so that must also be taken into account. Like the pixel-size entry, the focal length doesn't demand a great deal of precision, but you should get as close as you can. Otherwise, the performance numbers may not reflect your actual results and the baseline guiding parameters may be sub-optimal.
5. Mount connection pane: mount guide speed. This is another area that seems to cause confusion. The guide speed is a parameter set in the mount or in themount driver, it's not something controlled by PHD2. PHD2 never sets the mount guide speed, it only reads it. It is usually expressed as a multiple of the sidereal rate and is typically in the range of 0.5x - 1x sidereal. Despite what you may read elsewhere, it's usually best to use guide speeds in this range rather than much lower speeds. Higher guide speeds can help to clear backlash more quickly and may help to overcome stiction problems. If you say 'yes' to the connection option prompt, PHD2 will attempt to read the current guide speed from the mount. If this fails for some reason, you'll need to enter the guide speed manually. PHD2 uses this value to automatically set the calibration step-size and to aid in checking calibration results; but the guide speed information is not important for the actual guiding. If you're using different guide speeds on the RA and Dec axes, enter the larger value. If you really can't determine what the guide speed settings are in the mount, leave the setting at the default value of 0.5X. This pane also has a checkbox regarding the presence of high-precision encoders in the mount. These devices are somewhat rare but are sometimes included on expensive, high-precision mounts, and you are likely to know if you have them. Most users will leave this box unchecked.