Posts made by oliof

@yoshimitsuspeed the IR probe does not work as a scanning probe but dc42 indicated it should be pissible to turn it into one with firmware modifications. Nobody has indicated that this work is planned though.

@Exerqtor one for @droftarts

@br7408 it didnt endeavor the threat of replacemebt I guess.

@Electriceye to check drivers to work you cant just use a multimeter, you need to use an oscilloscope to see whether they properly generate steps. Alternately you can use a stepper driver analyzer (search the forum for more info), but in the end that's more or kess an oscilloscope with sone predefined settings.

Blown drivers usually exhibit "craters" or little blow holes, so inspecting them visually is another option. Posting high resolution, focussed photos of drivers here allows us to help determine whether a driver is blown or not.

If a driver looks good, the next most likely culprits are still motor wiring/crimps (testable with a pull test holding the housing and tugging on the wires and solder defects for the pins (also visually detectable).

Regarding the Octopus board: The heatsinks on the plastic housing act much less as a proper heat dissipator than the vias designed into duet boards and the high copper content on the duet board.
The duet boards are best cooled by blowing a bit of air above and below the board along the drivers.

Another drawback of the stepstick format is the inherent current limitation and the usual arrangement making proper cooling on top and bottom of the stepsticks difficult, especially with banks of jumpers blocking airflow.

@br7408 it may be a faulty probe, a similar case of this was handled under warranty (ref https://forum.duet3d.com/topic/30051/ir-probe-faulty-triggers-well-before-the-actual-trigger-point/22). One for @Phaedrux I guess.

@br7408 ISTR that there is a chance for false triggers at high distances due to stray reflections. I dont remember what the workaround/mitigation was.

@bugpwr best to open a separate thread for the separate issue so this can be marked solved.

one of the advantages of CoreXY is that the motors are static for both axes so you get right of the flying X motor. You pay for that with longer belt runs and a bit more challenging belt tension tuning.

its probably easier, faster, and will garner a better file if one were to remodel in fusion from the reference openscad model. I personally think its great to have the reference files in an open, almost human readable format (I cant run fusion, but I can run OpenSCAD on a tomato class computer if the need be).

repair / reinforcement brackets, wall holders to turn rods into hangers, all kinds of connectors; emergency replacement wheels for 1:32 slot cars, self watering plant pots, shims, spacers, wedges, skadis holders of all kinds for a sewing station, ....and some more I forgot about

@Electriceye said in Motor problems on RatRig V-Core 3:

Warning: Driver 0.2 warning: phase B may be disconnected

So...that's not good, looks like 2 drivers may be toast. What a way to start a build.

Before you worry about the drivers being blown, provide photos of the stepper connections on the board and motor side, and of the drivers. The error above may very well be about a wiring issue (either phases not being AA BB, or bad connection).

consider setting up AP mode on the printer for a direct connection.

Besides scanning probes, ypu can also consider ways to reduce the dependency on bed probing:

• build a bed mount that allows for expansion at temp without warping (maxwell / kinematic mount)
• build a machine with a fixed bed (delta / raising gantry which can be trammed with simple endstops)
• use a bed with high thermal mass and a low coefficient of thermal expansion

@elmoret are you saying catographer works with RepRapFirmware? That would be surprising news.

@Polyneutron21 electrical compatibility does not mean functional compatibility. Cartographer speaks the klipper multi mcu protocol, which is very different to RRF's CAN-FD implementation

@droftarts there are the fly SHT36v3 max and SB2040 max boards that are supported by teamgloomy, so those would work.

as superbrain said. Teamgloomy built a reference config using a start_print macro from the slicer, you can have a look at https://github.com/TeamGloomy/Troodon-V2/tree/improved/Config/sys

@SanderLPFRG super interesting! will you also test at elevated bed temps (60/80/100c) to see whether raised ambient from bed has an effect? would be interesting for bed meshes etc.

@axiom octoprint can be run on an rpi5 https://community.octoprint.org/t/raspberry-pi-5-octoprint/60487/2

@o_lampe rails on top of X axis also reduces the lever force of the toolhead with a design considering centre of mass, so I second your recommendation.

@mikeabuilder the PanelDue is a pretty old product and likely would need a firmware change to accomodate your request.

It would be nice to have though to be able to have named tools.