January 22, 2017 at 11:38 am #25759
Okay this is a weird one for me I have had my MPCNC for a while now I bought all of the electronics and belts and screws and so on from you and I must say I have had a ball using this thing. From printing to etching and now I’m trying out my hand at routing and out of no where the Z axis won’t move in both directions. I have changed the ramps board, arduino, stepper controller, updated the firmware and even changed out the stepper motor. for the life of me I can’t figure it out.
Silverback94January 22, 2017 at 11:43 am #25761
Use the RC7 firmware, and test with manual movements from repetier. If that works it’s a gcode issue if that doesn’t work we can leave gcode out of it.January 22, 2017 at 12:00 pm #25762
Sorry I should have been more specific, that is the version that I updated to and I was trying manual movements cause my first thought was gcode as well.January 22, 2017 at 12:15 pm #25763
check your z endstop port. If it is triggerd somehow it will only move one way.January 22, 2017 at 12:25 pm #25768
Well that’s the funny thing, if I click on the Z up the motor goes down if I click on the Z down the motor goes down until it hits the endstop then it quits. Now if I flip the wires on the motor connector and do the same thing the motor moves in the opposite direction but it won’t move in both directions just one depending on how I plug it in???January 22, 2017 at 12:33 pm #25770
Oh you are using endstops…check your firmware settings there are multiple things you need to adjust.
Sorry but I don’t support endstops because of this. You have a min and max setting, direction setting, safety setting, home direction setting, home speed setting, bump setting.January 22, 2017 at 12:37 pm #25771
Ah ha I am used to the older version with just the true/false statement on the min. let me check those out and I will let you know.
And thank you very much for the help.January 22, 2017 at 1:00 pm #25778
well I disabled endstops altogether and it still only moves in one directionJanuary 22, 2017 at 1:02 pm #25779January 22, 2017 at 1:09 pm #25783
Use my firmware and physically unplug them and see what happens.January 22, 2017 at 1:24 pm #25790
I get this when I try to upload
exit status 1
using typedef-name ‘fpos_t’ after ‘struct’January 22, 2017 at 1:26 pm #25796
this is the ver. im trying B16_32_fullG-112515January 23, 2017 at 1:53 am #25804
I ran into that error at one point also. You can rename that variable throughout the code, to something other than fpos_t like fpos_t1 or fpos_tbacon for example, and then save and compile.
Found my answer here originally
JohnJanuary 24, 2017 at 5:11 pm #25922
Thank you John, It’s going to be a couple of days before I can try it out but I will let you know.January 26, 2017 at 9:01 am #26024
Well here is the update, I have brought the mega and the ramps into the house along with a power supply and a stepper for the z axis. In response to Johns post I did get the B16_32_fullG-112515 version to load by changing the fpos_t to fpost instead of fpos_t1 after looking trough the forum he suggested that seemed to work better. Now I did not change any settings in the firmware just loaded it and tested with repetier manually moving the z axis and I still have the same problem, if I move the stepper to x or y it functions normally???January 26, 2017 at 9:28 am #26028
I don’t believe changing the firmware was the best of options. This is not a common issue around here.
What manual speeds are set in your repetier?January 26, 2017 at 9:31 am #26029
the firmware you are using is also an old one. If you use the newer RC7 I have a feeling it would compile properly for you. either comment out the lcd or install the lcd library. as soon as the nest working reviosn comes out I will put up another non lcd version.January 26, 2017 at 9:45 am #26031
I didn’t have a problem with the RC7 compiling I only went back to the old one after you posted this “Use my firmware and physically unplug them and see what happens.” I thought that’s what you meant, no problem though i will go back to RC7 and see what happens. the manual speeds are set to; Travel feed rate 500 and z axis feed rate 100.January 26, 2017 at 9:48 am #26032
the z axis can only go 8mm/sJanuary 26, 2017 at 9:49 am #26033
and the x and y are maxxed at 190mm/s, but 80 is more reasonableJanuary 26, 2017 at 9:57 am #26034
still only moves in one directionJanuary 26, 2017 at 10:01 am #26035
still sounds like your z enstop pin is shorted.
Disable them in the firmware and that should make it work.
if it is only going down and makes a noise trying to go up you have to much friction in the system, if it make no noise at all it is an endstop issue.January 26, 2017 at 10:03 am #26036
but if you bought it from me I actually test the endstops for shorts so it should not be the issue, unless you sorted the pins when you put on your ensdtops. either way disable them in the firmware and I am confident that will sort it out.January 26, 2017 at 10:05 am #26037
I don’t even have it attached to the machine, and the endstops are disabled, I even just now tried using the LCD control panel to move the z axis up and down and it only moves in one direction, I don’t know what the heck is going on with this thing…January 26, 2017 at 10:10 am #26038
The pins can be shorted. I suggest you disable them in the firmware. My firmware has them enabled by defualt. The pins, solder points, or mega can be the endstop issue but disabling them in the firware should fix it.
I can give you all kinds of options to try but I prefer to eliminate the most likely issues one at a time in order.January 26, 2017 at 10:12 am #26039
yes they are disabled in the firmwareJanuary 26, 2017 at 10:20 am #26043
I feel we have bee through all of this.
1-flip the plug, if it moves the other way it is not mechanical.
2-swap drivers, if it still doesn’t move
3-check to make sure all pins are in the drivers and in the ramps to arduino.
4-disable the endstops in the firmware
5-maybe your mega diedJanuary 26, 2017 at 10:24 am #26044
1-flip the plug, if it moves the other way it is not mechanical. I moves the other way so doesn’t seem to be mechanical.
2-swap drivers, if it still doesn’t move one of the first thing that I did and didn’t change anything.
3-check to make sure all pins are in the drivers and in the ramps to arduino. Done and Done
4-disable the endstops in the firmware Done and Done
5-maybe your mega died Changed out the Mega and same problem.January 26, 2017 at 10:40 am #26046
Fixed it!!!January 26, 2017 at 11:12 am #26048
what was it?
You must be logged in to reply to this topic.