Topics created by PetrKroupa

@dc42 PERFECT. I confirm that fix si wortking.

OKscan.png

@PetrKroupa thanks for confirming that.

@PetrKroupa Thanks for reporting this, I can confirm there is a problem in 3.5b2. It will be fixed in the next beta.

@T3P3Tony - I have a little update on that. There were enough parts to print and of course I ran out of filament. In the meantime, I received the new 6HC v1.02. I upgraded from v1.01 28V supply voltage to 45V. The filament arrived and I continued printing. The error no longer appeared. I have no idea how much difference there is in the FW for version 1.01 and 1.02, but maybe it will help you in your search.

20230321_195946.JPG

@dc42 - problem solved. Thanks for help.

20220614_055931.JPG

@dc42 - Good idea. And yes, it works. Thanks a lot!

Basically, just hide the W axis at the end of the tool change macro. And re-enable it at the beginning of the tool change macro. I will try solved my goal by using an event when one filament runs out so that printing continues with the next filament. Now just find enough time .... 🙂

Good afternoon, can you tell me if you managed to solve this problem? Did you end up using the limit switches on additional axes or did you change the board / firmware / find another way?

@dc42 The removal is somewhat of a bummer, I use numLayers to determine when to modify PA values in my calibration script, e.g.:

Now, instead, I have to pass in total layer count on every layer change, not blocked, just less elegant.

var begin = 0.030 var end = 0.060 var increment = 0.003 var layer_count = 0 if !exists(job.file.numLayers) if !exists(param.L) abort "Missing layer count" set var.layer_count = param.L var step_count = {floor((var.end - var.begin) / var.increment)} var layer_step_size = {floor(var.layer_count / var.step_count)} if mod(job.layer, var.layer_step_size) == 0 var steps = job.layer / var.layer_step_size var pa_value = {var.steps * var.increment + var.begin} echo "Pressure advance set to " ^ {var.pa_value} ^ " at layer=" ^ {job.layer} ^ " for " ^ {var.layer_step_size} ^ " layers" M572 D0 S{var.pa_value}

It's called like so in my layer change custom gcode settings:

M98 P"k/pressure-advance-calibration.g" L[total_layer_count]

I will have to try to replace the whole sensor. It's weird.

Here is the event log, including the log from 1LC

2021-12-31 17:39:33 Error: Filament error on extruder 0: sensorError 2021-12-31 17:39:33 Resume state saved 2021-12-31 17:39:37 Printing paused at X328.0 Y217.3 Z9.5 2021-12-31 17:39:37 Printing paused at X328.0 Y217.3 Z9.5 2021-12-31 17:39:37 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 25.00mm/rev, allow 50% to 125%, check printing moves every 10.0mm, version 4, mag 129 agc 95, measured sensitivity 25.11mm/rev, min 97% max 104% over 89544.7mm 2021-12-31 17:39:37 Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 25.00mm/rev, allow 50% to 125%, check printing moves every 10.0mm, version 4, mag 129 agc 95, measured sensitivity 25.11mm/rev, min 97% max 104% over 89544.7mm 2021-12-31 17:39:38 Diagnostics for board 121: Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7 (2021-12-16 12:25:01) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) Never used RAM 2188, free system stack 2717 words Tasks: Move(notifyWait<null>,11.3%,91) HEAT(notifyWait<null>,5.6%,95) CanAsync(notifyWait<null>,0.0%,59) CanRecv(notifyWait<null>,2.3%,74) CanClock(notifyWait<null>,0.4%,65) ACCEL(notifyWait<null>,0.0%,61) TMC(notifyWait<null>,59.6%,57) MAIN(running<null>,381.7%,351) IDLE(ready<null>,0.0%,26) AIN(delaying<null>,98.4%,142), total 559.3% Last reset 08:20:10 ago, cause: VDD brownout Last software reset data not available Driver 0: pos 39923177, 420.0 steps/mm,standstill, SG min 0, read errors 14, write errors 0, ifcnt 13, reads 27915, writes 0, timeouts 16, DMA errors 0, CC errors 0, failedOp 0x6f, steps req 39412543 done 39412543 Moves scheduled 414732, completed 414732, in progress 0, hiccups 0, step errors 0, maxPrep 654, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 0/6, peak Rx sync delay 230, resyncs 0/0, no step interrupt scheduled VIN voltage: min 27.9, current 28.0, max 28.1 MCU temperature: min 38.7C, current 52.7C, max 58.5C Last sensors broadcast 0x00000002 found 1 182 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 495202, send timeouts 0, received 614292, lost 0, free buffers 37, min 35, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 751, adv 35393/104433 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 0, other errors 0 === Filament sensors === Interrupt 4 to 40us, poll 8 to 4836us Driver 0: pos 140.27, errs: frame 89 parity 0 ovrun 0 pol 0 ovdue 0 2021-12-31 17:39:38 filament error 2021-12-31 17:39:38 Diagnostics for board 121: Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7 (2021-12-16 12:25:01) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) Never used RAM 2188, free system stack 2717 words Tasks: Move(notifyWait<null>,11.3%,91) HEAT(notifyWait<null>,5.6%,95) CanAsync(notifyWait<null>,0.0%,59) CanRecv(notifyWait<null>,2.3%,74) CanClock(notifyWait<null>,0.4%,65) ACCEL(notifyWait<null>,0.0%,61) TMC(notifyWait<null>,59.6%,57) MAIN(running<null>,381.7%,351) IDLE(ready<null>,0.0%,26) AIN(delaying<null>,98.4%,142), total 559.3% Last reset 08:20:10 ago, cause: VDD brownout Last software reset data not available Driver 0: pos 39923177, 420.0 steps/mm,standstill, SG min 0, read errors 14, write errors 0, ifcnt 13, reads 27915, writes 0, timeouts 16, DMA errors 0, CC errors 0, failedOp 0x6f, steps req 39412543 done 39412543 Moves scheduled 414732, completed 414732, in progress 0, hiccups 0, step errors 0, maxPrep 654, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 0/6, peak Rx sync delay 230, resyncs 0/0, no step interrupt scheduled VIN voltage: min 27.9, current 28.0, max 28.1 MCU temperature: min 38.7C, current 52.7C, max 58.5C Last sensors broadcast 0x00000002 found 1 182 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 495202, send timeouts 0, received 614292, lost 0, free buffers 37, min 35, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 751, adv 35393/104433 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 0, other errors 0 === Filament sensors === Interrupt 4 to 40us, poll 8 to 4836us Driver 0: pos 140.27, errs: frame 89 parity 0 ovrun 0 pol 0 ovdue 0

@dc42 Thanks. This is exactly how I use it on the first printer. Sufficient 5V power supply and jumpers as you wrote. I just didn't want to solder on the new board. That's why I asked if there was any other solution.

@PetrKroupa related github issue:
https://github.com/Duet3D/RepRapFirmware/issues/623

T3P3 created this issue in Duet3D/RepRapFirmware open MFM intermittent connection error #623

@petrkroupa thanks for confirming that has fixed the issue!

@chrishamm - Perfect! Many thanks for info! 👍

It can definitely be improved a lot, but it is enough for the basic function. Thanks to everyone for the help.

daemon.g

G4 S1 if heat.heaters[1].current > 55 && heat.heaters[1].current < 1000 ; hotend temp more than 55c ? ; hotend temp more than 55c ?, termostacic fan set to 45c (fan have time to start spin) if fans[1].rpm < 500.0 ; hotend fan spining faster than 500rpm? M150 R128 ; Neopixel red! M104 S0 ; set hotend temp to 0c M291 P"Hotend fan error!!!" S1 M98 P"pause.g" ; run pause.g else ;M150 U128 ; Neopixel green else ;M150 U128 ; Neopixel green G4 S1

Hello,

I confirm that it works. 6HC is powered by an external 5V source. switch 5v internal - off, The other two are connected.

config:

M80
G4 S2
.
.
.

It works exactly the way I wanted it to. Thanks so much for the help !!

@alankilian -11mA. 4,6V.

It also occurred to me. I tried to add a resistor (just to try) to reduce the current. Nothing has changed until the input voltage is lower than 2.7V. Then the driver stops working completely.

There is some planned work for the config tool coming yes.