I am building an MPCNC primo (dual endstop), and an having issues with the firmware.
Am using SKR 1.4 with TMC 2209 V1.2
This is the firmware I downloaded from V1:
V1CNC_Skr1p3_Dual_2209-2.0.7.2-src
currently I have the X axis working and z axis working but only one Y motor working
I have downloaded several different versions of marlin and have had the X nd Y axis working but the Z moves while making a high pitch whine, I downloaded the Firmware from v1 engineering and it cured the whine but the Y motor stopped turning.
I know its something in the marlin software just don’t know where the bit of code I am having problems with is.
Its a SKR 1.4 (not turbo)
How do you do M122, don’t have repiteir host just the mpcnc and firmware
Pulled out the endstops and that didn’t change it
Swapped the motors round and the motor worked in the new spot and the motor put in the no working position stopped working
I have also had different motor not turning with different firmware loaded, so its definitely code.
I hope this helps, have been working through this problem and looking through the marlin code learnt a lot, but still frustrating. I’m suspecting that the motor information is not being sent the the stepper driver hence it not working. I checked the pin numbers in the 1.4 file and they seem correct.
That is fine, as I said above I had other firmware in that had the motor running,
the issue there was that it made the z axis motor make a high pitch noise with a partial run, so I changed the firmware now this motor won’t run.
I also had the no run happen on an x axis motor with a different bin file.
Which means at some point they have all been operating properly. The kicker is not at the same time,
I missed the first part. As I understand, you are using 1.3 firmware on a 1.4 board. If so, you probably have to alter boardname in configuration.h (near line 132) and check the pins-file and compile the firmware yourself.
I’m afraid you’re in uncharted territory. I don’t have a 1.4 board, and I’m not sure what pins those should be set to. If you figure it out, we can document it here, and link from the software release page.
This is not the setting… Stallguard is the sensorless homingthing in the TMC drivers. I assume you have removed the diagpin from the drivers? Else they can interfere with the endstopswitches…