When i try to home it moves up a few mm and then nothing. issuing a m119 shows the zmin as triggered when it shouldn’t be and open when it should be triggered. is there a way to reverse that without modifying the firmware and reflashing?
Where did you get the firmware? Which board is it?
firmware from the github skr pro 1.2
Which one? Hopefully MarlinBuilder releases, but there are still several versions.
I went and looked at where i got the files and it seems to take me to the same place as you just linked. I basically just followed the link from the skr pro 1.2 setup guide.
I have used the dual end stop firmware but havent wired up the end stops yet. Trying to get all my issues ironed out before I do them. That shouldnt affect the z probing i dont think, shoukd it?
There are two dual endstop skr pro versions. Dual is for MPCNC DualLR is for the Low Rider. Can you please find the filename of what you flashed and copy and paste it in? They do act differently w.r.t. Z homing/probing. Alternatively, you can past the response from M119, along with M115, and we can figure it out.
I’m positive I didn’t use the low rider one but ill double-check.
15:05:15.260 : Reporting endstop status
15:05:15.260 : x_min: TRIGGERED
15:05:15.260 : y_min: TRIGGERED
15:05:15.260 : z_min: TRIGGERED
that’s what M119 read out for me earlier today. Ill send an M115 tomorrow and report back.
That isn’t dual endstop firmware.
Im 100% positive i flashed the dual endstop firmware. V1CNC_SkrPro_Dual_2209-2.0.7.2
Is it possible that its somehow resetting to the default firmware after being rebooted after a while of being off?
It definitely isn’t supposed to do that. I can’t imagine it doing that. But there was someone else saying their firmware seemed to revert back after a while too.
I have definitely never seen that on any other boards, like rambos. But these skrs are newer.
First, flash the firmware again (it is just putting the firmware.bin on the sd card) and verify that worked (M119 should show 5 endstops and M115 should show v509D). If that doesn’t fix the Z endstop, then we can focus on that. Then we can worry about watching the FW version.
Ill be heading to mess with it in a few hours so ill report back then.
So i did M115 before reflashing and it says
14:50:24.453 : FIRMWARE_NAME:Marlin bugfix-2.0.x (Github) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:STM32F407ZGT6 EXTRUDER_COUNT:3 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
14:50:24.453 : Cap:SERIAL_XON_XOFF:0
14:50:24.453 : Cap:BINARY_FILE_TRANSFER:0
14:50:24.453 : Cap:EEPROM:0
14:50:24.453 : Cap:VOLUMETRIC:1
14:50:24.453 : Cap:AUTOREPORT_TEMP:1
14:50:24.453 : Cap:PROGRESS:0
14:50:24.453 : Cap:PRINT_JOB:1
14:50:24.453 : Cap:AUTOLEVEL:0
14:50:24.453 : Cap:Z_PROBE:0
14:50:24.453 : Cap:LEVELING_DATA:0
14:50:24.453 : Cap:BUILD_PERCENT:0
14:50:24.453 : Cap:SOFTWARE_POWER:0
14:50:24.453 : Cap:TOGGLE_LIGHTS:0
14:50:24.453 : Cap:CASE_LIGHT_BRIGHTNESS:0
14:50:24.453 : Cap:EMERGENCY_PARSER:0
14:50:24.453 : Cap:PROMPT_SUPPORT:0
14:50:24.453 : Cap:AUTOREPORT_SD_STATUS:0
14:50:24.453 : Cap:THERMAL_PROTECTION:0
14:50:24.453 : Cap:MOTION_MODES:0
14:50:24.453 : Cap:CHAMBER_TEMPERATURE:0
14:50:24.453 : echo:DEBUG:INFO,ERRORS
14:50:24.453 : echo:Active Extruder: 0
So it seems the firmware reset to the base firmware.
Reflashed it. Now it shows the 5 endstops and right firmware number. Took some cuts. Unplugged it and im going to let it sit and ill come back to it in a couple hours and see what happens.
1 Like
Did you test the Z endstop?
Yes and it worked perfectly after fiddling with homing it a few times. My biggest issue was making sure the plate was flat so the homing was accurate. Just bent it a litte and it worked great. Hopefully the firmware sticks. If it does then i can start doing tool changes and get making inlays like i want.
1 Like