Lost my Endstops!

39 views
Skip to first unread message

Alan Mclean

unread,
Sep 11, 2018, 7:46:39 AM9/11/18
to Jetty Firmware
I have just upgraded my CTC Replicator Dual clone to 7.7 and now it's crashing into the ends of the rods and causing the steppers to click alarmingly!!

According to the "Invert Endstops" field there are "Non Installed", I changed that and committed the change after powering down the CTC and restarting it the Invert Endstops field s still set to No Endstops Installed.   I checked this more than once.

The endstops are present and were working properly under Sailfish 7.6.

According to Machine Information 
The Profile Name is Replicator Dual
Driver Type Mightyboard (it has the 2560 processor)
Name CloneR1  (Chosen during the upgrade from 7.6 to 7.7)

Under geometry type the axis endstops ="max"    so they are listed.

I'm at a loss now and any help would be much appreciated.


Thanks.            aamcle

Rich Webb

unread,
Sep 11, 2018, 10:46:50 AM9/11/18
to Jetty Firmware
It's possible that the CTC build of Sailfish 7.6 stored configuration information differently than the public build of 7.7. If that's what has happened, you might want to try the option to reset to factory defaults (Utilities -> Restore Settings) or completely erase and reinitialize the EEPROM (Utilities -> EEPROM -> Erase EEPROM).

See sections 3.7.20 and 3.7.21 in the manual.

Jetguy

unread,
Sep 11, 2018, 8:49:18 PM9/11/18
to Jetty Firmware
Clone R1 is a different printer!!!!
That's your problem right there.


On Tuesday, September 11, 2018 at 7:46:39 AM UTC-4, Alan Mclean wrote:

Jetguy

unread,
Sep 11, 2018, 8:51:54 PM9/11/18
to Jetty Firmware
Again, Clone r1 is a core XY firmware so endstops are handled completely different.
No wonder you have issues, you loaded Core XY firmware on a Cartesian printer- heck no- it won't home properly.

Not trying to make fun of you in any way, mistakes happen, just trying to share the gravity of the mistake made so maybe others don't repeat.

Jetguy

unread,
Sep 11, 2018, 8:56:27 PM9/11/18
to Jetty Firmware
Again, in a lot of situations, user flashed firmware, doesn't do the EEPROM reset and the firmware is using bad data and yes, we see offsets and slamming axis ends.
Again, that happens a lot.

However, this case is different, you chose the wrong firmware type for the hardware printer you have- maybe not fully understanding the name and assuming a 2560 is correct because your board has a 2560- but again this is a combo that would never work, Core XY firmware on a Cartesian printer.
"Name CloneR1  (Chosen during the upgrade from 7.6 to 7.7)"

The correct type to flash and upload for a CTC

Jetguy

unread,
Sep 11, 2018, 8:58:20 PM9/11/18
to Jetty Firmware
And, after you then flash the correct firmware, then ALSO ensure you do the EEPROM reset procedure to match the new correct firmware.
Then your printer will actually work.

Alan Mclean

unread,
Sep 11, 2018, 9:20:46 PM9/11/18
to jetty-f...@googlegroups.com
All done and working, thanks again.


Alan

--
You received this message because you are subscribed to the Google Groups "Jetty Firmware" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jetty-firmwar...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages