Multi-touch is controlled by the A and S parameters in the M558 command, see https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M558_Set_Z_probe_type.

A reminder: H corrections to the G30 probe points in bed.g should only be made if you have established that your Z probe has a different trigger height at different probe points (typically caused by effector tilt that varies with XY position).

The issue I found (DWC not giving the "Load filament" option with recent 2.0RC builds) is fixed in the 2.0 release firmware. I hope that was the only issue.

@dc42 said in Firmware 2.0RC6 and 1.21.1RC6 released:

Were you able to access the SD card via DWC or PanelDue after the error occurred, without either resetting the Duet or sending M21?

I sent M122 from DWC after that shutdown all system so i didn't test it.

I can get PWM output using M42 command. I tried to track the differences between functions that are writing pwm values in M106 and M42 command, but it seems that it points to the same function in the end... That's why I'm asking on forum.

The reduced buffer sizes apply only to output sent to DWC, USB and PanelDue - not to the file write buffers.

I have just released firmware 2.0RC6 so I am closing this thread and starting a new one. Those of you who have outstanding issues with RC5, please test again using RC6 and report any issues that are still present in that thread.

You need to make the tool active before you can heat it, by sending an appropriate T command (e.g. T0) or by selecting the tool in DWC.

@bendiesel said in multi wifi network:

Ok so if I send the m587 over yat followed by m500 that should save everything ? Or do I need to m500?

No, just the M587 command

Firmware 2.0RC5 is out so I have started a new thread for it and I am closing this one.

Firmware 2.0RC5 is out, so I have started a new thread for it and I am closing this thread.

You are aware that if you don't want that behavior, you can add M564 H0 to your config.g?

that's why they moved the erase button a bit further back on the board in the newer pcb revisions... 😉

@dc42 good call, I'll add 10ms delay after the turning off the driver. I did have some very rare problem with Marlin where right after tool change the feeding of new material would fail with motor squealing with skipped steps. Perhaps related to the relay being in inconsistent state. In Marlin the relay control had some delay (300ms) only after altering the relay state.

@T3P3Tony I'll be happy to shed some light into this "frankenprinter" I've built from assorted parts. As the moniker hints, it's not that pretty but it's surprisingly functional. And it does not fully hate it's maker as far as I can tell.

@mikesplane, see https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond.

@dc42 OK, thanks.
I would have never assumed it to be that way but I can accept it. 😂

Alright i think i can handle it from here. Sometimes complex problems have simple solutions.

Thank you for your time.
Xenjamo

@davea said in Firmware 2.0RC2 released:

@dc42 Thanks for tip on the M558 parameter. I'm not sure what changed in the printer but changing M558 H from 10mm to 15mm fixed the issue. First time cal. after power up works fine now.

So now you need to run calibration, then run M665 and M666 without parameters and copy the values displayed to the M665 and M666 commands in config.g. Or, if you are using config-override.g, you can just use M500 to save them. After that you should be able to change your M558 H parameter back to a lower value, for faster probing.

you can see whats in my config.g file further up.
i commented out all the network stuff, rebooted and the wifi led didnt flash

first m122
=== Diagnostics ===
Used output buffers: 1 of 32 (1 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J1D8-3SD6R-T3SZX
Static ram used: 16152
Dynamic ram used: 100248
Recycled dynamic ram: 2384
Stack ram used: 3576 current, 4504 maximum
Never used ram: 7784
Last reset 00:00:41 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7784 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 31.3, current 31.4, max 31.8
Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.000153; fastest: 0.000049
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

WiFi -
Network state is disabled
WiFi module is disabled
Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===

sent m552 s0, no reply on yat
M122 returns

=== Diagnostics ===
Used output buffers: 1 of 32 (9 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J1D8-3SD6R-T3SZX
Static ram used: 16152
Dynamic ram used: 100448
Recycled dynamic ram: 2184
Stack ram used: 3576 current, 4664 maximum
Never used ram: 7624
Last reset 00:02:15 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 7784 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 31.1, current 31.9, max 31.9
Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.099142; fastest: 0.000049
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

WiFi -
Network state is starting
WiFi module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===