Posts made by DonStauffer

Had an internet problem, so I cycled the power on my router. Internet is up again, but the PanelDue flashes this message over and over and the DWC won't connect. I'm in the middle of a print, so I can't cycle the Duet 2 WiFi (3.6.0 alpha 2 I think) power right now. I hope this message being repeated constantly doesn't eventually crash the Duet. I don't see a way to stop it. This is a bit concerning since I have no emergency stop except turning the power off.

https://drive.google.com/file/d/1LCv6xmfYNOJrZTD_DPjfoaHpMnVHaB1b/view?usp=sharing

@Woody78 Be aware that on the Duet 2 M150 will only work when there is no movement of the printer carriage. The workaround I'm using is the Adafruit NeoDriver card, which works by I2C communication between Duet and NeoDriver, so you use M260 instead of M150. It's not fast, so you won't get fancy stuff, but it works for progress metering adequately, I think.

If you use the NeoDriver, be aware that although the NeoDriver has pull-up resistors built in, you have to add your own too. I think 4.7 k ohm, but in theory that depends on how long your I2C wiring is. The resistors go from 5V+ to each of the I2C lines (data and clock). Before I added pull-up resistors I was getting intermittent "I2C Transmission Error" problems.

Using the NeoDriver, you don't need the voltage level shifter circuit.

@curieos I've never been able to get M300 to work right, no matter what I do. It's just broken.

@Phaedrux Would it? I would think the wattage might affect it, but I don't see why voltage would.

@rechrtb Immediately after a disconnect this morning:

