Posts made by Marco_76

@marco_76 said in Multiple z motors homing with firmware 3.3:

]

Solved!
I changed the names of the pins: exp.e2stop --> duex.e2stop
So now the sensors for Z are the following and it is working fine

M574 Z1 S1 P"zstop+duex.e2stop+duex.e3stop"

thanks,
Marco

@dc42 Thank you. The issue was in the pin to be inverted. I used "!exp.heater5" and not it's working again.

As always you are top starts in supporting the community.

@dc42 thanks. After some tentative I think I understood the logic. It's working fine for my double motors for the Y axis (see at the end of the post the new config.g), but I still have problems for the Z axis.

other tests I did:

• with M119 I tried with only Z1 sensor activated, only Z2, only Z3, all together. I get Z: at min stop only when Z1 is activated, and when all sensors are activated (but of course in this case also Z1 is activated)
• leds in the duex board are working fine, if I activate a sensor I see the led changing status
• the only difference between Z1 sensor is that this is connected to the duet board, while Z2 and Z3 sensors are connected to E2 endstop and E3 endstop of duex
• I'm using optic sensors for all axes

I tried to launch the Object Model Browser in DWC but it is returning all empty. See here:

M409
{
"key": "",
"flags": "",
"result": {
"boards": [
{}
],
"directories": {},
"fans": [
{},
{},
{},
{}
],
"global": {},
"heat": {},
"inputs": [
{},
{},
{},
{},
{},
{},
{},
{},
null,
{},
null,
{}
],
"job": {},
"limits": {},
"move": {},
"network": {},
"scanner": {},
"sensors": {},
"seqs": {},
"spindles": [
{},
{},
{},
{}
],
"state": {},
"tools": [
{},
{}
],
"volumes": [
{},
{}
]
}
}

Here the new config.g

; Drives
M569 P0 S0 ; physical drive 0 goes backwards(X1) (X)
M569 P1 S0 ; physical drive 1 goes backwards(Y1) (Y)
M569 P2 S1 ; physical drive 2 goes forwards (Z1) (Z)
M569 P3 S0 ; physical drive 3 goes backwards(E1)
M569 P4 S0 ; physical drive 4 goes backwards(E2)
M569 P5 S1 ; physical drive 5 goes forwards (X2) (U)
M569 P6 S1 ; physical drive 6 goes forwards (Y2) (V)
M569 P7 S1 ; physical drive 7 goes forwards (Z2) (W)
M569 P8 S1 ; physical drive 8 goes forwards (Z3) (A)

M584 X0 Y1:6 Z2:7:8 U5 E3:4 P4 ; set drive mapping (number of visible drivers P)
M350 X16 Y16:16 Z16:16:16 U16 V16 I1 ; configure microstepping with interpolation for axis
M350 E8:8 IO ; configure microstepping with no interpolation with extruders
M92 X200.00 Y200.00 Z4260.00 U200.00 E1900.00:1900.00 ; set steps per mm
M566 X1000.00 Y1000.00 Z10.00 U1000.00 E6.00:6.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z500.00 U12000.00 E2400.00:2400.00 ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z20.00 U1500.00 E120.00:120.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 U800 E400:400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 U-23 S1 ; set axis minima
M208 X321 Y308 Z275 U298 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"
M574 Y1 S1 P"ystop+e1stop"
M574 U1 S1 P"e0stop"
M574 Z1 S1 P"zstop+exp.4+exp.9" ; set endstops for Z (zstop), W (exp.4), A (exp.9)

@dc42
I confirm that if I use M950 S0 C"exp.heater5" doesn't work. I tired with M950 S0 C"exp.heater5" Q500 and it's working but with the small movement again. I checked the tech specs of the servo and should operate at 50Hz.

Hi, I just upgraded the firmware from 2.05 -> 3.0 -> 3.3
I have a configuration with a double independent extruders and 3 independent motors for z axis. The three Z axis have endstops.

here the problem

I tied to changed the configuration based on the online guide, but I have a strange behavior:

