Hi Chris,

I'd like to see i.e. the GCODE Console output always visible on screen, so I do not need to switch between the several sections back and forth again and again when experimenting.

Other than that, I'd like to have instead if a single line input for gcode some sort of 'copy and paste' multiple line edit window (again ... when experimenting...)

On top, some sort of customizing aspect when using pre-defined interactions, like 'Run Mesh ...'

I know, last points belong more into the 'feature request' section, but ...

Glad you sorted it out

As said, I made good experience with a paperclip. Flattened one end, put it between the connector and the housing, wiggled a bit, other side. Et Voila.

Keep in mind the config_override.g, so editing config.g might not show any difference

Ever thought about putting all the hardware on top, just the tubes running down, so more clearance around the nozzle, using the 3 holes around the centerhole for mounting the hardware, keeping the balls at the designated spots?

In theory, you can also use this then to add a direct drive instead of using a bowden

Picture?

Cheap Solution

https://github.com/JohnSL/FSR_Endstop

Had the cf arms as well, I mean, I still have them, but I wanted to rebuild my second delta, but never happend... ...
so you could create a mount for the arms to the Smart Effector shouldn't be too complicated, if you need some help there let me know.

You have the Tricklaser Trucks?

But money is the problem ... got the point\

If you want an easy and cheap solution, go for the pressure sensors...

I'd say get one of the Smart Effectors... I do NOT believe it makes sense to include firmware support as just a very few people may use this piece of hardware.... (still have on in my box of parts I ripped out of different printers )

If it does not flash, it is either the wiring or the PCB.

I managed to screw one smart effector, was just a tiny spot on the PCB, looked like some 'dirt', was actually this was causing lot of trouble as I could not calibrate the printer. Was showing different results everytime....

Doublecheck the wires / crimps in worst case, redo them to be sure (on both ends).

When you tap the hotend while connected, does the LED flash?

Check for physical damage

Thanks for the reply.

I checked both of my config.g and the .gcode, as well as the additional starting script for the T0 and it was always there, not only in the config.g

I tried to put it into several places, had T-1 in the ending script, beginning of the start script a T-1 followed by a T0, just played around a bit.

When I use this sequence:

M140 S[bed0_temperature] ; get bed heating up
M116 H0 ;wait for bed heater
G10 P0 S[extruder0_temperature] R60 ; set extruder temp
M116 P0 ; and wait for extruder

T0 ; Activate Tool 0

It waits for the bed to heat up, then the tool becomes active, started heating and moving, not waiting until the hotend reached its temperature:
Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault

Even if I try the M116 without additional parameter, it does the same when I have the T0 after the heating section.
If I have the T0 before the section, every print which is not the first print after a reset waits forever.

I have multiple printers (not all Duet based), so I prefer to use my old way of working.

If this is a feature I have to deal with it, but maybe it is not ...

Holy Sh*t