@kj3d

Thanks Deckingman - you are spot on, the typo was the result of the issue.

The separation of the V,W, A,B axis was simply for configuration. In operation it sees all 4 as a single axis, which its now doing very well. Levels through with no issues and simply works just as intended.

Now off to Specsavers for some new glasses and a stop at the pie shop for a big helping of humble pie!"!

M569 P1.0 S0 ; V
M569 P1.1 S0 ; W
M569 P2.0 S1 ; A
M569 P2.1 S1 ; B

; set drive mapping
M584 X0.0:0.4 Y0.1 Z0.2 E0.3 U0.4 V1.0:1.1:2.0:2.1 R0
M350 X16 Y16 Z16 E16 U16 V16 W16 A16 B16 I1 ; configure microstepping with interpolation
M92 X357.19 Y80.00 Z636.00 E420.00 U357.19 V636.00 W636.00 A636.00 B636.00 ; set steps per mm
M566 X900.00 Y900.00 Z600.00 E120.00 U900.00 V600.00 W600.00 A600.00 B600.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z1000.00 E1200.00 U6000.0 V1000.00 W1000.00 A1000.00 B1000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z200.00 E250.00 U500.00 V200.00 W200.00 A200.00 B200.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z1000 E800 U800 I60 V1000 W1000 A1000 B1000 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 U0 V0 W0 A0 B0 S1 ; set axis minima
M208 X1170 Y1050 Z740 U1170 V740 W740 A740 B740 S0 ; set axis maxima

; Endstops
M574 X0 S1 P"io1.in+io4.in" ; configure active-high endstop for low end on X via pin io1.in
M574 Y0 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z0 S1 P"io3.in" ; configure active-high endstop for low end on Z via pin io3.in
;M574 U0 S1 P"io4.in"
M574 V0 P"1.io0.in+1.io1.in+2.io0.in+2.io1.in"

@dc42

Thanks - thats good to know. problem resolved and board working very well!!

URIKA - I reloaded the DWC Web Control - SD file.zip and all sorted

https://github.com/Duet3D/RepRapFirmware/releases/download/3.5.0-rc.1/DuetWebControl-SD.zip

Thanks everyone for the help

Hi

That worked. I can now reliably detect the stall. Ideally I would like to stop the filament feeding when the stall is detected.

At present I use G1 E1000 F1000 to feed filament up to a second extruder, how would be best to interrupt the G code part way if a stall is detected if it reaches the second extruder after 900mm (bearing in mind the end stop limitations with the canbus boards)

@droftarts

Thanks Ian, Will try that in the morning and let you know how I got on.

@dc42

Thanks for that. I was looking to sense when the filament had completed its feed from the feed extruder to the main extruder before that started its load sequence.

Reporting the stall would be a useful event, but I cant see how to configure that?

Alternatively monitoring the main extruder during the actual operation of G1 E2000 F1000 controlled by the 3HC board (running the feed extruder) (The main extruder has a filament sensor on it (albeit that's controlled by a tool board) Is it possible to monitor sensors (located on other boards) whilst a G1 command is executing on a distinct and separate canbus board, if so how and do I have any choice on monitoring frequency?

The error message I get is unable to initiate extruder end stops

@droftarts

m122 b1
Diagnostics for board 1:
Duet EXP3HC rev 1.01 or earlier firmware version 3.4.6 (2023-07-21 14:15:46)
Bootloader ID: not available
All averaging filters OK
Never used RAM 158504, free system stack 173 words
Tasks: Move(notifyWait,0.0%,128) HEAT(notifyWait,0.1%,88) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.5%,80) CanClock(notifyWait,0.1%,71) TMC(notifyWait,57.0%,99) MAIN(running,32.1%,409) IDLE(ready,0.0%,40) AIN(delaying,10.2%,263), total 100.0%
Last reset 01:49:18 ago, cause: software
Last software reset at 2021-08-15 15:42, reason: HardFault bfarValid precise, available RAM 154828, slot 2
Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x30303051 SP 0x20002fd8 Task MAIN Freestk 350 ok
Stack: 30303030 20002ff8 00000000 00000000 70707070 00023a09 ffffffff 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 0000007c ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
Driver 0: pos 212040, 684.0 steps/mm,standstill, SG min 0, mspos 344, reads 50872, writes 19 timeouts 0, steps req 212040 done 212040
Driver 1: pos 0, 684.0 steps/mm,standstill, SG min 0, mspos 8, reads 50875, writes 16 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 50881, writes 11 timeouts 0, steps req 0 done 0
Moves scheduled 3, completed 3, in progress 0, hiccups 0, step errors 0, maxPrep 24, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -3/15, peak Rx sync delay 180, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.0, current 24.0, max 24.0
V12 voltage: min 12.2, current 12.2, max 12.3
MCU temperature: min 31.7C, current 32.7C, max 32.7C
Last sensors broadcast 0x00000000 found 0 28 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 52504, send timeouts 0, received 321264, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 292, adv 37101/37190

@droftarts

The extruder is simply to convey filament to the other extruders and its "Load" code is below

;Motor stall detection

;T2 ; select tool 2
;M302 P1 ; enable cold extrusion
;G4 S1 ; wait for one second
;G4 S1
;G1 P1.1 F3000 ; retract a little filament
;M400 ; wait for move to finish before changing current

;M915 E2 S3 ; set stall sensitivity
;M913 E80 ; motor current to 30%
;M83 ; relative extrusion
;G1 H1 E800 F1000 ; feed up to 800mm until stall
;M913 E100 ; restore normal motor current
;M302 P0 ; disable cold extrusion
;M291 P"Filament Prime complete!" S0 T3 ; display message

(The lines appear above appear commented out - in the macro they are not)

Hi

Just a quick question when will stall detection be available via canbus satellite boards (In latest full release (3.4.6) it does not appear to be possible. I am trying to get stall detection via a 3HC expansion board connected via canbus. The drive is connected to the 3HC board

@ScrewsLoose

Hi,

We are using a mixture of conventional stepper motors both with and without closed loop encoders and a mixture of 6HC Motherboard and 1XD and 1HCL boards with Clearpath servos. The performance of the Clearpath Servos is stunning.

@dc42

Thank you for your reply and an insight into the latest firmware. The good news is that the firmware has not caused any obvious issues (we are always very wary / cautious)

However the dwell timing issue is still present. I have been through the three points you listed and it has not cured the issue.

The most significant "controlling" factor seems to be the direction called in the M569 call. after dwell the motor with S1 starts earlier than the motor with S0.

M569 P31.0 S1 ; Y (first Y)
M569 P32.0 S0 ; Y (second Y)

The Clearpath servos give us the option to reverse motor direction in the firmware of the servo (we can then run both Y M569 lines as S1 or S0 - that gets round the issue on an operational level but does require a service engineer to configure a motor dependent on if its on the left or right side of the gantry. We would prefer not to do that (it increases the risk of an error during replacement of a servo - should it be needed. It seems much simpler to take a stock motor and simply fit it rather than having to use left hand or right hand direction motors)

We are fairly certain that the issue is Firmware related rather than a fault on the 1XD boards.

How is the dwell period controlled for timing from the hardware?

@droftarts

Thanks, please see below the macro used for testing Y axis. (number of cycles at line 3 varied between 4 and 100 - dwell issue is present in every cycle)