• Z1 -> if I trigger manually the endstop of Z1 it stop. This stop. This is the only axis working as expected
• Z2 -> if I trigger manually the endstop of Z2 it doesn't stop
• Z3 -> it doesn't move in the direction of homing (but the motor works. I tested this moving up & down after running G92)

I tried M119 when all Z are still not homed, and here the result, where it looks like doesn't see endstops for Z2 and Z3 (axis W and A)
Endstops - X: at min stop, Y: at min stop, Z: not stopped, U: at min stop, V: at min stop, W: no endstop, A: no endstop, Z probe: not stopped

For simplicity I extract here only the Z axis part of config.sys and the the extract of Z in the homeall.g

OLD configuration, which worked well:

Config.g
M569 P2 S1 ; physical drive 2 goes forwards (Z1) (Z)
M569 P7 S1 ; physical drive 7 goes forwards (Z2) (W)
M569 P8 S1 ; physical drive 8 goes forwards (Z3) (A)
M584 X0 Y1:6 Z2:7:8 U5 V6 W7 A8 E3:4 P4 ; set drive mapping
...
M574 X1 Y1 Z1 U1 V1 W1 A1 S1 ; set active high endstops

Homeall.g
M584 Z2 W7 A8 P7 ; split Z motor control to Z1, Z2, Z3
G1 H1 Z-310 W-310 A-310 F350 ; move Z down until the endstop is triggered
M584 Z2:7:8 P4 ; back to combined axes

NEW configuration on firmware 3.3

Config.g
M569 P2 S1 ; physical drive 2 goes forwards (Z1) (Z)
M569 P7 S1 ; physical drive 7 goes forwards (Z2) (W)
M569 P8 S1 ; physical drive 8 goes forwards (Z3) (A)
M584 X0 Y1:6 Z2:7:8 U5 V6 W7 A8 E3:4 P4 ; set drive mapping
...
M574 X1 S1 P"xstop"
M574 Y1 S1 P"ystop"
M574 U1 S1 P"e0stop"
M574 V1 S1 P"e1stop"
M574 Z1 S1 P"zstop+exp.4+exp.9" ; set endstops for Z (zstop), W (exp.4), A (exp.9)

Homeall.g
G1 H1 Z-310 F350 ; move quickly to X axis endstop and stop there (first pass)

@dc42 I tired but using S0 it is not even moving. At least with P0 was doing small angle movements. any Idea?

Hi, I just updated my firmware from 2.05 to the latest version 3.3
I have a duet wifi + duex configuration and I'm now doing all required changes.

I'm using a servo which was working fine with the old configuration. It is attached to the duex PWM pins. Here changes I did:

OLD Config.g
M307 H5 A-1 C-1 D-1 ; Disable the 5th Heater to free up PWM channel 3 on the Duex board
NEW Config.g
M950 P0 C"exp.heater5" ; map 5th Heater or PWM channel 3 on the Duex board

with the old configuration, to move the servo from 0 to 180 degrees I was just using M280 P0 S0, or M280 P0 S90. Now it is still moving, but the servo doing very small movements (about 10 degrees).

My servo is an MG996R

Thanks for your help.

Marco

Dear duet community, I did a quick prototype which is supposed to speed up the calibration of my 2 independent nozzles (the lockdown is probably having bad effects on me :). I use a pi camera on the bed, looking up, and image recognition on raspberry to detect the position of the first nozzle vs the second one. So far I developed a web server on raspberry which is guiding me in a simple 2 min process in 4 steps. It is very accurate as I measure 0.05mm and more. I was thinking that would be even easier by automating all the process by sending gcode directly from raspberry to duet wifi, simulating how the DWC is doing when you put manual gcode. How can I do this?

Next step would be to add a load cell to compare z offset...

I landed to the slice engineering mosquito heater 50W and should be compatible with E3D V6 (22mm x 6mm) . This will drive 2A per heater. Thanks for your support.

