@Kiolia That's fixed then. DWC uses M106 Pnnn Snnn to set specific fan speeds. If you select the tool fan slider, DWC sends M106 Snnn instead.

@droftarts Thank you!

@droftarts
Not to worry, just logging incase and of the information is helpful.

the same ocurred to me but it happened when i was experimenting with the second motion system. While the machine was printing , i wanted to move the unused axes. i have trigerred a flag in daemon.g to select the next motion system and move W axes and machine started moving to a different place and stopped. and the machine is still in printing state
61628f46-9ae2-4c99-93ac-6f05699c96e3-image.png

@dc42

axis_limits.g config-override.g config.g config-user.g tools.g

@dc42 were you able to look into this issue?

@Woody78 Be aware that on the Duet 2 M150 will only work when there is no movement of the printer carriage. The workaround I'm using is the Adafruit NeoDriver card, which works by I2C communication between Duet and NeoDriver, so you use M260 instead of M150. It's not fast, so you won't get fancy stuff, but it works for progress metering adequately, I think.

If you use the NeoDriver, be aware that although the NeoDriver has pull-up resistors built in, you have to add your own too. I think 4.7 k ohm, but in theory that depends on how long your I2C wiring is. The resistors go from 5V+ to each of the I2C lines (data and clock). Before I added pull-up resistors I was getting intermittent "I2C Transmission Error" problems.

Using the NeoDriver, you don't need the voltage level shifter circuit.

Possible bug in 3.6.b1. Once a printer is Estop'ed the PanelDue sometimes doesn't reconnect and gets stuck in a connecting state. I have absolutely no idea how to gather data for this other than an observation + the behaviour is inconsistent.
This may be related to another issue I am diagnosing (I am not sure its a RRF issue or just a user setup issue so I didn't mention it before) where the PanelDue connected to a D36HC w/ SBC seems to have random slow response times. Pressing a button can take up to 2 seconds before the press is registered/actioned, some other times is instant like normal. This behaviour is not present in any of my D2 machines that do not include an SBC

@charliedrums I'm glad you solved it! Thanks for the update.

@droftarts said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

@Mr-Crispin said in [3.6.0-beta.1] installation issues (SOLVED) heads up only.:

Bootloader ID: not available

That definitely means it's on an old version of the bootloader, so worth updating.

And i admit i have a little bit of hesitance to update the bootloader on an older toolboard, as i tried that a year or so ago on another v1.0 board which bricked it.

I wonder if this, and the updating malfunctioning, are indicative of something else? Possibly CAN wiring, or CAN termination problems?

Ian

The bricking occurred on my other machine. And it has been updated with no issues (although not to 3.6 yet)

I dislike RJ11 connectors, I removed them on both of my 6hc boards and added JST-XH connectors with twisted pair silicone wire.

My day job is as a network installation engineer, including fibre optics, so im happy enough with my connections.

Ok, I've tried uploading the firmware bin file directly to the board and installed the update from there, this appears to have worked. I will run through some print tests and hopefully it's all working correctly now.

[edit]
Having run a few test prints at different layer heights, it seems the latest beta firmware 99% resolves the artifacts issue I was having with 3.5.3. There is still a very faint hint of artifacting in a few areas but not enough to be an issue for my prints.

@rechrtb Immediately after a disconnect this morning:

10/3/2024, 11:20:49 AM M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-alpha.4 (2024-08-13 15:11:39) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-9T6BU-FG3SN-6JKD0-3S06Q-9AY7D Used output buffers: 3 of 26 (24 max) === RTOS === Static ram: 23368 Dynamic ram: 70472 of which 0 recycled Never used RAM 22036, free system stack 122 words Tasks: NETWORK(1,ready,13.6%,222) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,286) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,85.4%,610) IDLE(0,ready,0.9%,29), total 100.0% Owned mutexes: === Platform === Last reset 01:19:41 ago, cause: power up Last software reset at 2024-09-21 14:08, reason: User, Gcodes spinning, available RAM 13020, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x08 Aux0 errors 0,3,0 MCU temperature: min 33.2, current 48.3, max 48.7 Supply voltage: min 23.8, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/56, heap memory allocated/used/recyclable 4096/3124/1496, gc cycles 1004 Events: 0 queued, 0 completed Date/time: 2024-10-03 11:20:48 Slowest loop: 45.92ms; fastest: 0.10ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 8 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 9.4ms, write time 0.0ms, max retries 0 === Move === Segments created 6, maxWait 3515020ms, bed comp in use: none, height map offset 0.000, hiccups added 0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00, mcet 0.016 Pos req/act/dcf: 60000.00/60000/0.00 0.00/0/0.00 13592.00/13592/0.00 no step interrupt scheduled Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min n/a Driver 3: standstill, SG min 0 Driver 4: standstill, SG min n/a Driver 5: standstill, SG min 0 Driver 6: standstill, SG min 0 Driver 7: standstill, SG min 0 Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: === DDARing 0 === Scheduled moves 66, completed 66, LaErrors 0, Underruns [0, 0, 0] === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 === GCodes === Movement locks held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 0 0, running macro Autopause is idle in state(s) 0 Q0 segments left 0 Code queue 0 is empty === Filament sensors === check 0 clear 25429311 Extruder 0 sensor: no data received Extruder 1 sensor: no data received === DueX === Read count 1, 0.01 reads/min === Network === Slowest loop: 13.13ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.2.0beta1 MAC address 84:f3:eb:83:47:be Module reset reason: Turned on by main processor, Vcc 3.36, flash size 4194304, free heap 39196 WiFi IP address 192.168.1.130 Signal strength -41dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0