Posts made by oliof

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

@SelfHatenMarine the guy you bought it from is almost right, you only need to setup the wifi and then you can use the duet web control.

On a Mac, I would use the Terminal.app and the built-in screen command for the serial connection.

I would suggest some quality time with the extensive documentation at https://docs.duet3d.com, especially the Getting Started page.

Also, make a backup of the SD card before changing anything.

@RodrigoRMaraujo should work

@Pyper yeah and you can see a pretty neon-ish/pink leaning light/muted color palette on the print sample (-:

@RodrigoRMaraujo your best bet is to return the board under warranty. With these clones it's always an element of luck whether they work or not.

I dimly remember from my scara times that you need to be careful defining the angular range and endstop position, I am pretty sure I got it wrong multiple times until the moves went into the direction I wanted. So a diagram of the machine with endstop positions and your config.g may also help shed light on the situation.

@Carter3DP which slicer are you using? Simplify3D has a "flip Y axis" setting that sonetimes spuriously is on.

You can also temporarily try flipping your axes in RRF with M579 (i.e. M579 X-1 to flip X), but I wouldnt see that as more than a stopgap measure

@stuartofmt it's been a problem 2008-2012ish in some networks I've been on, but I can say its never been a problem for a Duet2Wifi, Duet3mini, or any of the ESP8266/ESP32 modules for the STM port.

@CamperWill what's your M208 acis definition for Z? if you do have a bed mesh that goes down to -5.5 you need to set the Z axis minimum to about that. I would set it to -6.

If this machine has been decomissioned for a while you also may need to check that the piezo control board is tuned to the new environment but that does not seem to be the issue.

More soecific advice would require a couple photos of the machine and probaby a full copy of your config files.

also try a resistor of appropriate resistance in lieu of a thermistor to check whether the duet reports the right temperature.

@CamperWill first off, a piezo probe reporting all negative values is kind of expected and you need a rigid surface for good results.

I am assuming you didnt get this warning or/and better mesh bed results under RRF2. The former may be because no warning was issued in that older firmware, but I don't know for sure.

When you do subsequent mesh bed runs, are the results comparable or is the high variability random for all your points? You could also do a repeatability test for your probe. Lastly, if you reduce rhe dive soeed for probing, does the range/error reduce?