RepRapFirmware 3.0

clearlynotstef

@bearer duet 2 Wi-Fi

A Former User

@clearlynotstef said in RepRapFirmware 3.0:

@bearer duet 2 Wi-Fi

Then maybe you should wait for someone else to tell you that driver 0 is not the one labeled for Z as you seem to ignore me telling you that ... because you're not going to have much success until you do.

clearlynotstef

@bearer... I'm not disagreeing with you, I thought you were proposing a different way of achieving this setup, not trying to correct the way I currently have it setup, it wasn't particularly clear. "Should be driver 2" sounds like a suggestion, not a fact. One would think the drivers would be numbered sequentially from one side of the board to the other.

dc42

@clearlynotstef said in RepRapFirmware 3.0:

@bearer... I'm not disagreeing with you, I thought you were proposing a different way of achieving this setup, not trying to correct the way I currently have it setup, it wasn't particularly clear. "Should be driver 2" sounds like a suggestion, not a fact. One would think the drivers would be numbered sequentially from one side of the board to the other.

You would think that; but they are not. The order is 2 1 0 3 4.

clearlynotstef

@dc42 good to know. I think I'm going to abandon running them off one stepper anyway (unless there's a way to use two endstops that makes sense), so I'll have two drivers driving two motors on the y axis, each with an endstop. Let's say y driver and e1 driver. Does any sample g code exist for setting these up with their own end stops on 3.0 beta?

dc42

@clearlynotstef said in RepRapFirmware 3.0:

@dc42 good to know. I think I'm going to abandon running them off one stepper anyway (unless there's a way to use two endstops that makes sense), so I'll have two drivers driving two motors on the y axis, each with an endstop. Let's say y driver and e1 driver. Does any sample g code exist for setting these up with their own end stops on 3.0 beta?

No, but it's fairly straightforward with RepRapFirmware 3. Use M584 in config.g (before any M350 or M906 commands) to define your Y motors:

M584 X0 Y1:4 Z2 E3

and use M574 to define the endstop switches:

M574 X1 S1 P"xstop" ; X min active high endstop switch
M574 Y1 S1 P"ystop,e1stop" ; Y min active high endstop switches
M574 Z1 S1 P"zstop" ; Z min active high endstop switch

Omit the M574 Z command if you use a Z probe to home Z.

clearlynotstef

@dc42 thanks! While I've got you. Let's say I do want to use the z driver for both Y motors, obviously I could only move them both or neither, but could I configure it with two end stops such that it isn't home until they're both pressed?

A Former User

@clearlynotstef said in RepRapFirmware 3.0:

@dc42 thanks! While I've got you. Let's say I do want to use the z driver for both Y motors, obviously I could only move them both or neither, but could I configure it with two end stops such that it isn't home until they're both pressed?

Wire switches in series or parallel depending on normally closed or normally open; but the first motor won't stop until both swtiches are active so you will have collisions.

clearlynotstef

@dc42

I'm stuck. I've used your gcode above, omitting the z line as I'm using a probe.

M584 X0 Y1:4 Z2 E3
M574 X1 S0 P"xstop" ; X min active high endstop switch
M574 Y1 S0 P"ystop,e1stop" ; Y min active high endstop switches

I've switched the S1 to S0 (but tried it both ways).
The machine properties window lists X, Y, Z, E0 for endstops. X works as expected. The Y axis (as a reminder, two motors and two end stops) does not. The respective indicators on the board light up when the endstop is triggered, but machine properties never switches to Yes. Interestingly, if I remove one of "ystop" or "e1stop" from the second M574 command, machine properties switches to Yes for the Y axis upon pressing the endstop that remains (Y axis turns to Yes if I remove e1stop from the command and press the ystop endstop, or if I remove ystop from the command and press the E1 endstop), but if I keep both, Y never turns to Yes if I press either or both endstops.

any ideas?
is it the even desired behavior that Y turns to yes in the machine properties window if any of the endstops belonging to that axis are triggered (or both?) Why is E0 showing as an endstop in that list?

Thanks as always!

denke

@dc42 Would you consider adding a new gcode to "load default pin assignment" and not load it by default?
This way if someone wants "compat mode" because has a fairly defualt use case he/she can put it somewhere in the top of config.g, if not then the user can create a custom pinout for him/herself without the need to deassign pins from their default function first.

I think it would create a clearer case.

... ?

dc42

@clearlynotstef said in RepRapFirmware 3.0:

@dc42

I'm stuck. I've used your gcode above, omitting the z line as I'm using a probe.

M584 X0 Y1:4 Z2 E3
M574 X1 S0 P"xstop" ; X min active high endstop switch
M574 Y1 S0 P"ystop,e1stop" ; Y min active high endstop switches

I've switched the S1 to S0 (but tried it both ways).
The machine properties window lists X, Y, Z, E0 for endstops. X works as expected. The Y axis (as a reminder, two motors and two end stops) does not. The respective indicators on the board light up when the endstop is triggered, but machine properties never switches to Yes. Interestingly, if I remove one of "ystop" or "e1stop" from the second M574 command, machine properties switches to Yes for the Y axis upon pressing the endstop that remains (Y axis turns to Yes if I remove e1stop from the command and press the ystop endstop, or if I remove ystop from the command and press the E1 endstop), but if I keep both, Y never turns to Yes if I press either or both endstops.

any ideas?

is it the even desired behavior that Y turns to yes in the machine properties window if any of the endstops belonging to that axis are triggered (or both?) Why is E0 showing as an endstop in that list?

Thanks as always!

Are you definitely running RepRapFirmware 3 beta?

dc42

This topic is getting long and hard to navigate, so I am locking it and creating a new one.