Jump to content

  •  

CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.

Photo

Starsense error can’t find telescope number.

mount Celestron
  • Please log in to reply
28 replies to this topic

#1 nrcapes

nrcapes

    Vostok 1

  • -----
  • topic starter
  • Posts: 175
  • Joined: 30 Aug 2018
  • Loc: Minnesota

Posted 07 April 2020 - 11:42 PM

I just git my 6se mount back from Celestron under warranty repair. After one nights observing I now get the dreaded ‘cannot find telescope number,’I really don’t want to send it again if I can resolve the problem. So here is what I’ve done:
1) tried swapping out the Starsense HC for my NexStar+ HC. Get a 17 error.
2) tried switching the Starsense HC to the aux port on my 6SE mount. Same error ss (1).
3) tried unplugging the SS camera from the AUX port. Same result.
4) reflashed the firmware with CFM. Same result.
5) tried using the Celestron lithium power pack thinking thst my a/c current might be dirty. Same result.

Before I call Celestron and schedule another warranty return and loss of the scope for a couple of weeks I’d appreciate any helpful hints. Note: Nothing but celestron equipment has touched the mount. I am sure I didn’t plug the HC into the guide port by mistake. I have used a Celestron splitter to hook up the SS camera and the electronic focus motor to the single aux port. I have also instead used the Celestron SkySynch gps on one splitter port with the pass through connect going to the electronic focus motor. My ac standard Celestron power adapter iutputs 2 amps.

Thanks!

#2 Michael_Swanson

Michael_Swanson

    Author of The NexStar Users Guide

  • *****
  • Vendors
  • Posts: 2,828
  • Joined: 23 Apr 2003

Posted 08 April 2020 - 12:36 AM

Ouch.  What was the problem that occasioned a trip to Celestron?  

 

For now, stick with testing using only the NexStar+ HC.  No response 16/17 errors indicate the HC cannot communicate with the MC board inside the mount.  Disconnect everything else from the mount and try the NexStar+ HC in both the AUX and HC (inside the fork arm) ports.  If you still get no response 16/17 errors in both ports than Celestron either broke the MC board or the disturbed the cable harness that connects to the MC board.  (this is assuming the NexStar+ HC is working correctly)

 

Best regards,
Mike Swanson
https://www.NexStarSite.com


  • JREnglar and The_Fly like this

#3 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 08 April 2020 - 12:59 AM

I have recently read in the Sequence Generator Pro forum of problems with a faulty Celestron Focusers causing similar weird  HC and ASCOM controller communication issues.  But park that thought for a moment and lets defer to basic fault funding analytics, which you can test in daylight......

 

I would remove all accessories, all splitters and pare back to only scope and Nexstar + HC. Perhaps do a factory reset. Does it then respond? If no, it does sound like time to call Celestron again. 

 

I once had a problem with an AUX port splitter. The plug end tends to be flimsy and minor cord wrap can cause a disconnect requiring its replacement. But going back to zero devices and adding splitter later can help eliminate that possible causation. Plug devices individually into the AUX port.

 

Then try with only Starsense HC and it's camera. Add the accessories one at a time until you find the glitch. Connect the focusser last in this sequence to test for the highlighted . If the scope works, but focusser doesn't, then at least you only have to return one component. 

 

The SkySync GPS offers an AUX port. Try GPS and Starsense camera via that (again isolates a splitter glitch). The fact that it must have worked when leaving Celestron testing makes the splitter a prime candidate. 

 

However, what does strike me is that 2 amps is probably  too low for scope and so many accessories. The SE is an older model and its power supply was designed long before many of the accessories. You could simply be short of amps. The above step by step diagnostics process will help test for power limitation issues, of which I encountered many as I added ever more accessories. Your scope is in motor vehicle parlance "fully loaded".



#4 terrypaula

terrypaula

    Mariner 2

  • *****
  • Posts: 257
  • Joined: 20 Feb 2018

Posted 08 April 2020 - 02:43 AM

