Best posts made by SonnyD1

@dc42

Like this?

@jay_s_uk Apparently that was the issue. I bought a USB 3.0 cable and made it up and now its working. Don't know what to do with that data yet but thats a different issue. I'm making progress thanks to the help. Thank you.

@droftarts adding a code example for the G10 showing the offsets and explaining how one get them. I’m any case, I’m complete I think.

@droftarts They are both named correctly IAW your instructions. Here are the files:

; deployprobe0.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Sat Aug 10 2024 17:00:40 GMT-0400 (Eastern Daylight Time)

M280 P0 S10	; deploy BLTouch

; retractprobe0.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Sat Aug 10 2024 17:00:41 GMT-0400 (Eastern Daylight Time)

M280 P0 S90	; retract BLTouch

I might have a bad crimp. I'm going to redo the connection.

@droftarts said in Configuring Multiple Probes/Endstops:

What reading for the Z probe is reported in DWC?

Where do I find this? Dashboard?

UPDATE: I found the issue. Conducting further tests to confirm. I must have had a bad crimp/connection. I made a whole new wire and now it deploys on command. The connectors on the Roto toolboard are so tiny that crimps are kinda tough. So much as a couple frayed wires and ya lose continuity.

@Phaedrux so that was one thing I just figured out. I unplugged one motor and homed Y. I repeated this for each motor and discovered how the obvious escapes me sometimes. The motors are mirrored so obviously one would be backwards. Fixed that now moving on. Still trying to get a complete homing cycle. Thank you very much for the reply.

@Phaedrux Yes I found it. I had two wires swapped on the U axis endstop. Thank you very much. I'm still not up and running but its progress. WIFI Module fires right up now.

@moth4017 so I lowered it to 1900. Repeated the G32 that was triggering the error and it completed this time. I'm pretty sure that will be enough current. If not, now I know I will have to add additional cooling to the boards. I may end up doing that anyway. Thank you for the help but I think you've solved my issue for now.

@Phaedrux Ok so my board is mounted horizontally with 10mm of air on the bottom side. I am going to raise that amount as much as I can and add a 24v blower wired to "Always on" that will blow across the bottom of the board on the drivers. Also, I turned down the current to 65%. I don't plan on speed printing with this printer so I will run some tests to see if that's enough. Based on your advice these items will resolve my issue. It will take some time to complete the hardware adjustments so for now I will consider this issue solved until I can run some additional tests. That is, unless you disagree?

@droftarts ; Tools
M563 P0 D0 H1 F0 ; define tool 0 that used low end X carriage
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H2 F2 X3 ; define tool 1 that used high end U carriage
G10 P1 X0 Y1.6 Z.34 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

@Phaedrux Yup that fixed it. So my M568 lines now read as:

M568 P0 S{first_layer_temperature[0]} R{first_layer_temperature[0] -15} A2 ; set E0 active/standby temp
M568 P1 S{first_layer_temperature[0]} R{first_layer_temperature[0] -15} A1 ; set E1 active/standby temp

Thank you for your help everyone. I'm still having other issues with my startup code but I will address those in another post. I don't want to flood this post. I consider this particular issue resolved.

@br7408 Your the first person outside of work that knows what that symbol means. Nice to meet ya Chief!

@fcwilt I did not. I didn't even look for them because I figured the configurator would have created them. They are created now and I am conducting further testing.

I got it now. I have my speed turn up to a point that I like it and it probes Z in the center of the bed like it should too. Thank you @fcwilt and @droftarts.

@dc42 There is a 2mm space between the printed duct/base and the board. The fins inside the duct channel the air directly to the bottom of each driver chip then dispersed out across the bottom of the board via the 2mm gap. I hope I'm explaining that well enough.

@droftarts

Ian,

So the M587 did indicate that I had two. Apparently, its case sensitive. I had one in all caps and one not in caps of the same network. I can see how that could be confusing to a computer. I cleared them both out with the M588 and confirmed with a M587. Then I input new M587 parameters. I think that may have been the issue. I just went through about 10 off/on cycles and it connected quickly every time. I couldn't see that before because I was working with the paneldue. The DWC shows everything much better. I will conduct some additional testing to confirm, but I think that's got it. I'll let you know.

Sonny

@rechrtb Yes same UN and PW. They were both the same network. One I entered in all caps, the second was lowercase. The M587 command showed them both. When it attempted to connect, that apparently caused a conflict. Once I cleared them both out and entered in one single M587 parameter, the issue went away and it connects perfectly now.

@Phaedrux Yea you nailed it. I went and ran another jumper wire and it worked. So I ran all new wiring. Musta been a bad crimp like you said. The LED on the switch lights up and I get a filament error when I remove filament just like it should. I know I'm a pain and this was a headache but I really appreciate you hangin in there with me. Sometimes the most obvious solution eludes me. TYVM!!!

@jay_s_uk Yea I meant IO2. It just strikes me as weird hooking one device across two pin locations. I understand now. Thank you for your patience and clarification @dc42 , @droftarts , @jay_s_uk , and @Phaedrux for the help. Configuring it will be the next interesting endeavor. Still got some hardware work to do first.

@Phaedrux Yup, I found the 120 error. For some reason my config.g had the z scanner connected to a 120 board. I must have screwed it up when I was configuring.