10/3/2024, 11:20:49 AM 	M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-alpha.4 (2024-08-13 15:11:39) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JKD0-3S06Q-9AY7D
Used output buffers: 3 of 26 (24 max)
=== RTOS ===
Static ram: 23368
Dynamic ram: 70472 of which 0 recycled
Never used RAM 22036, free system stack 122 words
Tasks: NETWORK(1,ready,13.6%,222) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,286) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,85.4%,610) IDLE(0,ready,0.9%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:19:41 ago, cause: power up
Last software reset at 2024-09-21 14:08, reason: User, Gcodes spinning, available RAM 13020, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x08
Aux0 errors 0,3,0
MCU temperature: min 33.2, current 48.3, max 48.7
Supply voltage: min 23.8, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/56, heap memory allocated/used/recyclable 4096/3124/1496, gc cycles 1004
Events: 0 queued, 0 completed
Date/time: 2024-10-03 11:20:48
Slowest loop: 45.92ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 9.4ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 6, maxWait 3515020ms, bed comp in use: none, height map offset 0.000, hiccups added 0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00, mcet 0.016
Pos req/act/dcf: 60000.00/60000/0.00 0.00/0/0.00 13592.00/13592/0.00
no step interrupt scheduled
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 66, completed 66, LaErrors 0, Underruns [0, 0, 0]
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.0
=== GCodes ===
Movement locks 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 0 0, running macro
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
check 0 clear 25429311
Extruder 0 sensor: no data received
Extruder 1 sensor: no data received
=== DueX ===
Read count 1, 0.01 reads/min
=== Network ===
Slowest loop: 13.13ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.0beta1
MAC address 84:f3:eb:83:47:be
Module reset reason: Turned on by main processor, Vcc 3.36, flash size 4194304, free heap 39196
WiFi IP address 192.168.1.130
Signal strength -41dBm, channel 11, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

The other was also Keenovo, but 400W @24V rather than 750W @120V. This isn't subtle: the insulation on the other one doubled the heat up speed and also stabilized running temperature. The insulation on the Railcore has no effect on either, it seems.

It's not a huge big deal. Everything works. I just expected different behavior, and wondering if I really got a good PID tuning or not.

@rechrtb I'll try to remember to do that.

@dc42 I suspect it was just running out of memory, but I haven't tried this particular construct again with more free memory. I'll try it tomorrow.

@droftarts My experience is different, and it makes sense.

If you're not losing much heat at all, even while you're heating the bed, it will heat up faster. My experience with aerogel insulation is that it loses very little heat. My other printer will heat up in half the time it did before the insulation.

@engikeneer It does not heat up faster or slower. I'm disappointed and I wonder if I can manually tune it better.

@dc42 The Adafruit documentation is ambiguous because it's internally contradictory by one byte. So I don't know.

@moth4017 Mine took 2 hours. I'm a bit disappointed that the bed doesn't heat any faster with the insulation. I've done this before almost the same way and did get a massive decrease in heat time (it was a Marlin machine). Maybe this tuning algo doesn't handle insulated beds very well. If so, maybe tuning it manually might help.

The bed is around 300x300mm. No big deal, everything works. Once the tuning finished I put the line in config.g.

@DonStauffer Finally:

9/8/2024, 6:03:08 PM Warning: heater behaviour was not consistent during tuning
Auto tuning heater 0 completed after 3 idle and 25 tuning cycles in 7440 seconds. This heater needs the following M307 command:
M307 H0 R0.307 K0.119:0.000 D21.47 E1.35 S1.00 B0
Edit the M307 H0 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.

What does it mean "was not consistent"? What does one do about it? I've always found the bed heater to be consistent as far as I can tell.

I've been doing lots of perusing previous posts about PID tuning and didn't find anything helpful in my situation. I did notice discussions about where the bed thermistor is. In my case (Railcore) the thermistor in use is in a slot on the bed top surface and the heater is on the bottom. So I'd estimate there's 4mm of aluminum bed between heater and thermistor. Keenovo 700W 120VAC heater controlled by SSR. Heater does have its own thermistor but it's not being used.

I just insulated the bottom of the bed and tried to run a PID tuning. Almost 2 hours and still going. Bed temperature slowly seesawing above and below the target, on about a 4 min 20 sec cycle:

9/8/2024, 3:59:07 PM M303 H0 S70
Auto tuning heater 0 using target temperature 70.0°C and PWM 1.00 - do not leave printer unattended
9/8/2024, 3:59:12 PM Auto tune starting phase 1, heating up
9/8/2024, 4:01:39 PM Auto tune starting phase 2, settling
9/8/2024, 4:16:43 PM Auto tune starting phase 3, measuring
9/8/2024, 5:49:26 PM M303
Heater 0 is being tuned, phase 4 of 4, measuring

Also, why does it say "phase 4 of 4" when it's only on phase 3 according to the original command?

@rechrtb I don't think the disconnects are running out of memory. They happen even when nothing is happening on the printer, and that out of memory only happens when a job fails in the middle and doesn't reclaim memory. While I've been debugging new code, that happens occasionally but not frequently like teh WiFi disconnects. A restart fixes it, and I don't have it happen too much any more, while the WiFi disconnects continue to happen. I just was assuming there's RF pollution around.

Also I've watched it happen spontaneously, the reconnect, with no reset, and there was no error. Often I'm actually just editing a macro when it happens, and I may not have even run a print job in days.

@rechrtb It hasn't been too horrible. Just horrible enough...

Here's the console log, RRF 3.6.0 alpha 4 with the WiFi firmware you posted here; the " Incompatible software" error message is just from having the alpha RFF:

8/21/2024, 11:52:40 AM Connection interrupted, attempting to reconnect...
Operation failed (Reason: Service Unavailable)
8/21/2024, 11:52:41 AM Connection established
8/21/2024, 11:52:43 AM Connection interrupted, attempting to reconnect...
Operation failed (Reason: Service Unavailable)
8/21/2024, 11:52:43 AM Connection established
8/21/2024, 11:52:54 AM Incompatible software versions
The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors.

@rechrtb Sorry for the delay. COVID-19. I'll try to figure this out today.

@rechrtb I'll install and test it and report back. Thanks!

@dc42 Thanks for the information.