I wonder why I got the same error, "cannot find telescope number," after running a successful firmware update to my StarSense/AVX?  To fix it I tried completely power down, disconnecting everything from everything then reattaching just the SS-HC and SS camera. The error didn't return thankfully.  Why would having my computer attached to the SS at initialization would I get the, "cannot find telescope number" error?  I was having some weird issues with the SS before I ran the firmware update.

 

Anyone know what causes that error?


Edited by terrypaula, 08 April 2020 - 02:49 AM.


#5 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 08 April 2020 - 04:11 AM

I updated my Evolution and 4SE this week (both with Starsense) and did not see this error. However, I had detached the serial to USB cable before recycling power and proceeding after the update. 

 

My guess is that the telescope must decide which device currently has control, be that HC, Tablet/phone or Laptop. Having just been controlled by CFM/laptop using a (virtual) serial port, and whilst that connection remains established and still open, my guess is it is expecting CPWI/laptop (or other like Windows software) to offer the next step in order to proceed with an alignment. Then, if CPWI isn't installed/open, I suspect it fails to connect to scope. Solution, disconnect from laptop unless you intend to proceed with it as your favoured control device. 

 

However, I think this is a different issue to the OP.

 

BTW, your "weird issues with Starsense" should hopefully be resolved by the update. There have been some critical firmware updates to the AVX and Starsense HC in the last two years. 


Edited by Noah4x4, 08 April 2020 - 04:17 AM.


#6 nrcapes

nrcapes

    Vostok 1

  • -----
  • topic starter
  • Posts: 175
  • Joined: 30 Aug 2018
  • Loc: Minnesota

Posted 08 April 2020 - 09:47 AM

I have recently read in the Sequence Generator Pro forum of problems with a faulty Celestron Focusers causing similar weird  HC and ASCOM controller communication issues.  But park that thought for a moment and lets defer to basic fault funding analytics, which you can test in daylight......

 

I would remove all accessories, all splitters and pare back to only scope and Nexstar + HC. Perhaps do a factory reset. Does it then respond? If no, it does sound like time to call Celestron again. 

 

I once had a problem with an AUX port splitter. The plug end tends to be flimsy and minor cord wrap can cause a disconnect requiring its replacement. But going back to zero devices and adding splitter later can help eliminate that possible causation. Plug devices individually into the AUX port.

 

Then try with only Starsense HC and it's camera. Add the accessories one at a time until you find the glitch. Connect the focusser last in this sequence to test for the highlighted . If the scope works, but focusser doesn't, then at least you only have to return one component. 

 

The SkySync GPS offers an AUX port. Try GPS and Starsense camera via that (again isolates a splitter glitch). The fact that it must have worked when leaving Celestron testing makes the splitter a prime candidate. 

 

However, what does strike me is that 2 amps is probably  too low for scope and so many accessories. The SE is an older model and its power supply was designed long before many of the accessories. You could simply be short of amps. The above step by step diagnostics process will help test for power limitation issues, of which I encountered many as I added ever more accessories. Your scope is in motor vehicle parlance "fully loaded".

Thanks Noah: I just did all you suggested. In particular, still getting error 17 and on Back error 16, with the NexStar+ HC plugged into either the HC port or the AUX port. I was able to do a Factory Reset with the HC after hitting Back 3 times but after cycling power got the same errors. Next step is to call the big C and probably send the mount and HC back again. 



#7 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 08 April 2020 - 10:23 AM

Sorry, but sounds like another trip to Celestron for diagnosis and repair is required. But I would also return the focusser so they can test that too. 



#8 Michael_Swanson

Michael_Swanson

    Author of The NexStar Users Guide

  • *****
  • Vendors
  • Posts: 2,828
  • Joined: 23 Apr 2003

Posted 08 April 2020 - 10:32 PM

From my message above: "If you still get no response 16/17 errors in both ports than Celestron either broke the MC board or the disturbed the cable harness that connects to the MC board."  If you have ever had the base open before, it might be worth a look to reseat all the cable connections to the MC board.  Unfortunately my web hosting service is having issues right now and my website is down, otherwise I would send you to the disassembly articles there.

 

Also, what did they when they had the scope?  Might help to diagnosis what they broke...

 

Best regards,
Mike Swanson
https://www.NexStarSite.com



