@deckingman I really do love the idea and the results! (That's my printer)
Best posts made by TypQxQ
RE: Limited service from me during 3D Meetup Sweden
RE: Markforged Kinematics Troubleshooting
Beautiful build! A lot like how I want to do it.
I was thinking of calibrating the steps per unit of the X axis in regards to Y to get it completely square.
Because when moving Y axis you need X axis to be stationary but X stepper has to move with it, needing belts and such to be perfectly equal.
I use this calibration cross to check on my CoreXY:
Latest posts made by TypQxQ
RE: 3.1.1 on Duet3 6HC +3HC +SBC intermittent disconnects.
After powercycle it printed fine.
3.1.1 on Duet3 6HC +3HC +SBC intermittent disconnects.
It all started with the Webinterface going down on last print, it showed 71% and the print was finished. Couldn't refresh it either.
I rebooted the Pi and started another job.
When I checked on it it was jerking and had done this for half an hour according to logs, connecting and disconnecting from about 15 minutes into the print.
It was still printing but jerking on and off. See video below:
2020-10-20 21:29:41 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin) 2020-10-20 21:28:40 Connection to Duet established 2020-10-20 21:28:40 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin) 2020-10-20 21:28:39 Connection to Duet established 2020-10-20 21:28:39 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin) 2020-10-20 20:15:41 m204 Maximum printing acceleration 1500.0, maximum travel acceleration 4000.0 2020-10-20 20:14:19 Height map loaded from file heightmap.csv 2020-10-20 20:14:19 Leadscrew adjustments made: -0.036 0.010 0.028, points used 3, (mean, deviation) before (0.001, 0.023) after (0.000, 0.000)
Here are the board diagnostics:
2020-10-20 22:00:36 m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6JKDD-3SJ6L-TB62G Used output buffers: 1 of 40 (14 max) === RTOS === Static ram: 154604 Dynamic ram: 163936 of which 44 recycled Exception stack ram used: 544 Never used ram: 74088 Tasks: NETWORK(ready,1972) HEAT(blocked,1088) CanReceiv(suspended,3412) CanSender(suspended,1392) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,2672) IDLE(ready,76) Owned mutexes: === Platform === Last reset 49:57:19 ago, cause: software Last software reset at 2020-10-18 20:03, reason: User, spinning module LinuxInterface, available RAM 74276 bytes (slot 1) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 38.5, current 42.4, max 42.8 Supply voltage: min 27.9, current 32.0, max 32.0, 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: ok, reads 60978, writes 106 timeouts 0, SG min/max 0/1023 Driver 1: ok, reads 60978, writes 106 timeouts 0, SG min/max 0/1023 Driver 2: standstill, reads 60984, writes 101 timeouts 0, SG min/max 0/103 Driver 3: standstill, reads 61036, writes 49 timeouts 0, SG min/max 0/1023 Driver 4: standstill, reads 61037, writes 49 timeouts 0, SG min/max 0/1023 Driver 5: standstill, reads 61037, writes 49 timeouts 0, SG min/max 0/1023 Date/time: 2020-10-20 22:00:36 Slowest loop: 1006.46ms; fastest: 0.14ms === 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: 372, MinFreeDm: 313, MaxWait: 86366307ms Bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves: 80670, completed moves: 80630, StepErrors: 0, LaErrors: 0, Underruns: 439, 1045 CDDA state: 3 === 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.1 Heater 1 is on, I-accum = 0.0 === 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 ready with "G1 X248.397995 Y209.645996 E0.009770" 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 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is not empty: 5 of 16 codes have been queued. === Network === Slowest loop: 1.44ms; 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 1019462, longest wait 8ms for type 6029 === Linux interface === State: 0, failed transfers: 94 Last transfer: 21ms ago RX/TX seq numbers: 60047/54289 SPI underruns 94, overruns 94 Number of disconnects: 1 Buffer RX/TX: 1464/2688-0 === Duet Control Server === Duet Control Server v3.1.1 File: Buffered code: G1 X247.232 Y209.454 E0.00977 Buffered code: M107 Buffered code: G1 X247.353 Y208.670 E0.02260 Buffered code: G1 X247.399 Y208.106 E0.01613 Buffered code: G1 X247.525 Y207.146 E0.02760 Buffered code: G1 X247.639 Y205.227 E0.05481 Buffered code: G1 X248.778 Y205.227 E0.03247 Buffered code: M107 Buffered code: G1 X248.624 Y205.565 F18000.000 Buffered code: G1 X248.228 Y205.412 Buffered code: G1 F1800.000 Buffered code: G1 X248.117 Y207.188 E0.11391 Buffered code: G1 X248.010 Y208.011 E0.05314 Buffered code: G1 X247.942 Y208.725 E0.04591 Buffered code: G1 X247.858 Y209.258 E0.03456 Buffered code: G1 X247.825 Y209.461 E0.01232 Buffered code: G1 F14400.000 Buffered code: G1 X247.858 Y209.258 E-0.03250 Buffered code: G1 E-0.96750 F2400.00000 Buffered code: G1 X243.838 Y205.227 F18000.000 Buffered code: G1 E1.00000 F2400.00000 Buffered code: G1 F900.000 Buffered code: G1 X243.726 Y207.108 E0.05373 Buffered code: G1 X243.601 Y208.064 E0.02747 Buffered code: G1 X243.555 Y208.623 E0.01600 Buffered code: G1 X243.428 Y209.454 E0.02395 Buffered code: M107 Buffered code: G1 X243.398 Y209.646 E0.00977 Buffered code: G1 X242.203 Y209.646 E0.05995 Buffered code: G1 X242.232 Y209.454 E0.00977 Buffered code: M107 Buffered code: G1 X242.353 Y208.670 E0.02260 ==> 1360 bytes Daemon: Finishing macro daemon.g, started by system > Next stack level Code buffer space: 1392 Configured SPI speed: 8000000 Hz Full transfers per second: 27.64 File /opt/dsf/sd/gcodes/estop_Spring.gcode is selected, processing 2020-10-20 22:00:36 Connection to Duet established 2020-10-20 22:00:36 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
The led on the toolboard was blinking fast and I couldn't get a diagnostics:
2020-10-20 22:04:13 Connection to Duet established 2020-10-20 22:04:12 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin) 2020-10-20 22:04:12 M122 b1 Error: M122: Response timeout: CAN addr 1, req type 6024, RID=23 2020-10-20 22:04:11 Connection to Duet established 2020-10-20 22:04:11 Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)
Any idea what's wrong?
3.2beta2 inconsistent G32
First time it tapped the 1st point, then 2d point twice.
Then twice good.
Last it tapped the 1st point, then 3d point twice.
2020-10-17 21:33:07 G32 Error: Bed calibration : 3 factor calibration requested but only 1 points provided Error: Bed calibration : 3 factor calibration requested but only 0 points provided Error: M950: Pin 'io3.in' is not free 2020-10-17 21:32:46 G32 Leadscrew adjustments made: 0.005 0.009 -0.003, points used 3, (mean, deviation) before (0.004, 0.004) after (-0.000, 0.000) 2020-10-17 21:32:21 G32 Leadscrew adjustments made: 0.030 0.009 0.010, points used 3, (mean, deviation) before (0.016, 0.008) after (-0.000, 0.000) 2020-10-17 21:27:01 G32 Error: M950: Pin 'io3.in' is not free 2020-10-17 21:22:49
; bed.g ; called to perform automatic bed compensation via G32 ; T-1 P0 ; deselect all tools but don't run any tool change macro files M98 P"homeu.g" ; Home U, drop any mounted tool so the endstop reaches bed. M950 J4 C"nil" ; Use the input pin on io3 on the main board Z M558 P8 C"0.io3.in" F250 A2 T24000 S0.02 ; Set the pin of Z probe G31 Z-1 ; Set the trigger height as -1 so that 0 is not touching the switch. G30 P0 X5 Y264.5 Z-99999 ; probe near left leadscrew G30 P1 X495 Y495 Z-99999 ; probe near back leadscrew G30 P2 X495 Y5 Z-99999 S3 ; probe near front leadscrew and calibrate 3 motors M558 P8 C"nil" ; Set the pin of Z probe M950 J4 C"0.io3.in" ; Use the input pin on io3 on the main board Z
RE: Duet 3 touch screen
I have a 7” IPS screen with HDMI for my Pi that controls the Duet3 and I find it very hard to control the small interface that is not touch optimized. I’d go with a PanelDue if I’d do it again because of the interface.
I rather pick up a iPad or laptop than try to click those buttons or write anything on that 7” screen.
RE: how to deal with old filament
I also have problems with the PLA becoming brittle inside a PTFE tube. It's different between different brands. EasyPrint from 3D Prima is worst I have, It's enough for it to be left half a day inside PTFE and it's broken in several places.
Generally all materials get brittle when they absorb moisture and I dry even my PLA for better end results.