@oliof the work on supporting those displays is not yet complete. In particular, the code to allow values to be changed when an item such as desired temperature is touched has not been written yet.

In order to achieve a satisfactory speed, these displays need a dedicated high speed (15MHz) SPI channel to drive the LCD. The touch screen interface needs another SPI channel, but the standard shared SPI channel would probably suffice for that.

@dc42 said in Unexpected behaviour - 3.5.0b1:

@OwenD thanks, I'll list this as a known issue. I'll probably replace the use of M0 to cancel tuning by M303 H-1 or something like that.

That would make more sense in my mind as it avoids stop.g being run.
I'll mark this as solved for now.

Ha, I was about to ask the same, thanks for updating the documentation! 👍

@Phaedrux Thank you! I've done this and will test it for a while.

@chrishamm
Thanks. I'll mark this as solved.

@Denis please start a new thread for this request, because it has nothing to do with the title of this one.

@joergs5 I found a workaround (half an hour after writing this thread - that's typical...)

RRFLibraries 3.4-dev is newer than 3.5-dev, so I copied the .h file from 3.4 to 3.5, it compiles ok now. I can live with this workaround.

If someone fells over the next trap like me, errors about WifiAuth, this is because the changed MessageFormats.h of ...WifiSocketServer...-dev is needed to compile.

@niocio01 please start a new thread to describe the issue you are seeing, because the title of this one is not appropriate.

If it happens again on RC3+ please capture an M122 immediately and post it here.

@dc42 with updated Toolchange behavior?

So far, no issues. 👏 But haven't printed/changed filaments a lot yet

@mandragora said in Failed to start accelerometer data collection:

There was a topic on forum about different wiring the accelerometer when using daughter board because this board shifts few pins around. Try look for that.

I think you mean this: https://forum.duet3d.com/topic/29410/input-shaping-accelerometer-not-found/4?_=1661187418835

@dc42 No issues between 3.4.1 and 3.4.2-rc2 were found on our machines. Thanks!

@dc42
This is now fixed.
Thanks for the prompt attention 👍

M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.2rc2+ (2022-08-13 11:34:57) running on Duet WiFi 1.02 or later Board ID: 08DGM-917NK-F2MS4-7J1DA-3S86T-TZTWD Used output buffers: 3 of 26 (22 max) === RTOS === Static ram: 23860 Dynamic ram: 78520 of which 0 recycled Never used RAM 6844, free system stack 202 words Tasks: NETWORK(notifyWait,6.4%,237) ACCEL(notifyWait,0.0%,348) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,90.7%,464) IDLE(ready,2.9%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:32 ago, cause: software Last software reset time unknown, reason: HardFault bfarValid precise, none spinning, available RAM 40780, slot 2 Software reset code 0x0072 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0xa5a5a665 SP 0x20004b98 Task MAIN Freestk 1027 ok Stack: a5a5a5a5 00000000 2000bde0 0000005a ffffffff 0042ca4d 0042c930 61070000 20001c6c 20002084 00000000 20002030 00000000 00000000 200115d4 00000000 00000000 0045b60d 00000005 00456da3 00000000 00000000 00000002 200115d4 00000000 00000009 0000005a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 15.8, current 16.3, max 16.5 Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/25, heap memory allocated/used/recyclable 2048/570/188, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min n/a Driver 1: ok, SG min n/a Driver 2: ok, SG min n/a Driver 3: ok, SG min n/a Driver 4: ok, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2022-08-14 07:25:19 Cache data hit count 1313699203 Slowest loop: 8.92ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.9ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock 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 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: ok === Network === Slowest loop: 60.58ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27beta1 WiFi MAC address bc:dd:c2:89:a0:bb WiFi Vcc 3.38, reset reason Power up WiFi flash size 4194304, free heap 24736 WiFi IP address 192.168.1.163 WiFi signal strength -53dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0

@dc42 said in DotStar not working from 3.4.1:

rameters. I think your LEDs were only lighting up in older versions of RRF because of the bug that we fixed in 3.4.

That worked out! A little more code to just dim the strip but we can dim it better than with the P value (that stops at 10 and R U and B goes down to 1)

@jay_s_uk

Thanks for the guidance! It was out of date.

@dc42 said in CAN connectivity: Duet 3 MB6HC to EXP3HC:

@kroybal this will most likely be resolved by updating the bootloader on the 3HC.

This resolved my issue, when I updated the firmware and forgot to do the bootloader as well.

Appreciate the help!

I would also encourage the use of the ReleaseMgr plugin by @MintyTrebor to help with highlighting the changes in the release notes that match your duet configuration.

https://github.com/MintyTrebor/ReleaseMgr/