#9 The_Fly

The_Fly

    Lift Off

  • -----
  • Posts: 8
  • Joined: 26 Jul 2017

Posted 16 April 2020 - 02:57 PM

I have this identical problem on my 6 year old NexStar 8SE (which has been used a lot since I bought it). The problem happened when I changed to StarSense, so I assumed the problem was in the StarSense.  I performed the tests in your post and got 16/17 from the NexStar+ HC plugged into both the forkarm connector and the AUX port, so it would seem the problem is certainly in the motor control circuitry.  You mentioned a potential cable harness issue in your post.  Can you say a bit more about that?

 

Thanks in advance for your thoughts!

Ouch.  What was the problem that occasioned a trip to Celestron?  

 

For now, stick with testing using only the NexStar+ HC.  No response 16/17 errors indicate the HC cannot communicate with the MC board inside the mount.  Disconnect everything else from the mount and try the NexStar+ HC in both the AUX and HC (inside the fork arm) ports.  If you still get no response 16/17 errors in both ports than Celestron either broke the MC board or the disturbed the cable harness that connects to the MC board.  (this is assuming the NexStar+ HC is working correctly)

 

Best regards,
Mike Swanson
https://www.NexStarSite.com

 



#10 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 16 April 2020 - 03:05 PM

This month (April 2020), Celestron has updated firmware for Starsense HC and various mounts to solve a problem of bad Starsense data (data corruption in SSA camera). 

 

By coincidence I updated my firmware only last week. Mine now works fine, and it fixed a weird issue I had with Starsense HC not remembering Time-Loc = GPS. Might another firmware update be needed by those suffering from this? See

 

 

https://www.celestro...-update-history


Edited by Noah4x4, 16 April 2020 - 03:10 PM.


#11 Michael_Swanson

Michael_Swanson

    Author of The NexStar Users Guide

  • *****
  • Vendors
  • Posts: 2,828
  • Joined: 23 Apr 2003

Posted 16 April 2020 - 05:12 PM

This month (April 2020), Celestron has updated firmware for Starsense HC and various mounts to solve a problem of bad Starsense data (data corruption in SSA camera). 

 

By coincidence I updated my firmware only last week. Mine now works fine, and it fixed a weird issue I had with Starsense HC not remembering Time-Loc = GPS. Might another firmware update be needed by those suffering from this? See

 

 

https://www.celestro...-update-history

Noah,

 

