@wdenker sorry, I was looking at your config.g you posted earlier, and I could have sworn it said the extruder drive was on 0.0 and the filament sensor was on 1.out1.in!
Could you post your current config.g, in case anything has changed?
@droftarts we figured it out. The bltouch had a small metal shaving in the pins from factory. Then the fans the config.g somehow didn't get copied over. So I got a little ahead of myself with this post.
I would like to see a paramater added to G1 command for example G1 M5 Z10 which would say move motor 5 positive 10 and leave the remainder z motors stationary so that on bigger builds you can get the bed closer to level prior to running a G32 mechanically leveling the bed. This is critical for bigger dual gantry machines as if the one head corner is close and the opposite corner is 20 mm away the secondary head will crash into the bed before it can probe the other corner.
What you can do is what I did.
Each Z stepper has it's own endstop sensor.
With this you can home using G1 H1 moves as you would for X and Y.
I designed and printed adjustable mounts for the endstop sensors so I can tweak their position to get the bed very nearly level using the G1 H1 approach and then finish the leveling using G32.
@wdenker There is no post processing script. I simply took two short gcode files (generated with sandify) with roughly the same amount of moves and cobbled them together. TwoTools.gcode
@wdenker, as @Alex-cr said you can set up the second temperature sensor as an over-temperature cutout, using the M143 command.
If they are thermistors or PT1000 sensors, you can average them by connecting them in series or in parallel and then treating them as a single sensor with double or half the resistance. Series connection is safer because if either connection breaks, the whole sensor will go open circuit; however when using thermistors, the average will be biased towards the lower temperature of the two.
It's quite unusual to deal with a bulk warranty claim. For the sake of keeping things clear and accurate, would you please create a separate thread for each item?
Please include as much detail as possible for each one. What hardware exactly, what the problem is, relevant photos, M122 or config.g, and most importantly where and when it was purchased.
Sorry for the inconvenience but I think this will help things progress the smoothest.
@wdenker i don’t think that is how it works... unless you want to do parallel printing, but that adds a whole new level of complexity to the slicer side, daisychaining control boards via SBC, probably syncing Z, or go with Autodesk project Escher kind of way... complicated stuff..
As current setups go, you do mirror or duplication, and while it looks individual, it really isn’t. Without a user error, they will not collide.
If you’d like to just add redundancy and eliminate the potential user slicing error, you could put an extra endstop (preferently optical) on one of the gantries and before they collide, they stop.
