CoreXY axis don't move at printing
-
@phaedrux
I really wish there were a error code but there is nothing.
If you want I make a video from it. Maybe you will see on it more but i doubt it.
It's like the motors are getting no command to move. -
And just to confirm, you can jog the axis motors around no problem? It's only when you start a print?
Have you tried a different gcode file to print? -
@phaedrux
Could it be possible that I the gcode will be saved if I abort the print?
And if I used for the first print Marlin setting because forget to switching to reprap?
Could that be the problem?here my ressurect.g:
; File "Calibration/CFFFP_xyzCalibration_cube.gcode" resume print after print paused at 2019-03-19 18:29
M140 P0 S60.0
G10 P1 S0 R0
G10 P0 S210 R210
T0 P0
G92 X147.352 Y146.170 Z0.300
M98 Presurrect-prologue.g
M106 P0 S0.00
M106 P3 S0.00
M106 P4 S0.00
M106 P5 S0.00
M106 P6 S0.00
M106 P7 S0.00
M106 P8 S0.00
M106 S0.00
M116
M290 S0.000
G92 E0.00000
M83
M23 Calibration/CFFFP_xyzCalibration_cube.gcode
M26 S7271 P0.000
G0 F6000 Z2.300
G0 F6000 X147.352 Y146.170
G0 F6000 Z0.300
G1 F3600.0 P0
M24 -
You can test by deleting the resurrect.g
-
@phaedrux said in CoreXY axis don't move at printing:
And just to confirm, you can jog the axis motors around no problem? It's only when you start a print?
Have you tried a different gcode file to print?Thats right. I can move the axis and home it and everything is fine until I want to print. Then it doesn't move.
-
@phaedrux said in CoreXY axis don't move at printing:
You can test by deleting the resurrect.g
Ok one moment I'll try it and give you some feedback
-
OK I think I found the problem.
It was the ressurect.g.But now I get this error
I attached the M122 for better diagnostic.
18:33:54
Resume state saved
Print auto-paused due to low voltage
18:33:54
M24
Printing resumed
18:33:38
Resume state saved
Print auto-paused due to low voltage
18:33:37
M32 "Calibration/CFFFP_xyzCalibration_cube.gcode"
File Calibration/CFFFP_xyzCalibration_cube.gcode selected for printing
18:33:31
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSJ-6J1F2-3SJ6T-K9RR8
Used output buffers: 3 of 20 (10 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98912 of which 0 recycled
Exception stack ram used: 488
Never used ram: 6148
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3812) IDLE(ready,200)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:49 ago, cause: power up
Last software reset at 2019-03-19 17:59, reason: User, spinning module GCodes, available RAM 6308 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04417000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 35.3, current 37.7, max 37.9
Supply voltage: min 9.9, current 10.9, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/100
Driver 1: standstill, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-03-20 18:33:32
Cache data hit count 1092080024
Slowest loop: 3.54ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 239, MinFreeDm: 238, MaxWait: 282492ms, Underruns: 0, 0
Scheduled moves: 8, completed moves: 7
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
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 1 in use
Movement lock held by http
http is idle in state(s) 1 5
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle 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 ===
Slowest loop: 14.21ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address cc:50:e3:0d:1c:9e
WiFi Vcc 3.44, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 14912
WiFi IP address 192.168.178.9
WiFi signal strength -64dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
I don't understand why the VIN is decreasing that much.
- WiFi -
-
What is your power supply?
Are the VIN terminals screwed down tightly?
-
@phaedrux said in CoreXY axis don't move at printing:
What is your power supply?
Are the VIN terminals screwed down tightly?
PSU is 24V/15A
and yes I screwed it tight down. -
Have you tested the output of the PSU with a multimeter?
It could be failing. Do you have another 24v PSU to test with?
-
Is there a T0 or T1 statement to select a tool somewhere in a config file or in the print gcode?
-
@mrehorstdmd Yeah there is one inserted by cura in the slicer start code.
;FLAVOR:RepRap ;TIME:917 ;Filament used: 1.36441m, 0m ;Layer height: 0.2 ;Generated with Cura_SteamEngine 4.0.0 T0 M190 S60 M104 S210 M109 S210 M82 ;absolute extrusion mode G28 ;Home G1 Z15.0 F6000 ;Move the platform down 15mm ;Prime the extruder G92 E0 G1 F200 E3 G92 E0 M83 ;relative extrusion mode G1 F1500 E-6.5 ;LAYER_COUNT:100 ;LAYER:0 M107 P1 G0 F3600 X130.865 Y142.007 Z0.3 ;TYPE:SKIRT G1 F1500 E6.5 G1 F2400 X131.315 Y141.665 E0.0282 G1 X131.808 Y141.389 E0.02819 G1 X132.336 Y141.185 E0.02824 G1 X132.886 Y141.058 E0.02816 G1 X133.509 Y141.009 E0.03118 G1 X153.491 Y141.01 E0.99691If there wasn't the heater wouldn't heat.
-
@mrehorstdmd said in CoreXY axis don't move at printing:
Is there a T0 or T1 statement to select a tool somewhere in a config file or in the print gcode?
I don't think so. I uploaded the gcode. It's in the first post as an attachment.
@Phaedrux I'll will check the VIN and give feedback in a few minutes
-
@phaedrux said in CoreXY axis don't move at printing:
Have you tested the output of the PSU with a multimeter?
It could be failing. Do you have another 24v PSU to test with?
Yeah you were right
the VIN decreases from ~24V to ~10V.
Did you know a good PSU which I could buy? It seems that I have no luck with that printer.I had to change nearly every piece exclude the frame
-
I would recommend a Meanwell PSU. The wattage will depend on if you're powering a PCB bed heater as well, or if it's an SSR controlled AC mains heater.
-
I second that. MeanWell makes good stuff. Avoid the cheapo "LED" power supplies that litter ebay. MeanWells cost just a few $ more and are far more reliable.
How can you tell junk from the good stuff? Look for certification marks like CE, UL, TUV, etc. The more of those it has, the better.
-
@mrehorstdmd said in CoreXY axis don't move at printing:
How can you tell junk from the good stuff?
It also helps to buy from reputable distributors like mouser or digikey.
Here's the one I use. (canadian mouser store front) https://www.mouser.ca/ProductDetail/Mean-Well/SE-200-24/?qs=sGAEpiMZZMsPs3th5F8koBXG%2F88ctzcM7%252bcCQ8TI45g%3D
-
@phaedrux said in CoreXY axis don't move at printing:
Meanwell
Ok. And yes I have a PCB bed heater connected to the duet.
What a PSU could you recomment for a Duet 2 Wifi, PanelDue 7i, E3D Chimera, PCB bed heater, one tool fan and two part fans. I realy appreciate your help. Thanks a lot! -
@phaedrux said in CoreXY axis don't move at printing:
canadian mouser store frontSorry but I'm from germany and it's very expensive to ship and tax. But thank you now I know what I'll looking for.
Hopefully everything will work after that replacement. -
Well Mouser is just an example of a reputable distributor. You'd have to find something similar locally.
The PSU I linked is suitable for a printer without a PCB heated bed.
This link will help you calculate how big the PSU needs to be: https://duet3d.dozuki.com/Wiki/Choosing_the_power_supply
