Topics created by crchisholm

Glad to hear.

can you disable / unconfigure it (after homing/leveling/whatnot) to avoid it stopping a print, or will the pin drop if you do?
(as a band aid while you figure something else out)

Excellent! Sorry about the typo...

Thank. I am letting my frustration level subside a bit and will jump in this tomorrow.

@crchisholm said in no connectivity - no blue light.:

Using an older backup (cant find the more recent one) I got the blue light to come on for a short time and accessed DWC. Homed the Y axis, and the light promptly went out half way home and I could no longer ping the ip.

I have a copy of the config.g file from one of my posts on this forum. If I remember correctly, that is the only thing I’ve changed. If I find an older version of the SD, can I just update config.g, copy in the newest update file and see where that leaves me?

Yes, you can do that. You may need to update Duet Web Control on the SD card it it is very old.

I just wanted to pop in here and say how I resolved this issue of a blinking BLTouch after replacing the pin. Apparently the new pin was not properly formed when cast. After hours of troubleshooting I took the BLTouch apart, removed the pin and sanded it lightly with 400 grit emery paper. I then put a very light coat of silicone lubricant on it and reassembled. After this it worked just fine.

@crchisholm said in Strange behavior from BLTouch:

No, it doesn’t blink. Also, I don’t know if this has anything to do with the problem, but if I deploy with M 401, and then trip it with my finger, the pin retracts and then deployed again right away. (That may well be normal behavior, fhough)

I think that's normal behaviour. M401 tells the firmware that you want the probe extended. For BLTouch there is no reason to use M401 or M402 except for testing the deploy and retract macros.

Well, turns out there was a wiring/termination issue. I re-terminated the wires (black and white) and everything worked great. Thanks for all the suggestions.

longshot, but maybe try if your router has a usefull dns server that allows you to use the duets host name regardless if ip address?

Well I said I successfully edited the config, but I didn’t realize that the config.g file was zero bytes after the save. I’ve been having some issues with loosing the connectivity quit often and I guess that happened during the save.

I grabbed the config.g.bak but unfortunatly without my last setup for the probe. Oh well. Set it up once, I can do it again.

Thanks for the suggestions.
Charlie

@stephen6309 sorry for the late thanks, but thank you for responding

Ahhh....that explains why It would skip anything less than 30 in the X direction. My offset is X30 Y15. Should have figured that out. Thanks.

Great. Thank you. I cut the trace before submitting this question, but glad I don’t have to fuss with the resistor.

Glad it's working.

The control wire can go to various pins, you can choose any of the additional heater outputs on the expansion connector. Our standard instructions use pin 8, see https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_2_WiFi_Ethernet_without_a_Duex_2_or_Duex_5_expansion_board.

Ouch. Then I guess I shouldn't mention the t-shirt and shorts whether we've been having recently. Opps. To late.

Very cool! So if I create a small device that the filament runs through and when it runs low the micro switch opens or closes to stop the print job until I can change filament spools. I like that!!! No more checking every five minutes when I know I am at the end of the spool.

These commands should already exist in the config.g. you can just change the values.

If you post your config.g file we can point out where.

This guide discusses how to setup the motor directions, etc

https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Movement_section

ok......false alarm. I got it to work and send a response. Not sure what I am doing differently but it works now

@dc42

Well, you just sold me!!