Hi duet team,
I'm trying to print at >100mm/sec but when I'm exceeding 60mm/sec I see the temperature of the heater block dropping. I have a setup with a dual e3dv6. So I would like to upgrade to the volcano heater block and use the e3d 80w heater cartridges.

So here the question: Is the duet wifi able to handle 2X 80W heaters? I'm running it at 24V so should be 6.6A overall. Also, I'm managing the heater of the bed with a switch so no load on the duet wifi.

Thanks,
Marco

Dear duet community,

I started to print with ABS with my COREXYU printer and I have the classical warping issues. The print is sticking to the heated bed (which is at 110°) but the print is deformed in the sides. I've seen approaches to fix (rafts, ...) but I'm planning an enclose.

So here the questions:

• I've seen fully closed boxes which make sense to me but I'm worried for the electronic (duet and power supply). looking around I understood that 40-50 degrees should be ok to minimize the problem but... isn't an issue to have the duet and the power supply at these temperatures?
• Alternatively I'm thinking to keep the bottom 15 cm open, where most of my electronic is (duet + power supply at least, while the steppers and end stop sensord unfortunately are in the top part). Imagine a box with the bottom open and positioned at 15 cm from ground. The heating should go anyway up and by saturating the chamber shold keep worm only the printing area, while the bottom would remain fresh. Is this a bed idea?

thanks,
Marco

Just an update for the benefit of the community. I got again the error and I fixed with solution 2. I temporarly put a cable attached to the ground, and when I switch on the 3d printer, if showing 2000 degrees, I just connect hotend to the ground and reset the heater. I will do a more stable solution as suggested by dc42.

Thanks!

@dc42 Thanks option 1 worked: I Moved the thermocouple a bit out of the e3d hotend (2mm) and now works well.

I'm puzzled as the sensor (which is the e3d one) has a shilding which should avoid any contact with the hotend. Looks like the trial and error of Windows: restart and looks if it is fixed

By the way thanks for your help, as always you are fast and to the point!

Top!

@dc42

Thanks. I tend to exclude option 3 as I get the message immediately when I switch on the 3d printer, without any movement of steppers. Also, there is a flex3drive system, so the extruder is far from the sensor. I will investgate 1 & 2 and be back to you.

@dc42

by reading config.g I realized that I run the check on P0 which is the bed and not the heater. Sorry again.
In fact in config.g I have the following.

; Heaters
M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0 (bed)
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M305 P1 X150 ; set thermistor for heater 1 thrugh the extended mini board
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M305 P2 X151 ; set thermistor for heater 2 thrugh the extended mini board
M143 H2 S280 ; set temperature limit for heater 2 to 280C

by reading hetaer 1 with M308 P1 I get this message:
Heater 1 uses Thermocouple (MAX31856) sensor channel 150, last error: sensor short to other wiring, thermocouple type K, reject 50Hz

@dc42

The physical sensor is definetly a E3D K-Type Thermocouple. Do you mean that I configured wrongly the sensor in config.g?

@dc42

Here the error
Heater 0 uses Thermistor sensor channel 0, last error: sensor not ready, T:100000.0 B:4138.0 C:0.00e+0 R:4700.0 L:0 H:0

Sensors are E3D K-Type Thermocouples
The Board is the latest I think using MAC31856

Thanks

@dc42

Sorry I messed.
I have a Thermocouple Daughter Board + 2 K thermocouples

forget the PT100

@BoA Thanks for the feedback. Yes I know but there is no option of open circuit: the PT100 is a unique cable of 70 cm, and I soldered an extension of other 40 cm cables which are going directly to the Board

Hi, I have a setting with a duet wifi + Thermocouple Daughter Board and two PT100, one per extruder. I have the left extruder that randomly is showing 2000 degrees.

here some details:

• it may work for long time with no issues (several days) and at a certain point is showing this issue
• Most of the times I just restart the 3D printer (even with no movement of the axes) and the message disappear
• sometime it stay there, I try multiple times with no result
• when happen, I try to move the cable to understand if any short circuit but looks to have no results
• I tried multiple times to unplug and plug again the sensor to the Board, with no changes

any Idea?