Posts made by jphilly

@t3p3tony I wired a usb c breakout board to the back of the jst header, just with the d+ d- pads

I wanted to use a dual right angle connector on my paneldue so I did this as a proof of concept: 6ft usb c cable working. In case anyone was wondering

Well it seems like the plastic mount I had the board on was somehow shorting it out. Moved the board around/put it on 30mm of standoffs and it kept working as long as it wasn't touching the mount.

@dougal1957

@jphilly said in Duet 2 Wifi MAX31865 bad response:

I've connected a generic MAX31865 board to the spi0 header

It's connected like this post

My wires are about 4in long. 3v3 is connected, vin is not

@phaedrux

It's one of the adafruit clones like this with a 430ohm ref resistor

@phaedrux 3.3

I've connected a generic MAX31865 board to the spi0 header on my duet wifi but it fails to initialise.

It's connected like this post

When I run

M308 S1 P"spi.cs1" Y"rtd-max31865" R430

it returns "Error: M308: Failed to initialise RTD: bad response from sensor"

I've tried cs1 and cs3 but neither will work. Is there a way to troubleshoot the connection?

@t3p3tony I thought it was probably running completely then pausing because it moved, dwelled, then popped up saying it was paused. I tried offloading the dwell and resume to another macro and calling that instead which seems to have removed the noticeable dwell but it doesn't resume so it's hard to tell if it's doing anything. I guess I'll just have to retry when it gets added

I've been trying to set up filament-error.g to resume automatically if it hasn't failed recently but M24 doesn't seem to be working in the script.

var curtime = state.upTime

M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y200 F6000 ; go to X=0 Y=200

; filament error:
if var.curtime - global.lastfail > 30
	G4 S3
	M24
else
	G0 X200
	echo {var.curtime - global.lastfail}

global.lastfail is set in resume.g and I can echo that so it's set. I can get a move to work in the if clause but M24 is not triggering.

On a maestro these 2 board overlap real estate, so one has to be on a riser for both to be installed. Which would be better to put on a riser/ does it matter? Currently I have the drivers on a riser (maybe 15-20mm up)

@diamondback said in New hot end system from E3D?:

E3D mentioned around 120$ for a full hotend with 4 nozzles.

I was quite a bit off then, but I can't see the nozzles or heater being cheap to replace since they're a one off.

I'm not sure about M12 staying put when changing nozzles. At least on my mosquitos it takes a fair bit of torque to loosen a cold nozzle and they're saying it'll be hand loosenable but who knows

It would be nice if e3d would get away from using structural heat breaks and groove mount. It does look like there might be a through hole/screw option for deltas just looking at their page. I assume it'll be priced around the mosquito's level but it's worse imo esp. with the non standard nozzles.

@dc42 So would there be a way to save the z position so it doesn't have to rehome or would it have to be parked? Z homing is the main problem since I likely wouldn't be able to raise the bed fully once there's a print on it.

The only definite position I could drop it to is z max which would take a longer time than possible with power outage given 2mm lead screws

@fcwilt Yeah, problem is that requires re-homing, which is unnecessary if the printer doesn't move when powered down.

Whenever I power down with M81, the board reports vin under-voltage which clears the head position. I get that's the default because it's assumed something will move with no power but there's no option to keep positioning data after a planned power down.

Besides having to re-home after power downs I'd like to be able to pause a print, power down, and resume later with the saved position data. (It'd require some cooling and extra heating on the heaters to avoid a fault but that's sort of separate)

I have 24v on vin and 5v on usb so after vin < 9v it's still on.

@dc42 Thanks for the fix, I'll try the beta when it releases

@Argo Doesn't seem like there's room on the bottom of the expansion for a heatsink

@Phaedrux This is what I get, note the graph and driver sensor.

Last time this happened I touched the pcb and it was warm, so the overheat message isn't erroneous.
The driver should be running at 900mA which is below their max.
They are thermostatically cooled: the fan starts at 40 and will be at 100% at 65. The fan monitors the driver overtemp flag and the mcu temp. Problem is, despite the warnings on the console, the flag didn't raise and turn on the fan as it should have. Even when the driver was overheating the graph and reading didn't change as it should have.

I'm using a Maestro with the 2 driver expansion module. One of the drivers on the module reports overheating to the console but the drivers sensor doesn't show it, it just stays at 0C. Are the drivers on the module not measured by the sensor or is something gone wrong?