DougQuaidHauser

1 hour ago, Shimrod said:

I am not certain, but I think the Starsense HC with usb port only shipped with 1.16 firmware, as it was only released mid 2016 - the 1.1.6 firmware was released around March 2016 and 1.15 was released August 2015. So I definitely don't think your firmware would go back beyond 1.15 - assuming it restores firmware and doesn't just clear all the settings. I don't use my handset so I will try later and see what happens!

 

https://www.celestron.com/pages/firmware-update-history

My HC states:

Ver: 01.16.16055

Bld: Feb 24 2016.

1 hour ago, StevieDvd said:

You need to run the setup for the older drivers to add them to the list of loaded drivers (including what windows says is the best). I've plugged an old PL2303 adapter in and used the update driver to show what drivers are on my system. If you have tried that already sorry for the misunderstanding. The com port it selected is hidden but it did set one and can be seen under properties|port settings|advanced

 

I would not think the jerry rigging of a serial adpater cable to feed into the usb input of another serial adapter (inside the handset) is a good idea.  I may be wrong but not something I'd expect to work.

 

 

I think I've tried, no matter what I do or what drivers I install, it just never appears in device manager, no com port is shown, its like there is no com port to be found, even if I search for hidden, or legacy?

Yes its probably a wacky idea to try, can do it cheaply as well, just have a hunch the PL2303 chip in the HC is faulty, so on the off chance a serial signal is still being sent out the HC, might work, slim chance.

38 minutes ago, Shimrod said:

I have read on Cloudy Nights that some people have resolved this issue (device descriptor request failed) by performing a factory reset on their handset (Hold down 0 while powering on the handset). It is starting to sound like a handset failure. I'm guessing this is the first time you have connected the handset to a PC and have not previously used it with a laptop to control the mount?

Yes it is the first time I have tried to connect it to my PC for autoguiding last week (first attempt for autoguiding), is when I noticed it will not connect to my PC and the relevant software, I hadn't tried previously as the AVX and Starsense appeared to be working normally, other than not amazing tracking, but put it down to my probable amateur polar alignment. I am more used to connecting my Nexstar SLT mount to my PC with no real issues.

I will be honest, currently I am scared to do a factory reset as Ive heard that you need HC firmware later than 01.15 or later to update using WIFI (if I have to get a Celestron WIFI module to update), and it says its currently 01.16 so worried I may lose that ability. Saying that I dont have a clue what it would revert to as not familiar.

On 28/08/2022 at 11:15, StevieDvd said:

A few more things to try:

1. Are you using 32 or 64 bit windows and the driver for the correct version

2. You may be able to add a driver to the 'unknown device' by right-clicking - can't verify as I have no unkown devices to check this.

3. The newer PL2303 drivers had issues with Win 10 - see this NexStar related web page note it says the PL2303 is the chip in the handset

 

Hello and thanks, all my windows systems are 64bit these days. I tried adding a driver by right clicking with no luck unfortunately, just always tells me windows is using the best driver already.

I think my next plan is to use the cable to connect my non-USB Nexstar HC to PC and see if that works, it has a built in serial adapter. First I need to do a bit of jerry rigging as the end of the cable has a RJ22 connecter, and obviously this will not fit in a mini USB b port of the starsense HC. Need to buy a few parts first. And if that doesnt work, will have to bite the bullet and get the Celestron WIFI module and hope that works.

On 28/08/2022 at 11:19, malc-c said:

Ignore the fact this is an ardiuo (it's the easiest thing on hand I could use to show you that opens a new com port).  When you connect the handset via the USB cable are you saying that you get no indication at all in device manager or does it create a new com port but it has a yellow exclamation mark against it ?  - If you are getting an indication that windows detected the hardware with the normal audio bing-bong sound, but device manager is unchanged then try connecting the handset to a different computer to rule out your computer or windows installation as being the reason you are having this trouble.

If you manage to get the com port to show up but it has no driver installed, open up properties and navigate to the tab shown, and select hardware ID  - copy the fist line in the box below and google that string - this will identify the correct chipset used and driver required

If on connecting the handset to two computers you get the same result of hardware being detected but not showing up in Device manager then  check you haven't enabled to option to hide devices.  Click on View Tab and then Select View hidden devices and see if it is then made visible

Hello, when I connect the starsense HC windows detects it as an unknown USB device (see diagram 2), as far as I can make out this should not happen when using a device via a PL2303 chip, windows should detect it as a serial com port, if it was detected the correct  way (as a com port) then I am sure any driver would be accessible etc.

I can plug the Starsense HC in via USB and even unplugged from the AVX mount it will be powered by the USB cable. I have tried it on 2 laptops, and my PC, all running different versions of windows and get the same result.

I have a cable I use for my Nexstar SLT mount with an inline PL2303 chip and when connected to windows it triggers a com port (see diagram 1). When I try the same thing using my Nexstar HC via PL2303 cable when unplugged from the mount it is not powered by the USB cable.

I am convinced its the PL2303 chip in the HC giving the problem.

14 hours ago, malc-c said:

I have a serial device(serial camera shutter release) that needs a prolific 2303 driver, and the attached works on both windows 7 and 10 (the observatory PC is old but does the job).  Worth a try 

PL2303_64bit_Installer.zip 431.24 kB · 3 downloads

Thanks, I tried it but no luck. I have no way of making changes in device manager as no USB serial port is being detected when the HC is plugged into the PC. I think if it was then could update it with the PL2303 software.

5 hours ago, StevieDvd said:

If you open Device Manager and right-click on the unknown device, then select properties it may tell you what driver it needs (most likely Prolific). If you have installed a Prolific driver then choose the Update driver option when right-clicking on the device and find the driver(s) on your PC - you may have several but you can test them one at a time.  I have found that it pays to restart the PC each time as the driver can be cached by the OS.

 

Greetings, I think the issue is that the Prolific PL2303 chip in the HC is simply not doing what it is supposed to do, possibly broken/faulty?

An example would be my pre 2016 Nexstar+ HC that has a RJ22 connector. To connect it to my PC I purchased a cable with a RJ22 to USB and the housing contains a chip (FTDI) which creates a virtual com port (USB serial port) via USB. So when I plug just the unit into my PC a com port will appear in device manager.

I am sure for newer mini USB b HC's this chip is in the HC (It is because I opened the HC to check) instead removing the need for a special cable, so plugging in the HC should trigger a virtual com port on my PC. For my HC this is not happening, the PC just detects it as an unknown USB device.

I am getting the impression over the last day that this is not a one off problem for me alone.

8 hours ago, Shimrod said:

Can I just check - when you are connecting the handset to the PC you also have the handset connected to the mount (and the mount powered on)? I don't recall installing any specific drivers for my Starsense handset, but I mostly control my AVX using CPWI and skyportal these days. I can check my astronomy laptop later to see if I have anything special installed.

Hello, I connect the HC to my PC with the AVX turned on or off, same story, the HC is treated like a faulty unknown USB device. I can plug the HC into the PC and it is powered by the PC via USB with the mount off even.

I can't connect to CPWI or anything mount related as it stands.

Thanks

27 minutes ago, Cosmic Geoff said:

You may want to check this elsewhere, but this may be the same issue as with the Sky-watcher Synscan handsets, where the newer ones have a USB port, but if you want to use the USB port for firmware updates and such, you still need a serial chip driver loaded on your laptop or PC.

If your Starsense software dates from 2016, yes, you really ought to update it, as IIRC this fixes various issues.

Yes I've seen mention of Prolific PL2303 drivers, after installing they just never appear in my Device Manager ports tab, tried on a windows 7, 10, and 11 laptop and just never works like stated. Plugging in the HC to PC, it just gets treated like a faulty unknown USB device. Ive thought of bypassing the HC with the Celestron wifi module but I've heard that you cant update the firmware over wifi with older versions so would be wasting £160+ for nothing?

PS Where would be a better area of the forum to post this? Thanks

I bought a used Starsense Autoalign recently for my AVX mount and noticed that the firmware version is from 2016 so I want to update it. The hand controller has a mini USB b connector on it, when I connect it to my PC the PC does not recognise it, neither does CFN. I have tried the Starsense hand controller on my Nexstar SLT mount with the same issue (So must be the HC and not the mounts). My old SLT mount HC has a RJ22 jack, I have a convertor cable so that I can connect with USB and it works just fine. I assumed the newer hand controller's with mini USB b connectors would be more simple.........obviously not.

Anyone had the same issue?

Cheers

2 hours ago, Shimrod said:

The release notes are out of date - this is the install screen of the downloaded software - and the version history after installing - you can see a fixed for the gamepad slewing.

 

Wow thanks, super helpful and very much appreciated the advice, the update sorted the issue, works a charm now

5 hours ago, Shimrod said:

I had a look on TeamCelestron and there was someone reporting this same issue with 2.4.1 (and also with 2.4.0). I notice the latest release from the Celestron website is 2.4.2 so you might want to download that and see if it has fixed the issue. I've been using a gamepad for a while with my AVX and CPWI, but the version I have installed is currently 2.3.5

Thanks, but when I check the website it says 2.4.1 is the latest, it does not list 2.4.2? 

Greetings people!

I realised recently that linking my laptop to my Celestron 127 SLT mount using CPWI makes the Nexstar hand controller unusable whilst linked, a bit pointless if the laptop is inside away from the scope outside (For astrophotography).

I discovered online that you can use a wireless gamepad to control the mount, perfect! The default controls make the Left stick slew the X axis, and the Y axis, fair enough, problem is pressing Left or Down moves the mount, but it can only move Left or Down, pressing Right or Up the mount does not move, even though you can see these inputs are being registered when making them. Completely bizarre and have tried with multiple gamepads.

Am I being dumb?

Cheers any help appreciated.

16 hours ago, Andrew_B said:

Have you done much astrophotography just using basic camera lenses? Shopping secondhand can get you some real bargains and you might be surprised how much detail you can capture with something like a short telephoto.

There are a few advantages with this approach - shorter focal length means tracking errors are less of an issue and camera lenses typically have faster focal ratios than scopes so even when stopping them down a bit to control aberrations you can normally get away with shorter exposures. You're still learning the same workflow that applies to shooting with a scope but it's easier and less likely to cause frustrations and astrophotography can be tricky enough without making things harder than they need to be when you're a beginner.

Hello, yes it is something I want to try as well, and to answer your question, I am a complete noob with regards to astrophotography at this stage. So far I have tried it this year without much success due to using a 127 Mak. Mostly done planetary imaging, post processing video up to now which has been a blast.

I have a Canon 1000D DSLR but bought it used just the body so would need to buy a lens, but zero clue at this point which lens would be compatible as never been a camera person. Once researched I could buy a used lens and give it a go.

5 hours ago, Cosmic Geoff said:

I suggest that you match your ambitions to your equipment and budget. Neither the achromats you mention nor your alt-az mount are suitable for "proper" deep space imaging. For the latter you need to spend a lot of money for an APO scope and a heavy imaging equatorial GoTo mount.

However if you tailor your ambition to dabbling in some EVAA imaging, you can use a Startravel 102mm and the Nexstar alt-az mount.  I have used a Startravel 102mm + a Nexstar SLT mount (albeit on a more rigid permanent tripod) + a ASI224MC camera to take many pleasing shots of galaxies, star clusters, planetary nebulae, comets etc.  An exposure of a few seconds suffices. The images can be live-stacked with suitable software.  

If you search in the EVAA reports section, you may find some of my results.

Hi and thanks for the input. Trust me my ambitions at this stage are really low, hell Id be happy seeing a bit of nebulosity etc in some images at this point, the fun is in the learning for me, dont want to be one of those 'all the gear, no idea' guys. My plan is to get a small APO now, and then get an appropriate mount for it in time.

Could you clarify what EVAA means? Ive had a brief look in that forum. Thanks

Thanks for the advice. I completely forgot about about chromatic aberation being a Maksutov user, and a Newtonain user before that, not used to refractors so no point me purchasing the ones I mentioned as would only use the OTA for astrophotography, as you mentioned already, I have a real nice visual scope already in the Mak 127.

I dont want to break the bank so to speak (wife) so have been looking at the Skywatcher ED70 scope (£300) but in reviews people keep mention needing a £200 field flattener so not sure about that one now. Do all small refractors require a field flattener for astrophotography?

PS excellent photo of orion, Id be more than happy with images close to that

Update:

I purchased a generic FTDI USB cable on ebay for under 20 quid and the handcontroller firmware updated no problem.

It also enables me to link the handcontroller to my laptop using CPWI.

Cheers for the advice

Greetings

I was wondering which OTA would be best for deep sky astrophotography, an 80mm F/5 or a 102mm F/5, (Skywatcher Startravel 80 & 102, Orion, Bresser etc) or is there no real benefit to the extra aperture at my beginner status?

Currently I have been having great fun with my Celestron 127 Mak with a Nexstar Alt-Az GoTo mount using a DSLR camera for planetary imaging, but obviously this is terrible for deep sky due to the near F/13 scope. I am looking to buy a small refractor OTA whilst using this same mount (yes I know its an Alt-Az and not an equatorial mount) for some beginner deep sky imaging and learning the ropes.

So in a nutshell, is it better to go with the 80mm and lighter payload, or go with a 102mm (Not that either are easily available)?

All advice appreciated.

28 minutes ago, PeterCPC said:

I don't believe that the Meade cable will work. These do https://www.firstlightoptics.com/celestron-mounts/lynx-astro-ftdi-usb-to-serial-adapter-for-celestron-handsets-5m.html

 

Thanks perfect, save me time and wasted money.

I purchased a used Celestron Nexstar 127 SLT recently and was wondering if it would be wise to upgrade the Firmware on the hand controller as high odds it has never been updated.

It is the older hand controller as has the RS-232 jack on it. Is it worth updating the firmware? I'd also like to use the cable to extend the reach of the hand controller as the stock telephone style cable is more irritating than good, as well as potentially linking it to my laptop.

Additionally, is it better to buy a RS-232 cable, and separate converter RS-232 to USB, or to buy an all in one RS-232 USB cable on Amazon such as a Meade LX200 GPS contol cable? or something along this line? No idea if cables have to be compatible.

https://www.amazon.co.uk/Telescope-Control-Upgrade-Console-AUTOSTAR/dp/B08LP8BL1G

Thanks for any advice.

Hi Cosmic Geoff, thanks for the advice, I did not get a chance to get out for month after due mostly to weather, and then completely forgot what board I signed up to.

But I did buy a power supply, read the manual etc and got the hang of auto 2 star alignments in the end. Although I was guilty a couple of weeks ago of wasting an hour failing to align due to forgetting the yanks like to reverse the month and days, so instead of trying to align 11th July i told it that it was 7th November, cheers Celestron (Muppet).

Hey people, brand new to the forum, greetings.

I finally have a telescope again after a 20 year break of being an online astronomer (God knows why it took so long to get another telescope?!).

I managed to get a good priced Celestron SLT 127 Maksutov (2016) on Ebay a couple of weeks back and last night was the first chance to actually get it out (Cloudy last few weeks). Anyway, for the life of me I could not get the Nexstar Alt-Az GOTO mount to align. I tried Skyalign, Auto two-star, and two-star align with no luck (Using Pollux, Rigel etc).  Im guessing maybe thinking back that I set it to daylight saving and that threw it off, or maybe the handset is lacking updates? After months of seeing the process done on Youtube stating how simple it is, I am feeling slightly low IQ now lol.

Either way in manual mode I still had great views of the Moon and Orion nebula first up. Any advice?