Found myself with a printer I can't communicate with

Moderator: vert

buttervonwaffle
Posts: 40
Joined: Sat Jan 05, 2019 6:12 pm

Re: Found myself with a printer I can't communicate with

Post by buttervonwaffle » Thu Jan 10, 2019 12:03 pm

try sending G-code M119 and check the status of your switches. you might need to reverse them in configuration.h this is how the code should look it will be in your configuration.h file

Code: Select all

// Mechanical endstop with COM to ground and NC to Signal uses "false" here (most common setup).
#define X_MIN_ENDSTOP_INVERTING false // set to true to invert the logic of the endstop.
#define Y_MIN_ENDSTOP_INVERTING false // set to true to invert the logic of the endstop.
#define Z_MIN_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define X_MAX_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define Y_MAX_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define Z_MAX_ENDSTOP_INVERTING false // set to true to invert the logic of the endstop.
#define Z_MIN_PROBE_ENDSTOP_INVERTING true // set to true to invert the logic of the probe.
Also you can check and make sure you connectors are connected to the board for the x end stop.
If something I said just helped you out tremendously you can drop a little ramen money, the coding monkeys in my basement will appreciate it - Feed them here

You can private message me if you have any questions I might be able to help.

bunnysando
Posts: 11
Joined: Wed Jan 09, 2019 11:32 am

Re: Found myself with a printer I can't communicate with

Post by bunnysando » Thu Jan 10, 2019 1:39 pm

When you say send gcode M119 do you mean through something like easyprint or repetier? I tried that and looked at the logs but it's pretty undecipherable to me.

if I change configuration.h do I re-upload the whole firmware thing again?

I noticed that the Z endstop lights up when activated, but the x endstop does not.

buttervonwaffle
Posts: 40
Joined: Sat Jan 05, 2019 6:12 pm

Re: Found myself with a printer I can't communicate with

Post by buttervonwaffle » Thu Jan 10, 2019 1:50 pm

Yeah you would send the g code through easyprint, repetier or similar 3d slicing software.
Now basically what your looking for when you send the gcode m119 is to see if when the head is in the center and middle of the z axis x axis and y axis away from the end stops. That none of the end stops are reading triggered. Then manually press the x endstop and send the m119 g code and see if it reads triggered. But definitely check your x endstop connections make sure they are connected, if all else fails the x axis end stop could be fried but luckily they are cheap off ebay.

I would however run those tests, check connectors and confirm its not a firmware related issue.

And yes if you change configuratiion.h you will need to upload the firmware over again.
If something I said just helped you out tremendously you can drop a little ramen money, the coding monkeys in my basement will appreciate it - Feed them here

You can private message me if you have any questions I might be able to help.

bunnysando
Posts: 11
Joined: Wed Jan 09, 2019 11:32 am

Re: Found myself with a printer I can't communicate with

Post by bunnysando » Fri Jan 11, 2019 4:08 am

I was able to upload the new configuration.h, still had some funny behavior...autohome wasn't effective, it just kept moving +10x and +10Y from it's current position. Tried printing and the head bumped into the other side of the gantry.

I put head in center of all axis, and ran M119...it said

11:52:39.459 : x_min: TRIGGERED
11:52:39.459 : y_min: TRIGGERED
11:52:39.461 : z_min: open

I also unplugged the x and y endstops and got the same result.

So I grabbed some new ones off ebay...here monday

buttervonwaffle
Posts: 40
Joined: Sat Jan 05, 2019 6:12 pm

Re: Found myself with a printer I can't communicate with

Post by buttervonwaffle » Fri Jan 11, 2019 8:48 am

you can try switch all the endstop code to true that i posted.
I also just checked my endstops on my printer the only one i see that lights up is the z end stop. I personally think you have a firmware issue going on, But I could be wrong.

Code: Select all

// Mechanical endstop with COM to ground and NC to Signal uses "false" here (most common setup).
#define X_MIN_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define Y_MIN_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define Z_MIN_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define X_MAX_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define Y_MAX_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define Z_MAX_ENDSTOP_INVERTING true // set to true to invert the logic of the endstop.
#define Z_MIN_PROBE_ENDSTOP_INVERTING true // set to true to invert the logic of the probe.
If something I said just helped you out tremendously you can drop a little ramen money, the coding monkeys in my basement will appreciate it - Feed them here

You can private message me if you have any questions I might be able to help.

Post Reply

Who is online

Users browsing this forum: No registered users and 14 guests