@droftarts
https://forum.duet3d.com/post/118277

@droftarts, I am y happy with my Enegetic pei magnetic sheet. It’s thin, one sided, and smooth, and I get very good result. It was the recommended sheet in the voron part list at the time I built my printer.

@developeralgo222 I know several people are trying to help you (and I'll try to where I can as well), but can you do the following?

Post your latest config.g file In the console type M98 P"config.g", and post what the results are. Can you please verify if you have tested X and Y motor movement like dc42 has described below---

dc42 said in Configs for PCB PnP for Duet3D 6XD and 3 x 3HC expansion boards:

Test motor movement like this: Send G91 to put the machine into relative movement mode Use G1 H2 commands to command individual motors regardless of their homed status. For example, G1 H2 X10 should move the X axis by +10mm, and G1 H2 X-10 should move it by -10mm. Read the endstop states, either by using M119, or in Duet Web Control start the Object Model Browser and expand sensors/endstops. Check that the state changes as expected when you operate the endstop.

--- and let us know what happens (nothing? error light on the HSS86 driver?)
4. What do you have the microstep settings set to on the driver (with the SW3、SW4、SW5、SW6 switches)

While we are trying to help you 'piece by piece', it is very helpful for us if you respond by answering all the questions previously asked - it helps us work out what could be going wrong. In addition, posting your updated config.g once you make changes is extremely important, as it helps us 'peer review' the changes that have been made. If we can't see the config.g file, we won't be 100% sure with whats going on.

@dc42 said in Reboots/crashes - RRF 3.5.0-rc1:

@Exerqtor thanks, let's see if that resets more often than before.

Only one new crash since the daemon.g changes was done:

M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-12-07 09:49:06) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 102844 Dynamic ram: 123212 of which 12 recycled Never used RAM 12492, free system stack 182 words Tasks: NETWORK(1,ready,1204.8%,209) HEAT(3,nWait,1.4%,353) Move(4,nWait,0.1%,357) CanReceiv(6,nWait,2.7%,774) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.4%,350) TMC(4,nWait,38.1%,108) MAIN(1,running,3867.8%,670) IDLE(0,ready,269.7%,29) AIN(4,delaying,46.5%,264), total 5431.5% Owned mutexes: === Platform === Last reset 01:37:14 ago, cause: software Last software reset at 2023-12-08 18:27, reason: AssertionFailed, Gcodes spinning, available RAM 11400, slot 1 Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x20011fbc Task NETW Freestk 495 ok Stack: 00000913 000af408 0002de51 2002bed4 2002be01 000001a7 2002c100 20031510 2002c118 2001e888 a5a5a5a5 a5a5a5a5 0d362e30 00000000 00000000 00000000 2003151c 00000800 20035a28 2002c100 20018678 2002bf9d 20018678 2001e888 000300db 00000000 00000000 Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 5834478, completed 5834477, timed out 0, errs 0 MCU temperature: min 35.9, current 36.3, max 39.1 Supply voltage: min 22.2, current 24.1, max 26.7, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/27, heap memory allocated/used/recyclable 2048/1544/1192, gc cycles 11635 Events: 0 queued, 0 completed Driver 0: standstill, SG min 256, read errors 0, write errors 1, ifcnt 39, reads 44886, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 240, read errors 0, write errors 1, ifcnt 39, reads 44886, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 80, reads 44886, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 85, reads 44886, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 81, reads 44886, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-12-08 20:05:11 Cache data hit count 4294967295 Slowest loop: 12.91ms; fastest: 0.14ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 7.7ms, write time 4.5ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === 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 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, 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 SBC is idle in state(s) 0 Daemon is doing "G4 P10" in state(s) 0 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === in 0 notIn 0 Extruder 0 sensor: no filament === CAN === Messages queued 52517, received 119640, lost 0, errs 1, boc 0 Longest wait 2ms for reply type 6053, peak Tx sync delay 278, free buffers 26 (min 25), ts 29171/29170/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 5.96ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42960 WiFi IP address 192.168.10.x Signal strength -52dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0

So i guess that didn't do much 😅.

@droftarts Yeah I have an old version..
I tried to update and now I cannot connect to the internet I got this error
M587 S"xxx" P"xxx"
Error: Failed to add SSID to remembered list<LF>ok<LF>
what is wrong?

after m122
M122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0 running on Duet WiFi 1.02 or later<LF>Board ID: 08DDM-9FAM2-LW4S4-6J1DJ-3S86K-TJSRX<LF>Used output buffers: 4 of 24 (4 max)<LF>=== RTOS ===<LF>Static ram: 30516<LF>Dynamic ram: 90640 of which 580 recycled<LF>Exception stack ram used: 312<LF>Never used ram: 9024<LF>Tasks: NETWORK(ready,1888) HEAT(blocked,1464) MAIN(running,3740) IDLE(ready,156)<LF>Owned mutexes:<LF>=== Platform ===<LF>Last reset 00:08:13 ago, cause: power up<LF>Last software reset at 2023-11-18 14:58, reason: User, spinning module GCodes, available RAM 5648 bytes (slot 3)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0xffffffff<LF>Error status: 0<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 20.0MBytes/sec<LF>SD card longest block write time: 0.0ms, max retries 0<LF>MCU temperature: min 31.8, current 34.5, max 34.7<LF>Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power[Warning: Maximal number of characters per line exceeded! Check the line break settings in [Terminal > Settings > Text] or increase the limit in [Terminal > Settings > Advanced].]

WhatsApp Image 2023-12-08 at 21.13.36.jpeg
the printer is Rostock MAX v3.2 delta

thank you.

@gloomyandy yeah, got you! As I already checked, by setting the tolerance to 0.004 it did already the trick.

thanks a lot!

@dc42 thank you for the detailed explanation. I'll keep an eye on the Never Used RAM

BTW would be possible to expose memory related vars via Object-Model?

Extracting data from M122 is prone to error. I need to update my regex for each firmware version.

Would be super useful to have a consistent API that exposes this kind of data via HTTP

@Casugo

Glad to help whenever I can.

Frederick

@johny said in G32 doesnt save after True Bed Leveling:

I don't have mesh.g can you share it please?

I can provide an example mesh.g file for creating the height map used for Mesh Compensation, using G29.

The only thing "special" about bed.g and mesh.g is that there is the command G32 which runs bed.g and G29 which runs mesh.g (if it exists).

I recommend using them as intended which keeps the DWC interface "in sync" with your code.

DWC Compensation Menu.jpg

You could put the code for bed leveling or height map creation in any file at all - they simply won't be run using G32 or G29.

Would you like the example mesh.g file?

Frederick

@droftarts
I just plugged the servo, and it works!

Thank you for the support!

@JoergS5 I'm reading the discussion so I can know what kind of progress have already been made.

I've noticed that the robot viewer is not avaiable anymore, is there any specific reason for that?

@Exerqtor

I got the files.

I suspect it is a matter of getting the regex expressions just right. I don't use that technology much and I am not surprised to see I didn't get them quite right.

I've got a couple of tools for working with regex expressions - tools from the vendor of EditPad.

Thanks much.

Frederick

@JoergS5 I think I can probably help with it, just need to understand what progress you've made so far and learn a little bit better about RRF microcontrollers

Hey @raykholo, unfortunately there are no means to control paneldue remotely. You can display popups on paneldue with M291 gcode.

https://docs.duet3d.com/User_manual/Reference/Gcodes#m291-display-message-and-optionally-wait-for-response

Hey @Exerqtor, thanks for testing and your detailed response.

I am glad we could sort this out. 🙂

@India Did you get it working? If so, please let us know, and what steps you took, so the information is here for other people, and so I can mark the thread as solved.

Ian

@dc42 3da964da-65b3-4911-b67e-aca1a928e543-image.png

I have tried to home the axis with d0 d2 and d3 with the same results

The encoder have 450 - 650 mm maximum cable length

@moe-adams9093 can you post your current config.g?

Also, see https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_CNC

Ian

@martinv thanks for the update. I'll mark this as solved.

@Tinchus I've asked @chrishamm to respond.

Not sure what I did, but I did the code

M569 P52.0 D4 M569.6 P52.0 V1

And again, I got:

Error: M569.6: Driver 52.0 basic tuning failed, the measured motion was inconsistent Warning: Driver 52.0 warning: tuning/calibration failed

Inside the closed loop plugin
newenc.PNG
newenc2.PNG