@chrishamm said in SPI Changes in Current 3.2 Beta Firmware:

but I believe that was fixed months ago

mystery solved:)

If the relay module works with an input current that is okay for the pin on the mcu (2mA?) then happy shiny.

@dc42 Hi the resume state seems to be behaving properly now, although I've noticed something with the pause which I'll raise in another thread. Thanks again.

@dc42 said in Mesh stops after end RRF3.2 beta 3:

@Touchthebitum said in Mesh stops after end RRF3.2 beta 3:

Confirmed and tested, mesh compensation works on 3.2 beta 2 but not on beta 3

Is this in standalone mode, or with attached SBC?

attached SBC (Rasp Pi4)

And here we go again

pronterface captured:

Lost connection to Linux Warning: Discarded msg src=10 typ=4510 RID=42 exp 43 Done printing file Cancelled printing file 0:/gcodes/VCP-Ormerod-Belt-Clip.gcode, print time was 0h 22m Rx0:11a20a7f 02 00 00 00 00 00 00 00 Rx0:11a30a00 02 00 00 00 00 00 00 00 Rx0:11a50a00 03 00 00 00 00 00 00 00 Rx0:11a20a7f 02 00 00 00 00 00 00 00 Rx0:11a30a00 02 00 00 00 00 00 00 00 Rx0:11a50a00 03 00 00 00 00 00 00 00 Rx0:11a20a7f 02 00 00 00 00 00 00 00 Rx0:11a30a00 02 00 00 00 00 00 00 00 Rx0:11a50a00 03 00 00 00 00 00 00 00 Rx0:11a20a7f 02 00 00 00 00 00 00 00 Rx0:11a30a00 02 00 00 00 00 00 00 00 Rx0:11a50a00 03 00 00 00 00 00 00 00 Error: Failed to switch off remote heater 1: Response timeout: CAN addr 10, req type 6013, RID=42 [ERROR] Error: Failed to switch off remote heater 1: Response timeout: CAN addr 10, req type 6013, RID=42

M122 via serial

=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta3 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DGM-9T66A-G63SJ-6J1D6-3SD6R-9U0BA Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 122124 Dynamic ram: 138812 of which 84 recycled Never used RAM 131172, free system stack 120 words Tasks: Linux(blocked,79) HEAT(blocked,277) CanReceiv(blocked,794) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,18) MAIN(running,669) IDLE(ready,19) Owned mutexes: USB(MAIN) === Platform === Last reset 00:54:23 ago, cause: power up Last software reset at 2020-11-08 16:33, reason: User, GCodes spinning, available RAM 131236, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0x04 [ERROR] Error status: 0x04 MCU temperature: min 32.0, current 35.2, max 37.0 Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0 Driver 0: position 2357, standstill, reads 47099, writes 19 timeouts 0, SG min/max 0/1023 Driver 1: position -32, standstill, reads 47098, writes 19 timeouts 0, SG min/max 0/1023 Driver 2: position 7680, standstill, reads 47117, writes 0 timeouts 0, SG min/max not available Driver 3: position 0, standstill, reads 47103, writes 14 timeouts 0, SG min/max 0/174 Driver 4: position 0, standstill, reads 47104, writes 14 timeouts 0, SG min/max 0/145 Driver 5: position 0, standstill, reads 47103, writes 14 timeouts 0, SG min/max 0/187 Date/time: 2020-11-08 17:50:13 Slowest loop: 7067.05ms; fastest: 0.11ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 350, MaxWait: 1058464ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 22194, completed moves 22194, StepErrors 0, LaErrors 0, Underruns [0, 501, 3], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === 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 ready with "M122" 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 SBC* is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages sent 27548, send timeouts 27522, longest wait 2ms for type 6012, free CAN buffers 47 === SBC interface === State: 0, failed transfers: 1 Last transfer: 13752ms ago RX/TX seq numbers: 0/37238 SPI underruns 1, overruns 1 Number of disconnects: 1, IAP RAM available 0x20a78 Buffer RX/TX: 0/0-0

Network connection to the Pi is dead. I will sort out the power to the pi, and then try again.

@dc42 said in Beta 3 Duetwifi standalone constant reboot menu files outmemory:

Unfortunately the Duet WiFi/Ethernet doesn't really have enough RAM to support a 12864 display along with all the stepper drivers that it can support. We may provide a means in a future release to reduce the number of stepper drivers supported, to make more RAM available.

Ok, will wait this release in beta 2, thank you.

yes, I did update the tool board firmware as well

11/7/2020, 10:32:49 PM M115 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2-beta3 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-11-07 11/7/2020, 10:32:46 PM M115 B10 Duet TOOL1LC firmware version 3.2beta3 (2020-11-07)

Thanks, that will help me to track the problem down.

Issue still present with 3.2 beta3 and corresponding Toolboard update

I've tested M917 and it is working on a tool board for me.

@dc42 said in Software assertion with 3.2 beta 2:

M701

Apologies, I hadn't linked the issue to the M701/M702 commands. I thought it was something in the macro that triggered it. Thanks for the quick response!

Take a look here: https://forum.duet3d.com/topic/19257/downgrade-from-3-2beta2-to-3-1-1/2

@Phaedrux That tool list is from my config file. The CAN ID for the tool board was edited to 121, the boards default. The M582 and M522 are commented since the SBC complains about them. The PWM output was changed to 121.io0.out due to the config tool only allows temp0 and temp1. The config.json has been edited with the IO changes, so that the tool board IO comes up blank on the config tool.

config.g
config.json

@oozeBot Yes, both will be fixed in b3. I noticed temperatures from the drop-down list were no longer applied when clicking on them but that's been fixed already. Likewise I made a change to address #1.

@Carlo Thx for the ultra quick response.

I did notice some lags in 3.2-b2 as well but we've changed the firmware quite a bit to get rid of them. You should be able to confirm this when we've released 3.2-b3.

Moved to the beta firmware forum and updated the title for @chrishamm to see

Thanks, looks the same. I just tried sprinkling bed.g with M400 between each G30, but that didn't change anything. I witnessed skipping of the second point though.

I'll wait for beta3 then.

Possibly related: https://forum.duet3d.com/topic/19329/3-2beta-2-bed-g-not-executed-completely-out-of-order-in-order/2