Posts made by Lucas

undefined

@jay_s_uk Okay thanks I didn't know. I had this SD card on the Duet since the beginning without any trouble and I forget about it.
Anyway I removed it and it works great now

undefined

I removed the SD card on the duet and rebooted and now the communication works even with version 3.2b3.2

Thank you @chrishamm for your help!

undefined

Yes I do have a SD card on the Duet, am I not supposed to?

undefined

@chrishamm Here is the result of "sudo journalctl -u duetcontrolserver -e" after I tried again to upgrade to 3.2b3.2:

-- Logs begin at Sat 2020-11-14 23:00:45 CET, end at Sat 2020-11-14 23:05:01 CET. --
Nov 14 23:00:49 duet3 systemd[1]: Started Duet Control Server.
Nov 14 23:00:52 duet3 DuetControlServer[388]: Duet Control Server v3.1.1
Nov 14 23:00:52 duet3 DuetControlServer[388]: Written by Christian Hammacher for Duet3D
Nov 14 23:00:52 duet3 DuetControlServer[388]: Licensed under the terms of the GNU Public License Version 3
Nov 14 23:00:53 duet3 DuetControlServer[388]: [info] Settings loaded
Nov 14 23:00:53 duet3 DuetControlServer[388]: [info] Environment initialized
Nov 14 23:00:53 duet3 DuetControlServer[388]: [info] Connection to Duet established
Nov 14 23:00:54 duet3 DuetControlServer[388]: [info] IPC socket created at /var/run/dsf/dcs.sock
Nov 14 23:01:32 duet3 DuetControlServer[388]: [info] System time has been changed
Nov 14 23:02:22 duet3 systemd[1]: Stopping Duet Control Server...
Nov 14 23:02:22 duet3 DuetControlServer[388]: [warn] Received SIGTERM, shutting down...
Nov 14 23:02:22 duet3 systemd[1]: duetcontrolserver.service: Main process exited, code=exited, status=143/n/a
Nov 14 23:02:22 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'exit-code'.
Nov 14 23:02:22 duet3 systemd[1]: Stopped Duet Control Server.
Nov 14 23:02:42 duet3 systemd[1]: Started Duet Control Server.
Nov 14 23:02:42 duet3 DuetControlServer[1132]: Duet Control Server v3.2.0-beta3
Nov 14 23:02:42 duet3 DuetControlServer[1132]: Written by Christian Hammacher for Duet3D
Nov 14 23:02:42 duet3 DuetControlServer[1132]: Licensed under the terms of the GNU Public License Version 3
Nov 14 23:02:43 duet3 DuetControlServer[1132]: [info] Settings loaded
Nov 14 23:02:44 duet3 DuetControlServer[1132]: [info] Environment initialized
Nov 14 23:02:44 duet3 DuetControlServer[1132]: [warn] Downgrading protocol version 3 to 2
Nov 14 23:02:44 duet3 DuetControlServer[1132]: [warn] Incompatible firmware, please upgrade as soon as possible
Nov 14 23:02:44 duet3 DuetControlServer[1132]: [info] Connection to Duet established
Nov 14 23:02:44 duet3 DuetControlServer[1132]: [info] IPC socket created at /var/run/dsf/dcs.sock
Nov 14 23:02:45 duet3 DuetControlServer[1132]: [error] Failed to merge JSON: {"key":"spindles","flags":"d99vn","result":[{"active":0,"current":0,"frequency":0,"max":10000.0000000,"tool":-1},{"active":0,"current":0,"frequency":0,"max":100
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    System.Text.Json.JsonException: Failed to deserialize property [Spindle].Max (type Int32) from JSON 10000.0000000
Nov 14 23:02:45 duet3 DuetControlServer[1132]:  ---> System.Text.Json.JsonException: The JSON value could not be converted to System.Int32. Path: $ | LineNumber: 0 | BytePositionInLine: 13.
Nov 14 23:02:45 duet3 DuetControlServer[1132]:  ---> System.FormatException: Either the JSON value is not in a supported format, or is out of bounds for an Int32.
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.Utf8JsonReader.GetInt32()
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.Serialization.Converters.JsonConverterInt32.Read(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.JsonPropertyInfoNotNullable`4.OnRead(ReadStack& state, Utf8JsonReader& reader)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.JsonPropertyInfo.Read(JsonTokenType tokenType, ReadStack& state, Utf8JsonReader& reader)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.JsonSerializer.ReadCore(JsonSerializerOptions options, Utf8JsonReader& reader, ReadStack& readStack)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    --- End of inner exception stack trace ---
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack& readStack, Utf8JsonReader& reader, Exception ex)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.JsonSerializer.ReadCore(JsonSerializerOptions options, Utf8JsonReader& reader, ReadStack& readStack)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.JsonSerializer.ReadCore(Type returnType, JsonSerializerOptions options, Utf8JsonReader& reader)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at System.Text.Json.JsonSerializer.Deserialize(String json, Type returnType, JsonSerializerOptions options)
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at DuetAPI.ObjectModel.ModelObject.UpdateFromJson(JsonElement jsonElement, Boolean ignoreSbcProperties) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/ObjectModel/Base/ModelO
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    --- End of inner exception stack trace ---
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at DuetAPI.ObjectModel.ModelObject.UpdateFromJson(JsonElement jsonElement, Boolean ignoreSbcProperties) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/ObjectModel/Base/ModelO
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at DuetAPI.ObjectModel.ModelCollectionHelper.UpdateFromJson(IList list, Type itemType, JsonElement jsonElement, Boolean ignoreSbcProperties) in /home/christian/Duet3D/DuetSoftwareFramewor
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at DuetAPI.ObjectModel.ObjectModel.InternalUpdateFromModel(String key, JsonElement jsonElement, Boolean ignoreSbcProperties) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/Ob
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at DuetAPI.ObjectModel.ObjectModel.UpdateFromFirmwareModel(String key, JsonElement jsonElement) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPI/ObjectModel/ObjectModel.cs:line
Nov 14 23:02:45 duet3 DuetControlServer[1132]:    at DuetControlServer.Model.Updater.Run() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Model/Updater.cs:line 212
Nov 14 23:02:50 duet3 DuetControlServer[1132]: [info] Flashing IAP binary
Nov 14 23:02:51 duet3 DuetControlServer[1132]: [info] Flashing RepRapFirmware
Nov 14 23:02:57 duet3 DuetControlServer[1132]: [info] Verifying checksum
Nov 14 23:02:59 duet3 DuetControlServer[1132]: [info] Firmware update successful
Nov 14 23:03:00 duet3 DuetControlServer[1132]: [warn] Lost connection to Duet (Timeout while waiting for transfer ready pin)

And for information it worked great with versions 3.2b1 and 3.2b2

undefined

@chrishamm Hi, I flashed the Duet to version b3.2 via bossa, the dial LED was pulsing but the communication between the Duet and the Pi was still broken. So I flashed version 3.1.1 to the Duet and now the communication works again even if the Pi is still on version 3.2-b3.2.

undefined

Hello,

As @Phaedrux suggested I changed my setup to power the Pi separately and as expected it was still working perfectly.
And then I saw that @dc42 released the version 3.2beta3.2 of ReprapFirmware and that one of the purpose of this release is to address communication issues with an attached single board computer. So I decided to give a new shot to the 3.2beta3 and... I encountered the same issue that the one described in my first post
The upgrade is stuck on "Sending update request to DCS..." for 25 minutes now and DuetWebControl is displaying this message: "Please wait while updates are being installed...". Usually this process takes a few seconds and I'm pretty sure that if I stop the upgrade I'll have the same communication problem as before.

Here are the upgrade logs:

sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  duetcontrolserver duetruntime duetsd duetsoftwareframework duettools duetwebcontrol duetwebserver reprapfirmware
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 33.9 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 https://pkg.duet3d.com unstable/armv7 armhf duetsoftwareframework armhf 3.2.0-beta3 [2,034 B]
Get:2 https://pkg.duet3d.com unstable/armv7 armhf duetsd all 1.1.0 [2,102 B]
Get:3 https://pkg.duet3d.com unstable/armv7 armhf duettools armhf 3.2.0-beta3 [62.2 kB]
Get:4 https://pkg.duet3d.com unstable/armv7 armhf duetcontrolserver armhf 3.2.0-beta3 [226 kB]
Get:5 https://pkg.duet3d.com unstable/armv7 armhf duetruntime armhf 3.2.0-beta3 [28.9 MB]
Get:6 https://pkg.duet3d.com unstable/armv7 armhf duetwebserver armhf 3.2.0-beta3 [83.9 kB]
Get:7 https://pkg.duet3d.com unstable/armv7 armhf duetwebcontrol all 3.2.0-beta3 [3,507 kB]
Get:8 https://pkg.duet3d.com unstable/armv7 armhf reprapfirmware all 3.2.0-beta3-2 [1,157 kB]
Fetched 33.9 MB in 10s (3,450 kB/s)
Reading changelogs... Done
(Reading database ... 57772 files and directories currently installed.)
Preparing to unpack .../0-duetsoftwareframework_3.2.0-beta3_armhf.deb ...
Unpacking duetsoftwareframework (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../1-duetsd_1.1.0_all.deb ...
Unpacking duetsd (1.1.0) over (1.0.6) ...
Preparing to unpack .../2-duettools_3.2.0-beta3_armhf.deb ...
Unpacking duettools (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../3-duetcontrolserver_3.2.0-beta3_armhf.deb ...
Unpacking duetcontrolserver (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../4-duetruntime_3.2.0-beta3_armhf.deb ...
Unpacking duetruntime (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../5-duetwebserver_3.2.0-beta3_armhf.deb ...
Unpacking duetwebserver (3.2.0-beta3) over (3.1.0) ...
Preparing to unpack .../6-duetwebcontrol_3.2.0-beta3_all.deb ...
Unpacking duetwebcontrol (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../7-reprapfirmware_3.2.0-beta3-2_all.deb ...
Unpacking reprapfirmware (3.2.0-beta3-2) over (3.1.1-1) ...
Setting up duetruntime (3.2.0-beta3) ...
Setting up duetcontrolserver (3.2.0-beta3) ...
Installing new version of config file /opt/dsf/conf/config.json ...
Creating group dsf with gid 995.
Creating user dsf (n/a) with uid 995 and gid 995.
Setting up duettools (3.2.0-beta3) ...
Setting up duetwebserver (3.2.0-beta3) ...
Setting up duetsoftwareframework (3.2.0-beta3) ...
To modify config files consider adding yourself to the dsf groupd: # usermod -a -G dsf <username>
Setting up duetwebcontrol (3.2.0-beta3) ...
Setting up duetsd (1.1.0) ...
Setting up reprapfirmware (3.2.0-beta3-2) ...
Sending update request to DCS...

So before I reboot and flash everything again, do you want me to try something or get some logs?

undefined

@Phaedrux It's a Pi3 and the only peripheral is the official raspberry camera. I didn't knew it's recommended to power them separately, I'll change my wiring. Thanks for the information!

undefined

@Phaedrux the Pi is powered by the Duet via the ribbon cable and the duet is powered by a 24V power supply on the "Power In" connector.

I flashed the Duet to the version 3.1.1 and flashed the Pi again too and now it's working. I'll stay on the stable version for now.

I don't really know why the communication was broken because both the Duet and the Pi seemed to work fine on their own.

Anyway, thanks everyone for your help!

undefined

Hello, I prepared a new SD card with the latest DuetPi image but I still have an error while trying to update to the unstable branch:

sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  duetcontrolserver duetruntime duetsd duetsoftwareframework duettools duetwebcontrol duetwebserver reprapfirmware
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 34.0 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 https://pkg.duet3d.com unstable/armv7 armhf duetsoftwareframework armhf 3.2.0-beta3 [2,034 B]
Get:2 https://pkg.duet3d.com unstable/armv7 armhf duetsd all 1.1.0 [2,102 B]
Get:3 https://pkg.duet3d.com unstable/armv7 armhf duettools armhf 3.2.0-beta3 [62.2 kB]
Get:4 https://pkg.duet3d.com unstable/armv7 armhf duetcontrolserver armhf 3.2.0-beta3 [226 kB]
Get:5 https://pkg.duet3d.com unstable/armv7 armhf duetruntime armhf 3.2.0-beta3 [28.9 MB]
Get:6 https://pkg.duet3d.com unstable/armv7 armhf duetwebserver armhf 3.2.0-beta3 [83.9 kB]
Get:7 https://pkg.duet3d.com unstable/armv7 armhf duetwebcontrol all 3.2.0-beta3 [3,507 kB]
Get:8 https://pkg.duet3d.com unstable/armv7 armhf reprapfirmware all 3.2.0-beta3-1 [1,260 kB]
Fetched 34.0 MB in 9s (3,647 kB/s)
Reading changelogs... Done
(Reading database ... 57772 files and directories currently installed.)
Preparing to unpack .../0-duetsoftwareframework_3.2.0-beta3_armhf.deb ...
Unpacking duetsoftwareframework (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../1-duetsd_1.1.0_all.deb ...
Unpacking duetsd (1.1.0) over (1.0.6) ...
Preparing to unpack .../2-duettools_3.2.0-beta3_armhf.deb ...
Unpacking duettools (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../3-duetcontrolserver_3.2.0-beta3_armhf.deb ...
Unpacking duetcontrolserver (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../4-duetruntime_3.2.0-beta3_armhf.deb ...
Unpacking duetruntime (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../5-duetwebserver_3.2.0-beta3_armhf.deb ...
Unpacking duetwebserver (3.2.0-beta3) over (3.1.0) ...
Preparing to unpack .../6-duetwebcontrol_3.2.0-beta3_all.deb ...
Unpacking duetwebcontrol (3.2.0-beta3) over (3.1.1) ...
Preparing to unpack .../7-reprapfirmware_3.2.0-beta3-1_all.deb ...
Unpacking reprapfirmware (3.2.0-beta3-1) over (3.1.1-1) ...
Setting up duetruntime (3.2.0-beta3) ...
Setting up duetcontrolserver (3.2.0-beta3) ...
Installing new version of config file /opt/dsf/conf/config.json ...
Creating group dsf with gid 995.
Creating user dsf (n/a) with uid 995 and gid 995.
Setting up duettools (3.2.0-beta3) ...
Setting up duetwebserver (3.2.0-beta3) ...
Setting up duetsoftwareframework (3.2.0-beta3) ...
To modify config files consider adding yourself to the dsf groupd: # usermod -a -G dsf <username>
Setting up duetwebcontrol (3.2.0-beta3) ...
Setting up duetsd (1.1.0) ...
Setting up reprapfirmware (3.2.0-beta3-1) ...
[fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)

I don't understand why the connection between the Duet and the Pi doesn't work anymore.

undefined

@Phaedrux Okay thanks I'll do that

undefined

I managed to connect to the duet via USB and YAT and the firmware version is 3.2 beta3 and it seems to work well.

Here is the M122 diagnostic:

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta3 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J1F0-3SS6K-9A1QH
Used output buffers: 1 of 40 (1 max)
=== RTOS ===
Static ram: 122124
Dynamic ram: 166656 of which 228 recycled
Never used RAM 103184, free system stack 188 words
Tasks: NETWORK(ready,547) HEAT(blocked,365) CanReceiv(blocked,948) CanSender(blocked,371) CanClock(blocked,356) TMC(blocked,66) MAIN(running,1352) IDLE(ready,19)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:42 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 103184, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0x00
MCU temperature: min 30.2, current 35.7, max 35.9
Supply voltage: min 0.2, current 0.2, max 1.9, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 0.1, current 0.1, max 0.2, under voltage events: 0
Driver 0: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 1: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 2: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 3: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 4: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 5: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 8.44ms; fastest: 0.14ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -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.
=== Network ===
Slowest loop: 0.23ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 0, send timeouts 0, longest wait 0ms for type 0, free CAN buffers 47
ok

Version 3.2beta3 seems to be installed on the Raspberry too but the connection between the duet and the Pi doesn't works.

Should I still try to flash the duet to install version 3.1.1 or run it in standalone mode or is there something I can do to restore the connection between the Pi and the duet?

undefined

@jay_s_uk Thanks I'll look into it

undefined

Hello,

I have a Duet 3 MB6HC with a Raspberry Pi attached running RRF3.2 beta 2. I tried to update to version 3.2beta3 with:

sudo apt-get update
sudo apt-get upgrade

But it stayed blocked on "Sending DWC update" or "Sending DCS update" I can't remember. After a few hours I had to reboot the raspberry. Now if I try to go to Duet Web Control I have the following error message: "Failed to connect to Duet, please check your connection (DCS is not started)".
I tried to downgrade to 3.1.1 following this topic: https://forum.duet3d.com/topic/19257/downgrade-from-3-2beta2-to-3-1-1/9 but I got an error as well: "[fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)"

Any idea of what I can do?

Thanks

undefined

@dc42 Here is the M122 when the printer is frozen:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J1F0-3SS6K-9A1QH
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154820
Dynamic ram: 133832 of which 44 recycled
Exception stack ram used: 528
Never used ram: 103992
Tasks: HEAT(blocked,296) CanReceiv(blocked,948) CanSender(blocked,351) CanClock(blocked,352) TMC(blocked,18) MAIN(running,1230) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:04:08 ago, cause: software
Last software reset at 2020-09-20 17:12, reason: User, LinuxInterface spinning, available RAM 103992, slot 1
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0x020
MCU temperature: min 40.5, current 41.1, max 41.3
Supply voltage: min 23.7, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Driver 0: position 97280, standstill, reads 2810, writes 17 timeouts 0, SG min/max 0/228
Driver 1: position 94720, standstill, reads 2810, writes 17 timeouts 0, SG min/max 0/182
Driver 2: position 448, standstill, reads 2811, writes 17 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 2811, writes 17 timeouts 0, SG min/max 0/528
Driver 4: position 0, standstill, reads 2818, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 2818, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-09-20 17:16:50
Slowest loop: 11.09ms; fastest: 0.14ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.7ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 364, MaxWait: 27315ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 16, completed moves: 16, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" 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
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.
=== Network ===
Slowest loop: 0.00ms; fastest: 5726623.00ms
Responder states:
HTTP sessions: 0 of 8
- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 967, send timeouts 967, longest wait 0ms for type 0, free CAN buffers 48
=== SBC interface ===
State: 0, failed transfers: 0
Last transfer: 18ms ago
RX/TX seq numbers: 7647/7649
SPI underruns 0, overruns 0
Number of disconnects: 1
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0-beta1+1
File:
Finishing macro /sys/before-print.g, started by G1 X85.779 Y137.166 E0.02389
> Next stack level
Suspended code: M109 S210 ; set temperature and wait for it to be reached
Suspended code: G21 ; set units to millimeters
Suspended code: G90 ; use absolute coordinates
Suspended code: M83 ; use relative distances for extrusion
Suspended code: ; Filament gcode
Suspended code: G1 Z0.200 F7800.000
Suspended code: G1 E-1.50000 F3600.00000
Suspended code: G1 X86.638 Y146.405 F7800.000
Suspended code: G1 E1.50000 F3600.00000
Suspended code: G1 F2400.000
Suspended code: G1 X85.779 Y145.546 E0.03809
Suspended code: G1 X85.779 Y144.784 E0.02389
Suspended code: G1 X87.230 Y146.235 E0.06435
Suspended code: G1 X87.992 Y146.235 E0.02389
Suspended code: G1 X85.779 Y144.022 E0.09813
Suspended code: G1 X85.779 Y143.260 E0.02389
Suspended code: G1 X130.860 Y188.341 E1.99896
Suspended code: G1 X131.622 Y188.341 E0.02389
Suspended code: G1 X85.779 Y142.498 E2.03274
Suspended code: G1 X85.779 Y141.737 E0.02389
Suspended code: G1 X132.384 Y188.341 E2.06652
Suspended code: G1 X133.146 Y188.341 E0.02389
Suspended code: G1 X85.779 Y140.975 E2.10030
Suspended code: G1 X85.779 Y140.213 E0.02389
Suspended code: G1 X133.907 Y188.341 E2.13408
Suspended code: G1 X134.669 Y188.341 E0.02389
Suspended code: G1 X85.779 Y139.451 E2.16787
Suspended code: G1 X85.779 Y138.689 E0.02389
Pending code: G1 X135.431 Y188.341 E2.20165
Pending code: G1 X136.193 Y188.341 E0.02389
Pending code: G1 X85.779 Y137.927 E2.23543
Pending code: G1 X85.779 Y137.166 E0.02389
Trigger:
Finishing macro config.g, started by system
> Next stack level
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 31.91
File /opt/dsf/sd/gcodes/top dome mk 85 helmet by do3d.gcode is selected, processing

The GCode I posted earlier is my "Before Print" Gcode and it's all of it. The next GCode lines are the lines from the print itself but I think that the last completed line is the line 12 of my "Before Print" Gcode because the Tool is still positioned at the end of the purge line and the extruder isn't reset to position 0 as it should be on line 13.
Also I said in my previous post that I didn't have the "Heightmap loaded" notification when it freezes but it was a mistake I do have the "Height map loaded from file heightmap.csv" notification before the freeze.

undefined

@dc42 Yes a Duet 3 with a Raspberry Pi 3 attached

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.0-beta1+1
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2-beta1 (2020-09-15b1)
Duet Web Control 3.2.0-beta1+2

undefined

Hello,

I also encounter random freezes since the 3.2 beta 1. It happens in almost 1 out of 3 print.
I do a purge line at the beginning of each print with the following GCode:

M561	; Clear any bed transform
G28	; Home all axes
G29 S1	; Grid compensation

T0      ; Select tool 0
M116	; Wait for tools

; Purge line
G1 Z0.2
G1 Y2 X25 F15000        ; move out of build volume
G1 X150.0 E24 F1200     ; finish purge line
G4 P4000	        ; Wait to let the plastic cool a little
G92 E0                  ; reset extruder position to 0

And it freezes right after doing the purge line. It might be an issue with the heightmap loading as suggested by @dc42 because effectively I normally receive the "Heightmap loaded" notification just after the purge line and when my print freezes I don't have this notification.

undefined

Hello,

I have a similar issue. I paused a print, the tool goes back to X0 Y0 as expected then I resumed the print, the tool goes back to the last printing position and stays there.

I tried to pause and resume multiple times but the print never continued, I had to stop it.

undefined

@jay_s_uk Yeah that's what the changelog seems to indicate but I don't have a mesh.g file so I thought it was supposed to behave like a G29 S0

undefined

Hello,

I updated my printer to the 3.2 beta 1 version and I encounter an issue with the new plugin system: Each time I refresh the page (F5) all the started plugins stop.

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.0-beta1+1
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2-beta1 (2020-09-15b1)
Duet Web Control 3.2.0-beta1+2

undefined

Hello,

I updated my printer to the 3.2 beta 1 version and I have a problem with the G29 command.

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.0-beta1+1
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2-beta1 (2020-09-15b1)
Duet Web Control 3.2.0-beta1+2

The G29 command doesn't do anything anymore (neither does the "Run Mesh Compensation (G29)" button in DWC). But G29 S0 works as expected.

I don't have a mesh.g file so if I understand correctly the changelog:

G29 with no S parameter now runs file sys/mesh.g if it exists; otherwise it behaves like G29 S0 as before

G29 is supposed to act like a G29 S0, no?