Topics created by SonnyD1

@Phaedrux configtool.json How bout this?

@droftarts That is outstanding. I'm glad I could help. I'm the one that set this IDEX up in the beginning but I couldn't remember how. All it took was a clogged nozzle resulting in a nozzle change to throw all my work out of whack. I couldn't remember how I did it in the first place thus this post. As usual, you've managed to rescue me. I have a much better understanding of the offset and will hopefully retain it better. Thank you!

@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 That's exactly what I was thinking. I need some exaggeration. Thanks for the help. I'll get back with ya!

@droftarts I appreciate your help. Thank you very much!

@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.

@oliof WOW. I never would have thought. They weren't even that tight. I loosened em up just a bit and it works perfectly. Why? Thank you @dc42 and @Phaedrux for your replies but it appears the screws were to tight. I feel stupid that the solution was that simple. Thank you.

@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.

@SonnyD1 I think you mean the '2.0mm pitch jumper', ie the jumper fits on pins that are 2mm apart.

Ian

@SonnyD1 said in SFS V2.0 to Duet 3 Mini:

paneldue

Does the PanelDue firmware match?

@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.

@droftarts @achrn Between the two of you, its working properly now. This is my first time using the new config tool. I don't remember the old one making these kinds of mistakes so I didn't think to check. There is an always on fan on my board that isn't functioning that I'm sure I can figure out on my own. I appreciate your help and patience during this process. Hopefully, I can get through the rest of the commissioning process on my own. TYVM!

@dc42 Ok...Thank you very much. I'm sure I'll need your help again when I start to configure this thing.

@T3P3Tony Ok outstanding. Thank you!

@dc42 will the heat from the bed/hot end be an issue? Will I have to stow it during a print? How much heat can it handle?

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.

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

@Phaedrux I did as you advised and sent that email. I haven't yet received a reply.

Thank you for the help everybody. What I wanted to accomplish isn't possible with my current hardware. I've decided to go in another direction and replace the 12864 with a paneldue. I really appreciate you taking the time @dc42 and @DIY-O-Sphere.

@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.