Is your hand control now a newer version than 1.20.19207 (August-2019)?  That is the newest version I see listed at the firmware history page (though Celestron's site uses Cloud Flare's content delivery network so it is possible I'm still seeing an older page).

 

Best regards,
Mike Swanson
https://www.NexStarSite.com



#12 Michael_Swanson

Michael_Swanson

    Author of The NexStar Users Guide

  • *****
  • Vendors
  • Posts: 2,828
  • Joined: 23 Apr 2003

Posted 16 April 2020 - 05:17 PM

I have this identical problem on my 6 year old NexStar 8SE (which has been used a lot since I bought it). The problem happened when I changed to StarSense, so I assumed the problem was in the StarSense.  I performed the tests in your post and got 16/17 from the NexStar+ HC plugged into both the forkarm connector and the AUX port, so it would seem the problem is certainly in the motor control circuitry.  You mentioned a potential cable harness issue in your post.  Can you say a bit more about that?

 

Thanks in advance for your thoughts!

Hi,

 

From this page of my website:

https://www.nexstars...m/OddsEndsI.htm

 

here is my article explaining no response errors:

https://www.nexstars.../NoResponse.htm

 

and these are the article about disassembling the base of the mount to access the MC board (slightly different model but pretty much the same):

https://www.nexstars.../N58Azimuth.htm

 

Let us know what you find.

 

Best regards,
Mike Swanson
https://www.NexStarSite.com


  • The_Fly likes this

#13 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 16 April 2020 - 05:39 PM

Noah,

 

Is your hand control now a newer version than 1.20.19207 (August-2019)?  That is the newest version I see listed at the firmware history page (though Celestron's site uses Cloud Flare's content delivery network so it is possible I'm still seeing an older page).

 

Best regards,
Mike Swanson
https://www.NexStarSite.com

Correct Mike. That is the 1.20.19207, my bad....

 

The April 2020 firmware updates are to various mounts and fix a Starsense camera issue where Third Gen WiFi is embraced and that was causing data corruption in SSA camera. It also fixed the weird bug I reported where Time-loc in the Starsense HC refused to remember = GPS. That’s what I meant when I mentioned a Starsense HC fix, albeit that it’s firmware  does remain 1.20.19207. But my gear is now fine. 


Edited by Noah4x4, 16 April 2020 - 05:41 PM.


#14 Michael_Swanson

Michael_Swanson

    Author of The NexStar Users Guide

  • *****
  • Vendors
  • Posts: 2,828
  • Joined: 23 Apr 2003

Posted 16 April 2020 - 06:39 PM

Noah,

 

I understand now - it was a fix to the MC firmware in your Evolution mount and/or the WiFi bridge firmware which resolved that error.  One of them must have been corrupting communication on the AUX bus resulting in bad comms with the GPS module and StarSense camera.

 

Best regards,
Mike Swanson
https://www.NexStarSite.com



#15 The_Fly

The_Fly

    Lift Off

  • -----
  • Posts: 8
  • Joined: 26 Jul 2017

Posted 16 April 2020 - 09:41 PM

I very much appreciate your help.  I'll read the articles and, hopefully, be able to resolve the problem.

 

I'm not trying to be mysterious.  When registered for Cloudy Nights, coukldn't figure out a way to leave my name.

 

It's Jerry Stein.

+++++++++++++++++++++++

 

 

Hi,

 


 

From this page of my website:

https://www.nexstars...m/OddsEndsI.htm

 

here is my article explaining no response errors:

https://www.nexstars.../NoResponse.htm

 

and these are the article about disassembling the base of the mount to access the MC board (slightly different model but pretty much the same):

https://www.nexstars.../N58Azimuth.htm

 

Let us know what you find.

 

Best regards,
Mike Swanson
https://www.NexStarSite.com



#16 The_Fly

The_Fly

    Lift Off

  • -----
  • Posts: 8
  • Joined: 26 Jul 2017

Posted 17 April 2020 - 04:11 PM

Hi,

 

From this page of my website:

https://www.nexstars...m/OddsEndsI.htm

 

here is my article explaining no response errors:

https://www.nexstars.../NoResponse.htm

 

and these are the article about disassembling the base of the mount to access the MC board (slightly different model but pretty much the same):

https://www.nexstars.../N58Azimuth.htm

 

Let us know what you find.

 

Best regards,
Mike Swanson
https://www.NexStarSite.com

Mike,

 

I ran across the following video on the process 16/17 error issue. Any impact on your opinion?

 

https://www.youtube....h?v=41LyIRLfwzs

 

Thanks.

 

Jerry



#17 mclewis1

mclewis1

    Thread Killer

  • *****
  • Posts: 19,999
  • Joined: 25 Feb 2006
  • Loc: New Brunswick, Canada

Posted 18 April 2020 - 12:56 PM

​I have a feeling that the StarSense "can't find the telescope number" error message is somewhat analogous to the No Response 16/17 errors in that the hand controller is querying the motor controller board and isn't getting an appropriate response.

 

If I had an SE with StarSense, and/or the GPS, wifi, focuser, and the AUX splitter the first thing I would do (ok second, the first would be making sure my battery was fully charged, and long before I touched any firmware) is remove everything including the splitter and run the scope with the original hand controller. Doesn't matter what firmware levels or anything like that, just using the original hand controller and test it.

 

Then I'd swap it for the StarSense setup and test it again. Then I'd add the splitter, and test. Then the GPS and test ... etc. etc. The last thing I would add back into the mix would any external PC connectivity (either via the hand controller or via wifi).

 

I have a suspicion that on the SEs with a splitter and many or all of the other devices plugged in that the AUX bus signals are getting close to the noise levels and under some conditions messages on the bus are getting interrupted.  



#18 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 18 April 2020 - 02:24 PM

Mike,

 

I ran across the following video on the process 16/17 error issue. Any impact on your opinion?

 

https://www.youtube....h?v=41LyIRLfwzs

 

Thanks.

 

Jerry

I have just watched the video. I have seen that characteristic before, but in a completely different setting. When I dabbled with the  NexRemote Virtual Hand Controller (which preceded CPWI) it always initially reported my telescope as being an "Advanced GT"- yet it is an 'Evolution'. I think this might be simply a default whenever the HC can't recognise the scope and is NOT relevant to the 'Error 16/17' issue described in this thread. I no longer use my Nexstar + HC (or NexRemote), but if I recall correctly it has a Menu feature called <Mount Type> where you select the correct mount. I suspect that this might be what was necessary to fix the issue described in the video. But this is (probably) not relevant to the Starsense error 16/17 as a Starsense HC doesn't require that step (or at least I have never seen it or had to set it!).

 

Mike Swansons guidance remains sound (as always!).

 

But do check via <Menu> <Hand Controller><Get Version> that your firmware is up to date.

 

Current firmware is listed at https://www.celestro...-update-history. You should have Starsense HC Firmware 01.20.19207.

 

However, even if you do, I would still run CFM before trying anything else. There have been updates to MC hardware in April 2020 for many mounts to fix a data corruption error affecting the Starsense camera which, I suspect, is failing to intilise here. The SE series isn't specifically listed in this Firmware History as (I believe) its motor board is auto-fixed by running HC Firmware updates as it has no special features (like WiFi or GPS). However, if you have not upgraded your firmware in the last ten days I recommend that you do so now. When I run CFM it additionally checks for updates to MC, LISA and other internal updates, so the fact you might have the latest Starsense HC firmware from July perhaps  doesn't necessarily mean that you have the latest motor MC updates from this month.

 

Mark's (mcLewis1) explanation is also highly likely and his approach to systematic diagnosis spot on. You must strip back to bare bones and test each device in isolation to find the culprit. But don't ignore what I said about a faulty Celestron Focuser. Try without that first as I have heard that there have been a few with faults that can mess up other devices.

 

Good luck! Hope you don't have to call Celestron!


Edited by Noah4x4, 18 April 2020 - 02:26 PM.

  • The_Fly likes this

#19 The_Fly

The_Fly

    Lift Off

  • -----
  • Posts: 8
  • Joined: 26 Jul 2017

Posted 18 April 2020 - 03:35 PM

I have just watched the video. I have seen that characteristic before, but in a completely different setting. When I dabbled with the  NexRemote Virtual Hand Controller (which preceded CPWI) it always initially reported my telescope as being an "Advanced GT"- yet it is an 'Evolution'. I think this might be simply a default whenever the HC can't recognise the scope and is NOT relevant to the 'Error 16/17' issue described in this thread. I no longer use my Nexstar + HC (or NexRemote), but if I recall correctly it has a Menu feature called <Mount Type> where you select the correct mount. I suspect that this might be what was necessary to fix the issue described in the video. But this is (probably) not relevant to the Starsense error 16/17 as a Starsense HC doesn't require that step (or at least I have never seen it or had to set it!).

 

Mike Swansons guidance remains sound (as always!).

 

But do check via <Menu> <Hand Controller><Get Version> that your firmware is up to date.

 

Current firmware is listed at https://www.celestro...-update-history. You should have Starsense HC Firmware 01.20.19207.

 

However, even if you do, I would still run CFM before trying anything else. There have been updates to MC hardware in April 2020 for many mounts to fix a data corruption error affecting the Starsense camera which, I suspect, is failing to intilise here. The SE series isn't specifically listed in this Firmware History as (I believe) its motor board is auto-fixed by running HC Firmware updates as it has no special features (like WiFi or GPS). However, if you have not upgraded your firmware in the last ten days I recommend that you do so now. When I run CFM it additionally checks for updates to MC, LISA and other internal updates, so the fact you might have the latest Starsense HC firmware from July perhaps  doesn't necessarily mean that you have the latest motor MC updates from this month.

 

Mark's (mcLewis1) explanation is also highly likely and his approach to systematic diagnosis spot on. You must strip back to bare bones and test each device in isolation to find the culprit. But don't ignore what I said about a faulty Celestron Focuser. Try without that first as I have heard that there have been a few with faults that can mess up other devices.

 

Good luck! Hope you don't have to call Celestron!

My scope has no electronic accessories (GPS, splitter or anything else), so I'm persuaded its a problem in the motor control board circuitry.  Before I order a replacement, I'll take a look at the board itself and make sure all connectors are properly seated.  

 

I'll report back once the problem is resolved.

 

Jerry



#20 terrypaula

terrypaula

    Mariner 2

  • *****
  • Posts: 257
  • Joined: 20 Feb 2018

Posted 18 April 2020 - 09:02 PM

To mclewis1  -  In your response  #17

I find it hard to believe it could be my motor control board on the "can't find telescope number," error I replaced the control board about 9 months ago because it had a bad connection to the Dec motor.  It would cut out when slewing.  After I replaced the motor control board I haven't had ANY problems until I updated the firmware to the mount and handset.  I hate to say it except having to have both the wireless dongle connected and a usb wire connected to run the mount with CPWI.  Tonight is the first clear night I've had since to check things out to see if it'll run with just my usb connected.

 

Tonight I'm running my TS 503ed with a T3i connected for the firsttime.  Talk about a lightweight wide field EEA setup on an AVX; I gotta say I'm excited to see the results.  I was using ab ES 102ed but this scope is sooo easy to use with a camera its not funny.  All I had to do was buy a Celestron SCT camera adapter, it screws straight onto the focuser and it turned the perfect length.  I locked the focuser after focusing with a 24mm ep.  I removed it and the scopes 1.25" sct adapter then replaced it with the T2 - sct adapter and after turning on the camera I noticed barely had to touch the 2-speed focuser.  Pretty cool.



#21 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 19 April 2020 - 02:12 AM

Hi TerryPaula, I have had an idea....

 

A user can normally control scope using CPWI by EITHER connecting by SkyPortal external WiFi accessory or by HC cable. You then select in CPWI either "hand controller" or "WIFi". To need both connected simultaneously simply doesn't make sense. But that seems to be how yours is working. How odd!

 

I have tried to replicate this and whilst it will all work  with both plugged in simultaneously  the selection of which control device is active  is dictated by the WiFi or HC setting and the other device is dormant.

 

However, I too couldn't get CPWI, Starsense and GPS to play nicely until I upgraded firmware for both Stasense  HC and upgraded to CPWI 2.3.4.final rc1 .I did this last week, and that timing has set me thinking.....

 

When did you upgrade your firmware? Have you done so in the last week? 

 

The latest Starsense HC firmware was released in July 2019 so it is odds on that you have that. But in April 2020, there were MC board firmware updates released for Evolution, CGX, AstroFi and other mounts to fix a problem with data corruption manifesting in the Starsense camera and a problem with the WiFi Bridge in third generation Celestron WiFi.

 

I have just spotted that  the SE Series is NEVER listed in the Celestron Firmware History, so you cannot compare your current MC board firmware version with any external reference point. We hence don't know if the SE series.MC also, needed an upgrade, but I suspect it might.

 

I wonder if the more recent upgrade to CPWI needs an upgrade to all MC boards(?), but because your HC firmware was already up to date you need to run CFM again to benefit solely from the April 2020 MC update? I wonder if this might cure the many other 16/17 error problems being reported with SE mounts? If you have run CFM this week, then it's something else. But I thought it worthy of mention.


Edited by Noah4x4, 19 April 2020 - 02:14 AM.


#22 MickTaurus

MickTaurus

    Explorer 1

  • -----
  • Posts: 92
  • Joined: 24 Aug 2019
  • Loc: United Kingdom

Posted 19 April 2020 - 12:39 PM

 

I have just spotted that  the SE Series is NEVER listed in the Celestron Firmware History, so you cannot compare your current MC board firmware version with any external reference point. We hence don't know if the SE series.MC also, needed an upgrade, but I suspect it might.

 

I wonder if the more recent upgrade to CPWI needs an upgrade to all MC boards(?), but because your HC firmware was already up to date you need to run CFM again to benefit solely from the April 2020 MC update? I wonder if this might cure the many other 16/17 error problems being reported with SE mounts? If you have run CFM this week, then it's something else. But I thought it worthy of mention.

 

I have today updated firmware for NexStar 8se, and it appears to have updated various mounts in the packages folder.

 

Anyway don't know if it will make any difference.

I was getting cannot detect ss camera error will see what happens tonight.

Attached Thumbnails

  • CFM.png

Edited by MickTaurus, 19 April 2020 - 12:40 PM.


#23 Noah4x4

Noah4x4

    Gemini

  • *****
  • Posts: 3,431
  • Joined: 07 Apr 2016
  • Loc: Colchester UK

Posted 19 April 2020 - 01:12 PM

I hope it works for you MickTaurus,  I  have an Evolution and 4SE, and both work fine after running CFM this month.

 

EDIT.

just noticed you are running a Mac and me Windows/PC. 


Edited by Noah4x4, 19 April 2020 - 01:13 PM.


#24 MickTaurus

MickTaurus

    Explorer 1

  • -----
  • Posts: 92
  • Joined: 24 Aug 2019
  • Loc: United Kingdom

Posted 19 April 2020 - 05:34 PM

I hope it works for you MickTaurus,  I  have an Evolution and 4SE, and both work fine after running CFM this month.

 

EDIT.

just noticed you are running a Mac and me Windows/PC. 

All good here Noah.

No cannot detect ss camera error at all this evening after updating firmware today.

waytogo.gif

 

Oh and yes running CFM from Mac laptop, I have Windows 10/PC desktop but usb cable won't reach.


Edited by MickTaurus, 19 April 2020 - 05:37 PM.


#25 Michael_Swanson

Michael_Swanson

    Author of The NexStar Users Guide

  • *****
  • Vendors
  • Posts: 2,828
  • Joined: 23 Apr 2003

Posted 19 April 2020 - 08:38 PM

 

I have just spotted that  the SE Series is NEVER listed in the Celestron Firmware History, so you cannot compare your current MC board firmware version with any external reference point. We hence don't know if the SE series.MC also, needed an upgrade, but I suspect it might.

 

I wonder if the more recent upgrade to CPWI needs an upgrade to all MC boards(?), but because your HC firmware was already up to date you need to run CFM again to benefit solely from the April 2020 MC update? I wonder if this might cure the many other 16/17 error problems being reported with SE mounts? If you have run CFM this week, then it's something else. But I thought it worthy of mention.

The SE series uses MCupdate to load MC firmware.  The Celestron Firmware History only lists firmware managed by CFM (not MCupdate nor HCupdate).  The SE series has not had an MC update in well over 10 years and Celestron has not looked at it in that long.  It would definitely be possible for Celestron to produce new StarSense HC firmware and NexStar+ HC firmware that is incompatible with the SE mount, but since the original post from nrcapes indicates he continued to have problems when he also tested with his NexStar hand control, I don't think new StarSense firmware is an issue here.

 

The firmware on Terry's AVX on the other hand is managed by CFM but I'm not yet clear what his issue might be.

 

Jerry - the video is not what you are experiencing from my understanding.  The video shows that individual's StarSense HC is working but his NexStar+ HC is not working and I agree with the YouTuber's assessment that his NexStar+ HC is having problems (might be as simple as recrimping the RJ-12 plug or opening the HC and reseating the coiled cable's connector).  As I understand it, both your StarSense and your NexStar+ HCs are not working.  Still sounds like your MC board has an issue or the internal cabling needs re-seated.

 

Mick - the new Evolution MC firmware is not applicable to your SE mount.  If you were previously experiencing errors detecting the StarSense camera it is unlikely any firmware updates were involved in producing or fixing the error so you might want to watch for any unique cabling combinations (splitters, jacks in use, etc.) if the issue arises again. 

 

Best regards,
Mike Swanson
https://www.NexStarSite.com




CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.


Recent Topics





Also tagged with one or more of these keywords: mount, Celestron



Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics