Topics created by MartinNYHC

@martinnyhc you have a v1.2 toolboard there. Says on the PCB, top right of your photo.

Ian

@martinnyhc what is the red Status LED on the tool board doing?

@jay_s_uk NOW i got it 🙂 I think that's the way for me.

After a reinstall it works again 🙂 Thanks.

Connected it to io7.out and it works.

@dc42 said in Duet 3HC CAN bus timeout:

@martinnyhc when you run M122 B1, what bootloader version does it report?

See https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_bootloader for how to update the bootloader if it is an old version (prior to version 2.3) or reported as "version not available".

Thanks 🙂

code_text14/02/2022, 16:11:29 M122 B1 Diagnostics for board 1: Duet EXP3HC firmware version 3.4.0rc1 (2022-02-08 09:04:27) Bootloader ID: not available All averaging filters OK Never used RAM 158828, free system stack 200 words Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.7%,99) MAIN(running,90.9%,414) IDLE(ready,0.0%,39) AIN(delaying,1.4%,263), total 100.0% Last reset 00:19:22 ago, cause: software Last software reset data not available Driver 0: pos 0, 574.3 steps/mm,standstill, SG min 0, mspos 8, reads 62247, writes 16 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 62247, writes 16 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 62253, writes 11 timeouts 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter -1/11, peak Rx sync delay 181, 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.2 MCU temperature: min 28.6C, current 29.2C, max 29.4C Last sensors broadcast 0x00000000 found 0 105 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 13967, send timeouts 0, received 15100, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 14/02/2022, 16:12:53 Upload of Duet3Bootloader-SAME5x.bin successful after 0s 14/02/2022, 16:13:25 M997 B1 S3 Board 1 starting bootloader update 14/02/2022, 16:13:48 M122 B1 Diagnostics for board 1: Duet EXP3HC firmware version 3.4.0rc1 (2022-02-08 09:04:27) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 158948, free system stack 200 words Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.5%,99) MAIN(running,91.2%,437) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0% Last reset 00:00:20 ago, cause: software Last software reset data not available Driver 0: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 12746, writes 11 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 12747, writes 11 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 12747, writes 11 timeouts 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 0/8, peak Rx sync delay 177, 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.2 MCU temperature: min 29.0C, current 29.0C, max 29.2C Last sensors broadcast 0x00000000 found 0 121 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 186, send timeouts 0, received 273, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

I suppose you could remap the toolfan to a new fan number and control it manually. The slicer fan commands wouldn't do anything anymore. But that would only get you a fixed manually set fan speed, not one that scales with slicer commands.

DWC used to have (still does maybe?) a pin next to the fan speed slider for the tool that would let you fix the speed, but it was only active while the DWC window was open. I'm not sure if it's still there or not. I rarely look at DWC at all in my workflow.

FYI: just installed RRF 3.4.0beta7+4 and the heater is working again 🙂

Thanks. Will do so.

@martinnyhc it's on my list to remove that restriction for simple filament present/absent sensors, but it probably won't happen in RRF 3.4.

You have to call the probe deploy from within your homez and then again in your beg.g or other macros that need the probe. Conditonal gcode makes this an easy check and remedy.

The error is because the NC probe state is 1000 when the probe is not connected or triggered. you have to include in your macros the logic to address these states.

You should go look a the macros for Euclid Probe. We've been running this reliably for over 2 years at this point, both with fixed dock and moving bed pickups.

Also, we have found that inspecting the actual probe value is more reliable that checking the probe token in the object model. In the case of a mis-deploy, which is really rare with Euclid Probe, the probe value is more telling.

It was controlling the "bed fan" 😉

Will check tomorrow. Currently printing the ringing tower.

@phaedrux yes 🙂
No worries
I can imagine there is lots of work

@martinnyhc
I don't see why it shouldn't work as long as you have enough drivers. Most brain is in the toolchanging macros and the tip-forming retraction macro. (they don't use a filament cutter...)

It would be interesting to have a triple selector that feeds three filaments to a mixing hotend. 😬
sigh so many options, but no time and money

@martinnyhc said in Controlling two fans at the same time:

I found out that PWM is not working properly when connecting two fans in parallel to one port. I have two electronics bay fans, would like to connect them seperately to two ports but it would be very nice if I still can control them parellel. Is that anyhow possible?

Thx.

2-wire fans are not designed to work with PWM. It's a miracle that so many of them do.

If you connect two dissimilar fans in parallel, then I am not surprised of they behave oddly when you PWM them. But if they are identical fans, I would expect a parallel connection to work.

I decided to use a SD card again and only mounting the macro and sys folder via network. That should solve the issue and I don't need to take care of backing up these files.

@phaedrux said in Unexpected start Gcode behaviour:

Calibrating the Z offset during a print?

Did this work previous to 3.3? Are you using an SBC?

I wonder if it's the same issue as here: https://forum.duet3d.com/topic/22667/m291-messages-ignored-by-paneldue/9

What PanelDue firmware version are you running?

These questions remain.

@martinnyhc said in 5V 1LC Toolboard:

But connecting the LED's to the Duet3 6HC 5V PWM (VFD, Laser, Servo Drive) should work, right?

Yes, the MB6HC can supply a lot more 5V current than the tool board can.

@gloomyandy oh ok, yeah I was expecting an actual temperature. Thanks.