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

No response 16

  • Please log in to reply
17 replies to this topic

#1 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 07:50 AM

My 127slt mount just began showing the dreaded no response 16. It appears the main board firmware may have been corrupted by astroberry driving the hand control and mount/scope bought in August 2020, and the hand control has the latest firmware. 
 

My question concerns a method apparently posted on the nexstar site. Am I 1. To roll back the hand control firmware to an earlier version posted there; 2 use Mc update to reflash the motor control; and then 3 reflash the hand control to the most recent?

 

Has anyone had error 16, and if so, did this work?

 

thanks


Edited by Maritime, 25 February 2021 - 07:52 AM.


#2 Jim Davis

Jim Davis

    Aurora

  • *****
  • Posts: 4,819
  • Joined: 05 Jul 2014
  • Loc: Lewisberry, PA

Posted 25 February 2021 - 08:04 AM

Most of the time Error 16 and 17 are caused by damage to the hand controller cable. The errors mean that the HC cannot communicate with the motor controllers in the mount. Before you try changing anything else, make sure the cable, connector or socket are not damaged in some way.

 

This site gives some tips: https://www.nexstars.../NoResponse.htm



#3 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 08:08 AM

Thanks. I’ve try another nexstar plus from a 6se and a starsense handcontrol with the same result, in each aux Jack on the mount. So, anybody tried reflashing the motor control board and do I have the steps right?  Thanks 

 

edit. I did open the arm and reseat all cables. 


Edited by Maritime, 25 February 2021 - 08:09 AM.


#4 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 08:14 AM

https://www.celestro...1a91b78ec&_ss=r

 

Celestron appears to recommend reflashing the motor control board if the other methods don’t work, and they haven’t for me. 



#5 mdavister

mdavister

    Ranger 4

  • -----
  • Posts: 321
  • Joined: 10 Jul 2007
  • Loc: Pennsylvania

Posted 25 February 2021 - 08:19 AM

Sometimes the error can be caused by a bad cable or crimp on the connector.



#6 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 09:03 AM

Sometimes the error can be caused by a bad cable or crimp on the connector.

I believe I have largely eliminated that by using two other hand controls and all the aux ports. Thanks


Edited by Maritime, 25 February 2021 - 09:10 AM.


#7 demarko69

demarko69

    Mariner 2

  • *****
  • Posts: 222
  • Joined: 20 Feb 2020
  • Loc: Arizona

Posted 25 February 2021 - 11:10 AM

I once had an issue with murphy 16/17 ,I just did a CFM update (not that I needed to update) to my 8se and Nexstar+ and I was back to the races



#8 Lasko

Lasko

    Vostok 1

  • -----
  • Posts: 102
  • Joined: 15 Jan 2021
  • Loc: Sacramento, CA

Posted 25 February 2021 - 12:03 PM

It appears the main board firmware may have been corrupted by astroberry 

If Fedex ever delivers my 4B I am going to start setting this up.  How can Astroberry corrupt the firmware?



#9 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 02:19 PM

I once had an issue with murphy 16/17 ,I just did a CFM update (not that I needed to update) to my 8se and Nexstar+ and I was back to the races

Didn’t work for me.  I think the motor control firmware was corrupted.



#10 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 02:19 PM

If Fedex ever delivers my 4B I am going to start setting this up.  How can Astroberry corrupt the firmware?

Thats my theory....



#11 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 04:21 PM

New motor control firmware appears to have cured it. 


  • mlord likes this

#12 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 04:53 PM

If Fedex ever delivers my 4B I am going to start setting this up.  How can Astroberry corrupt the firmware?

I don’t know how, but I infer it did-azimuth was dead. After reflashing Mc firmware, it was restored. 



#13 demarko69

demarko69

    Mariner 2

  • *****
  • Posts: 222
  • Joined: 20 Feb 2020
  • Loc: Arizona

Posted 25 February 2021 - 09:53 PM

New motor control firmware appears to have cured it. 

how did you update mc firmware



#14 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 10:47 PM

Nexstar site has the routine-you must use an earlier version of the hand control firmware, so using cfm and the file posted on the nexstar site is step one. Then you use the Mcupdate utility to update or reflash the mount-that is like taking a beating, and it is step two. Finally, you use cfm to restore the newest files to the handcontrol. It is a horrible, tedious process but it works. 



#15 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 25 February 2021 - 11:50 PM

https://www.nexstars...pgradeHowTo.htm



#16 Lucretius

Lucretius

    Lift Off

  • -----
  • Posts: 2
  • Joined: 16 Jan 2021

Posted 26 February 2021 - 08:47 PM

Just went through this same "No Response 16, No Response 17" scenario a couple weeks ago with a 130SLT.  Had to follow these instructions here before MCUpdate would even recognize my motor control board:

 

https://www.nexstars...xStarGPSFix.htm

 

After flashing my Nexstar+ with version 5.22.3280 firmware (via CFM offline), MCUpdate then could "see" the motor control board had a status of "Boot" on both axis' but could not recognize the model of either axis.  I decided to ignore the warnings of not recognizing those axis models and flashed each with the latest version of SLT firmware (5.16) and the status of each axis returned to "Running" with the model recognized.  I then flashed the Nexstar+ HC with CFM online.  The mount has been working fine since then.



#17 Maritime

Maritime

    Viking 1

  • *****
  • topic starter
  • Posts: 817
  • Joined: 19 Aug 2020

Posted 26 February 2021 - 10:20 PM

Wasn’t that as much fun as a beating in a dark alley from an ugly woman....



#18 Lucretius

Lucretius

    Lift Off

  • -----
  • Posts: 2
  • Joined: 16 Jan 2021

Posted 26 February 2021 - 11:25 PM

The fun part was all the online research it took to be able to restore the SLT mount to operational.  Getting CFM and MCUpdate to work with Win 10, figuring out which com port for the HC, getting Win 10 to recognize the chip set in the HC, etc...  Very thankful of the cloudynights forums and especially nexstarsite for all the information they provided.  Otherwise my SLT mount would still be poor version of a manual Dobsonian.


Edited by Lucretius, 26 February 2021 - 11:31 PM.



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






Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics