The NexStar 5i is my imaging platform and now and again I replace the 5" SCT with a Tasco Short Tube 80. Because I have Ray's Brackets changing OTAs is a snap.
This wedge is easier to manipulate,
though I still need to modify the azimuth knob because it is impossible
to grip, especially when it is cold. But other than that, it is sturdy
enough for a small platform like the N5i.
|
I
started out using the Celestron Wedge/Tripod that came with my NexStar
5i kit, but found that it hurt my back to get it set up properly so
I finally bought a NexStar 8i tripod and a NexStar wedge. There is
a fine latitude adjustment kit that you can buy from 
SOFTWARE :
The other thing that limited me was running an older notebook (Dell Latitude CPI-A). I didn't feel comfortable running everything I wanted to run on it, so I had to pick and choose between applications and I certainly couldn't autoguide and use NexRemote (the software formerly known as hcAnywhere) and in the winter I liked to be inside while the scope was outside freezing so... I made due.
|
Then there's the aforementioned NexRemote and its not-quite-released but still available on the Astrogeeks site, NexHub, which is a software-based RS-232 multiplexor built specifically for NexStar telescopes (ASCM, CGE). I also take advantage of the Logitech Wireless Wingman Rumblepad which can drive NexRemote. I honestly don't know how you'd employ NexRemote without it. Last but not least, there's Starry Night Pro 3.1 which is used instead of the latest and greatest SNP simply because SNP3 works and SNP4 is well... really nice on cloudy nights but you don't want to trust your imaging platform to it, IMO.
|
However,
I bought a refurbed Dell Inspiron 5100 with XP Home and can now run
all the software I want -- and this includes but is not limited to :
The only thing not mentioned above is that I use remote control software from the notebook at the telescope (over a Wireless G card) to an XP Home system inside. During the Summer I doubt I'll use it much, but when it gets cold, I'll certainly do it again. The software I have been using is not freeware, but I think with the faster system I can get away with running a free VNC version.
So this brings me back to hardware again, because the new Dell system doesn't have any serial ports. In fact, it only has 2 USBs which can be a bit of a drag if you've got a requirement of 2 RS-232 ports and 2 USB ports. But luckily, the Inside Out Networks Edgeport series was suggested to me. I picked up the small Edgeport 22/c which provides 2 USB ports as well as 2 RS-232 ports and best of all, it appears to actually work! No BSODs as yet, but it is still early. ;-)
CABLE CLUTTER
A side benefit of the Edgeport 22/c is that it has allowed me to reduce the cable clutter of the setup. The first photo shows the Edgeport on the base w/only one cable to it. So you can see how small it is. I want to replace the 3 foot USB A/B cable I've got tied up (see the 3rd picture) with a retractable cable, and then I'll have everything as tidy as I'd like. But regardless, I'm down to power to the scope, power to the camera, and the USB cable from the Edgeport to the computer as my only "out" cables.
I should probably explain why my camera is in using a diagonal. Normally, I use a flip mirror and have the camera shooting straight through. But doing so means the camera will hit the base if I need it to be close to perpendicular to the base. So I thought while I return to testing autoguiding, I'll use the diagonal. If autoguiding turns out to be something doable in more than one area of the sky, I can make up for the loss w/the diagonal by taking longer exposures. And then I can shoot anywhere in the sky!
Final thoughts :
If you are handy with electronics, using an AUX2PC "thingie" (forgive the technical jargon) instead of a serial cable to the real hand control is nice. You can't use the real HC and NexRemote anyway, and real HCs are expensive and sensitive to temperature so it is nice to leave it in a box and not have to mess with it.
The hex file for the camera needed to be changed to allow it to connect to the USB port on the Edgeport without reporting an error for not having enough power. This is available for both the MX716 and MX916 cameras and can be found in the files section of the Yahoo group for Starlight Xpress. The 716 file is used for both cameras.
For some reason, the camera will not connect properly when the Wingman is plugged in, even though the Wingman is not plugged into the Edgeport. So, I have to start w/the Wingman connected, do my alignment w/NexRemote, unplug the Wingman, connect the camera, fire it up with Maxim, and then plug the Wingman back in. Go figure!
Oh yes, connecting more than one piece of software to the telescope through the Celestron ASCOM driver... Technically, you are supposed to run this piece of software called POTH first. It is an ASCOM hub to which you connect the telescope driver -- NexStar 5i, COM whatever. Then in the software you want to use to control the scope, you choose POTH as your device. Well, it wasn't written anywhere that I knew about so it never dawned on me that this is what you are supposed to do.
At first, I started up SNP and connected to the scope on one COM port, and then fired up Maxim and changed the COM port to the second one (through NexHub -- SCOPE ---> NexRemote -->NexHub --> 2 COM ports) and this caused all sorts of problems. So then I just left them go to a single COM port and this seems to work just dandy. The only problem found so far is when I shut down and who cares if you pull an error at the end of the night?!
So that's that at this point. If anyone has any questions, you know where to find me. ;-)